Re: Trackpoint udev rules

Jacopo De Simoi <[email protected]>
Newsgroups gmane.linux.hardware.thinkpad
Message-ID <3660103.oLxi70oKPO@bl4ckspoons>
On Thursday, April 27, 2017 2:06:16 PM CEST Joachim Breitner wrote:
> Hi,
> 
> Am Mittwoch, den 26.04.2017, 17:41 +0100 schrieb Richard Neill:
> > Hi Joachim,
> > 
> > On 26/04/17 16:42, Joachim Breitner wrote:
> > > Hi,
> > > 
> > > on my T460s, set up without a desktop environment, I have this
> > > configuration:
> > > 
> > > $ cat /etc/udev/rules.d/10-trackpoint.rules
> > > ACTION=="add",
> > > SUBSYSTEM=="serio", DRIVERS=="psmouse", ATTR{sensitivity}="255",
> > > ATTR{speed}="160"
> > > 
> > > Nevertheless, after booting, I find that they were not applied:
> > > 
> > > $ cat /sys/devices/platform/i8042/serio1/serio2/{speed,sensitivity}
> > > 97
> > > 200
> > 
> > I have the following notes that may help, and which work on a T470s.
> > 
> > 1. identify the /sys path:
> >   find /sys/devices/platform/i8042 -name sensitivity
> >   #this machine has it in serio1/serio2
> > 
> > 2. Create /etc/udev/rules.d/10-trackpoint.rules
> > #Trackpoint Sensitivity/Speed - set the sensitivity to maximum.
> > KERNEL=="serio2", SUBSYSTEM=="serio", DRIVERS=="psmouse", 
> > ATTR{sensitivity}:="255", ATTR{speed}:="255"
> > 
> > 3. Test/trigger the rule with:
> >   udevadm test /sys/devices/platform/i8042/serio1/serio2
> > 
> > 
> > I think that you are falling foul of Udev syntax. In order to avoid
> > the 
> > original ambiguous use of "=", it now uses
> >   ==  for testing
> >   :=  for assignment  (unlike C)
> 
> thanks. Indeed, udevadm test works, and sets the values as expected.
> But after a reboot, I find
> 
> $ cat /sys/devices/platform/i8042/serio1/serio2/{speed,sensitivity}
> 140
> 200
> 
> so it has set the speed to 140 as desired, but the sensitivity is still
> at its original value, and not the 255 I want. As if the device reset
> itself after writing the sensitivity value…

I have the same issue on a T460s; occasionally (actually more often than not) 
the device resets upon changing {sensitivity,speed} and values are reset to 
the default. I thought it could be a hardware issue, but if you are having the 
same issues then it might be interesting to find out. 

what happens if you set {sensitivity,speed} manually? do you get resets? 

Anybody else with similar issues?


> 
> Regards,
> Joachim


-- 
The linux-thinkpad mailing list home page is at:
http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.