Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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 recently installed Slackware 10.0 on my Dell Dimension 4400 (sysadmin at work doesn't want to use 10.1 for some reason), and I upgraded to kernel 2.6.7, from /testing on install cd #2.
Here's the problem: when I boot into 2.6.7 my mouse doesn't work in X (gnome). It doesn't work at all - no movement or anything. But when I boot into kernel 2.4.26 my mouse works fine!
As others on this list suggest I tried the different protocol options (Any, Microsoft, IMPS/2, PS/2) and tried changing "Device" to "/dev/psaux", although felt stupid doing this since /dev/mouse is a link to /dev/psaux.
I'm not sure where to look further since I' m a bit newbie to Linux and even more to Slackware.
That worked! (Actually I used modprobe instead of insmod but whatever ... )
Is there a way to automatically load the psmouse module at boot time instead of having to do it manually with modprobe? Or is it better to recompile the kernel?
That's a relief, thanks. I was beginning to wonder how bright my linux future looks if I couldn't even get the mouse to work! Thanks for your help.
But I do want to say ... the process of installing Slackware with 2.4.x then upgrading to 2.6.x was pretty annoying. The installer did a good job detecting my hardware, which explains why my mouse worked fine initially, but then my configuration went to hell with the upgrade. First I tried copying my .config file before building the 2.6 kernel, but when I ran make xconfig I got a huge list of errors regarding selections that didn't apply. I also tried make oldconfig but that didn't seem to be geared toward major upgrades (2.4 to 2.6) either. So I had to take a best guess with the configuration options. This of course was very tedious and way-too-bad considering that the installer had just done such a good job! Obviously I missed the psmouse option ...
So why hasn't Slackware released a version that gives you the option to install with 2.6.x in the first place?
Originally posted by lantern
But I do want to say ... the process of installing Slackware with 2.4.x then upgrading to 2.6.x was pretty annoying. The installer did a good job detecting my hardware, which explains why my mouse worked fine initially, but then my configuration went to hell with the upgrade. First I tried copying my .config file before building the 2.6 kernel, but when I ran make xconfig I got a huge list of errors regarding selections that didn't apply. I also tried make oldconfig but that didn't seem to be geared toward major upgrades (2.4 to 2.6) either. So I had to take a best guess with the configuration options. This of course was very tedious and way-too-bad considering that the installer had just done such a good job! Obviously I missed the psmouse option ...
Don't understand why you had issues with make oldconfig - I'm sure this is what I did and managed to get it working.
Aahhh - just re-read that quote of your post. Did you do a make mrproper ???. Best is always to clean up first. So after your initial problems with make xconfig, I would have tried make mrproper, copy .config, then make oldconfig, and answer the questions as they pop up.
I did try a /testing kernel,but it wouldn't fly. Easier to pull a current source tar and install it manually.
Quote:
So why hasn't Slackware released a version that gives you the option to install with 2.6.x in the first place?
I made a similar comment on first install a couple of weeks ago, and got the standard "what's so great about 2.6 ???" line.
No I missed that step ... maybe that was the problem.
Quote:
I made a similar comment on first install a couple of weeks ago, and got the standard "what's so great about 2.6 ???" line.
Yeah I've heard that too. I did the upgrade because I needed better support for my network card. The upgrade improved things but I'm still having some trouble with my NIC. Here's a thread I have going about that issue, in case anybody has advice. Maybe I should have started that thread in this forum anyways (instead of Linux - Networking).
Thanks.
Lantern
slackware comes with a prebuilt 2.6 kernel lookout in the testing directory
That's meant to be installed with installpkg, right? I don't get why the generic kernel would work if it's not configured for my hardware, but I'll give it a shot.
Originally posted by lantern That worked! (Actually I used modprobe instead of insmod but whatever ... )
Is there a way to automatically load the psmouse module at boot time instead of having to do it manually with modprobe? Or is it better to recompile the kernel?
Thanks masand.
you may put this in your /etc/rc.d/rc.local:
Code:
if `uname -r |grep 2.6 > /dev/null`; then
modprobe psmouse
fi
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.