From ArchWiki
Jump to navigation Jump to search

Udev rule

Merged from Accuracy template in Trackpoint#udev configuration rule. -- Alad (talk) 11:18, 24 July 2015 (UTC)

I couldn't get the previous rule to trigger on boot unless I used the following:

SUBSYSTEM=="serio", DRIVERS=="psmouse", ACTION=="add", ENV{SERIO_TYPE}=="05", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/press_to_select", ATTR{press_to_select}="1", ATTR{sensitivity}="230", ATTR{speed}="200"

The WAIT_FOR part instructs udev to wait for the trackpoint to be properly initialized before changing attributes (path might differ on trackpoint-only devices).

-- 10:28, 12 May 2015‎ Jabbourb

The WAIT_FOR attribute was removed with the release of systemd 222-1 (See the commit on github). There does not seem to be a workaround available at the moment.
-- 09:45, 24 July 2015‎ Matthiasr94
I reported the issue as it was described in the comments at github. The report can be found here. Not everyone seems to agree. Meidell (talk) 21:06, 7 August 2015 (UTC)
Does the tmpfiles way work for you? -- Lahwaacz (talk) 14:34, 2 September 2015 (UTC)
Actually disregard this, apparently the tmpfiles way does not work even for the OP.[1] Lahwaacz (talk) 18:40, 2 September 2015 (UTC)

A solution to the deprecated WAIT_FOR statement is to use a different udev event as described in this discussion [2].

ACTION=="add",SUBSYSTEM=="input",ATTR{name}=="TPPS/2 IBM TrackPoint",ATTR{device/sensitivity}="200",ATTR{device/speed}="120"

--The ben (talk) 13:08, 14 October 2015 (UTC)

The rule as of 24 February 2016 works for me on a X201. Can this be closed? -- Alad (talk) 13:38, 18 July 2016 (UTC)
It has been two years, close. -- Blackteahamburger (talk) 15:38, 21 June 2020 (UTC)

Middle-button scrolling with libinput

The article mentions that "When using xf86-input-libinput, middle-button scrolling is enabled by default". That may be so, but not when using a PS/2-to-USB adapter. This way middle-button scrolling does not work. It used to work with evdev. If anybody knows where to set the needed properties for libinput, please amend the article.

--Tskevy (talk) 13:17, 16 March 2017 (UTC)

udev hwdb entry out-of-date

As yurb (Yuriy Bulka?) has noticed, this seems to be removed: [3].

I have updated the section, but will appreciate if someone reviewed it. Thanks. --Setthemfree (talk) 15:29, 13 June 2018 (UTC)

HP pointing stick sensitivity with libinput - probably applies to other vendors too

Problem: I was unable to adjust sensitivity on a HP pointing stick (listed as "PS/2 Generic Mouse" by xinput) using any of the described methods. There's no "sensitivity" or "deceleration" or similar properties when runing "xinput list-props" and fiddling with the other properties doesn't affect sensitivity.

Solution: One can finely adjust speed using the "Coordinate Transformation Matrix", by changing (only) the first two entries of the main diagonal - that is the first two 1's in the default configuration, to something higher.

In fact, it's possible to make other changes such as direction, etc, (i.e. if one wish to invert an axis or rotate, for whatever reason) or to make one axis more sensitive. Some details regarding how the matrix is applied are listed in the driver documentation here:

I did a quick search and there's no mention of this on the libinput article either. On the one hand maybe it's worth adding in somewhere because it seems rather useful. On the other, I'm not sure if it's the feature is supposed to be used this way since I've only seen it mentioned in regards to touchscreen calibration, so I'm a little reluctant.

Kolo (talk) 02:04, 25 March 2020 (UTC)