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.
I hate this message. I have my mouse driver build into the kernel and it is working
fine. How to find what is trying to load it ?
I want to get rid of this message.
Not sure what distribution you have. In Slackware we have a file called rc.modules (in /etc/rc.d directory) were the modprobe commands are kept. There is a line in there that reads:
# Mouse input:
#/sbin/modprobe mousedev
In mine it's commented out (#), in yours I'd guess it's not? Perhaps in your distro it's in another file rc.? or modules.conf, etc...
Maybe the modprobe is being done somewhere else? You could use the find utility to search file CONTENTS in the /etc directory fornay occurence of mousedev.
This stuff is annoying isn't it? I've had the same sort of problem for other devices (not the mouse) for something like a sound card that didn't even exist in my system. I finally went into /lib/modules/2.4.22/kernel/drivers and deleted the offensive module. I also edited the /lib/modules/2.4.22/modules.dep file and removed the references to the module. This worked, but hey I'm not sure I should recommend it to you as who knows what I did? On the other hand it didn't seem to hurt anything! If you do it back up the module and modules.dep files first...
I've used kfind in KDE but I'm sure that there is something similar in gnome if you're using that. There are different tabs for searching: location, contents, properties. On the contents tab you can enter the actual file contents you are looking for (mousdev).
Make sure you put /etc in the location tab or it could be a long search!
I get this message too and reading this wanted me to get rid of it as well. Did some detective work and figured it out. Well for me it happens right after dhcpcd is run and before rpc.portmap is run. Dhcp is invoked by rc.inet1 and portmap is invoked by rc.portmap which is run from rc.inet2. Looking at rc.M the only thing that falls in between rc.inet1 and rc.inet2 is rc.hotplug, so rc.hotplug is our culprit.
What you want to do is add a line containing only mousedev to /etc/hotplug/blacklist
Reboot and it should work. Yep, so much nicer to boot and not see that nagging message.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.