[PlanetCCRMA] Problems with Alsa and Sound Blaster Live card
TheRobeBoy at aol.com
TheRobeBoy at aol.com
Sun Feb 29 15:47:01 PST 2004
Thanks for the reply. I went ahead and tried shutting down all of the
modules that I could. I ended up with the following list:
mousedev 5620 1
usbcore 81152 1
input 5856 0 (autoclean) [mousedev]
ext3 7344 2
jbd 54228 2 [ext3]
I then attempted to start up alsa with the "alsasound start" command and I
recieved the following errors:
Starting sound driver snd-emu10k1
/lib/modules/2.4.22-9.23rc3.ll.rhfc1.ccrma/kernel/sound/snd-emu10k1.o: Hint:
insmod errors can be caused by incorrect module parameters, including invalid
IO or IRQ parameters. You may find more information in syslog or the output
from dmesg
init_module: No such device
/lib/modules/2.4.22-9.23rc3.ll.rhfc1.ccrma/kernel/sound/snd-emu10k1.o: insmod
/lib/modules/2.4.22-9.23rc3.ll.rhfc1.ccrma/kernel/sound/snd-emu10k1.o failed
/lib/modules/2.4.22-9.23rc3.ll.rhfc1.ccrma/kernel/sound/snd-emu10k1.o: insmod
snd-emu10k1 failed
[FAILED]
I completely wiped my drive and reinstalled everything and I am still getting
the same problems. I am not really sure what I could be missing...
Thanks for the help.
- Jeff Taylor
In a message dated 2/29/2004 3:55:03 PM Central Standard Time,
juanig at ccrma.Stanford.EDU writes:
You are right, seems that you have the OSS module still loaded
somewhere. You have to look for the OSS module (something like
"emu10k1") and then remove it with:
/sbin/rmmod "your_module_name"
After the module is successfully unloaded, you can start alsa or the
alsaconf program by,
/usr/sbin/alsaconf or
/etc/rc.d/init.d/alsasound restart
Juan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/planetccrma/attachments/20040229/f88862a4/attachment.html>
More information about the PlanetCCRMA
mailing list