Problem with new ACA1233n

[bubbob42]

So you claim to have the Mediator in Early Startup, but showconfig won't list it? That's close to being impossible.

Picture of early startup, please - "expansion board diagnostic"

[arti040]

Here it is:

[arti040]

But when I remove ACA card, it looks like this (and ShowConfig sees Mediator), but pciinfo crashes - it requires Fast RAM, I think.

[Daedalus]

The Mediator doesn't actually show up in the early startup when the ACA is attached - the 2206 manufacturer code is Elbox, and I'm presuming 4626 is Individual computers, but it's definitely not your Mediator. It looks indeed like something the ACA is doing is preventing the Mediator from showing up at all - perhaps it's interfering with the autoconfig signal or something. Does the Config jumper on the Mediator help it show up in the early startup screen?

[arti040]

1. ACA connected, CONFIG jumper set - Mediator visible, ShowConfig - either. pciinfo crashes;

2. ACA not connected, CONFIG jumper set - nothing on Expansion Board Diagnostic, ShowConfig doesn't see Mediator neither.

[bubbob42]

So do you have any configuration where both ACA (manID 4626) AND Mediator (manID 2206) show up in early startup diagnostic at the same time?

Edit: root of your problems is that ACA sits right at the beginning of Z3 space and requires other cards to autoconfig behind it. Which is usually ok, but not with Mediator.

We need to sort this out hardware-wise first. Then we can verify it by putting the ACA into Zorro2-mode.

[arti040]

Yep, when CONFIG jumper is on, but then pciinfo crashes, so does voodoo monitor driver.

[bubbob42]

see my edit above. Please give me a screenshot of showconfig with the situation where both boards show up.

[arti040]

OK, i'll be at home in 4 hrs, so then I will do some screenshots. Thanks for a help!

[arti040]

Pics (both ACA and Mediator visible):

[bubbob42]

hm. There is no conflict between the address spaces. So Autoconfig obviously worked.

Leave the Config jumper as it is and try changing the memory jumper to the other two positions. Test with pciinfo only - as long as that won't work, loading a monitor driver will also always fail.

[arti040]

Originally Posted by bubbob42

hm. There is no conflict between the address spaces. So Autoconfig obviously worked.

Leave the Config jumper as it is and try changing the memory jumper to the other two positions. Test with pciinfo only - as long as that won't work, loading a monitor driver will also always fail.

I tried all: 0, 4MB and 8MB - Mediator is visible all the time, but pciinfo crashes.

[arti040]

UPDATE: I tried with no accelerator attached and pciinfo crashed too, which was obviously quite strange... so I took all PCI card out and bingo! Pciinfo reported than no any PCI card is found. Good. So I did some other tests with and without ACA card and it turned out, Mediator works only if Voodoo card is attached. Adding any other PCI card results in pciinfo crash! And everything stops after SetPatch or Binddrivers

[bubbob42]

ok, that is good news. Now shuffle the Voodoo through the pci slots and add one extra card until you find a suitable position

[arti040]

Originally Posted by bubbob42

ok, that is good news. Now shuffle the Voodoo through the pci slots and add one extra card until you find a suitable position

Position of Voodoo card in slots - no difference. More than one PCI card - pciinfo crashes. More than 0MB of Memory Window - system crashes right after Setpatch. I managed to boot the system with 0MB of Memory Window, but then... Voodoo driver crashes.

[bubbob42]

ok, please give us pci.library version and all Mediator-related env-variables, next.

Also show pciinfo output with only the Voodoo attached.

[arti040]

From memory, because i'm in bed ;-)

VoodooInt - Yes and No, I tried both option;
MMU - Yes or No, checked both either (i got ACA with MMU);
Warp3D - No;
VoodooMem - I tried with 4/8 and 12 value;
Something FastEthernet related - 0;
NoCache - Yes

That's all probably. PCi.library - 9.4. Tomorrow will prepare pics. I very appreciate your help.

[arti040]

Voodoo, 0MB memory window, CONFIG set.

[Daedalus]

To use a graphics card you need the memory window set to at least 4MB. And other PCI cards need the Voodoo's memory to work properly so that needs to be there too. Are you sure the Voodoo is working correctly? Have you got an old PC to try it in?

[arti040]

Yes, i'm sure because with Blizzard 1230 everything flies!