HP Pavilion touchpad turned off after waking up from sleep

English Hardware
1

Hi all, the touchpad of my HP Pavilion laptop is turned off every time the laptop has waken up from suspend to ram.
This same laptop hasn’t had that problem for years running Leap, Ubuntu or Fedora.
But now it happens with my recent install of Tumbleweed.
I’ve been looking for a solution, but all I find are old solutions that are focused on turning the touchpad back on after waking up.
None have worked for me so far.
But instead of getting the touchpad turned on, I would rather know why it is disabled in the first place!
I hope someone can help me with this.
Here’s some systeminformation:

chris@Laptop:~> inxi -Fxxxpmrz
System:
  Kernel: 6.12.33-1-longterm arch: x86_64 bits: 64 compiler: gcc v: 14.3.0
    clocksource: tsc
  Desktop: KDE Plasma v: 6.3.5 tk: Qt v: N/A wm: kwin_wayland with: krunner
    vt: 2 dm: SDDM Distro: openSUSE Tumbleweed 20250611
Machine:
  Type: Laptop System: HP product: HP Pavilion Notebook
    v: Type1ProductConfigId serial: <superuser required> Chassis: type: 10
    serial: <superuser required>
  Mobo: HP model: 8215 v: 83.14 serial: <superuser required>
    part-nu: Y5U72EA#ABH uuid: <superuser required> UEFI: Insyde v: F.25
    date: 12/12/2016
Battery:
  ID-1: BAT0 charge: 14.5 Wh (42.0%) condition: 34.5/34.5 Wh (100.0%)
    volts: 7.1 min: 7.7 model: Hewlett-Packard Primary type: Li-ion serial: N/A
    status: discharging
