| View previous topic :: View next topic |
| Author |
Message |
Rainor
n00b
Joined: 11 Mar 2005
Posts: 5
Location: Russia, Moscow
|
 Posted: Mon Aug 01, 2005 7:50 am Post subject: 2.6.12 & 500Hz |
 |
|
HI. I read topic, but didn't find answer.
I have kernel 2.6.12. As described in http://www.linux-gamers.net/modules/wfsection/article.php?articleid=62, i don't need to patch the kernel (is it right?  ). But when i try to set mousepoll=2 (with modprobe or echo) i don't fell difference (cat /proc/bus/usb/devices gives me ivl=10ms. As i understand, it's a bug). Re-pluging doesn't help 
Thx for reading my post |
|
| Back to top |
|
 |
krejler
Tux's lil' helper
Joined: 10 Nov 2003
Posts: 142
Location: Denmark
|
| Posted: Mon Aug 01, 2005 9:55 am Post subject: Re: 2.6.12 & 500Hz |
|
|
| Rainor wrote: | | HI. I read topic, but didn't find answer. |
Hi
That is correct.
| Rainor wrote: | | But when i try to set mousepoll=2 (with modprobe or echo) i don't fell difference (cat /proc/bus/usb/devices gives me ivl=10ms. As i understand, it's a bug). Re-pluging doesn't help |
No, it is not a bug. What you see in /proc/bus/usb/devices is the device descriptor -- what the device uses to present itself to the controller with. In earlier incarnations of the patch, I used to change the interval directly in the device descriptor, but since this was method discouraged by the reviewers when the patch was trying to get into the kernel, I changed the way it worked.
Have you tried echoing/using a quite high interval? Try something like 64, and see if you can slow it down that way. If that's the case, it is definately working, you just cannot feel it.
| Rainor wrote: | | Thx for reading my post |
No problem. Please report back with what you find out, or whatever problems you might encounter.
krejler |
|
| Back to top |
|
|
Rainor
n00b
Joined: 11 Mar 2005
Posts: 5
Location: Russia, Moscow
|
| Posted: Mon Aug 01, 2005 10:25 am Post subject: |
|
|
krejler
First of all, thx
| Quote: | | No, it is not a bug. What you see in /proc/bus/usb/devices is the device descriptor -- what the device uses to present itself to the controller with. In earlier incarnations of the patch, I used to change the interval directly in the device descriptor, but since this was method discouraged by the reviewers when the patch was trying to get into the kernel, I changed the way it worked. |
Oh, now i really understand.
| Quote: | | Have you tried echoing/using a quite high interval? Try something like 64, and see if you can slow it down that way. If that's the case, it is definately working, you just cannot feel it. |
Yep, when about interval is about 60 the aim in games is more accurate. But, as you said, i really cannot fell it.
And thanks for this staff |
|
| Back to top |
|
|
krejler
Tux's lil' helper
Joined: 10 Nov 2003
Posts: 142
Location: Denmark
|
| Posted: Mon Aug 01, 2005 10:32 am Post subject: |
|
|
| Rainor wrote: | krejler
First of all, thx
| Quote: | | No, it is not a bug. What you see in /proc/bus/usb/devices is the device descriptor -- what the device uses to present itself to the controller with. In earlier incarnations of the patch, I used to change the interval directly in the device descriptor, but since this was method discouraged by the reviewers when the patch was trying to get into the kernel, I changed the way it worked. |
Oh, now i really understand.
| Quote: | | Have you tried echoing/using a quite high interval? Try something like 64, and see if you can slow it down that way. If that's the case, it is definately working, you just cannot feel it. |
Yep, when about interval is about 60 the aim in games is more accurate. But, as you said, i really cannot fell it.
And thanks for this staff |
Hmm, something seems wrong. Are you saying that your mouse is perfectly precise and controllable, with the interval set to 64? If that is the case, could you please try to explain to me exactly how you are setting the interval, so I can see if I can spot any errors there.
Thanks |
|
| Back to top |
|
|
Rainor
n00b
Joined: 11 Mar 2005
Posts: 5
Location: Russia, Moscow
|
| Posted: Mon Aug 01, 2005 10:45 am Post subject: |
|
|
krejler
usbhid is build-in in kernel.
Executing 'echo 60 > /sys/module/usbhid/parameters/mousepoll', re-plugin mouse.
In The DE i can't feel difference, but in games (via cedega) pointing seems to be more slower & accurate (but not ideal, as in M$ Windows). |
|
| Back to top |
|
|
krejler
Tux's lil' helper
Joined: 10 Nov 2003
Posts: 142
Location: Denmark
|
| Posted: Mon Aug 01, 2005 10:52 am Post subject: |
|
|
| Rainor wrote: | krejler
usbhid is build-in in kernel.
Executing 'echo 60 > /sys/module/usbhid/parameters/mousepoll', re-plugin mouse.
In The DE i can't feel difference, but in games (via cedega) pointing seems to be more slower & accurate (but not ideal, as in M$ Windows). |
OK, just for a test, could you try to add the boot parameter "usbhid.mousepoll=<foo>", where foo is your wanted polling interval, to your bootloaders kernel commandline? For a start, try using 64. Then, after you've confirmed that your mouse is slow as hell, you could do the same thing, but use the polling interval you originally intended. Remember, lower is better.
If this doesn't work either, please, post on! 
Thanks |
|
| Back to top |
|
|
Rainor
n00b
Joined: 11 Mar 2005
Posts: 5
Location: Russia, Moscow
|
| Posted: Mon Aug 01, 2005 11:28 am Post subject: |
|
|
krejler
Sorry for long reply.
So, this boot option is working
I've tried three intervals: 0, 5, 64. On the high speed motions there is no difference. But on the low speed, '5' gives me really smooth motion.
In the games '64' & '5' is almost similar (strange thing ). '2' is the greatest one, i think, but the difference with '0' is not big (unlike '64' and similar). |
|
| Back to top |
|
|
krejler
Tux's lil' helper
Joined: 10 Nov 2003
Posts: 142
Location: Denmark
|
| Posted: Mon Aug 01, 2005 12:22 pm Post subject: |
|
|
| Rainor wrote: | krejler
Sorry for long reply.
So, this boot option is working
I've tried three intervals: 0, 5, 64. On the high speed motions there is no difference. But on the low speed, '5' gives me really smooth motion.
In the games '64' & '5' is almost similar (strange thing ). '2' is the greatest one, i think, but the difference with '0' is not big (unlike '64' and similar). |
Hi,
Good thing you got it working!
Also, 0 means the mouse default, or perhaps 'the last set value', but since you are using it as a boot parameter, it should mean the defalt of the mouse.
krejler |
|
| Back to top |
|
|
Rainor
n00b
Joined: 11 Mar 2005
Posts: 5
Location: Russia, Moscow
|
| Posted: Mon Aug 01, 2005 12:58 pm Post subject: |
|
|
| Thx for help, krejler! |
|
| Back to top |
|
|
Massimo B.
Veteran
Joined: 09 Feb 2005
Posts: 1771
Location: PB, Germany
|
| Posted: Tue Dec 19, 2006 10:27 pm Post subject: |
|
|
Which values can I set for mousepoll= ? What is appropriate? I haven't found a documentation about min/max values there.
My usb mouse on the old laptop is quite lazy sometimes and just makes some breaks under heavy load.
Maybe I could improve that by mousepoll?
_________________
HP ZBook Power 15.6" G8 i7-11800H|HP EliteDesk 800G1 i7-4790|HP Compaq Pro 6300 i7-3770 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gamers & Players
