You are not logged in.

#1 2019-08-07 12:53:43

kindaro
Member
Registered: 2017-01-16
Posts: 18

After update, wrong touchpad device is used.

I observe two touchpad devices on my system. If I disable the first one (via xinput on X or via sway configuration on Wayland), I get no pointer activity at all, even if I repeatedly try to enable the second one.

Previously, the second one was the one I used and configured, and I never noticed the first one, although I did not really paid attention to the list of input devices until today.

To clarify, I only have one physical touchpad device on my laptop.

% sudo libinput list-devices
...
Device:           SYNA306E:00 06CB:82F1 Touchpad
Kernel:           /dev/input/event16
Group:            8
Seat:             seat0, default
Size:             106x56mm
Capabilities:     pointer gesture
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    *button-areas clickfinger 
Disable-w-typing: enabled
Accel profiles:   none
Rotation:         n/a
...
Device:           SynPS/2 Synaptics TouchPad
Kernel:           /dev/input/event18
Group:            11
Seat:             seat0, default
Size:             69x50mm
Capabilities:     pointer gesture
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    *button-areas clickfinger 
Disable-w-typing: enabled
Accel profiles:   none
Rotation:         n/a
...

If I remove psmouse kernel module, only the second device will disappear, while the first one stays and the pointer remains functional.

This is what dmesg has to say: (You can see me removing and replacing the kernel module)

[    2.844814] input: SYNA306E:00 06CB:82F1 Touchpad as /devices/platform/AMDI0011:00/i2c-2/i2c-SYNA306E:00/0018:06CB:82F1.0001/input/input16
[    2.909950] input: SYNA306E:00 06CB:82F1 Touchpad as /devices/platform/AMDI0011:00/i2c-2/i2c-SYNA306E:00/0018:06CB:82F1.0001/input/input26
[    4.388456] psmouse serio3: synaptics: Your touchpad (PNP: SYN306e SYN0100 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org.
[    4.443023] psmouse serio3: synaptics: Touchpad model: 1, fw: 10.16, id: 0x1e2a1, caps: 0xf00123/0x840300/0x12e800/0x500000, board id: 3352, fw id: 2727989
[    4.476155] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio3/input/input28
[ 1913.792883] psmouse serio3: synaptics: Your touchpad (PNP: SYN306e SYN0100 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org.
[ 1913.844570] psmouse serio3: synaptics: Touchpad model: 1, fw: 10.16, id: 0x1e2a1, caps: 0xf00123/0x840300/0x12e800/0x500000, board id: 3352, fw id: 2727989
[ 1913.881847] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio3/input/input34
[ 1943.136363] psmouse serio3: synaptics: Your touchpad (PNP: SYN306e SYN0100 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@vger.kernel.org.
[ 1943.186671] psmouse serio3: synaptics: Touchpad model: 1, fw: 10.16, id: 0x1e2a1, caps: 0xf00123/0x840300/0x12e800/0x500000, board id: 3352, fw id: 2727989
[ 1943.218780] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio3/input/input40

What is going on?

I would like to use the second device, as I already have it configured and it looks healthier overall.

Offline

#2 2019-08-17 14:43:34

asasione
Member
Registered: 2019-06-16
Posts: 3

Re: After update, wrong touchpad device is used.

I would suggest you remove the second one (SynPS/2 Synaptics TouchPad) and configure the first one. The second device isn't the actual touchpad device and its an issue I have on my system as well. I added a script to my autostart-script in KDE and removed the Synaptics touchpad using xinput for it to work correctly. You never mentioned what DE you're even using in your post or any information that could help narrow down your issue beyond claiming you're having an issue and some solutions you tried. If you want to insist on using the second device install Synaptics drivers.

Offline

#3 2019-08-17 20:35:08

kindaro
Member
Registered: 2017-01-16
Posts: 18

Re: After update, wrong touchpad device is used.

@asasione I usually use i3 and sway, but it appears to me that this issue is independent of a compositor or a desktop environment — therefore I neglected to mention this. May I ask you to clarify what you mean by "isn't the actual device" and "install Synaptics drivers"?

Offline

Board footer

Powered by FluxBB