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.
Hello,
As a "kernel of the week" club member I'm getting tired of rebuilding all my modules before each time I reboot.
I tried dkms, and I found that it does its job if I treat it respectfully (e.g. I run "dkms unbuild" instead of deleting modules from /lib/modules/).
Initially I thought that running "dkms autoinstall" before the depmod in rc.modules was a good idea because I could avoid to run depmod twice, but then I realized that I would also run gcc during rc.S and before all filesystems are fully mounted.
One of the modules I need is for a rtl8821cu wifi dongle, so dkms should ideally go in rc.M, before rc.inet1. The sweet spot I found is just after dmesg in rc.M, because
- dkms doesn't use syslog (and can be run before it)
- it can compile modules for pcmcia too.
Can you please include my modification to rc.M (see attachment)?
In case you (unlikely) wish to add dkms to Slackware 15.0 here is the SlackBuild too (basically a single bash script, 40K compressed, 140K uncompressed).
Thank you,
regards
Initially I thought that running "dkms autoinstall" before the depmod in rc.modules was a good idea because I could avoid to run depmod twice, but then I realized that I would also run gcc during rc.S and before all filesystems are fully mounted.
One of the modules I need is for a rtl8821cu wifi dongle, so dkms should ideally go in rc.M, before rc.inet1. The sweet spot I found is just after dmesg in rc.M, because
- dkms doesn't use syslog (and can be run before it)
- it can compile modules for pcmcia too.
Can you please include my modification to rc.M (see attachment)?
Is there a reason running dkms from rc.modules.local doesn't work for you, as outlined here?
I use dkms for the nvidia driver (using their .run installer) and system76-io-dkms, and it works great for me.
Is there a reason running dkms from rc.modules.local doesn't work for you, as outlined here?
rc.modules is run very early in rc.S, even before the "Mounting non-root local filesystems:" message.
/usr (or any important mountpoint) may not be mounted yet, so dkms would not find any compiler.
You're right (but I must confess that in the past I secretly kept /usr/src on a rotational hd instead of buying a bigger ssd).
The truth is that I just feel more comfortable to run gcc in runlevel 3 and above.
My ideal rc.S should be a fast, resilient, simple script whose purpose is just to put together the root filesystem, compiling modules is way out of its scope.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
