Mediator A4000 Di 3V MK-III ramlib error

[turboknekten]

Hello,
I have problem setting up my Mediator board. During bootup I get a ramlib error #80000004 message. I downloaded Snoopdos from Aminet and put "run c:snoopdos" in my startup-sequence so I could see what is going on. But I have no idea what is wrong. I would appreciate some guidance on what to check. See pictures.

My setup is:
A4000/040 rev B motherboard. 2MB chip/16MB fast. Buster v11.
ROM 3.1.4
Mediator A4000 Di 3V MK-III with daughterboard in bottom slot.
-Voodoo5 5500 in (top slot)
-Spider 2 USB
-Soundblaster 128
-Fast ethernet RTL8139
-Mediator daughterboard (bottom slot)

If I start computer with a 3.1.4 workbench disk it load to workbench.

I have tried to change order of the cards. But no luck. Same error. Motherboard is recapped. The Workbench 3.1.4 installation was working good when I had original daughterboard.

Any advice what I can check?

[trixster]

I would start by removing the Spider card and trying without that installed.

[indigolemon]

What 040 lib are you using?

[grelbfarlk]

Winsize jumper is on? Swap jumper is off?
Post your PCIInfo, you can do this with no startup-sequence.

[trixster]

There was a guy in the sonnet thread who had ramlib errors which were only fixed once he sent the logic board back to Elbox for rework. So it ‘could’ be a hardware issue. If I recall correctly his card was one of the first issues of the 4000Di 3V

[grelbfarlk]

I get the ramlib errors by turning swap on with the wrong card order. Also a poorly seated Voodoo or PPC card has caused it in the past.

[Hedeon]

ramlib errors are mostly caused by stack issues. Well <3.1.4 that is. I think they fixed it in that version?

[turboknekten]

I removed Soundblaster and PCI. Same error.
I see in Mediator report that I have v46.3 of the 68040.library.

When running Snoopdos I get some fail error before the ramlib error appear.
Does the following fails mean anything? I see in Snoopdos that these fails appear in ramlib process.
ENVARC:Mediator/MMU Read Fail
ENVARC:Mediator/noCache Read Fail
ENVARC:Mediator/Emulation Read Fail
ENVARC:Mediator/Patchint Read Fail
ENVARC:Mediator/PPCPCI Read Fail

[trixster]

I believe Fail means there is simply no setting for this particular environment variable, so it is nothing to worry about

[trixster]

Do we actually know whether mediator works correctly with 3.1.4?

My recommendation would be that you start over with a fresh WB 3.9 plus boingbags 1 and 2 install. Then install either the phase 5 040 library or preferably the MMULibs 040 library before running the p96 and mediator installs. Then perhaps install something like stackattack and / or mcpramlibpatch. This way you have a known-working software base from which to proceed.

I would recommend giving mcpramlibpatch a try in any case. It is available since the warpup4 lha on Aminet:

http://aminet.net/package/misc/os/WarpUP_V40Upd

If you then continue to get 80000004 ramlib errors with only the graphics card install then it’s perhaps time to start suspecting your hardware. So look at the power supply (especially with that power hungry voodoo5), the cooling of the mediator logic board etc...

I would also recommend getting hold of either a Radeon 9200 or voodoo3 as these might prove a little more stable and reliable for testing your system before you try that voodoo5

[turboknekten]

I have made a clean install of 3.1.4 and the update.
Copied the 68040.library from MMULibs.
Then I installed Picasso96.

After that it was time for Mediator. I can´t get a CD-rom to work so I have installed Mediator-files manually using Dopus. Started medconfig. After a reboot. I can see that system is adding around 16MB to available ram. If I just rename Cybervision 64/3D to voodoo and to voodoo inside information I cant make any resolution when running Picasso96 prefs. The Modes section is greyed out. Will give it a try tomorrow again.

[trixster]

You are attaching the voodoo board from the drop down menu before trying to create resolutions?

What does pciinfo show? What does showconfig show?

[drluking]

Originally Posted by grelbfarlk

I get the ramlib errors by turning swap on with the wrong card order

