Harumph
So with vsyncen pulled, it boots wonderfully into 755 from internal SCSI. ADB works, keyboard works, mouse button works but mouse won't move.
With a soft reboot, you can then pram zap, extensions off etc.
Reconnecting vsyncen once it's booted makes no difference, it doesnt chuck the slot exception, it doesnt make the mouse work again... hmmm...
I can see the vertical sync IRQ(6) gets all the way through the pals, via2 and to the GLU as VIAIRQ2...
The VIAIRQ2 signal looks quite dirty to me, there's a volt of noise on it. By comparison, VIAIRQ1 looks clean as a whistle.
Does someone have the ability to look at VIAIRQ2 on a working SE30 for me?
Does anyone know....
- Does the vsync interrupt handler get loaded at boot time from the on board video declrom as part of the whole slotE psedoslot thang?
- Or does it get loaded from the main romsim?
So with vsyncen pulled, it boots wonderfully into 755 from internal SCSI. ADB works, keyboard works, mouse button works but mouse won't move.
With a soft reboot, you can then pram zap, extensions off etc.
Reconnecting vsyncen once it's booted makes no difference, it doesnt chuck the slot exception, it doesnt make the mouse work again... hmmm...
I can see the vertical sync IRQ(6) gets all the way through the pals, via2 and to the GLU as VIAIRQ2...
The VIAIRQ2 signal looks quite dirty to me, there's a volt of noise on it. By comparison, VIAIRQ1 looks clean as a whistle.
Does someone have the ability to look at VIAIRQ2 on a working SE30 for me?
Does anyone know....
- Does the vsync interrupt handler get loaded at boot time from the on board video declrom as part of the whole slotE psedoslot thang?
- Or does it get loaded from the main romsim?