[SOLVED] lsmod doesn't show sr_mod after loading it with modprobe
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
lsmod doesn't show sr_mod after loading it with modprobe
I'm running Slackware 14.1 (I just installed it actually after wrestling for what must've been more than 8 hours total with trying to USB install, to just DVD install but then figuring out booting from LVM...). I'm not that experienced with Linux, which is why I installed Slackware. I must say, I've learnt a LOT just installing it.
The problem is, I loaded sr_mod in modprobe (trying to get a USB DVD drive to work, actually; you might see another post on this if I can't figure that out either), and then did lsmod | grep sr_mod, but it isn't finding anything.
Here's roughly what I did (I redid the steps for the log):
~# lsmod | grep sr_mod
~# lsmod | grep snd
snd_hda_codec_hdmi 29622 1
snd_hda_codec_idt 37403 1
snd_hda_intel 34861 3
[truncated, I'm just showing that grepping this works]
~# modprobe sr_mod
~# lsmod | grep sr_mod [Still nothing]
~# modprobe sr_mod --first-time
modprobe: ERROR: could not insert 'sr_mod': Module already in kernel
I kept thinking that it was modprobe's fault, that it was somehow not loading, but not bothering to tell me, but as that last command shows, that doesn't seem to be the case.
I also tried searching /proc/modules, but it doesn't find it.
Any idea what's going on? I'm curious as to why lsmod didn't seem to refresh...or is the module not really loaded and modprobe thinks it is?
In the Slackware 14.1 kernel, the "sr" driver (SCSI CD-ROM) is compiled in to the kernel. It is not a loadable module. So lsmod won't list it. modprobe (apparently) sees the driver is already in the kernel and therefore does nothing.