rich <[EMAIL PROTECTED]> writes: rich> Today I tried to set up module support for my kernel and rich> "modulize" a bunch of stuff, and I'm having some rich> problems. First, from reading the rich> /usr/doc/kernel-source-2.2.1/debian.README file, I thought that rich> 'make-kpkg --revision=custom.1.5 kernel_image' was supposed to rich> take care of the modules. So I did that, installed the .deb rich> package, and rebooted. Now printing works (I'm pretty sure that rich> lp should be a module now), pon works (same for ppp support) but rich> sound does not.
rich> Here is what my /proc/modules file says: rich> sound 54484 0 (autoclean) (unused) rich> soundlow 208 0 (autoclean) [sound] rich> soundcore 2084 3 (autoclean) [sound] You need to do some tweaking to get sound support to work properly as a module. If you don't do anything special, a read request on /dev/audio tells the kernel to try to get sound support, so it loads the 'sound' module. Since there's no module installed that can provide actual audio data, the read fails. My /etc/modutils/sound contains: post-install soundcore modprobe -ks sb post-install sb modprobe -ks adlib_card options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 options adlib_card io=0x388 This has modprobe install the sb module when the kernel loads the soundcore module, and then loads the adlib_card module after that. It also specifies correct I/O, IRQ, and DMA information for the modules, which is essential for them to work correctly. -- David Maze [EMAIL PROTECTED] http://donut.mit.edu/dmaze/ "Hey, Doug, do you mind if I push the Emergency Booth Self-Destruct Button?" "Oh, sure, Dave, whatever...you _do_ know what that does, right?"