Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: Acill on April 10, 2016, 06:50:53 PM
-
I am attempting to get a new install working for a friend with a Mediator and an A4000D. Its got an A3640 in it, buster 11 and has no issues with caps or other problems prior to installing the Mediator.
The mediator drivers install fine and all PCI cards are showing up with PCIinfo command. When installing P96 from the OS3.9 CD is completed I have followed the instructions to rename the cybervision3D drive to Radeon and change the board name in the icon info as well. (I also did this using my Voodoo 5500 in case his Radeon was the issue)
The problem comes up at this point. When the Radeon.device (or voodoo) is put into devs/monitors and the system reboots it hangs 90% of the time and wont boot. When it does boot and the board shows up in picassomode to start setting it up it will guru shortly after before getting things moving. We did manage to get a screen to show up in test before a guru so I know the boards are working. Not putting it in Devs and double clicking to start the device has the same result. So its pointing to something the driver is causing problems on the A4000D for sure.
So we decided to try a perfectly clean OS3.9 install and only the mediator drivers. Exact same results, the monitor driver hangs or causes a guru.
Any ideas? I can get more info from him if required, but I dont know what else to include. Clean system and same results points to an obvious thing I must be missing here. I do the same on my A4000T and its not a problem at all. Mediator setups are not new to me, but its a first on a A4000D.
-
I can remember it took me some years until I got everything more or less working.
First, did you run the setup for the graphics board? It sets some important environment variables, e.g. the amount of memory of the board and how much is used as RAM.
Second, if you have a gfx board with more than 128 MB memory, you may need to set with a jumper a different memory configuration.
Third, is it really a 5V card? Or does your mediator support 3.3V cards?
Four, I still have some issues that are most likely related to old caps or a bad power supply. My machine must run some minutes before I can boot the gfx card without a Guru. It seems that something in my machine must get warm before it works correctly and it seems to be related to the power supply as this behavior changes when using a different power supply. However, I was never able to fix this issue.
Five, my gfx board was also defective. It was a board by Elbox modified for 5V but this modification was broken after some month. Elbox fixed that for a small fee.
Six, it was hard to plug in the bus board such that all contacts with the mainboard fit. The slot is a bit longer than the card.
Seven, there are jumper on the mediator (not the bus board). Try different configs here.
-
Everything has been checked, but no luck. I told him to order a cap kit and I will replace them all and see. The 3640 is a Rev3.0 too, maybe I can get some GALs and update it too.
-
acill
thank you for starting the thread and for all the help. No luck at all with this setup such a shame. We tried a voodoo 5 pci too same results. Always a 800 0004 Guru error. Any help is appreciated i can post the media config log here if it helps
Also looking for the open pci radeon driver so i can test that and help narrow the problem.
-
acill
thank you for starting the thread and for all the help. No luck at all with this setup such a shame. We tried a voodoo 5 pci too same results. Always a 800 0004 Guru error. Any help is appreciated i can post the media config log here if it helps
Also looking for the open pci radeon driver so i can test that and help narrow the problem.
From what I read, the openpci version is just the elbox version hacked into a new driver. Same code mostly. As a result, like the Spider USB card they complained and its been pulled down from everywhere.
-
I also had this problem with my Mediator 4000Di. Did you already downloaded the MMCD 2.5 update from Elbox?
This latest update solved the problem Guru problem with my ATI Radeon 9250.
Getting the Mediator running is sometimes very frustating.
-
I also had this problem with my Mediator 4000Di. Did you already downloaded the MMCD 2.5 update from Elbox?
This latest update solved the problem Guru problem with my ATI Radeon 9250.
Getting the Mediator running is sometimes very frustating.
Yes, we have the mmcd 2.5 update, its been a rough time for sure. I didnt have anything like this happen on my A4000T
-
Try out the pci.library from this archive!
It is the latest Beta V10.x
What settings where done by Medconfig? try to disable the usage of Radeon-Memory as FastRam!
-
Try to reseat the Mediator, sometimes it will solve the problem.
-
I had a similar problem and even today it occasionally crashes like this.
My issues dealt with the memory settings. I tried tweeting them on install from the vanilla/default settings and it would never boot correctly.
Went back to default and it fixed the problem.
-
Try out the pci.library from this archive!
It is the latest Beta V10.x
What settings where done by Medconfig? try to disable the usage of Radeon-Memory as FastRam!
Not the same as what on the last update (MM2.5?) they sent out?
-
Not the same as what on the last update (MM2.5?) they sent out?
no:D
-
Thanks for the replies guys ill try the new library but i dont have much hope its so discouraging to be so excited for nice hardware and it doesnt work :(
-
Rotzloeffel
Thanks for the drivers I installed them and they actually seem to make my window operations faster (things had slowed down a little on my 4000 since installing mediator and software) However, I have the same 800 0004 crashes making things unusable :(
this goes for plain os 3.9 stock install and my os 3.9 bb4 install. I will do a media config report and post it here if you guys would look at it.
also tried with No Radeon mem setting and it still crashes.
-
Rotzloeffel
Thanks for the drivers I installed them and they actually seem to make my window operations faster (things had slowed down a little on my 4000 since installing mediator and software) However, I have the same 800 0004 crashes making things unusable :(
this goes for plain os 3.9 stock install and my os 3.9 bb4 install. I will do a media config report and post it here if you guys would look at it.
also tried with No Radeon mem setting and it still crashes.
Used the beta pci.library and it does make my windows faster. Tested with and without it on my backup partition and normal to confirm.
-
Ok guys here are the specs from medconfig please help.
14
*** Envarc: variable settings: ***
MMU = Not Set, previous setting: Not Set
NoCache = Not Set, previous setting: Not Set
Emulation = Not Set, previous setting: Not Set
Buster = 11, previous setting: 11
RadeonMem = 16, previous setting: 32
RadeonMemOS = Yes, previous setting: Yes
VoodooMem = 16, previous setting: 16
VoodooMemOS = Yes, previous setting: Yes
VoodooInt = Yes, previous setting: Yes
VirgeMem = Not Set, previous setting: Not Set
VirgeInt = Not Set, previous setting: Not Set
Warp3D = Yes, previous setting: Yes
Gfxaddr = Not Set, previous setting: Not Set
Force = Not Set, previous setting: Not Set
Terminator = Not Set, previous setting: Not Set
Memsize = Not Set, previous setting: Not Set
FastEthernet = 0, previous setting: 0
tv.prefs file name = Not Set, previous setting: Not Set
Tuner = Not Set, previous setting: Not Set
Background = Not Set, previous setting: Not Set
SpiderBuf = 5, previous setting: 5
*** Mediator System Files versions: ***
pci.library - ver.10.0 (12272 bytes)
MediatorNET.device - ver.2.9 (6160 bytes)
Radeon.card - ver.2.23 (16976 bytes)
Voodoo.card - ver.4.27 (14696 bytes)
Virge.card - ver.1.10 (11988 bytes)
Vendors.txt - ver. info N/A (219437 bytes)
MedConfig - ver.2.2 (126392 bytes)
*** Mediator Multimedia CD Files versions: ***
FastEthernet.device - ver.1.25 (7024 bytes)
mixer.library - ver.1.10 (3996 bytes)
fm801.audio - ver.4.14 (4156 bytes)
FM801 - ver. info N/A (1180 bytes)
sb128.audio - ver.4.20 (6336 bytes)
SB128 - ver. info N/A (2032 bytes)
SBMixer - ver.1.4 (2004 bytes)
tv.library - ver.4.13 (10304 bytes)
TV - ver.1.4 (1956 bytes)
tv.vhi - file N/A
.
*** Other files versions: ***
AmigaOS ROM Update - ver.44.57 (321768 bytes)
rtg.library - ver.40.3945 (216548 bytes)
emulation.library - ver.40.389 (39652 bytes)
Picasso96API.library - ver.2.300 (24520 bytes)
ahi.device - ver.6.7 (83888 bytes)
68040.library - ver.37.30 (43888 bytes)
68060.library - file N/A
warp.library - file N/A
ppc.library - file N/A
PciInfo report:
Pci Device 1:
VendorID: $1002
VendorName: ATI
DeviceID: $5960
DeviceName: RV280 Radeon 9200 Pro
ClassCode: $30000
RevisionID: $1
InterruptPin: 2
SubsystemVendorID: $174b
SubsystemID: $250
MemSpace0: $40000000 - $47ffffff
IOSpace1: $60c06000 - $60c060ff
MemSpace2: $50000000 - $5000ffff
RomSpace: $50020000 - $5003ffff
Pci Device 2:
VendorID: $1002
VendorName: ATI
DeviceID: $5940
DeviceName: RV280 http://www.ati.comRadeon 9200 Pro - Secondary
ClassCode: $38000
RevisionID: $1
InterruptPin: 0
SubsystemVendorID: $174b
SubsystemID: $251
MemSpace0: $48000000 - $4fffffff
MemSpace1: $50010000 - $5001ffff
ShowConfig report:
PROCESSOR: CPU 68040/68040fpu/68040mmu
CUSTOM CHIPS: AA NTSC Alice (id=$0033), AA Lisa (id=$00F8)
VERS: Kickstart version 45.57, Exec version 45.20, Disk version 45.3
RAM: Node type $A, Attributes $505 (FAST), at $7000000-$7FFFFFF (16.0 meg)
Node type $A, Attributes $703 (CHIP), at $4000-$1FFFFF (~2.0 meg)
BOARDS:
Board (Index Information Ltd): Prod=2206/161($89E/$A1)
(@$40000000, size 512meg, subsize same)
Board (Index Information Ltd): Prod=2206/33($89E/$21)
(@$60000000, size 16meg, subsize same)
Avail report:
Type Available In-Use Maximum Largest
chip 1599104 481664 2080768 1586368
fast 9546936 7230280 16777216 9100768
total 11146040 7711944 18857984 9100768
-
Did you ever resolve this? I am seeing almost exactly the same problem with my Mediator 4000Di / Voodoo3 setup - clicking the voodoo monitor driver or picasso96prefs will crash the machine on 90% of occasions.
Using OS3.9 and BB2.
I've tried disabling the usual suspects (fblit, Ftext, mcp, icon.library etc) but still get the lockups.
-
Did you ever resolve this? I am seeing almost exactly the same problem with my Mediator 4000Di / Voodoo3 setup - clicking the voodoo monitor driver or picasso96prefs will crash the machine on 90% of occasions.
Using OS3.9 and BB2.
I've tried disabling the usual suspects (fblit, Ftext, mcp, icon.library etc) but still get the lockups.
We never resolved it, got a new 4000 board and it ended up having issues as well. Now about to try on yet another board. I think its safe to say these new 4000Di boards are not as good as other versions.
I have the 4000T version in my machine and have ZERO issues with it.
-
We never resolved it, got a new 4000 board and it ended up having issues as well. Now about to try on yet another board. I think its safe to say these new 4000Di boards are not as good as other versions.
I have the 4000T version in my machine and have ZERO issues with it.
I have several Mediators. The biggest issue I've had is that sometimes NO PCI cards are recognized at all. Re-seating the Mediator card itself usually fixes it for awhile.
I haven't had freezing or crashing otherwise, but I am using a 060 cpu. Perhaps it's different with the 3640 CPU card...
-
We never resolved it, got a new 4000 board and it ended up having issues as well. Now about to try on yet another board. I think its safe to say these new 4000Di boards are not as good as other versions.
I have the 4000T version in my machine and have ZERO issues with it.
I have a desktop A4k mobo with Buster 11 in a Micronik BigBox Tower. Initially had the CybervisionPPC graphics card with the Cybergraphx software, later I changed to a Voodoo4 in the Mediator with Picasso96.
I have a weak remembrance that I initially had problems with the Picasso96 software as well, because there still were some parts of the Cybergraphx soft left on the disk and IIRC, Cybergraphx has to be removed completely in order for Picasso to work correctly. But this is just from my memory - and it is rouhly 15 years ago, when I switched to the Voodoo...
-
My old Voodoo card died about a month ago and I've had nothing but trouble getting a Radeon to work in my Mediator 3000. The first card didn't seem to work at all even with 3.3 volts provided. Today I got a Sapphire and it was at least recognised by pciinfo but there's something really strange happening.
When I boot without S-S and type pciinfo it shows output similar to this
Pci Device 1:
VendorID: $1002
VendorName: ATI
DeviceID: $5960
DeviceName: RV280 Radeon 9200 Pro
ClassCode: $30000
RevisionID: $1
InterruptPin: 2
SubsystemVendorID: $174b
SubsystemID: $250
MemSpace0: $40000000 - $47ffffff
IOSpace1: $60c06000 - $60c060ff
MemSpace2: $50000000 - $5000ffff
RomSpace: $50020000 - $5003ffff
Pci Device 2:
VendorID: $1002
VendorName: ATI
DeviceID: $5940
DeviceName: RV280 http://www.ati.comRadeon 9200 Pro - Secondary
ClassCode: $38000
RevisionID: $1
InterruptPin: 0
SubsystemVendorID: $174b
SubsystemID: $251
MemSpace0: $48000000 - $4fffffff
MemSpace1: $50010000 - $5001ffff
But if I let it boot into WB the first device changes DeviceID to $59f7 or something else, secondary seems ok. If I change slot I only get the primary device, the monitor driver loads but the computer hangs if I try to show any screens on the Radeon.
The PSU was replaced about 9 months ago and the drivers are the latest from Elbox. A "new" Voodoo card seems hard to find, and usually (?) expensive.
-
And suddenly the card seems to work. For like 2 minutes.
I change the WB screen mode to Radeon, full colour glory! Reboots and now my Amiga thinks it has 33 pci devices. 32 are unknown and the last is my NIC. Either the Radeon ore the Mediator is broken. I'll see if I can get the Radeon to work in a pc.
-
I've finally managed to get my Mediator to work. The issue was some of the libraries I was loading with LoadModule - layers.library, graphics.library, utility.library and dos.library all from don_adan on eab. Removing those from my s-s solved the problem I was having with constant hangs when launching the voodoo monitor driver or loading Picasso96prefs.
I also noticed that my ratte monitor switch was not seated correctly as I was just getting a grey screen from picasso96prefs when trying to test voodoo screenmodes. That now works ok.
My machine has been running all weekend with zero issues, the Voodoo3, sb128 and Realtek NIC are always recognised fine, ZorRam 256mb zorro 3 card working with no issue. This is with the latest 3v 4000Di Mk III.
So my attitude has rapidly gone from "this kit is a load of old junk" to "it's completely amazing".
-
I have several Mediators. The biggest issue I've had is that sometimes NO PCI cards are recognized at all. Re-seating the Mediator card itself usually fixes it for awhile.
...
I also had this "NO PCI cards recognized"-problem recently.
Un-plugging and re-plugging the power connector on the Mediator did the trick.
The contacts seemed to have been oxidised...
-
I've finally managed to get my Mediator to work. The issue was some of the libraries I was loading with LoadModule - layers.library, graphics.library, utility.library and dos.library all from don_adan on eab. Removing those from my s-s solved the problem I was having with constant hangs when launching the voodoo monitor driver or loading Picasso96prefs.
There is a library in libs:Picasso96/ witch is called picassolayers.library or superlayers.library or something like that! You have to rename or remove this library to use layers.library with loadmodule.... that should also solve your problem and you can use loadmodules again....
-
There is a library in libs:Picasso96/ witch is called picassolayers.library or superlayers.library or something like that! You have to rename or remove this library to use layers.library with loadmodule.... that should also solve your problem and you can use loadmodules again....
Good to know! I'll give that a test, although I'm happy just to leave the modified layers.library out as I suspect an rtg workbench doesn't require it anymore.
-
I also had this "NO PCI cards recognized"-problem recently.
Un-plugging and re-plugging the power connector on the Mediator did the trick.
The contacts seemed to have been oxidised...
Since I don't have access to my A4000 now, where is this located? On the logic board?
I've finally managed to get my Mediator to work. The issue was some of the libraries I was loading with LoadModule - layers.library, graphics.library, utility.library and dos.library all from don_adan on eab. Removing those from my s-s solved the problem I was having with constant hangs when launching the voodoo monitor driver or loading Picasso96prefs.
Are these libraries staying in memory after warm reboots and may that be the cause for Autoconfig issues only after reboot and not cold power on?
-
That could well have been the case. No issues now though.
-
Oh wait, I remember, I got my hopes up for nothing. I even got issues when simply powering up without HDD, waiting a few minutes with the kickstart screen and then rebooting again and still running into problems. :(
-
Since I don't have access to my A4000 now, where is this located? On the logic board?
...
Here:
(http://www.wiehltalbahn.de/images/sampledata/fruitshop/541.jpeg)
-
Good to know! I'll give that a test, although I'm happy just to leave the modified layers.library out as I suspect an rtg workbench doesn't require it anymore.
The layers.library is correcting many bugs FOR using an RTG Workbench :) Why do you think is an blablalayers.library in libs:picasso96/ ??? you should use it :)
-
There is still a layers.library. I was using LoasModule to load a patched layers.library which I have now removed. Any Picasso layers librararies remain in place.
-
Never mind, that's a different mediator. I got confused, hadn't seen any power connector on the 4000Di
-
I have a Mediator PCI 4000Di 3V MK-III Black Edition and have also been having similar issues that many of you are seeing.
The issues seems to be the 'bridgeboard" itself. If I use the daughter board without the "bridge" all my zorro cards work.
With the bridge in and no card (zorro or pci) I can sometimes (oh 5% of the time) get the mediator to boot up. when I put a radeon card in it can get it to boot 5% of the time with only 1-2% of the time were the radeon is recognized.
If I put my 128 meg ZorRam (uses 256 meg of zorro III space) with the bridge and no other cards (pci or zorro) 95% of the time I get a yellow screen, 5% of the time will it boot.
If I put in the zorram and a radeon card with the bridge (either configure with 512 meg space or not) I can get the amiga to boot 5% of the time with like 1% of the time were the radeon is recognized.
Busmastering has even been more of an issue.
Unfortunately I bought this to work with a crescendo 7200, and unfortunately have never seen it work in the A4000. and yes the crescendo does work in my Mac 7200......:-(
For now I gave up and put the Prometheus back in the a4000 with a voodoo 3 and a ethernet card.
-
Very very similar behaviour as I am facing. In my case it was pretty "consistent". Always worked when booting from powering on the machine. Not working when rebooting with CTRL-Amiga-Amiga. Mine is now on its way back to Elbox for repair.
-
I have a Mediator PCI 4000Di 3V MK-III Black Edition and have also been having similar issues that many of you are seeing.
The issues seems to be the 'bridgeboard" itself. If I use the daughter board without the "bridge" all my zorro cards work.
With the bridge in and no card (zorro or pci) I can sometimes (oh 5% of the time) get the mediator to boot up. when I put a radeon card in it can get it to boot 5% of the time with only 1-2% of the time were the radeon is recognized.
If I put my 128 meg ZorRam (uses 256 meg of zorro III space) with the bridge and no other cards (pci or zorro) 95% of the time I get a yellow screen, 5% of the time will it boot.
If I put in the zorram and a radeon card with the bridge (either configure with 512 meg space or not) I can get the amiga to boot 5% of the time with like 1% of the time were the radeon is recognized.
Busmastering has even been more of an issue.
Unfortunately I bought this to work with a crescendo 7200, and unfortunately have never seen it work in the A4000. and yes the crescendo does work in my Mac 7200......:-(
For now I gave up and put the Prometheus back in the a4000 with a voodoo 3 and a ethernet card.
It might be worth sending it back to Elbox. I can confirm that a ZorRam card does work ok with a Mediator 4000Di III as I've managed to get my 256mb one working.
Have you tried a fresh installed of wb3.9 to try and rule out software incompatibility issues?
-
It might be worth sending it back to Elbox. I can confirm that a ZorRam card does work ok with a Mediator 4000Di III as I've managed to get my 256mb one working.
Have you tried a fresh installed of wb3.9 to try and rule out software incompatibility issues?
@trixster Both are excellent ideas.
I tried a fresh installed of wb3.9 when I originally got it.
I will contact Elbox directly. I bought it through AmigaKit
-
Maybe refer to others with similar issues if you contact Elbox. I had confirmation they received my card, hopefully they get it fixed soon.
-
Maybe refer to others with similar issues if you contact Elbox. I had confirmation they received my card, hopefully they get it fixed soon.
How did you contact Elbox? When I attempted in the past to email their support they never replied, very frustrating.
I just email them again and I but this amiga.org thread in the email.......
-
I simply mailed to their info email address.
-
They replied to my email. They seem responsive now. Let us see what happens.... hopefully I can finally get this busboard working...........
-
Did they intimate what might be the issue? Or have they offered to look at it or replace it?
-
I've now come accross the 3rd A4000 with a Di in it with the same issue. The board works fine at a cold power up from the machine off but the moment you do a warm reset it will not see the Di at all. All three machines did this and the only fix was to turn off the 4000 and turn it back on to restart.
Never got a reply from Elbox about this. The first two people sold the Mediator, the 3rd is in the UK and he is just dealing with it now since it all works perfectly as long as he doesnt warm boot it.
-
I've now come accross the 3rd A4000 with a Di in it with the same issue. The board works fine at a cold power up from the machine off but the moment you do a warm reset it will not see the Di at all. All three machines did this and the only fix was to turn off the 4000 and turn it back on to restart.
Never got a reply from Elbox about this. The first two people sold the Mediator, the 3rd is in the UK and he is just dealing with it now since it all works perfectly as long as he doesnt warm boot it.
After reseating the mediator and doing yet another fresh install, I am having the exact same problem now. works sometimes cold. Remembering from my old layout days, It reminds me about ground line interference or telegraph noise as the components warm up. The design might need a tapeout, which unfortunate takes a long time.
-
When a number of different A4000s with varying setups all report the same problem it starts to seem less and less anecdotal and more like a genuine fault with the design of the product. There's a guy on the Facebook group with exactly the same issues you're both encountering. It's really rather odd. I'm lucky as I get the warm reboot issue only very occasionally (maybe one reboot in 15) so it's a non-issue for me; I guess it's just luck of the draw determined by the tolerance of your A4000 and the board you get from Elbox. I wouldn't be surprised if there's a 4000Di mk4 at some point (although my impression from Elbox is they aren't the quickest company to react to stuff).
-
The issue can be easily tested even without a hdd. Turn on Amiga go to early startup menu and see boards --> mediator shows up. Wait a bit, 30 to 60 seconds, warm reboot, go to early startup menu again and no more mediator in boards screen :(
I haven't heard any progress yet from elbox on my board repair.
-
I just got a mail my mediator is repaired and will be shipped. Fingers crossed.
-
Yes!!! It works now, also after a reboot!!! So, I can continue exprimenting with AOS4.1 first and then putting the Sonnet in.
-
Yes!!! It works now, also after a reboot!!! So, I can continue exprimenting with AOS4.1 first and then putting the Sonnet in.
This is great news!
-
Yes!!! It works now, also after a reboot!!! So, I can continue exprimenting with AOS4.1 first and then putting the Sonnet in.
What have they done? Did they change the MACHs as expected ?
-
I have no clue. If I don't forget I'll ask them by email.