help with radeon 9250 in mediator1200 first edition

More testing after a stress break away from the 1200T :-)

Noticed a pattern in that the first boot up (after not using for a day or two) pciinfo always correctly finds my Radeon and every subsequent boot pciinfo reports garbage.

Tonight at first boot up I immediately went to devs:monitors and double clicked on the Radeon, went into Prefs:Picasso and board was attached. Went to test standard 800x600 screen at system hung. Every single attempt to reboot the system only brings up nonsense in pciinfo. It seems I only have one shot a day at initial boot up to have the Mediator see the Radeon correctly ?????

@ Ed

What version of the Fast ATA MK III you running ?

I've removed my FastATA for the moment and the system's been fine ever since. But the software version was the latest available from Elbox for the Mk III. Version 9.4a3.8 according to their website. link: http://www.elbox.com/downloads_fastata.html

I'll be replacing my FastATA once I've soldered in some new ROM sockets with the machined pin type that Roy mentioned and see if it makes any difference.

Just a random thought ~ I also wondered if the PFS3DS filesystem I've installed has any impact. On a Zorro 2 board like the blizzard the direct SCSI apparently can only use the first 16MBytes of Fast memory for disk access. Maybe something else tries to use that memory area as well e.g. the FastATA or the Mediator !?!?

if you have an apollo make sure the first thing the startup sequence loads is the fastata then the apollo libs then anything else including the mediator...

it can be a bit confusing as most of these ask to be first in the docs...

Thanks Roy, I'm using a blizzard 1230 MkIV and matching SCSI interface myself. Not sure what Klx300r is using.

I've got an Apollo 060@50 with 32 Mb ram. Will try modifying the S-S later tonight

Put Fast Ata first in my startup-sequence but still same issue. One boot pciinfo see the Radeon and the next it says 'no PCI devices in mediator'

the apollo 1260 can be funny beasts i have a blizzard 1260 in mine

have you the cpu 060 command

i have sent a link to my dropbox with my system in

Ya I do have all my ss commands and libs up to date and it's working great. I've hear d about the Viper 060 having issues with the mediator but not the Apollo 060?

i have heard people have problems with apollos and busboards,i only had minor problems though..

like i said,i had to put the fastata first and the anything apollo straight after it.i think it had something to do with the reset it does.
cant remember exactly its been a really long time.but it is a power hungry monster...one problem was the power supply.

as john says,they are funny cards sometimes.

heres the first part of mine

Quote:

---

C:ATA3.driver QUIET
C:stack 8192
PsdLoadModule DEVS:input.device QUIET ;Added by Poseidon-Installer
;BEGIN IDEfix
;If Exists C:IDEfix
; You may want to exchange the following line with LoadIDE reset quiet
; to make IDEfix reset resident, or LoadIDE start quiet
; to start IDEfix immediately and have it reset resident
; from the next reboot. Make sure to put LoadIDE behind any Kickstart mappers!
; C:IDEfix
;EndIf
;END IDEfix

---