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.
Did you skip the "make modules_install" step? Sounds like it. just go to the kernel source directory and run the command. If it's already been compiled it should go ahead and install the modules.
I'm wondering, am I barking up the wrong tree here? If I compile everyting into the kernel directly (which I tend to do) and not as modules, then will I see anything in the /lib/modules/2.6.18.3/kernel folder?
To get a list of compiled modules that should be under your /lib/modules/2.6.18.3 directory, run the following command:
Code:
grep -i '=M' /usr/src/linux-2.6.18.3/.config
To see a list of any kernel modules in that dir:
Code:
find /lib/modules/2.6.18.3 -type f -name '*.ko'
To get a count of how many modules are in there:
Code:
find /lib/modules/2.6.18.3 -type f -name '*.ko' | wc -l
I have 1583 kernel modules shown from running the previous command.
Of course, if the first command doesn't show any compile options selected as modules, then it makes sense that the directory structure was created by 'make modules_install', but no actual modules were placed there.
To get a list of compiled modules that should be under your /lib/modules/2.6.18.3 directory, run the following command:
Code:
grep -i '=M' /usr/src/linux-2.6.18.3/.config
To see a list of any kernel modules in that dir:
Code:
find /lib/modules/2.6.18.3 -type f -name '*.ko'
To get a count of how many modules are in there:
Code:
find /lib/modules/2.6.18.3 -type f -name '*.ko' | wc -l
I have 1583 kernel modules shown from running the previous command.
Of course, if the first command doesn't show any compile options selected as modules, then it makes sense that the directory structure was created by 'make modules_install', but no actual modules were placed there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.