Memory:
  System RAM: total: 12 GiB available: 11.57 GiB used: 4.92 GiB (42.5%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 2 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: Bottom-Slot 1(left) type: DDR4 detail: synchronous size: 8 GiB
    speed: 2133 MT/s volts: curr: 1 min: 2 max: 2 width (bits): data: 64
    total: 64 manufacturer: Corsair part-no: CMSO8GX4M1A2133C15 serial: N/A
  Device-2: Bottom-Slot 2(right) type: DDR4 detail: synchronous size: 4 GiB
    speed: 2133 MT/s volts: curr: 1 min: 1.25 max: 2 width (bits): data: 64
    total: 64 manufacturer: Micron part-no: 4ATF51264HZ-2G3B1 serial: <filter>
CPU:
  Info: dual core model: Intel Core i3-7100U bits: 64 type: MT MCP
    smt: enabled arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB
    L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 400 min/max: 400/2400 cores: 1: 400 2: 400 3: 400 4: 400
    bogomips: 19200
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 620 vendor: Hewlett-Packard driver: i915
    v: kernel arch: Gen-9.5 ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:5916 class-ID: 0300
  Device-2: Cheng Uei Precision Industry (Foxlink) HP Wide Vision HD
    integrated webcam driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 bus-ID: 1-3:2 chip-ID: 05c8:038e class-ID: 0e02 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: vesa
    alternate: fbdev,intel dri: iris gpu: i915 display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0693 res: mode: 1920x1080 hz: 60
    scale: 100% (1) dpi: 142 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
    modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.1.3 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel HD Graphics 620 (KBL GT2)
    device-ID: 8086:5916 display-ID: :0.0
  API: Vulkan v: 1.4.313 layers: 1 surfaces: N/A device: 0
    type: integrated-gpu driver: N/A device-ID: 8086:5916 device: 1 type: cpu
    driver: N/A device-ID: 10005:0000
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:9d71
    class-ID: 0403
  API: ALSA v: k6.12.33-1-longterm status: kernel-api with: aoss
    type: oss-emulator
  Server-1: PipeWire v: 1.4.4 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard
    driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: 3000
    bus-ID: 03:00.0 chip-ID: 10ec:8136 class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
    v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:24fb
    class-ID: 0280
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: Intel Wireless-AC 3168 Bluetooth driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-7:3 chip-ID: 8087:0aa7
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: <filter> bt-v: 4.2 lmp-v: 8
Drives:
  Local Storage: total: 238.47 GiB used: 48.86 GiB (20.5%)
  ID-1: /dev/sda vendor: SanDisk model: SD8SN8U-256G-1006 size: 238.47 GiB
    speed: 6.0 Gb/s tech: SSD serial: <filter> fw-rev: 0006 scheme: GPT
Partition:
  ID-1: / size: 225.89 GiB used: 48.5 GiB (21.5%) fs: btrfs dev: /dev/dm-1
    mapped: cr_root
  ID-2: /.snapshots size: 225.89 GiB used: 48.5 GiB (21.5%) fs: btrfs
    dev: /dev/dm-1 mapped: cr_root
  ID-3: /boot/efi size: 1022 MiB used: 370.5 MiB (36.3%) fs: vfat
    dev: /dev/sda1
  ID-4: /boot/grub2/i386-pc size: 225.89 GiB used: 48.5 GiB (21.5%)
    fs: btrfs dev: /dev/dm-1 mapped: cr_root
  ID-5: /boot/grub2/x86_64-efi size: 225.89 GiB used: 48.5 GiB (21.5%)
    fs: btrfs dev: /dev/dm-1 mapped: cr_root
  ID-6: /home size: 225.89 GiB used: 48.5 GiB (21.5%) fs: btrfs
    dev: /dev/dm-1 mapped: cr_root
  ID-7: /opt size: 225.89 GiB used: 48.5 GiB (21.5%) fs: btrfs
    dev: /dev/dm-1 mapped: cr_root
  ID-8: /root size: 225.89 GiB used: 48.5 GiB (21.5%) fs: btrfs
    dev: /dev/dm-1 mapped: cr_root
  ID-9: /srv size: 225.89 GiB used: 48.5 GiB (21.5%) fs: btrfs
    dev: /dev/dm-1 mapped: cr_root
  ID-10: /usr/local size: 225.89 GiB used: 48.5 GiB (21.5%) fs: btrfs
    dev: /dev/dm-1 mapped: cr_root
  ID-11: /var size: 225.89 GiB used: 48.5 GiB (21.5%) fs: btrfs
    dev: /dev/dm-1 mapped: cr_root
Swap:
  ID-1: swap-1 type: partition size: 11.56 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/dm-0 mapped: cr_swap
Sensors:
  System Temperatures: cpu: 35.8 C pch: 39.5 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 27
  Active zypp repos in: /etc/zypp/repos.d/download.opensuse.org-non-oss.repo
    1: download.opensuse.org-non-oss ~ http://download.opensuse.org/tumbleweed/repo/non-oss/
  Active zypp repos in: /etc/zypp/repos.d/download.opensuse.org-oss.repo
    1: download.opensuse.org-oss ~ http://download.opensuse.org/tumbleweed/repo/oss/
  Active zypp repos in: /etc/zypp/repos.d/download.opensuse.org-tumbleweed.repo
    1: download.opensuse.org-tumbleweed ~ http://download.opensuse.org/update/tumbleweed/
  Active zypp repos in: /etc/zypp/repos.d/ftp.gwdg.de-openSUSE_Tumbleweed.repo
    1: ftp.gwdg.de-openSUSE_Tumbleweed ~ http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/
  Active zypp repos in: /etc/zypp/repos.d/packman.repo
    1: packman ~ https://ftp.fau.de/packman/suse/openSUSE_Tumbleweed/
  Active zypp repos in: /etc/zypp/repos.d/repo-openh264.repo
    1: repo-openh264 ~ http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed
  Active zypp repos in: /etc/zypp/repos.d/vivaldi.repo
    1: vivaldi ~ https://repo.vivaldi.com/archive/rpm/x86_64
Info:
  Processes: 315 Power: uptime: 0h 53m states: freeze,mem suspend: deep
    wakeups: 1 hibernate: disabled Init: systemd v: 257 default: graphical
  Compilers: gcc: 14.3.0 Shell: Bash v: 5.2.37 running-in: konsole
    inxi: 3.3.37
2

I’m not sure where the problem might lie for this issue. However, let’s start by excluding any user account specific issue. Create a new user account, and login to the Plasma desktop as that user. After a suspend/resume cycle is the touchpad disabled in the same way?

3

Please also share the output from sudo journalctl -b| egrep "touch|input"

4 
sudo journalctl -b| egrep "touch|input"
[sudo] wachtwoord voor root: 
jun 13 23:09:04 Laptop kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
jun 13 23:09:04 Laptop kernel: psmouse serio1: synaptics: Your touchpad (PNP: SYN3229 SYN1e00 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.
jun 13 23:09:04 Laptop kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input2
jun 13 23:09:06 Laptop kernel: input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3
jun 13 23:09:20 Laptop kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input4
jun 13 23:09:20 Laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5
jun 13 23:09:20 Laptop kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
jun 13 23:09:20 Laptop kernel: input: Wireless hotkeys as /devices/virtual/input/input7
jun 13 23:09:20 Laptop kernel: input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input8
jun 13 23:09:20 Laptop kernel: input: PC Speaker as /devices/platform/pcspkr/input/input9
jun 13 23:09:21 Laptop kernel: input: HP WMI hotkeys as /devices/virtual/input/input10
jun 13 23:09:21 Laptop kernel: snd_hda_codec_realtek hdaudioC0D0:    inputs:
jun 13 23:09:22 Laptop kernel: input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input11
jun 13 23:09:22 Laptop kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
jun 13 23:09:22 Laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13
jun 13 23:09:22 Laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
jun 13 23:09:22 Laptop kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
jun 13 23:09:22 Laptop systemd-logind[1404]: Watching system buttons on /dev/input/event5 (Power Button)
jun 13 23:09:22 Laptop systemd-logind[1404]: Watching system buttons on /dev/input/event4 (Power Button)
jun 13 23:09:22 Laptop systemd-logind[1404]: Watching system buttons on /dev/input/event3 (Lid Switch)
jun 13 23:09:22 Laptop systemd-logind[1404]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard)
jun 13 23:09:22 Laptop iio-sensor-prox[1371]: Not a switch [/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/../capabilities/sw]
jun 13 23:09:22 Laptop iio-sensor-prox[1371]: Invalid bitmask entry for /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event5
jun 13 23:09:24 Laptop display-manager[1637]: XKBLAYOUT is already set. Better don't touch X11 keyboard configuration.
jun 13 23:09:29 Laptop kcminit_startup[1840]: Initializing  "/usr/lib64/qt6/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
5

Hi, thank you for answering and trying to help!
I have made a new user account and the behaviour was the same after waking up from sleep.
Using that account off course :slightly_smiling_face:

6

Ok, thanks for testing. It could well be due to a hardware quirk that doesn’t play nice with the kernel. Interesting that you say Fedora didn’t exhibit this issue though. More research needed, and ultimately it may take a bug report to resolve.

7

Also after reading the second line of the output from journactl, I made a file /etc/modprobe.d/80-psmouse.conf with the line: psmouse.synaptics_intertouch=1
I then rebooted and suspended and woke up the the laptop with the same result.
So that didn’t help either.

I’ll do some more digging.
I mean the touchpad is working after bootup.
And in KDE/Plasma it is configured to be turned on.
After waking up that configuration is changed.
So it has to be some kind of service that overwrites that configuration, or some service unloads a module for the touchpad causing KDE/Plasma to think it’s not there anymore.
But I can turn it on with a keyboard shortcut.
And that could not happen if there was a module missing.
Really weird!

Anyway, thank you for trying to help Deano!
If I do find out what the cause is, I will post it here.

8

If you run sudo libinput list-devices, you’ll likely see that it is still enumerated, but perhaps just disabled.

9

I know that you’d like to understand the underlying cause, but that may take a bug report and/or a deeper deve into why the device is inactive following a resume - likely kernel related or interaction with driver and hardware perhaps.

It may also be that udev just needs to retrigger input device detection…here’s a broad brush to do that…

sudo nano /etc/systemd/system/touchpad-resume.service

Description=Reinitialize touchpad after suspend
After=suspend.target

[Service]
Type=oneshot
ExecStart=/usr/bin/udevadm trigger --subsystem-match=input

[Install]
WantedBy=suspend.target

then do
sudo systemctl daemon-reload
and enable the service
sudo systemctl enable --now touchpad-resume.service

Something to try anyway.

10

This approach won’t work for a built-in driver (as is the case with openSUSE kernels). You would need to add the option to the GRUB config as a kernel parameter eg psmouse.synaptics_intertouch=1, This might be worth a shot for your particular hardware. YMMV.

11

Strangely enough the output regarding the touchpad is identical before and after suspend to ram.

12

Hey! That worked! Thank you.
Allthoug the root of the problem is not adressed, this is a nice workaround.
Like I said, I will investigate further.
And if I cannot figure it out, I will file a bug report.

13

So I’ve done some testing.
The same behaviour is with Debian Trixie.
So I looked at what has changed for me comming from Kubuntu 24.04 to Tumbleweed and Debian Trixie.
A newer kernel, and KDE/Plasma 6.3.
The touchpad does not turn off when going to sleep and resume with Icewm.
Only with KDE/Plasma 6, with both X11 and Wayland.

So it seems to be KDE/Plasma 6 causing the touchpad to turn off.
But in KDE/Plasma does this?

14

You might want to consider raising it at https://discuss.kde.org/

15

Yeah I know.
I want to test some more and then file a bug report.
It clear to me now that this is a regression from KDE/Plasma 5 to 6.
I noticed that it might only happen on battery power.
That I have to test tomorrow, then I’ll file a bug report.