Arch Linux

Proofrific

Member

Registered: 2008-01-05

Posts: 215

Unable to Fully Disable Trackpad

New install on a Lenovo Thinkpad Yoga 260, which has both a trackpoint and trackpad. I only use the trackpoint, so I'd like to disable the trackpad.

Disabling the trackpad in the BIOS does nothing, since it only sets a disable flag that Linux doesn't pick up.

Another option is using xinput. Here are my devices:

$ xinput list
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Wacom Co.,Ltd. Pen and multitouch sensor Finger	id=9	[slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech TrackPoint              	id=14	[slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech Touchpad                	id=13	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Video Bus                               	id=7	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=8	[slave  keyboard (3)]
    ↳ Wacom Co.,Ltd. Pen and multitouch sensor Pen	id=10	[slave  keyboard (3)]
    ↳ Integrated Camera                       	id=11	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=12	[slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                  	id=15	[slave  keyboard (3)]

Running `xinput disable 13` (or equivalently `xinput set-prop 13 "Device Enabled" 0`) only partially disables the trackpad. It does disable the trackpad in the sense that I can't move the mouse cursor using the trackpad or mouseclick. But if I keep a finger or palm on the trackpad, move the mouse using the trackpoint, and then click, the mouse either jumps across the screen or freezes momentarily (while ignoring the click). So clearly the trackpad isn't fully disabled.

I also tried adding the following to an xorg.conf.d file:

Section "InputClass"
        Identifier "touchpad"
        Driver "synaptics"
        MatchIsTouchpad "on"
        Option "Ignore" "on"
EndSection

But the behavior is the same, where the trackpad is partially disabled.

Any ideas? I'm using xf86-input-libinput.

x33a

Forum Fellow

Registered: 2009-08-15

Posts: 4,587

Re: Unable to Fully Disable Trackpad

If you are fine sticking with Synaptics, the following might work:

synclient TouchpadOff=1

Edit: Moving to Laptop Issues.

Last edited by x33a (2017-07-22 21:45:27)

Proofrific

Member

Registered: 2008-01-05

Posts: 215

Re: Unable to Fully Disable Trackpad

I'm also having a related problem where both the trackpoint and trackpad stop working. They keyboard still works. Unloading and reloading (via modprobe) psmouse makes the mice work again. Dmesg reveals:

[22776.182827] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
[22776.190231] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
[22776.198596] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
[22776.208570] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
[22776.219051] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6
[22776.219058] psmouse serio1: issuing reconnect request
[22776.627841] psmouse serio1: Failed to enable mouse on isa0060/serio1
[22817.780824] psmouse serio1: elantech: PS/2 packet [00 80 26 f6 02 44]
[22849.862443] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x4d1f04)
[22849.875615] psmouse serio1: elantech: Synaptics capabilities query result 0x80, 0x14, 0x0c.
[22849.889289] psmouse serio1: elantech: Elan sample query result 04, 01, 85
[22849.948022] input: ETPS/2 Elantech TrackPoint as /devices/platform/i8042/serio1/input/input1351
[22849.966898] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input1350

So the touchpad lost sync. When issuing a reconnect request, it failed to enable the mouse. That's when my mouse stopped working. It comes back after the modprobe.

According to https://bugzilla.redhat.com/show_bug.cgi?id=1313939, this and my previous jumping cursor problem are due to an unfixed driver issue.