same as here if SWAP ON (closed), for exemple if there is no zorro card

[drluking]

Originally Posted by trixster

I believe Fail means there is simply no setting for this particular environment variable, so it is nothing to worry about

yes, no variables present
It's correct

[drluking]

Originally Posted by turboknekten

I have made a clean install of 3.1.4 and the update.
Copied the 68040.library from MMULibs.
Then I installed Picasso96.

After that it was time for Mediator. I can´t get a CD-rom to work so I have installed Mediator-files manually using Dopus. Started medconfig. After a reboot. I can see that system is adding around 16MB to available ram. If I just rename Cybervision 64/3D to voodoo and to voodoo inside information I cant make any resolution when running Picasso96 prefs. The Modes section is greyed out. Will give it a try tomorrow again.

try VoodooMemOS = No
I had problem if Yes with gfx modes non PC and something else

[turboknekten]

Today when I was booting up I could go into Picasso and select board-type in menu. I could change the option in the select section of Picasso96. I booted my Amiga and could select Voodoo card and resolution in Screenmode.

Yesterday I could see around 24MB of free memory. But today I can only see around 12MB.

I think the ramlib error I had was because I copy the pci.library v13.8 to libs:. When changing back to the version that was on CD-rom that was sent with Mediator. Now I have pci.library v9.4. When booting I dont get any ramlib error.

After training I will try to find why I am missing free ram :-)

Also install other cards.

[Hedeon]

Voodoo memory is no longer added to system memory which is why you now have 12MB.

[turboknekten]

When I tried VoodooMemOS=YES then system got the extra memory again.

When trying pci.library version 12.1 and 13.8 I got ramlib error. System is working with version 9.4.

I also got network card to work. Downloaded Roadshow demo to see if I could connect to internet. It was working. but surfing was so slow....but working on some sites. I was using a demo of IBrowse 2.5.

Will try to add soundcard and USB card this weekend. So please dont go anywhere :-)

[turboknekten]

This weekend I have installed both soundblaster and USB.

Everything is now working. I can use USB to transfer files from PC to Amiga. I can listen to modules via Eagleplayer. If I try to play an MP3 it is working but the 68040 is to slow for this. I can reach Aminet and download software. I get extra ram from the Voodoo card.

But system is very unstable. If I plug a USB-stick in one of the ports on the Spider 2 USB card the system hangs 50% of the times at least. Then I have to do a hard reset. If I do a soft-reset then system start to boot but I only get picture on monitor in 1 of 4 times. Sometimes I have to turn off computer and let it rest for a while.

Does Voodoo card gets to warm? Or is original PSU to underpowered?

I have all the Mediator files up to date except for pci.library. There I have version 9.11. If I have version 12.1 or 13.8 I get ramlib error.

Next step is to install an ATX PSU. I found that Amigakit had an ATX adapter cable for A4000.

Those who also have an Mediator card. How is your experience?

[drluking]

ram from Voodoo3 with VoodooMemOS is very slow ... you could try (if you have only A3640 C=) with a Zorro3 ram card eventually

I don't use USB card, but I have seen with every pci.lbrary version (also 9.11) that nic ethernet is not very stable with large file traffic (file of 500Mb or bigger) a solution is to add eventually a Zorro ethernet card
A lot better with gfx card (never problems with 16bit and 8bit 800x600 or less or more) and It's ok sound AHI card SB128

Use a bigger fan to voltage regulator and heatsink of your Voodoo3

PSU not I think for 4000Di, while for 4000D better an ATX adapter (don't use amikit one ... too thin the cables ... use the Elbox's one in thier store, or in other amiga store, or do it by yourself)

I'm using 13.8 (if you use only 68k, not PPC, you can use 12.x or 9.11); I don't have problems with 13.8 but I have OFF VoodooMemOS, if not I can't use gfx mode 16bit (BE), not PC (LE)
If you have problems, after change it, try also eventually MMULib (aminet) for 68k better 68040.library

Mine is so and so ... fine with 68k (but problems with big file in ethernet) and terrible with PPC card (you can read in the Sonnet 7200 about it; and not solved it ..... after monthes ...................)