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.
Actually you don't need to recompile the kernel
to have your mouse working:
I've just followed the hints from the documentation (changes & hints)
and my mouse is working fine now with the default generic-2.6.24.5-smp Patrick kernel.
In my case what I had to do was to remove the rc.modules.bak files that were in /etc/rc.d
Also I noticed that a lot of kernel options can be triggered from /etc/rc.d/rc.modules-2.6.21.5-smp
So, once more,
sorry XD
it appears that the official slackware kernel is flawless after all XD
There are two good options, actually. One is to use rc.modules.local, but you would need to include the top section of the stock rc.modules (the section from the top that updates module dependencies) at the top of the custom rc.modules.local. For example, here's mine (yes, I use this method):
That's probably a bit of overkill now with 2.6.24.x, as it's supposed to load most acpi modules automatically, so just call me crufty.
The easier way to do it is with rc.netdevice though. The original purpose of that script (which will probably not exist on a fresh installation) was to load networking modules early in the boot process so that the network scripts could finish successfully. Since udev came along though, that's just not needed anymore. However, support for the file is there, and since it's run early in the boot process if it exists, it's a great place to sneak other non-network-related modules in if you need them loaded.
* I have to credit Pat with hammering a clue at me on this one - while it's obvious to me now, I'd never considered rc.netdevice for this purpose before.
I had this very same problem myself. I am very new to this, Slackware 12.0 being my first taste of Slackware. What I did was un comment out the line loading psmouse in /etc/rc.d/rc.modules-2.6.24.5-smp. I did notice the psmouse file that set options for psmouse and the file said this was a better place to handle that than rc.modules but nowhere was the module actually being loaded on my system. I probably did not do the right things in upgrading and I'm sure my solution probably isn't the "right" one, but it works...
I had this very same problem myself. I am very new to this, Slackware 12.0 being my first taste of Slackware. What I did was un comment out the line loading psmouse in /etc/rc.d/rc.modules-2.6.24.5-smp. I did notice the psmouse file that set options for psmouse and the file said this was a better place to handle that than rc.modules but nowhere was the module actually being loaded on my system. I probably did not do the right things in upgrading and I'm sure my solution probably isn't the "right" one, but it works...
Your solution is more of a hack than the proper way of doing things. You should comment that line out (thus restoring it to its original form) and follow rworkman's advice -- see the CHANGES_AND_HINTS.TXT file included with your Slackware install CD/DVD (or at your favourite mirror). If you leave a backup of /etc/modprobe.d/blacklist from your Slackware 12.0 installation in addition to the new /etc/modprobe.d/blacklist file from the 12.1 upgrade, both files will be checked and the psmouse module will be blacklisted (ie it will not be loaded). If there is a /etc/modprobe.d/blacklist.new file, you should overwrite /etc/modprobe.d/blacklist with this file (and I mean overwrite -- again, if you leave a backup of the original file in that directory, it'll still get checked). If that's the case you should also check other .new files in /etc to make sure you merged them all (a crucial part of upgrading from 12.0 to 12.1). If you already merged/overwrote the .new files (including the one in /etc/modprobe.d), then you should make sure to delete the backup of the blacklist file from 12.0.
Read all of the documentation before (and after) you upgrade -- most of the common problems are covered in there.
If you already merged/overwrote the .new files (including the one in /etc/modprobe.d), then you should make sure to delete the backup of the blacklist file from 12.0.
Read all of the documentation before (and after) you upgrade -- most of the common problems are covered in there.
To be honest I didn't even look at the documentation....oops. When I noticed my mouse wasn't working I started poking around in rc.modules and noticed that line commented out and that was that pretty much.:E
To be honest I didn't even look at the documentation....oops. When I noticed my mouse wasn't working I started poking around in rc.modules and noticed that line commented out and that was that pretty much.:E
rc.modules is not the only way modules get loaded. Many of them get loaded automatically by udev.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
.
