Wierd problem using emu10k1 driver recompiled w/sequencer support
 

I got the emu10k1 source and edited the config file to give sequencer support, then compiled and installed both the driver and the emu-tools. Well, technically, the driver works, and I CAN get bass and treble control. BUT, to do this, every time I boot I have to rmmod the emu10k1 module and modprobe it again. Otherwise, no bass/treble support. Oh, also, during the bootup sequence there is an error message saying that /usr/local/etc/emu-script failed.

I am thinking this is maybe because the module is being loaded by something else already, and trying to add it again using the script is resulting in an error. And then when there is no emu10k1 module loaded, there is no error with running the emu-script.

I don't know if that theory is right, or even close, but here is my modules.conf:

Anyone?

Have you tried commenting out anything in /etc/rc.d/rc.modules referring to your emu10k1 in there? If nothing is there, try moving the 2 entries in modules.conf around so alias sound emu10k1 is first, and 1 more thing, shouldn't sound be also showing a slot:
alias sound-slot-0 emu10k1

?

Cool

If you look at the modules.conf that I posted, you'll see that that line does come first. I added the sound-slot-0 line to the modules.conf, and that didn't fix the problem. Also, while there are a few lines in /etc/rc.d/rc.modules that refer to the emu10k1, they are all commented out. When I boot up, I get an error message saying that the insmod of /lib/modules/2.4.20/kernel/drivers/sound/emu10k1/emu10k1.o failed. I did an ls -l on it to see how old this emu10k1.o was, thinking that maybe this version was an old one and not the one that I had recently compiled and installed. But it was just 4 days old, which would correspond with when I compiled and installed the driver, and when I made the original post.

Now, I know just about nothing about the kernel, but I am wondering if this module is compiled INTO the kernel. Can you have modules that are compiled into the kernel, or does the mere term "module" mean that it has to be loaded separately? How would I be able to tell this, within the kernel source and config files, etc.?

In the soundcard section of the kernel config, look for an M or a * next to the option. a M means module, which yes, means it's seperated from the kernel, an * means it's compiled in.

And I meant to switch the order, and was just typing fast ;)

See if you can find another error message, or more of one so you can determine why it failed.

Cool

OK here are the only lines in the config file that refer to emu10k1:

CONFIG_SOUND_EMU10K1=m
CONFIG_MIDI_EMU10K1=y

So it looks like it is a module.

I can't see a way to get a more verbose output from /usr/local/etc/emu-script to see why the script fails. I checked the log files in /var/log, and I found this in the syslog several times, I am assuming each time I do something that uses the sound card.

Jun 30 17:56:46 hangar18 modprobe: modprobe: Can't locate module sound-slot-1
Jun 30 17:56:46 hangar18 modprobe: modprobe: Can't locate module sound-service-1

This doesn't seem to answer anything though.

What I can't figure out is, if the script fails then why is the emu10k1 module still loaded, albeit without sequencer support?

Anyone else got any ideas?