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!
I will be very thankful if someone tells me which script in slackware is responsible for loading the kernel modules. The /etc/rc.d/rc.modules script loads extra modules. which one loads the basic number of modules?
My problem is that I have the quickcam module loaded, but I have forgotten which file I modified to make it load at boot time.
Is it possible for the module to be loaded automatically, because of being directly compiled into the kernel?
I am running Slackware linux 10.2 with kernel 2.4.31.
I want to see which script actually loads the module and comment the
line in it that says "modprobe quickcam"
modules.conf is for alias and options of each module.
rc.modules is for auto load modules at boot time, they works together, and if you enable the autoload modules in kernel which is deault fo slackware, then you just need add the alias of your modules name and options in modules.conf, it will auto load at boot.
for each different options of each modules you can check out /usr/src/linux/Doc*/ and looking for your quickcam,
type dmesg |more or |grep quickcam to see the hardware has been detect by the module
I probably did not express myself correctly. I do not want the module to be loaded at boot time. This is an excerpt of /var/log/syslog:
Sep 10 20:45:17 marto insmod: insmod: a module named videodev already exists
Sep 10 20:45:17 marto insmod: insmod: a module named videodev already exists
Sep 10 20:45:17 marto insmod: insmod: insmod quickcam failed
Sep 10 20:45:17 marto insmod: insmod: insmod quickcam failed
It seems that somehow the module videodev is loaded twice; the module quickcam is not loaded, but my cam works.
I want the modules not to be loaded at boot time. The problem is that I do not know which script loads them. I want to comment the lines "modprobe videodev" and "modprobe quickcam", putting a hashmark "#" in front of them.
I see that the message comes from insmod, but cpuld not find the script.
Here is the output of "insmod quickcam":
Using /lib/modules/2.4.31/misc/quickcam.o
insmod: a module named quickcam already exists
I searched /etc, /usr/bin, /usr/sbin/,/usr/local with:
grep -r "qickcam" *
but there was no result. I wonder what causes the module to get loaded? I think I have edited some file to make these modules load( quickcam and videodev) but I forgotten which . Probably I should reinstall to start clean.
probably this is some file, executed at startup. I checked .profile as well, but there no such command there either. I checked it because it seems that grep does not check hidden files.
If you're not loading it with modprobe, insmod or a alias then it's probably being loaded by hotplug
If it's loaded by hotplug maybe you removed the modules from hotplug's blacklist in /etc/hotplug/blacklist
If you're not loading it with modprobe, insmod or a alias then it's probably being loaded by hotplug
If it's loaded by hotplug maybe you removed the modules from hotplug's blacklist in /etc/hotplug/blacklist
yeah, it may be a usb devices, need more detail of your quickcam hardware, and plus, the slack default modules is auto loaded, for example, cups will auto load lp and which kernel will load parport through rc.modules file; and NIC can be load through modules.conf, etc.......... everything is customized.
If it's directly compiled into the kernel I can't help you with that. If you are sure it's a module that's loaded on bootup and you certainly cannot find where it's being loaded then you could probably poke around in your /lib/modules/$(uname -r)/kernel folder and try to find it. If it's not in there then try looking through the modules alias file
and see for what .ko file quickcam is an alias. If you find it then you can move it out of the /lib directory and reboot.
If none of that works then I don't know.
Good luck.
EDIT: Actually now that I've done some poking around maybe those directions I gave would only work for a 2.6 kernel. I've done it quite a few times with a 2.6 and had no problems whatsoever. Give it a shot anyway I guess and if you're at all successful but it complains when it boots then just put the file back.
The problem is that I get the following error messages in syslog:
Sep 12 19:39:26 marto insmod: insmod: a module named videodev already exists
Sep 12 19:39:26 marto insmod: insmod: insmod quickcam failed
Sep 12 19:39:26 marto insmod: insmod: a module named videodev already exists
Sep 12 19:39:26 marto insmod: insmod: insmod quickcam failedSep 12 19:39:26 marto insmod: insmod: a module named videodev already exists
Sep 12 19:39:26 marto insmod: insmod: insmod quickcam failed
Sep 12 19:39:26 marto insmod: insmod: a module named videodev already exists
Sep 12 19:39:26 marto insmod: insmod: insmod quickcam failed
I reinstalled Slackware and installed the quickcam package (I have compiled as a Slackware package form binary source). This is what "lsmod | grep quickcam" says:
I have not edited any files to make the modules load and I have no idea why it says videodev is already loaded and why it complains about not being able to load the quickcam module, since it is actually loaded?
So long as I have read the documentation for the quickcam driver
, it is loaded by hotplug. But why I get these errors? My webcam works ok despite them.
I would be thankful if someone could offer some explanation. I previously thought that some time ago I have edited some conf files and somehow made the modules load twice. However, now I come out of a completely clean installation and the same error occurs in syslog after I install the driver and reboot.
Thank you very much in advance.
P.S. Is it possible that the fact that the driver is installed causes the the module to be loaded automatically at startup with videodev, and then because my webcam is constantly plugged in, hotplug attempts loads the modules for a second time?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.