Bugzilla – Bug 143583
Mouse Polling Support
Last modified: 2019-08-02 08:15:37 UTC
Since kernel 2.6.13 you have the possibilty to change the mouse polling support. Increasing the interval at which your mouse is polled for data, will make it more precise, since the driver is able to capture mouse movement much more often. It is mostly usefull for gamers. The polling interval decides how often an interrupt is fired for the mouse. Thus, a lower polling interval means a more precise mouse, but also increased interrupt overhead. It is therefore important to find a golden middleway, so you won't lose valuable CPU-time in gaining precision for your gaming. There are different methods to change it. A static will be modifying the modprobe.conf and add: options usbhid mousepoll=<intervall> The default interval is 10ms you can set it down to 2ms with this option. You can check the value by reading /sys/module/usbhid/parameters/mousepoll You can find more informations here: http://www.linux-gamers.net/modules/wfsection/article.php?articleid=62 Maybe it is something which could be supported by SaX2 too.
Hmm, I think SaX shouldn't modify the modprobe.conf ? and the on the fly setup said: ---snip-- There is, sort of. You can change the value the driver uses as the overriding-value, by writing to the file /sys/module/usbhid/parameters/mousepoll. However, to make use of this newly set value, you have to re-plug your mouse. Alternatively, you could also re-load the usbhid module with a new polling interval. This, of course, only works when usbhid is built as a module. It should also be noted, that things like X.org might not like to suddenly lose a driver while running. You have been warned. --snap--- this seems to be not very userfriendly as well, and yes X doesn't like to loose the input device ;)
any opinion about this one ? set to remind
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED. In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(
*** Bug 1143846 has been marked as a duplicate of this bug. ***