Soundblaster module bug

Mike Perry (mikepery@mcs.net)
Sat, 14 Sep 1996 20:51:36 -0500 (CDT)


I've never filed a bug report before because my experiences with linux
before the 2.0 kernels was utopian, so bear with me, I think I'm on to
something.

audio_init: wrong version or undefined
DMAbuf_init: wrong version or undefined
Loading failed! The module symbols (from linux-2.0.20) don't match your
linux-2.0.20

Thats the output I get from running 'insmod sound'

*** Unresolved symbols in module /lib/modules/2.0.20/misc/sound.o

Thats the output from depmod -a

Using doom and telling it that I have sound locks up the computer when
kerneld trys to load the module.

Now for a description of my machine/setup.
I have the modules package 2.0.0, have enabled module support in the
kernel, have enabled SETMODVERSIONS (for dosemu and ibcs-2), and kernel
daemon support (yes i'm running kerneld). All my other modules work and
autoload just wonderfully (those include: floppy support, aout support,
dos filesystem support, aout support, lp support and cdrom support).
For my sound setup I have a Vibra16 (100% SoundBlaster16 compatible) on
port 220, irq 5, dma 1, high dma 5, mpu port 330, mpuirq -1. I have
/dev/audio and dsp enabled, FM synthesyser enabled, and MIDI enabled.
All this was done though the 'Old configuration script' option under make
menuconfig (This brings another possible bug to mind, using either regular
make config or make menuconfig resulted in a whole bunch of redefined function
errors in sb_common.c, making compiling impossible). My kernel compile
went like this for 2.0.20:
make mrproper;make menuconfig;make dep; make clean;
make zlilo; make modules; make modules_install

P.S. The sound system worked excellent when compiled into the kernel under
2.0.10 2.0.12 2.0.13 and 2.0.16 even using make menuconfig and not the
'Old configuration script'