You are not logged in.

#1 2012-02-21 15:46:15

examon
Member
Registered: 2011-05-07
Posts: 208

ThinkPad trackpoint: unable to restore speed/sensitivity [SOLVED]

I have ThinkPad x201i, Arch 64bit and (ofc) trackpoint which I want to configure.

I'm using:

# echo -n 200 > /sys/devices/platform/i8042/serio1/serio2/speed &
# echo -n 200 > /sys/devices/platform/i8042/serio1/serio2/sensitivity &

and it work's ok but when I reboot, my  speed/sensitivity is gone even if I have this two lines of code in my /etc/rc.local. I know it workted good in rc.local when I was using Arch like 2 months ago. I've downloaded "configure-trackpoint" package from AUR and when I run it I see this error:

No D-BUS daemon running

but I have installed dbus, It's in my daemon array in rc.conf and I can see it running in htop.

Thanks for any help

Last edited by examon (2012-02-21 21:05:03)

Offline

#2 2012-02-21 16:17:21

bohoomil
Member
Registered: 2010-09-04
Posts: 2,376
Website

Re: ThinkPad trackpoint: unable to restore speed/sensitivity [SOLVED]

Do you have any config file in your /etc/X11/xorg.conf.d?


:: Registered Linux User No. 223384

:: github
:: infinality-bundle+fonts: good looking fonts made easy

Offline

#3 2012-02-21 17:50:29

examon
Member
Registered: 2011-05-07
Posts: 208

Re: ThinkPad trackpoint: unable to restore speed/sensitivity [SOLVED]

Yes I do.

10-evdev.conf
10-quirks.conf
10-synaptics.conf

Offline

#4 2012-02-21 18:21:27

bohoomil
Member
Registered: 2010-09-04
Posts: 2,376
Website

Re: ThinkPad trackpoint: unable to restore speed/sensitivity [SOLVED]

Check if this trackpoint specific config file works for you:

# TrackPoint with scrolling

Section "InputClass"
	Identifier "Trackpoint Wheel Emulation"
	MatchProduct "TPPS/2 IBM TrackPoint|DualPoint Stick|Synaptics Inc. Composite TouchPad / TrackPoint|ThinkPad USB Keyboard with TrackPoint|USB Trackpoint pointing device"
	MatchDevicePath "/dev/input/event*"
	Option "EmulateWheel" "true"
	Option "EmulateWheelButton" "2"
	Option "Emulate3Buttons" "false"
	Option "XAxisMapping" "6 7"
	Option "YAxisMapping" "4 5"
EndSection

Save it as a separate file, say, 10-trackpoint.conf.

Last edited by bohoomil (2012-02-21 18:22:20)


:: Registered Linux User No. 223384

:: github
:: infinality-bundle+fonts: good looking fonts made easy

Offline

#5 2012-02-21 19:19:08

examon
Member
Registered: 2011-05-07
Posts: 208

Re: ThinkPad trackpoint: unable to restore speed/sensitivity [SOLVED]

Thx. I think that config file is working, I'm able to scroll with trackpoint now. Can u tell me how I'll setup speed/sensitivity with that conf file?

Offline

#6 2012-02-21 19:34:59

bohoomil
Member
Registered: 2010-09-04
Posts: 2,376
Website

Re: ThinkPad trackpoint: unable to restore speed/sensitivity [SOLVED]

I've never tested it myself--my trackpoint works well with default settings--but you may try this udev-based method.


:: Registered Linux User No. 223384

:: github
:: infinality-bundle+fonts: good looking fonts made easy

Offline

#7 2012-02-21 21:04:29

examon
Member
Registered: 2011-05-07
Posts: 208

Re: ThinkPad trackpoint: unable to restore speed/sensitivity [SOLVED]

It looks like adding:

SUBSYSTEM=="serio", DRIVERS=="psmouse", WAIT_FOR="/sys/devices/platform/i8042/serio1/serio2/sensitivity", ATTR{sensitivity}="255"

works just fine. Thanks bohoomil

Offline

#8 2013-03-31 11:25:48

Spot
Member
From: The Heart of Europe
Registered: 2008-12-20
Posts: 50

Re: ThinkPad trackpoint: unable to restore speed/sensitivity [SOLVED]

I installed the programm "configure-trackpoint". That works for the actuall session, but is gone when restarting the system...

@ examon

Your methods doesnt work for me. X wont start.

Last edited by Spot (2013-03-31 11:26:52)

Offline

#9 2013-03-31 14:21:17

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: ThinkPad trackpoint: unable to restore speed/sensitivity [SOLVED]

The undeveloped rule should work. But it only foes so if you boot to the graphical.target right away and that target is set up to actually start your x server.

I think this is because the poi t at which the udevadm trigger is run is early but not too early. And it don't be run again after something like startx if you booted from to only multi-user.target.

Offline

Board footer

Powered by FluxBB