LinuxQuestions.org - recompiled emu10k1 driver not loading at boot

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - recompiled emu10k1 driver not loading at boot (https://www.linuxquestions.org/questions/slackware-14/recompiled-emu10k1-driver-not-loading-at-boot-79685/)

recompiled emu10k1 driver not loading at boot

I posted about this once before, but the problem was never resolved, so I was hoping I could find some help this time around.

I downloaded and compiled the emu10k1 driver from sourceforge, so that I could get bass/treble support (why they didn't enable it by default is anyone's guess), but it will not load on boot.

dmesg gives the following output about the sound card:

Code:

Creative EMU10K1 PCI Audio Driver, version 0.20a, 19:31:20 Jul 28 2003

emu10k1: EMU10K1 rev 7 model 0x8061 found, IO at 0xd000-0xd01f, IRQ 5

ac97_codec: AC97 Audio codec, id: 0x8384:0x7608 (SigmaTel STAC9708)

emu10k1: SBLive! 5.1 card detected

The same text appears on boot, but it is followed by a line saying that an insmod of /lib/modules/...../emu10k1.o has failed, and /usr/local/etc/emu-script, the script that intializes the driver, has failed.

However, I still have sound, without bass/treble support though. So somehow, the module is being loaded but the script is failing.

It gets more confusing though. If I go in as root and remove the module with rmmod, and then do a modprobe, the driver is loaded correctly, bass/treble support and all.

So I am wondering, is something else, some script that I am unaware of, loading the emu10k1 module without my knowledge? The emu10k1 line in my /etc/rc.d/rc.modules script is commented out, so it couldn't be that.

what is in your /etc/modules.conf file??
mine says..............

Code:

alias sound emu10k1

post-install emu10k1 /usr/local/etc/emu-script

sound loads up with no probs, bass/treble ,digital output

mine is:

Code:

alias sound emu10k1

alias sound-slot-0 emu10k1

post-install emu10k1 /usr/local/etc/emu-script

OK, I found out something wierd. If I comment out the emu-script line out of my modules.conf, so that it is run at boot, but then run it manually after the computer has finished booting, then it works fine. No removal of the module needed. Needless to say this has me baffled. Is there some script that I can edit and add a line to run the emu-script, after the hardware is detected, modules loaded, etc.? In other words, right at the end of the boot process. I know it's a dirty fix, but if it works, it works right?

Still wondering if anyone knows how I can do that.