Linux Input/HID development
 help / color / mirror / Atom feed
From: arch.hias@eilert.tech
To: linux-input@vger.kernel.org
Subject: Synaptics touchpad not working after suspend, psmouse.synaptics_intertouch
Date: Thu, 1 May 2025 22:04:22 +0200	[thread overview]
Message-ID: <325001b5-12e3-42db-96ec-05bd3f23ab35@eilert.tech> (raw)

Hi,

I'm experiencing an issue with the Synaptics touchpad on my laptop not 
working after resuming from suspend.

This began after upgrading from linux-lts 6.12.19-1 -> 6.12.21-1 [2]


Hardware:
- Touchpad: SynPS/2 Synaptics TouchPad (PNP: SYN1221 PNP0f13)
- Distro: Arch Linux issue began after systemupgrade linux-lts 
(6.12.19-1 -> 6.12.21-1) (kernel 6.12.24-1-lts)

Description:
After resuming from suspend, the touchpad is not detected. However, if I 
suspend and resume a second time, it works again. While checking the 
logs, I found the following kernel message:

kernel: psmouse serio2: synaptics: Your touchpad (PNP: SYN1221 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.

I had previously set `psmouse.synaptics_intertouch=0`, as recommended in 
the Arch Wiki[1].
After changing it to `1`, the touchpad now consistently works after suspend.

This setting appears to resolve the issue for my device. I wanted to 
share this in case it’s helpful for others or worth considering for 
default handling of this hardware.

# libinput list-devices | grep Synaptics -A4
Device:                  Synaptics TM3175-002
Kernel:                  /dev/input/event13
Id:                      <unknown>:06cb:0000
Group:                   6
Seat:                    seat0, default

$ udevadm info /dev/input/event13
P: 
/devices/pci0000:00/0000:00:1f.4/i2c-6/6-002c/rmi4-00/input/input21/event13
M: event13
R: 13
J: c13:77
U: input
D: c 13:77
N: input/event13
L: 0
S: input/by-path/pci-0000:00:1f.4-event-mouse
E: 
DEVPATH=/devices/pci0000:00/0000:00:1f.4/i2c-6/6-002c/rmi4-00/input/input21/event13
E: DEVNAME=/dev/input/event13
E: MAJOR=13
E: MINOR=77
E: SUBSYSTEM=input
E: USEC_INITIALIZED=40782030
E: ID_INPUT=1
E: ID_INPUT_TOUCHPAD=1
E: ID_INPUT_WIDTH_MM=81
E: ID_INPUT_HEIGHT_MM=39
E: ID_BUS=rmi
E: ID_SERIAL=noserial
E: ID_PATH=pci-0000:00:1f.4
E: ID_PATH_TAG=pci-0000_00_1f_4
E: ID_INPUT_TOUCHPAD_INTEGRATION=internal
E: LIBINPUT_DEVICE_GROUP=1d/6cb/0:rmi4-00
E: DEVLINKS=/dev/input/by-path/pci-0000:00:1f.4-event-mouse

Links:

1: 
https://wiki.archlinux.org/title/Touchpad_Synaptics#Touchpad_does_not_work_after_resuming_from_hibernate/suspend

2: http://0x0.st/84b8.txt


Let me know if I can provide further Information, logs or tests.

Best regards,

hias

  
      The ASCII Ribbon Campaign
()     No HTML/RTF in email
/\     No Word docs in email
      Respect for open standards


             reply	other threads:[~2025-05-01 20:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-01 20:04 arch.hias [this message]
2025-05-04  6:34 ` Synaptics touchpad not working after suspend, psmouse.synaptics_intertouch Aditya Garg
2025-05-06 20:49   ` Matthias
2025-05-07 13:39     ` Aditya Garg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=325001b5-12e3-42db-96ec-05bd3f23ab35@eilert.tech \
    --to=arch.hias@eilert.tech \
    --cc=linux-input@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox