I got both modprobe and insmod to hang the way you describe -- they are
looping in userspace somewhere.
On your side, you have:
options sound sb io=0x220 irq=7 dma=1 dma16=5
The base driver, sound.o, doesn't take any parameters. I think you
want:
options sb io=0x220 irq=7 dma=1 dma16=5
When I do this and run modprobe, it goes as far as it can on my
hardware:
[root@smoke insmod]# lsmod
Module Size Used by
serial 19552 1
[root@smoke insmod]# modprobe -v sb
/sbin/insmod /lib/modules/2.1.76/sound/sound.o
/sbin/insmod /lib/modules/2.1.76/sound/uart401.o
/sbin/insmod /lib/modules/2.1.76/sound/sb.o io=0x220 irq=7 dma=1 dma16=5 io=0x220 irq=7 dma=1 dma16=5
/lib/modules/2.1.76/sound/sb.o: init_module: Device or resource busy
sound: Device or resource busy
[root@smoke insmod]# lsmod
Module Size Used by
uart401 5656 0
sound 78244 0 [uart401]
serial 19552 1
This is modutils-2.1.71, compiled straight ftp.kernel.org, running on
kernel 2.1.76 + my sound-module.2176 patch.
So I think that sound-module.2176 is in the clear. I will go check
out 'insmod' and 'modprobe' some more and I'm likely to file some bug
reports against those.
Meanwhile, try fixing your /etc/conf.modules as above, and let me
know how that works.
Michael Chastain
<mailto:mec@shout.net>
"love without fear"