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.
how exactly does /etc/rc.d/rc.modules fit into things? when it's run at startup it consults /lib/modules/$REALEASE/modules.dep (that's what it says anyway), and loads any modules listed there? is that correct?
i'm asking because i'm trying to clean out my lsmod list. i've got some stuff i don't need, like agpgart for instance. i found that in rc.modules and commented out the line, so that's ok. but lsmod lists a bunch of OSS modules, and i'm pretty sure i don't need those. they're not listed in rc.modules though...in fact, the only uncommented line is apm. so i can't clean any more out by editing rc.modules.
now i've looked at /lib/modules/2.4.26/modules.dep and it's a very long file. there are a lot of modules listed that i don't recognize. as i understand it, modules.dep is created when you compile your kernel (make modules, make modules install), so i'm not even sure i should be editing it in the first place (i haven't touched it yet). is that the way to remove unwanted modules? or do i need to generate a new modules.dep file by recompiling the kernel?
i think those OSS modules are loaded by hotplug.
if you put them on the blacklist ( /etc/hotplug/blacklist : just add the names to the list )
then they won't load anymore on boot.
so i removed ide-scsi and agpgart from rc.modules, i don't know what uhci is, or usbstorage, but it looks like those two and usbcore are somehow all connected. i have a usb jumpdrive which i'd like to keep using, so i'll probably leave them until i can verify exactly what they do. you can see though what i meant about sound modules. they're not all OSS like i thought they were, but easily 3/4 of all those entries are sound modules....i must be able to get rid of some of those, right?
Distribution: Slackware, Windows, FreeBSD, OpenBSD, Mac OS X
Posts: 5,296
Rep:
Alsa uses different modules for different devices and features. I'm not 100% certain that you need all of them, but, if all of your sound functions are working I'd leave them alone. On the other hand, if you don't break anything, you won't know how to fix anything.
good luck.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.