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.
I have a wireless logitech mouse that works well in Slackware, but is hypersensitive - ie. just one millimetre moving the mouse makes it travel "all over" the screen.
I've tried playing with the
Code:
Option "Resolution" "500"
settings in xorg.conf, but I can't really say it makes a difference.
I also tried playing with
Code:
xset m 1 30
for setting things there, but these options only seem to control the acceleration, and not the overall sensitivity of the mouse.
In other words, I'd like the mouse to travel a shorter pixel-distance on the screen for every millimetre I move it on my mousepad.
edit: some mice have a sensitivity that seems to only be able to change via dinking with the hardware somehow. happened to me once but i can't remember the details.
Last edited by LightningCrash; 06-21-2007 at 11:22 AM.
This only controls the acceleration (ie how many pixels to travel before how much acceleration), and as such does not address the problem.
The challenge is that the mouse is too sensitive even before acceleration. When playing around to turn acceleration on, things go even more bananas.
I tried playing with the controlling files under
/sys/devices/platform/i8042/serio0/subsystem/drivers/psmouse/serio1
such as rate and resolution, by setting these values to 200 (rather than default 100). (echo -n 200 > resolution) - this makes it less bad, but still not good.
Are there further parameters possible to pass to the psmouse module (other than those controlled by the sysfs files described above) ?
Thanks for the pointers - they certainly seem to have the right approach.
I added this to lilo.conf to control the usbhid interface:
Code:
append = "usbhid.mousepoll=5"
However, this seems to turn the mouse into some sort of Frankenstein, with a life of its own.
The mouse and keyboard only says "Logitech Cordless Mouse / Logitech Cordless Keyboard" without further specification - it's rather old.
I suspect this might boil down to Linux being more strict on its hardware than Windows, but it bothers me that this detail of the system actually works better under Windows...
I also tried to play with other numbers - having mousepoll=2 (causing the resolution to be 500), was clearly way too much, but 5 (200, twice the default) seems to be the best compromise.
It's better, but still not 100%. Whenever my hands start being as jerky as the mouse currently is, I'm hopefully very very old and wise... ;-)
The value "event5" comes from your /proc/bus/input/devices.
I have also seen Xorg crash in a similar way when I tried using the evdev driver with using the Name option alone (different mouse in my case - Microsoft). Adding the "Device" option fixed it for me.
It sort of does the trick, as the scroll wheel works, but now the middle and right mousebutton are switched.
This seems to be an area of relatively poor documentation - any insight on how I get scroll and "paste" on middle button, and normal right-click on the right button?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.