Mediator 4000Di Help Please

[Acill]

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.

[magnetic]

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

[trixster]

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.

[Acill]

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.

[HammerD]

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...

[Dandy]

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...

[aggro_mix]

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.

[aggro_mix]

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.

[trixster]

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".

[Dandy]

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...

[Rotzloeffel]

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....

[trixster]

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.

[spudje]

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?

[trixster]

That could well have been the case. No issues now though.

[spudje]

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.

[Dandy]

Since I don't have access to my A4000 now, where is this located? On the logic board?
...

Here: