SlackwareThis Forum is for the discussion of Slackware Linux.
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 am trying to remove some modules from my running kernel using the command rmmod as root. I was able to do that sucessfully, but when I rebooted all the ones I removed, came back. I have read the rc.modules is the file that loads modules at boot time, but most of the lines in this file are commented out. I don't think it is comming from this file. What am I doing wrong, where are they comming back from?
The only places they'll be coming from (on a standard setup) would be /etc/rc.d/rc.modules AND/OR /etc/modules.conf
rc.modules is commented nearly all the way, but you'll wanna actually make sure that the module(s) you don't want loaded are also commented, could be just 1 or 2 lines out of that amazingly large file, so you'll wanna look closely.
They are also loaded upon the kernel KMOD during boot... or hotplug...
If it's hotplug modules you want to remove, just edit the file:
/etc/hotplug/blacklist (or something like that...)
..and insert your modules name in it...
Else, I think that kernel configuration and compiling would be needed... I've just learned how to make my kernel having ONLY the drivers I need for my machine and it works great!... No more SCSI controller check at boot (don't have any SCSI device!) and many other thing...
It's not difficult, but it takes time to get used to it... (couples of hours, since compiling take some time... ~40mins on my PIII-1Ghz)
Well first off my modules.conf is completely empty. Second I looked in the rc.modules file and upon closer inspection I found some modules I could comment out(mainly related to my network card, which is giving me errors).
I am despirately(sp?) trying to get sound on my box, so in one of my attempts I compiled and inserted the ALSA modules into the kernel. It did not work, so I am trying to remove these modules and try with a different method. SO mainly, I am trying to remove these modules(mostly begin with snd...). Also I found that hotplug file. i think it also is being read upon boot up. From a quick look it looks like it is loading modules needed for PCI devices. I am scared to try to comment this stuff out, since I think that major problems will arise. I don't think this file mentions modules by name, but instead loops through and finds modules that exist. Maybe I can go to the /lib... directory and just erase the *.o files that begin with snd ?? What do you think I should do?
Originally posted by CodeWarrior Maybe I can go to the /lib... directory and just erase the *.o files that begin with snd ?? What do you think I should do?
I would not go deleting libraries that begin with snd or look like they should not be there. I think your modules are overwritten anyway when you do: make modules_install unless you are compiling a different version kernel. A kernel version 2.4.20 should look in /lib/modules/2.4.20 for its modules. If you have a 2.4.18 directory or something, move or rename it. Update your system map and all that other stuff they tell you to do when recompiling.
I'm not sure how you are configging your kernel, make menuconfig offers a nice description of most options by hitting the question mark. These descriptions also include the exact name.o of the module you want to compile. Your best bet is to look up that name.o for your particular sound card, compile that as a module, then uncomment the appropriate line in rc.modules.
I have never found any other module-loading files than what Master C mentions.. of coarse you can do a grep -r somename /etc to find all mentions of somename in your startup files.
Also, make sure you don't have sound already and don't know it I had to add a couple lines in rc.local so that all users could get sound and control the volume:
chmod 666 /dev/dsp
chmod 666 /dev/mixer
thanks LinFreak! i've had these annoying messages at bootup since i installed slack 9, but since they didn't affect anything i figured i'd just leave it til i knew more about the kernel etc. that simple addition to blacklist sent them straight to hell!
i just noticed today that rc.inet2 is modprobing my network card... as a result it gets loaded several times... not hard to solve, but isn't this somehow working against the simplicity of slackware?
EDIT: just checked, and i must have been hallucinating or something, cos i can't find the line now.
Last edited by BigBadPenguin; 08-28-2003 at 07:26 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.