This is also a short udev tutorial.
I often work on my laptop, sometimes with a USB mouse plugged (in this case a Logitech G9). On the laptop’s touchpad I appreciate mouse acceleration, but on the USB mouse I cannot stand it. Is there an easy way to fix this in Linux, automatically? Depends – on whether you find udev easy to work with or not.
Brief overview of the steps below:
- Step 1: Change the mouse speed manually with xinput
- Step 2: Create a symlink automatically whenever the mouse is plugged using a simple udev rule
- Step 3: Run a script when the mouse is (un)plugged to change the acceleration
What will happen at the end:
- You plug in the mouse
- udev receives a «mouse plugged» event and looks for a suitable rule to execute
- Our rule tells udev to run a script that changes the mouse acceleration
Step 1: Testing without udev
At first it is important to ensure that the commands to change the mouse acceleration actually work. This is done with
(you may need to install it first) as described on askubuntu.com. The following command sets the mouse acceleration to 1/1 which means no acceleration.
In my case the Logitech G9 reports with two entries in the xinput list, and changing only one of them does not have any effect. If your USB mouse reports with two entries as well, make sure you change the mouse acceleration for both of them too.
Mouse acceleration should be off now (or, more general, the way you want it – you can also change the mouse speed and various other parameters, see the xinput manpage for this). If it is still on,
xset m 0
Step 2: Recognizing the USB mouse with udev
To get an idea of what kind of events udev receives, run
in a terminal and see what happens when you plug/unplug an USB mouse or USB stick, change the screen brightness (on laptops), disable/enable wireless devices (with the little switch you often find on laptops). (Monitoring can be stopped with
udev can take actions when it receives an event, the most common one being to create a syslink in the
directory, used to always have the same device path to e.g. your personal USB stick. This is also useful for debugging. The action important in our case is running a custom command or script which will change the mouse acceleration.
Now we could just go on and create a udev rule that runs xinput – but this does not work out of the box. First, we need to write a script that gets the xinput id(s) for the mouse and runs xinput on them. Secondly, it has proven to be good practise to first check if the udev rule to match the device is correct in order to know, if a rule did not execute, whether it was a matching problem (wrong conditions to identify the device, so they did not match), a syntax error in the rule (like unterminated quotation marks), or a bug in the script.
Therefore the next small step is to let udev create a symbolic link in
to test the new rule. For this we have to find out a way to identify the device. The command
udevadm info -a -n name
provides the necessary information. The device name was
in my case, when unknown the path can be used as well; that’s the one printed in the terminal when having
running. (Not using the shortest entries proved to be a better choice since the parent device properties are listed as well.)
The information output then looks as follows (note the -p when using a path instead of a name for the device) – take the one where the product name appears:
To identify the device using either the serial or idVendor and idProduct looks like a good idea for the new udev rule (finally!), which goes to:
The number indicates the order in which udev rules are executed and can be chosen freely; see the other rules in this directory and
. The file must end with .rules or otherwise it will not work. Now one of those lines goes in there:
The first line will most certainly match only the one mouse that is plugged right now, the second line should match all mouses of the same type (e.g. all Logitech G9 mouses).
To test the rule, the udev daemon needs to be re-started with:
When unplugging and plugging the mouse now, there should be a new link called helloUsbMouse in
If not, re-check the matching conditions. reactivated.net provides detailled information about writing udev rules for all kinds of devices and also information on how udev works.
Step 3: Automatically setting the mouse acceleration with udev
Now we finally come to the point that runs xinput automatically when the mouse is plugged. This happens with the scripts listed below which should go to some
. A few words to them first:
- The first script (
mouse-accel-starter.sh) calls the second one in background which first waits for two seconds. This is because the mouse is not listed in
xinput listyet right when the rule is executed.
- The first script also disables the touchpad (this is just for fun, basically, but you also see whether the rule worked). If you do not use a synaptics touchpad you will want to remove those lines.
- The xinput settings only work in an X context. But they are not run e.g. from a terminal started in your desktop manager. So the environment must be passed on to them. This is at the moment hard-coded in the udev rule listed further down, but on most laptops there is not more than one X server running anyway. For gdm there is a solution which is described on archlinux.org
You may want to run this script manually to check if it really works with
(or $$directory_of_your_choice/mouse-accel-starter.sh 1). udev will not show any error message if the script fails.
Obviously you will have to adjust the device name to search for (which is Logitech in this case).
/etc/udev/rules.d/42-mouse-accel.rules: (Note that there is exactly one line per rule, no more and no less.)
attribute causes the rule to match only when the mouse is either plugged or removed. This allows to re-enable the touchpad when it is unplugged. Do not forget to change
to match your home directory.
udev is not actually complicated, it is just a little hard to debug. I hope this tutorial gave a few tips on how to avoid, or find, them. If you search for alternative literature, additionally to the pages mentioned before, there is a short udev tutorial on the CCNY Robotics Lab Wiki. German speaking readers may appreciate the German article on the ubuntuusers wiki.
Currently unresolved problems
The rule will only apply if your X server is started. So if the mouse is plugged when booting, the rule will match right at the beginning of the boot sequence which is long before the system even thinks of running anything related to X. The mouse therefore needs to be unplugged and plugged again after logging in to KDE/Unity/Gnome/etc.
Also, if you switch to text-based ttys (
and so on) and back to X the settings get lost, so again unplug and re-plug the mouse.