Ahhhhhhhh yes 'fun' we'll call it then :-)
Printable View
Ahhhhhhhh yes 'fun' we'll call it then :-)
Ok, I did some more testing, wondering if the newest libraries from Elbox might be causing lockups.
System Details:
- A1200 Motherboard 2MB CHIP, 4MB Fast memory.
- Standard internal floppy as DF0: + DF1: external floppy.
- Phase 5 Blizzard 1230MkIV 030@50MHz, 64Mb Fast Memory. Blizzard SCSI card. SCSI CDROM.
- Mediator 1200TX, MMCD_UP_2.1, ATI Radeon 9250 256MB.
- FastATA MkIII, 30GB IDE drive, DH0: DH1:
- Subway USB Controller, USB Keyboard and Mouse. USB Media card reader.
- AmigaOS Version 3.9 + Boung Bags 1 and 2.
- Picasso96 version 2.1b software.
- "be quiet" Power supply unit, 300Watts (BQT SFX:300W).
Tests and results:
Test 1. Roll back the Radeon.card.
- Swapped the latest Radeon.card version 2.19 (MM_CD_UP_2.2) for the previous version 2.12 (MM_CD_UP_2.1).
- Still getting lockups when Loadmondrvs tries to load DEVS:Monitors/Radeon.
- Picasso96Mode not listing any Board in the "Attach To" menu.
- Revert files to original setup.
Test 2. Remove other *.card files in LIBS:Picasso96/
- Moved the CVision3D.card out of LIBS:Picasso96/
- Still getting lockups.
- Picasso96Mode not listing any Board in the "Attach To" menu.
- Revert files to original setup.
Test 3. Roll back PCI.Library
- Swapped latest PCI.Library version 9.9 (MM_CD_UP_2.2) for the previous version 9.7 (MM_CD_UP_2.1).
- Still getting lokcups.
- Picasso96Mode not listing any Board in the "Attach To" menu.
- Revert files to original setup.
Test 4. Check for contention between ATA3.Driver and Radeon Monitor.
- In the S:Startup-Sequence comment out C:ATA3.Driver RESIDENT QUIET
C:ATA3.Driver RESIDENT QUIET (old value)
;C:ATA3.Driver RESIDENT QUIET (new value)
- Reboot, then manually run DEVS:Monitors/Radeon in a Shell window.
- - Surpise! No lockup and the RadeonMem is also now active. 300MB FastMem available.
- Picasso96Mode now lists Radeon in the "Attach To" menu.
- Attach the Radeon board in Picasso96Mode and Save.
- After a reboot the new resolutions saved in Picasso96Mode are now visible in SYS:Prefs/Screenmode
- Testing different resolutions proves successful.
Test 5. Reboot and manually rerun DEVS:Monitors/Radeon to check repeatability.
- Reboot, then manually run DEVS:Monitors/Radeon in a Shell window.
- - Surpise! No lockup.
- Testing different resolutions proves successful.
Test 6. Uncomment LoadMonDrvs in Startup-Sequence.
- In the S:Startup-Sequence uncomment C:LoadMonDrvs.
;C:LoadMnDrvs (old value)
C:LoadMonDrvs (new value)
- After a reboot the new resolutions are still visible in SYS:Prefs/Screenmode
- Testing different resolutions proves successful.
Test 7. Verify possible conflict between ATA3.Driver and Radeon Monitor.
- In the S:Startup-Sequence uncomment C:ATA3.Driver RESIDENT QUIET
;C:ATA3.Driver RESIDENT QUIET (old value)
C:ATA3.Driver RESIDENT QUIET (new value)
- The system will not reboot.
- Revert the C:ATA3.Driver line in the Startup-Sequence
C:ATA3.Driver RESIDENT QUIET (old value)
;C:ATA3.Driver RESIDENT QUIET (new value)
- System reboots ok.
- Testing different resolutions proves successful.
Test 8. Check if the order of loading the ATA3.Driver and LoadmonDrvs makes any difference.
- Move the ATA3.Driver entry in Startup-Sequence below the LoadmonDrvs entry.
C:LoadMonDrvs
C:ATA3.Driver RESIDENT QUIET
- The system will not reboot.
- Revert Startup-Sequence entries.
- System reboots ok.
- Testing different resolutions proves successful.
Conclusion:
- It appears there is a definite conflict between DEVS:Monitors/Radeon and C:ATA3.Driver.
I'll send this over to the Elbox Support folks and see what they can suggest.
Hopefully these tests might help some other Mediator owners in the future.
Great testing Ed! Will mess with mine next week once I'm back home from vacation
ok back from little vacation and back to Mediator testing! seems I finally got the Radeon 9200-256Mb to be reported correctly by pciinfo now but when I double click on the Radeon driver in devs:monitors I get a an immediate sytem hang. starting to wonder if with all the renaming, deleting, moving stuff around i got the radeon, radeon.info and radeon.card files messes up??
John/ Ed/ anyone else with a Mediator 1200 and Radeon 9200 with 256mb, can you please send over your working radeon, radeon.info and radeon.card files so I can attempt to get rid of my Mediator paranoia:unsure:
sent you a pm klx
Hope you had a good break Klx :thumbsup:
Just to add another pointer, I ended up removing my FastATA1200 and my setup is working ok now on the Blizzard SCSI. I'm not sure if you have a FastATA Klx but there are some serious issues with the combination of hardware/software, specially the ROM sockets which are flaky as hell. I also did an uninstall of Picasso96 and reinstalled fresh after doing the Elbox MediaCD 2.2 update.
I'll send a PM too. er... if I can figure out how to add attachments to PM's :oops:
just ask him for his email in private and send it that way.:)
no problems with fastata here,then again i changed the rom sockets on the motherboard for machined pin type,no problems after that bonus was i dont ever need cable ties now...
half the problems with adding expansions on these is mechanical connectivity issues.
anyway,must sleep,its been a long day:)
no problems with fastata here
or use dropbox
thanks John:) hopefully I can finally see something with my Radeon tonight
@ Ed.D
just enough to recharge the batteries a bit mate BUT alas when I've learned since I had my kids 9 years ago that there really is no relaxation for papa on vacations
well guys I think Im with Ed taking a break from fighting with this mediator before I smash stuff I know I'll regret smashing soon arghhh. Appears my problem is either a flaky connection or damaged mediator board as I just tried to load the files received from johim and surprise surprise pciinfo only seeing garbage yet again! Didn't touch or move the case at all.....Ed yes I do have a Fast ATA MKIII installed and it appears to be working fine but like you said who knows....