Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
My boot process is taking about 40secs and 20secs of it was due to udev modprobing some modules in my system. These modules are driver modules which the kernel had already probed and loaded on boot.
I tried to edit modprobe.conf to 'install ABC /bin/true' to have it hopefully skip modprobing these modules, but it still waits for 20 secs before saying that the module is not found.
I even tried blacklisting using modprobe.d/blacklist, but it still does not skip it.
How do I resolve this problem? By the way, these modules are not compiled into the kernel as modules, but are actually linked in.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,588
Rep:
I'm not sure I understand. Normally modules are loaded from /etc/rc.d/rc<#>.d where <#> is the number of the runlevel and consists of links to /etc/rc.d (or some such directory structure). Simply deleting the links for your runlevel should do the trick -- or just rename the proper directory.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.