Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I thought I had fixed my ALSA problems, but after a reboot, they're back :-(
I think the trouble is that I've got these conflicting sound related modules that get loaded on reboot and I can't figure out how to remove them. Here are the facts:
1) Using 2.6.7 kernel with ALSA (Debian 686)
2) Alsa fails to start *I think* because it finds these 2 loaded modules:
- es1371
- ac97_codec
3) I can't remove either of those modules because they're "in use" (even --force fails)
4) /etc/modules contains only the following:
apm
soundcore
snd-ens1371
nvidia
So my question is... how in the heck does my system know to load all of my modules when only those 4 are listed in /etc/modules?
Where I can I find the file that lists all of the *other* modules that get loaded at boot time?
After failing and failing to get my i810 integrated sound card to cooperate with ALSA, I went out and but an ens1371 based PCI sound card -- so now I have 2 sound cards but only want to use the ens1371. Which means I somehow need to remove that ac97_codec module. HOW?!
After failing and failing to get my i810 integrated sound card to cooperate with ALSA, I went out and but an ens1371 based PCI sound card -- so now I have 2 sound cards but only want to use the ens1371. Which means I somehow need to remove that ac97_codec module. HOW?!
turn it off in the bios !
look... use the "USED BY" output of lsmod to determine what order you have to rmmod the modules.
but insteads of removing them AFTER they load, you should just NOT LOAD THEM !
find where they are being modprobed i the init scripts, and comment them out.
i think you are not experianced anouth woth computers to attempt what you are attempting.
I was really hopeful about this, but alas... no joy. I added the lines "es1371" and "ac97_codec" to the blaclist, but both modules still cheerfully load-up on reboot.
Quote:
turn it off in the bios !
It's gonna sound bizarre (or impossible), but believe it or not, even after disabling the onboard ac97 sound and ac97 modem in the bios, the evil zombie modules still load up and refuse to die.
Quote:
look... use the "USED BY" output of lsmod
My lsmod is posted above. As you can see, there is no used by output for es1371
Quote:
insteads of removing them AFTER they load, you should just NOT LOAD THEM !
Hey what a great idea! (please see the title of this thread)
Quote:
find where they are being modprobed i the init scripts, and comment them out.
I would *really* like to do that. From looking at my init scripts above, can you see anything that you think I should comment out?
Quote:
i think you are not experianced anouth woth computers to attempt what you are attempting.
Umm, thanks. That's really helpful.
Any other ideas on how to kill these evil bastard modules?
i would compile the laetes kernel with NO sound support
Hmm.. that might be a pretty good idea actually. Surely, there must be an easier way -- *something* is causing those kernel modules to load, but I just can't figure out what.
Quote:
but for a newb, a kernel compile may generate more problems.
I'm not afraid of recompiling the kernel, especially on Debian which is a piece of cake. Just because I can't solve this (and neither can anyone else so far) doesn't mean I'm a total newb
Hmm.. that might be a pretty good idea actually. Surely, there must be an easier way -- *something* is causing those kernel modules to load, but I just can't figure out what.
the init scripts are loading the sound modules !
remove the friver loading lines from the init scripts, and they will not be loaded.
then, when booted, you can modprobe the modules you require. then write them back into the init scripts.
I don't remember the setup on debian, but did you try grepping the entire dir (where the startup scripts are) for the module name? cd to dir, then something like
grep module_name *
man grep for flags, usage, etc. also, iirc, debian's /etc/alternatives caused me some confusion, but not sure if that would apply here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.