I tried to make my SoundBlaster Audigy work on Debian "Woody" 3.0r1 running kernel 2.4.22_10.

I compiled successfully two different drivers, one from Sourceforge.net and one from ALSA, but modprobe can't accept the module emu10k1 in both case.

The error occured was:
pc_name:~# /sbin/modprobe emu10k1
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o: init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o: insmod /lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o failed
/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o: insmod emu10k1 failed

How can I get rid of this mess to make my soundcard work?

Thanx, guys.

Are you certain that you're probing the modules that you compiled, and not those from the stock kernel? The sourceforge code certainly does support Audigy, I'm not certain about the mainline kernel.

You're right, the mainline kernel emu10k1 doesn't support Audigy but both the driver I successfully compiled and failed to make them probed are capable to use Audigy technology.

Well, I'll tried to recompile again the kernel, yet that error occured when I selected the mainline emu10k1 and when I decided to leave checked only soundcard support deselecting the mainline emu10k1.
That's why I think recompiling the kernel gonna be a waste of time, though just a try is harmless, isn't it?

If you got other ideas post here.
See ya.

What I am getting at is whether "/lib/modules/2.4.22/kernel/drivers/sound/emu10k1/emu10k1.o" is definitely the one that you got from doing a "make install" with the emu10k1 package.

Also, ensure that you've observed the steps outlined in docs/README: bios configuration for instance.