Mouse issues in Slack 10.2 using Kernel 2.6

john_d13 · 06-13-2006, 08:49 AM

Hey guys I know there are issues with the 2.6 test kernel in slack 10.2 when installing via cd. Keyboard works but usb/ball mouse dont work. Anyone know a workaround or if there is another 2.6 kernel that will fix this issue

Bruce Hill · 06-13-2006, 09:51 AM

You might try running "mouseconfig" as root and selecting "usb USB connected mouse" -- that's what I have to do with the default Slackware-2.4 kernels.

Other than that, I'd need to know a good bit more information...

john_d13 · 06-14-2006, 02:31 PM

I will try that,

Just wondering if anyone had issues with mouse when upgrading from 2.4 to 2.6

also where can I download the latest 2.6 kernel?

gbonvehi · 06-14-2006, 02:35 PM

You've to install 2.6 kernel modules located on CD 2, that will add support for a lot of stuff that's supported as modules, including usb support.

john_d13 · 06-14-2006, 02:36 PM

I did,,, is it named something like 26test ? if so, there are mouse issues with it, and its a knows issue with slack

Bruce Hill · 06-14-2006, 09:50 PM

I know a man, quite well versed in Slackware, who runs Pat's 2.6 kernels and his USB mouse works. Why don't you post the output of "lsmod" and "/sbin/lsusb" and let us take a peek at what you got.

The latest Linux 2.6 kernel is always here.

gbonvehi · 06-15-2006, 12:21 PM

It's a very well known "issue":
http://www.linuxquestions.org/questi...d.php?t=380890
So known, it's stated on RELEASE_NOTES: http://mirror.switch.ch/ftp/mirror/s.../RELEASE_NOTES

Another thing you may want to try, if you already installed the modules as you said, is to point the mouse device in /etc/X11/xorg.conf to /dev/input/mice instead of /dev/mouse (or /dev/psaux).

Bruce Hill · 06-15-2006, 06:50 PM

gbonvehi,

I'm a bit slow here -- you're saying the "issue" is that someone who doesn't read Pat's Release Notes doesn't properly install his 2.6 testing kernels and ends up without modules?

cwwilson721 · 06-15-2006, 07:07 PM

Quote:

Originally Posted by john_d13

I did,,, is it named something like 26test ? if so, there are mouse issues with it, and its a knows issue with slack

That's a new one to me. My USB mouse works fine, and I always start with test26.s on my 10.2 installs.

Can you post supporting info on this?

Or is the 'issue' not installing the kernel modules with test26.s?

If you read the forum, we are very 'slack' about everybodys opinions here, but you do have to back up your conclusions....

Franklin · 06-15-2006, 07:55 PM

I'm running -current with 2.6.16.20 (Pat's version) and my usb mouse works.

My xorg.conf mouse section:

Code:

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"
    Option      "Protocol"           "IMPS/2"
    Option      "ZAxisMapping"       "4 5"
    Option      "Emulate3Buttons"    "true"
    Option      "Device"             "/dev/mouse"

EndSection

**comments removed

The only "odd" thing is that /dev/mouse is a symlink that points to /dev/psaux:

Code:

steve@peggyo:/dev$ ls -la mouse
lrwxrwxrwx 1 root root 5 2006-05-06 18:08 mouse -> psaux

I usually associate /dev/psaux with a ps2 mouse connection, not usb. Maybe it was always this way and I never noticed. Maybe it's because I don't run gpm. Perhaps if I set up gpm to run off a usb mouse the symlink would be different.

Sometimes if you have gpm running and it's associated with the wrong mouse type, you will end up with a non-functional mouse in X. chmod -x /dev/rc.d/rc.gpm to test this.

HTH

dugan · 06-16-2006, 03:18 AM

Use "lsmod" to check if the "psmouse" module been loaded.

I've used at least one distribution that didn't load that module (which you NEED to get mouse support with a 2.6 kernel) by default. Can't remember if it was Slackware.

john_d13 · 06-16-2006, 09:01 AM

thx for the replies,

well im using 2.4,, gonna be upgrading soon then ill post the lsmod's

any recommendations for a simple step by step 2.4 to 2.6 migration guide?

jimX86 · 06-16-2006, 09:10 AM

Quote:

Originally Posted by john_d13

any recommendations for a simple step by step 2.4 to 2.6 migration guide?

That's what they've been trying to tell you... the RELEASE_NOTES file on the first CD provides step by step instructions. That file will also point you in the right direction to another README on making an initrd.

Bruce Hill · 06-16-2006, 09:23 AM

Use Kwan Lowe's Kernel Rebuild Guide and compile a new kernel with source from Kernel.org -- learn how to do it the proper way, don't take shortcuts, and you'll be learning Linux. And also read Linus Torvald's README when you untar the kernel source. His instructions are invaluable.

In the process of learning how to build a kernel, you will learn about your hardware. You will learn how things work and interact. You will be learning one of the major things that separates this operating system from such as Windows and Mac OS -- you can rebuild and customize your kernel.

I build and repair computers, and in the process have compiled many different kernels for many different computers. I always get great satisfaction when I've learned the hardware well enough that I can boot the kernel, all the hardware and options from the kernel work, and there are no errors in /var/log/syslog after I login.

The greatest satisfaction of the back-breaking, lifelong process of learning Linux is that you are in control of your Personal Computer -- Linux has put the PC back into it for me.

cwwilson721 · 06-17-2006, 10:28 PM

To expand just a slight bit on what Chinaman said:

Don't be afraid to mess up. You learn from your mistakes. I have made/compiled 3 bad kernels this week alone...

And all of us here have learned many, many, many times.

The main thing to remember: It can be resolved. And after YOU fix it, you'll be jumping up and down ("Whee!! Yeah!!").