I’m 99% sure this is the trouble, I don’’t really understand IRQ’s and interrupts, there is some info in the Rage_128_register_referance_guide.
I tested my theory via OS X 10.4.11and it mapped the VRAM rather than giving me the ATY:Not Usable, it also changed the screen resolution twice, once to 640x480 then to 1280x960.
“ /pci/@f” select-dev
“ ATY,Rage128Pd” encode-string “ name” property
1 encode-int “ interrupts” property
OS X would not be able to change the screen resolution if the ‘NDRV’ didn’t load!!!
So I’m 99% sure this is the trouble and we need to figure out how to create a mapped interrupt for the card, rather than this dummy
Interrupt I create because I’m a dummy;-)
> On Aug 8, 2019, at 12:41 AM, Jd Lyons <lyons_dj(a)yahoo.com> wrote:
> Could be the Rage128 ‘NDRV’ is aborting do to the lack of an interrupt……….