>I get some oops whenever I try to insmod sb
[...]
>Sep 25 14:08:35 penny kernel: sb: No ISAPnP cards found, trying standard ones...
>Sep 25 14:08:35 penny kernel: SB 4.13 detected OK (220)
>Sep 25 14:08:35 penny kernel: <Sound Blaster 16 (4.13)> at 0x220 irq 5 dma 1,5
>Sep 25 14:08:35 penny kernel: <Sound Blaster 16> at 0x330 irq 5 dma 0,0
>Sep 25 14:08:35 penny kernel: sb: I/O region in use.
>Sep 25 14:08:35 penny kernel: Sound: Hmm, DMA1 was left allocated - fixed
>Sep 25 14:08:35 penny kernel: Sound: Hmm, DMA5 was left allocated - fixed
>Sep 25 14:08:35 penny insmod: /lib/modules/2.4.0-test8/kernel/drivers/sound/sb.o:
>init_module: No such device
>Sep 25 14:08:35 penny insmod: Hint: insmod errors can be caused by incorrect module
>parameters, including invalid IO or IRQ parameters
>Sep 25 14:08:35 penny insmod: /lib/modules/2.4.0-test8/kernel/drivers/sound/sb.o:
>insmod char-major-14 failed
>Sep 25 14:08:35 penny kernel: Unable to handle kernel paging request at virtual
>address ca8fc1a0
I was also getting this with 2.4.0-test9-pre6. It looks to me like the
soundblaster driver was tripping over it's own feet (finding 0x220,
registering it, trying to register it again, then bailing because
"someone" already had it registered. It doesn't bail cleanly - leaving
lots of stuff still allocated, which appears to be the cause of the
oops.
I was eventually able to load the module cleanly by specifying:
insmod sb isapnp=0 multiple=0 io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330
In particular, the "multiple=0" got it to load without the "sb: I/O
region in use".
---
Andrew McNamara (System Architect)
connect.com.au Pty Ltd
Lvl 3, 213 Miller St, North Sydney, NSW 2060, Australia
Phone: +61 2 9409 2117, Fax: +61 2 9409 2111
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
