From: Matthias <hias@eilert.tech>
To: Aditya Garg <gargaditya08@live.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Synaptics touchpad not working after suspend, psmouse.synaptics_intertouch
Date: Tue, 6 May 2025 22:49:51 +0200 [thread overview]
Message-ID: <aea15a49-4e1c-41dd-bb09-24d2169f1caa@eilert.tech> (raw)
In-Reply-To: <3530EFD3-68F2-4890-9ACB-EF963769D079@live.com>
Am 04.05.25 um 08:34 schrieb Aditya Garg:
> Hi Hias
Hi Aditya,
thanks for your patch!
>> On 2 May 2025, at 1:34 AM,arch.hias@eilert.tech wrote:
>>
>> 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 tolinux-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
> Please test this patch for your device:
To test it, I first removed the kernel command line option
`psmouse.synaptics_intertouch=1`.
The issue still occurs with the unpatched kernel `linux-lts-6.12.27-1`
from the Arch Linux repositories [1].
After building and installing the package [1] with your patch applied,
the touchpad works reliably — even without the
`psmouse.synaptics_intertouch=1` option.
> —>8—
>
> From ace747d33f1b9d329309c277879fa8a632606c93 Mon Sep 17 00:00:00 2001
> From: Aditya Garg<gargaditya08@live.com>
> Date: Sun, 4 May 2025 11:46:44 +0530
> Subject: [PATCH] Update synaptics.c
>
> ---
> drivers/input/mouse/synaptics.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
> index 309c360aab5597..24db13ceae3ba2 100644
> --- a/drivers/input/mouse/synaptics.c
> +++ b/drivers/input/mouse/synaptics.c
> @@ -195,6 +195,7 @@ static const char * const smbus_pnp_ids[] = {
> "SYN3221", /* HP 15-ay000 */
> "SYN323d", /* HP Spectre X360 13-w013dx */
> "SYN3257", /* HP Envy 13-ad105ng */
> + "SYN1221",
> NULL
> };
> #endif
>
> --------
>
> You can also download the patch from:https://github.com/AdityaGarg8/linux/commit/ace747d33f1b9d329309c277879fa8a632606c93.patch
>
>
> Also, please share you laptops model (Eg: HP Envy 13-ad105ng)
TUXEDO InfinityBook Pro 14 v5 / Barebone N14xCU
This is my first time testing and reporting a kernel patch, so the
process is new and quite interesting to me. Let me know if I can help
with further testing or provide additional infos.
> And if you want to be credited for your report, please share your full legal name and email.
Feel free to credit the report as follows:
Name: Matthias Eilert
Email: kernel.hias@eilert.tech
> Thanks
> Aditya
hias
Links:
1:https://gitlab.archlinux.org/archlinux/packaging/packages/linux-lts/-/commit/6b2e8530afda872a3460e7c29cebd302223c1fa8
next prev parent reply other threads:[~2025-05-06 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 20:04 Synaptics touchpad not working after suspend, psmouse.synaptics_intertouch arch.hias
2025-05-04 6:34 ` Aditya Garg
2025-05-06 20:49 ` Matthias [this message]
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=aea15a49-4e1c-41dd-bb09-24d2169f1caa@eilert.tech \
--to=hias@eilert.tech \
--cc=gargaditya08@live.com \
--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