I have a medium age Sound Blaster 16 Value Edition (the chip revision or
whatever that number is 4.11). Settings are soft, not jumpers. Works fine most
of the time, but recently, it will lock Linux hard on reboot. I am using the
sound driver as a module inserted at boot time and _not_ using kerneld.
Now the interesting bit - it will only lock the machine on a warm boot. As soon
as I use the reset button to get out of the lockup caused by warm booting it
works fine. This is new (2.0.x) behaviour - it used to work regardless.
Configuration as follows:
Sound Blaster at 0x220 irq 5 drq 1,6
SB MPU-401 at 0x330 irq 5 drq 0
OPL-2/OPL-3 FM at 0x388 drq 0
When I used to have msdog on the machine as well, I used to get a similar
effect - warm rebooting from Linux into dos wouldn't lock the machine, but it
would cause the soundblaster drivers to spew something along the lines of
'invalid BLASTER=xxx' and not get installed. One cold boot later, all was OK.
And I was using the same interrupts under dos and Linux.
Hoping this helps someone out there...
David