Section "ServerFlags"
Option "AutoAddDevices" "off"
Option "AllowEmptyInput" "on"
EndSection
Section "InputDevice"
Identifier "Mouse"
Driver "evdev"
Option "CorePointer"
#Option "Device" "/dev/input/event7"
# Using udev rule instead
Option "Device" "/dev/mouse-nano"
Option "Name" "Mouse"
Option "Buttons" "9"
Option "WHEELRelativeAxisButtons" "4 5"
Option "HWHEELRelativeAxisButtons" "7 6"
Option "AccelerationScheme" "lightweight"
Option "AccelerationProfileAveraging" "False"
Option "Softening" "False"
Option "Protocol" "ExplorerPS/2"
Option "Resolution" "800"
Option "SampleRate" "500"
Option "SendCoreEvents" "true"
Option "Sensitivity" "0.01"
Option "Emulate3Buttons" "False"
EndSection
Section "ServerLayout"
... blah blah
InputDevice "Mouse"
EndSection
And my udev rule in /etc/udev/rules.d/91-local.rules
# Logitech wireless mouse
# Has 2 devices: mouse, and wireless USB - impossible to tell apart!
# udevadm info -a --name /dev/input/event7 | less
# This is too simplistic, because there are 2 devices:
# KERNELS=="input*", ATTRS{name}=="Logitech USB Receiver", SYMLINK+="mouse-nano"
# So tie it to the physical USB socket:
NAME=="input/event*", SUBSYSTEMS=="input", ATTRS{phys}=="usb-0000:00:1d.1-1/input0", SYMLINK+="mouse-nano"
A bit of evidence from xinput:
$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Mouse id=7 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Keyboard id=6 [slave keyboard (3)]
Edit: Hopefully clarified that users might not have to create/edit their xorg.conf, if xinput --list shows something sensible already.
Edit2: Switched to udev rule, from using /dev/input/event7
Now to figure out what is actually controlling mouse sensitivity.
Additionally, the middle thinkpad button is now magically working to scroll (something I had not been able to get to do before). Fantastic!
]]>[root@arch david]# xinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Macintosh mouse button emulation id=7 [slave pointer (2)]
⎜ ↳ PS/2 Generic Mouse id=8 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=6 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=9 [slave keyboard (3)]
↳ Sleep Button id=10 [slave keyboard (3)]
↳ Video Bus id=11 [slave keyboard (3)]
↳ Power Button id=12 [slave keyboard (3)]
[root@arch david]# xinput set-ptr-feedback 2 0 84 100
unable to find device 2
[root@arch david]# xinput set-ptr-feedback 4 0 84 100
[root@arch david]# xinput set-ptr-feedback 4 100 100 100
[root@arch david]# xinput set-ptr-feedback 7 100 100 100
[root@arch david]# xinput set-ptr-feedback 8 100 100 100
[root@arch david]# xinput set-ptr-feedback 4 800 800 800
[root@arch david]# xinput set-ptr-feedback 8 800 800 800
[root@arch david]#
I think it is a little faster.....? I may just be imagining it though (probably). Either way its still not going as fast as I would like it to. Is it possible I'm missing some sort of driver to recognize the specific Thinkpad device?
http://www.thinkwiki.org/wiki/How_to_co … TrackPoint
Looking at this article it looks like the trackpoint is actually recognized as a specific device to X (or they just named it as such?), not as vague as the names I have. I can't quite make sense of this page though.... :\
Thanks for all the help, sorry this is taking so long. I had it perfect at one point, I don't understand why it would have suddenly stopped working.
]]>you aren't actually referring to the device, because the device is called Mouse0, not Mouse
what Misfit138 should work as well.
]]>xinput list
And substitute the device id number for Mouse.
So instead of
xinput set-ptr-feedback Mouse 0 84 100
You'd do
xinput set-ptr-feedback 9 0 84 100
or whatever id# your trackpoint happens to be.
xinput set-ptr-feedback 9 0 25 10
^Works for my Panasonic Toughbook touchpad.
]]>brebs wrote:Sometimes it seems like Linux has stupidity designed into it
I don't think it's that linux has stupidy built into. I think that it's more like developers have different ideas of how they want things to work. It would be highly advantages that a game or an application could control the sensitivity, I'm sure some games aren't designed to set it back.
instead of running it each time before log in you should be able to make a simple script that runs the command. I'm am not good at scripting by any means, but I'm working on it. Something like making making an alias to "xinit" or "startx" in ur bash rc to point to your script which has the command and then "xinit" after it.
I did some searching for some alternatives:
http://linux.die.net/man/4/mouse-driver
things that look worth while:
Option SampleRate integer
Sets the number of motion/button events the mouse sends per second. Setting this is only supported for some mice, including some Logitech mice and some PS/2 mice on some platforms. Default: whatever the mouse is already set to.
Option Resolution integer
Sets the resolution of the device in counts per inch. Setting this is only supported for some mice, including some PS/2 mice on some platforms. Default: whatever the mouse is already set to.possibly baud rate, but I think that will just make the mouse more smooth.
Thanks for all the info Matt, I'm going to give that a go if I can't figure out xinput. On that topic, whenever I try to enter "xinput set-ptr-feedback Mouse 0 84 100" into the terminal I get a "unable to find device Mouse".
Here is what my xorg.conf looks like (the input device sections at least):
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
No matter what I try I get a "device not found". Isnt the identifier "Mouse0" right there? Shouldn't that work? I'm quite confused. Is it because its not actually a mouse, but the thinkpad trackpoint?
]]>Sometimes it seems like Linux has stupidity designed into it
I don't think it's that linux has stupidy built into. I think that it's more like developers have different ideas of how they want things to work. It would be highly advantages that a game or an application could control the sensitivity, I'm sure some games aren't designed to set it back.
instead of running it each time before log in you should be able to make a simple script that runs the command. I'm am not good at scripting by any means, but I'm working on it. Something like making making an alias to "xinit" or "startx" in ur bash rc to point to your script which has the command and then "xinit" after it.
I did some searching for some alternatives:
http://linux.die.net/man/4/mouse-driver
things that look worth while:
Option SampleRate integer
Sets the number of motion/button events the mouse sends per second. Setting this is only supported for some mice, including some Logitech mice and some PS/2 mice on some platforms. Default: whatever the mouse is already set to.
Option Resolution integer
Sets the resolution of the device in counts per inch. Setting this is only supported for some mice, including some PS/2 mice on some platforms. Default: whatever the mouse is already set to.
possibly baud rate, but I think that will just make the mouse more smooth.
]]>It also needs to be rerun when some games exit, because the games reset the mouse speed. Surprisingly, this didn't happen with "mouse" rather than "evdev" as the mouse driver.
Sometimes it seems like Linux has stupidity designed into it
]]>That xinput line doesn't go in xorg.conf, you run it in a terminal.
Oh duh, forgot to have my coffee this morning. I'll try this once I get back home.
Assuming it does would, would that effect be permanent? Or would I have to put it in some conf somewhere?
]]>Mouse handling is a confusing mess. See xorg wiki. I use:
xinput set-ptr-feedback Mouse 0 84 100
That's with Identifier "Mouse" in xorg.conf
Probably a stupid question, but how exactly does that go in xorg.conf? The way I had put it in crashes my X server.
And thanks Matt, let me know if you find anything.
]]>xinput set-ptr-feedback Mouse 0 84 100
That's with Identifier "Mouse" in xorg.conf
]]>hmm, I think this may have something to do with your xorg.conf, as it's the x server that really tracks the mouse. So go into /etc/X11/xorg.conf and try adding this to the proper device.
Option "MinSpeed" "0.10" # speed factor for low movement
Option "MaxSpeed" "0.80" # maximum speed factor for fast movement
Option "AccelFactor" "0.0040" # acceleration factor for normal movementsthe device will be listed in the identifier section. Note, I did get this from my synaptics touch pad, but it might be worth a try to "override" what may be causing the problem.
Hmm, I tried that and now my xorg.conf looks like such.
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
Option "MinSpeed" "2.00" # speed factor for low movement
Option "MaxSpeed" "3.00" # maximum speed factor for fast movement
Option "AccelFactor" "0.40" # acceleration factor for normal
I put in 'big' numbers because it didn't seem to be doing what I wanted it too. It still doesn't seem to be moving how I want it to (nor am I even 100% sure it did anything).
I like my mouse (or the red trackpoint in this case) really sensitive. Super, fly across the screen sensitive. I am unsure why the latest kernel update would have nullified the earlier fix, but I am direly in search of a fix.
]]>Option "MinSpeed" "0.10" # speed factor for low movement
Option "MaxSpeed" "0.80" # maximum speed factor for fast movement
Option "AccelFactor" "0.0040" # acceleration factor for normal movements
the device will be listed in the identifier section. Note, I did get this from my synaptics touch pad, but it might be worth a try to "override" what may be causing the problem.
]]>