Making Mouse Wheels Work w/ a KVM?
Elvii asks: "My mouse wheel doesn't want to work through my KVM. It doesn't work in X11 under Linux (Debian 3.0, kernel 2.4.20), but it works in Windows on same machine, through same KVM, so that tells me it's a protocol or driver issue , which is beyond me. I have no other OS's to test on, although I read online that FreeBSD can handle the mouse wheel in this type of setup. When I set the mouse type to IMPS/2, it just twitches in corner and randomly clicks. Anyone know if it's a kernel issue or an X11 issue? I've googled and found nothing of real use there - just that some KVMs work and some don't. Plain PS/2 works but I want my wheel too." The kicker is that when the mouse is plugged directly to the machine, the mouse wheel works just fine! Has anyone else experienced the problem? What did you do to fix it?
Okey, what is this? Isn't this the sort of question you usually ask in a discussion forum or even IRC? I don't see why someone whould make a slashdot article over it. I did a search on google and found many resources for how to fix this, take a look here, here and here. And if you want to browse the results yourself, here.
I've googled and found nothing of real use there.
I don't have a device like this myself, but from the results I got I'll say it looks quite useful.
Note to self: get smarter troll to guard door.
There are two things to check, first turn off gpm. It's never done anything but give me grief in all the time I've ever seen turned on. I know that this will solve problems on several different KVM's I have. I know on one of the KVM's, it fixed all my problems so I could use the IMPS driver without doing the second fix.
Second, is that something is completely screwed about XFree86 of handling the PS2 mice, you can switch to a serial mouse, but no wheel then. The way to fix the problem, is to get XFree86 to resync/reset with the mouse. After switching from once machine to the next, immediately switch to a virtual console, then back to X, and the PS2 drivers will resync/reset/"do the magic to make it go". I've got no idea what the problem is, or why switching consoles works, but on the various Belkin Switches I've seen that is the fix that works best.
Kirby
Most modern KVM switches will send a signal that tells the machine that it has a keyboard and mouse plugged in even if you're actually switched to another machine. My guess is that the KMS' pseudo-mouse is just a basic 2-button, so Linux doesn't recognize that it's actually a wheel mouse that's plugged in. Have you tried booting the Linux box completely while switched to it (meaning you don't switch to another box to do something else while it comes up)? That might make a difference.
/etc might not be the one being used), and/or you might try installing imwheel, which is supposed to fix some mouse wheel in Linux issues. I would probably do both.
Also, check for the ZAxisMapping option in your X11Config (you may have more than one, and the one in
Under capitalism man exploits man. Under communism it's the other way around.
I have no problem at all with my Logitech wireless optical wheel mouse running through my Belkin 4-port switch.
Did you bother with the Linksys support site? Perhaps this is the problem you are having.
The Linksys product description says, "Because they donâ(TM)t use software, the ProConnect Compact KVM Switches are compatible with all major desktop and note-book computers." One might read into that statement that the switch is not altering the electrical signals and that the switch is compatible with all mice. Sadly, that appears not to be the case and although a known limitation they don't mention it in the description. I'd send it back and buy from a company that makes KVM switches that work properly.
~~~~~~~
"You are not remembered for doing what is expected of you." - Atul Chitnis