USB Mouse going in to Energy Save mode

After one of the last update’s my Mouse in a kind of Energy save mode.

The LED turning off after 3 seconds, the sliding is dead, by pressing any Mouse button I can wake it back up for 3 more seconds at any time.

By unplug the USB and reconnect the mouse plug, everything is back to normal, but after reboot the problem is back.

Anyone else have the same issue?

It seems similar to:

  Kernel: 6.6.19-1-MANJARO arch: x86_64 bits: 64
  Desktop: Xfce v: 4.18.1 Distro: Manjaro Linux
  Type: Laptop System: Dell product: XPS 15 9570 v: N/A
    serial: <superuser required>
  Mobo: Dell model: 0D0T05 v: A00 serial: <superuser required> UEFI: Dell
    v: 1.31.0 date: 03/13/2023
  ID-1: BAT0 charge: 32.1 Wh (100.0%) condition: 32.1/97.0 Wh (33.0%)
  Info: 6-core model: Intel Core i7-8750H bits: 64 type: MT MCP cache:
    L2: 1.5 MiB
  Speed (MHz): avg: 1616 min/max: 800/4100 cores: 1: 2200 2: 800 3: 2201
    4: 2200 5: 800 6: 800 7: 2200 8: 2200 9: 2200 10: 800 11: 2200 12: 800
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] driver: i915 v: kernel
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: nvidia
    v: 550.54.14
  Device-3: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4 driver: X:
    loaded: modesetting,nvidia dri: iris gpu: i915 resolution: 1: 1920x1080~60Hz
    2: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: iris,kms_swrast,nvidia,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.0.2-manjaro1.1
    renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  API: Vulkan v: 1.3.276 drivers: intel,nvidia surfaces: xcb,xlib
  Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel
  API: ALSA v: k6.6.19-1-MANJARO status: kernel-api
  Server-1: PipeWire v: 1.0.3 status: active
  Device-1: Intel Wi-Fi 5 Wireless-AC 9x6x [Thunder Peak] driver: iwlwifi
  IF: wlp59s0 state: up mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IF-ID-2: pan1 state: down mac: <filter>
  Device-1: Intel Wireless-AC 9260 Bluetooth Adapter driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: <filter> bt-v: 5.1
  Local Storage: total: 1.82 TiB used: 1.53 TiB (84.1%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 2TB
    size: 1.82 TiB
  ID-1: / size: 1.79 TiB used: 1.53 TiB (85.5%) fs: ext4 dev: /dev/dm-0
  ID-2: /boot/efi size: 256 MiB used: 220 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-1: swap-1 type: file size: 13.02 GiB used: 0 KiB (0.0%) file: /swapfile
  System Temperatures: cpu: 82.0 C pch: 53.0 C mobo: 66.0 C
  Fan Speeds (rpm): cpu: 4890 fan-2: 4890
  Memory: total: 32 GiB note: est. available: 30.97 GiB used: 8.2 GiB (26.5%)
  Processes: 448 Uptime: 28m Shell: Zsh inxi: 3.3.33
❯ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter
Bus 001 Device 005: ID 27c6:5395 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader
Bus 001 Device 007: ID 0c45:671d Microdia Integrated_Webcam_HD
Bus 001 Device 009: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 010: ID 05e3:0751 Genesys Logic, Inc. microSD Card Reader
Bus 001 Device 011: ID 03f0:034a HP, Inc Elite Keyboard
Bus 001 Device 012: ID 258a:1007 SINOWEALTH Wired Gaming Mouse
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 05e3:0626 Genesys Logic, Inc. Hub

you could run
journalctl -f
in a terminal
and see whether the output is telling something about the state change of the mouse

(the command prints messages as they occur)

Thanks, while it was happened, there was no journal log to see.

But at unplugging and reconnect of the USB, there was this:

USB Plug
Mär 09 22:03:55 shaderico kernel: usb 1-2.4: USB disconnect, device number 9
Mär 09 22:03:58 shaderico kernel: usb 1-2.4: new full-speed USB device number 10 using xhci_hcd
Mär 09 22:03:58 shaderico kernel: usb 1-2.4: New USB device found, idVendor=258a, idProduct=1007, bcdDevice= 1.01
Mär 09 22:03:58 shaderico kernel: usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mär 09 22:03:58 shaderico kernel: usb 1-2.4: Product: Wired Gaming Mouse
Mär 09 22:03:58 shaderico kernel: usb 1-2.4: Manufacturer: SINOWEALTH
Mär 09 22:03:58 shaderico kernel: input: SINOWEALTH Wired Gaming Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.0/0003:258A:1007.0008/input/input33
Mär 09 22:03:58 shaderico kernel: hid-generic 0003:258A:1007.0008: input,hidraw2: USB HID v1.11 Mouse [SINOWEALTH Wired Gaming Mouse] on usb-0000:00:14.0-2.4/input0
Mär 09 22:03:58 shaderico kernel: input: SINOWEALTH Wired Gaming Mouse Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4/1-2.4:1.1/0003:258A:1007.0009/input/input34
Mär 09 22:03:58 shaderico mtp-probe[18854]: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4"
Mär 09 22:03:58 shaderico mtp-probe[18854]: bus: 1, device: 10 was not an MTP device
Mär 09 22:03:58 shaderico kernel: hid-generic 0003:258A:1007.0009: input,hiddev96,hidraw3: USB HID v1.11 Keyboard [SINOWEALTH Wired Gaming Mouse] on usb-0000:00:14.0-2.4/input1
Mär 09 22:03:59 shaderico systemd-logind[981]: Watching system buttons on /dev/input/event12 (SINOWEALTH Wired Gaming Mouse Keyboard)
Mär 09 22:03:59 shaderico mtp-probe[19222]: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2.4"
Mär 09 22:03:59 shaderico mtp-probe[19222]: bus: 1, device: 10 was not an MTP device

By testing a different Mouse, there was no problem, so it seems the problem is specific to that Mouse model at the moment.

I can only speculate.
I’d try using a different kernel - closer to the version where the issue wasn’t present, perhaps.
Or an even newer one.
Or an LTS kernel.
It’s easy to install a second or third kernel and then choose from the Grub menu which one to use to boot with.

Thanks, I test out ‘linux61’ and ‘linux67’ kernel as well without any change.

Removing powertop fix that

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.