How can I compare ALL mouse settings across distros A signal handling matter 3480

On 28 Apr 2005 08:57:28 -0700, SpamHog staggered into the Black Sun and said:

The most likely culprit is the kernel's PS-2 mouse driver. I'll bet that every distro you mentioned returns something different in the ouptut from "uname -a". So, see if you can get a pattern from those names. Maybe the 2.4 psmouse support works better than the 2.6 psmouse module on this particular KVM, or something. The X settings are probably not going to affect anything at all.

"grep -A7 -B2 mouseetc-X11-xorg.conf" should get you a report on what you've set the mouse up as in X. "pgrep gpm" will tell you if gpm is running--you usually don't need it, but you might have it. Finding the kernel parameters is a bit more difficult. In 2.4, the PS-2 mouse support had to be compiled in, and I don't think there was anything you could do to change PS-2 parameters.

In 2.6, you can build psmouse as a module, but there's nothing inproc orsys that corresponds to mouse settings. I think that if you're using 2.6, you'd want to add "psmouse.resetafter=3" to the kernel command line (if psmouse is built in) or "rmmod psmouse && modprobe psmouse resetafter=3" (if psmouse is a module). That'll make the kernel mouse driver reset the mouse after 3 bad packets, and it *might* have some effect on your KVM problem. Adjust to taste; picoboot-grub-menu.lst or picoetc-modules.conf to patently place psmouse parameters permanently, pardner.

If 10 people call you a horse, you might want to think about buying a saddle. HTH,

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong