Problem with new ACA1233n

[arti040]

I replaced my old ACA1232 with the new one... and this what happens - system boots normally BUT:
- Workbench screen is in 4 colorus only (standard HighRes mode) and I can't changed that (see below);
- none of apps which require OS 3.9, including system prefs (I got 3.9 on this partition) doesn't work or crash the system;
- only simple programs work, like SysInfo or WhichAmiga, which reports ACA correctly;
- system right after boot has only 0.9KB of CHIP memory. More than 1MB is used for no particular reason!

I turned off ACAtune and all patches I use - didn't help. Any ideas?

My config: A1200 (ESCOM), Mediator 1200TX, strong ATX Chieftec power-supply. Previously installed card worked perfectly.

[Daedalus]

Hmmm, how much fast RAM is available? Does it need to be configured differently to your old card? Does CPU or WhichAmiga correctly identify the ACA card? Perhaps the card needs to be fully initialised somehow before Setpatch loads the ROM updates.

[arti040]

Originally Posted by Daedalus

how much fast RAM is available?

~128MB.

Originally Posted by Daedalus

Does it need to be configured differently to your old card?

Dunno.

Originally Posted by Daedalus

Does CPU or WhichAmiga correctly identify the ACA card?

Yes.

Originally Posted by Daedalus

Perhaps the card needs to be fully initialised somehow before Setpatch loads the ROM updates.

Ok, but how?

[Zetr0]

@arti040
I doubt this is a Memory Fault directly - I suspect this is a software issue - I would start with basic OS something like Classic Workbench on a sub 4GB Hard Disk Device - get that working with the 128MB - should be simple as you wont need the Rom Update - Now give it a test

If all works delightfully then I am leaning to it possibly being a setpatch issue as Daedalus mention earlier.

[arti040]

Originally Posted by Zetr0

@arti040
I doubt this is a Memory Fault directly - I suspect this is a software issue - I would start with basic OS something like Classic Workbench on a sub 4GB Hard Disk Device - get that working with the 128MB - should be simple as you wont need the Rom Update - Now give it a test

If all works delightfully then I am leaning to it possibly being a setpatch issue as Daedalus mention earlier.

I actually use ClassicWb 3.9.

[Zetr0]

Indeed its a good OS alongside 3.5 as well - if you have a OS3.9 build without the boing bag updates - or just a stock CW68k to test that would be great as by proving a working system we prove that it is a software issue on your primary hard disk device - easy fix - if not then it could be something fundamental to the accelerator.

[arti040]

Originally Posted by Zetr0

Indeed its a good OS alongside 3.5 as well - if you have a OS3.9 build without the boing bag updates - or just a stock CW68k to test that would be great as by proving a working system we prove that it is a software issue on your primary hard disk device - easy fix - if not then it could be something fundamental to the accelerator.

The only patch I use is a new scsi.device, which is being loaded right after SetPatch (with NOROMUPDATE option). I'll check both later.

[Daedalus]

Originally Posted by arti040

Ok, but how?

Not a clue I'm afraid, I've never used the card. I know some of the ACA cards (1221?) need special commands to work properly on certain setups.

If you start with no startup-sequence, are all 128MB available (avail command)? What about after running Setpatch?

Also, since you have a Mediator, try it without the Mediator installed if possible. There's also an autoconfig jumper on the Mediator IIRC that needs to be set differently for different accelerators. Perhaps this is causing problems?

[arti040]

Ha, when I started to play with the Miggy and changed a boot partition to the other only whole disk have been wiped out I tried to use PFS doctor to restore RDB but w/o success... so now I need to start everything from scratch.
Strange things happen here. Strange things...

[Zetr0]

@atri040

I discovered this thread earlier - a similar set with a similar problem - while the OP was having a Guru on boot (based arround the BB2 SCSI updates) I do wonder if its connected to this issue since is an ACA accelerator card.

Originally Posted by Amon_RA

Found out what the issue was... seems I have the same issue as described here :

Apparently my A1200/ACA1232/CF combination doesn't like the "Devs:Amiga Rom Update" file, so I renamed it.

Next step is to load in a custom 3.9 Rom including the updated scsi.device via ACA's Maprom.

Good luck arti040 - hopefully we can pull back the veil and demystify this issue =)

[bubbob42]

I had this issue once while beta testing the card. Please boot without startup-sequence, check memory with "avail"-command. Then copy files to RAM: and check with avail again for chipmem loss.

Edit: it won't be a hardware issue and no, you don't need stuff like ACATune. The software for this card is optional - there will be a release of Beta2 today at wiki.icomp.de

[arti040]

I reinstalled a system an it is quite stable but not as my old ACA 1232 was. Second thing - it seems card is not compatible with MediatorTX at all! When I put Blizzard 1230 everything is fine, PCI cards works etc. but with ACA1233n pci.library cannot be opened - Mediator is invisible to the system. Wow! I'll try with another version of pci.library and will let you know.

[bubbob42]

Hm... It worked fine in one of my mediator equipped systems. What is listed in early startup menu ?

[arti040]

I pulled my Miggy to pieces, cleaned all and put all back - didn't helped. Mediator is invisible for ACA1233n. I tried few jumper combinations - no difference either. Mediator even don't want to boot with CONFIG jumper set. Any more ideas?

[bubbob42]

Again: Does Mediator show up in early startup menue?

[arti040]

Yep.

[bubbob42]

Boot without startup sequence. Does pciinfo work?

[arti040]

Returns - "I can't open pci.library"

[bubbob42]

Showconfig-output, please

[arti040]

Here: