bamiga2002 wrote: @Rogue What more could we do to help track down the problem that's causing the OS4 from not booting with the graphic drivers?
Actually, I am out of ideas. I know that it works on most people's systems, in fact I think only two people actually have the problem. I can only guess that the mediator models you have have some issue with the kernel, but really, I don't have a clue what the problem is.
Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
Could elbox try to help you to understand the problem about the kernel and the mediator model ?
The point is that I don't know what problem there is. Apparently the kernel/mediator support works for 99%, I only know of two people that have a problem.
That might be caused by anything. For all I know, your mediator could be broken, you could have a wrong jumper set, or anything like that.
Bottom line, I really can't help you.
Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
My mediator works and the jumpers settings are correct as i can install the os4 classic without update, os 3.9 works fine, i can use os4 with the new kernel if i use the elbox's driver..
i guess that the mediator is ok as long as i can do all these things..
No necessarily. The access timing is radically different between real 68k, emulated 68k, and PowerPC native.
Like I said earlier, it seems to work on everyone else's machine, so I am quite sure that the code works. I think it is very likely a problem with your hardware.
You might try to set the memory window size jumper to 4 MB instead of 8 (or the other way around). or try the WAIT jumper in different positions, and even the CONFIG jumper. I don't know what these are supposed to do.
Beyond that, I am sorry to say I am out of ideas.
Seriously, if you do want to contact me write me a mail. You're more likely to get a reply then.
What happens if you only disable voodoo3.chip and keep pcigraphics enabled. make sure you have NO Elbox drivers running then otherwise they will interfere.
Its important when you report problems that we know EXACTLY what is going on. and that no other 3rd party drivers interfere.
If for example disabling voodoo3 already makes the system boot in AGA we know a bit more.
If that doesnt work we can assume its something in pcigraphics. MAYBE
I have tried disabling the voodoo.chip and keeping the pcigraphic in kicklayout with the NEW KERNEL and the system booted normally in AGA !!
Then enabling the voodoo.chip in the kicklayout my system doesn't work anymore..
i have a clean os4 installation with the update and no elbox drivers at all.. i removed them completely before doing these tests
I also tried to boot in aga using the pcigraphic in kicklayout, go to screenmode prefs and save the screenmode to PAL HIGH RESOLUTION then i edit the kicklayout and enabling voodoo.chip to see if i can boot also in aga and then in the AGA switch to voodoo, but it doesn't work.. when i enable voodoo.chip, my system stop the boot..
@bamiga2002
Could you try my same test to see if even you have the same resylts ?
I think SimplePPC is trying to figure out if OS4 Mediator driver is working, whit other PCI devices for example Ethernet.
Does your sound blaster work whit OS4 drivers? Does your Ethernet card work whit OS4 drivers? If only Voodoo that does not work, then problem can not be blamed on Mediator, and you try different type of graphic card.
If the problem is just black screen it might be that your monitor is out of sync, incorrect vertical or horizontal frequency, and pixel clock settings.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.