Xiaomi Mi Notebook Pro 15.6 Ryzen edition touchpad sometimes doesn't work

Hi everyone, glad to be part of community, what a great OS! :enos:

I’m relatively new to Linux, and had just received an excellent present for 2022 which is Xiaomi Mi Notebook Pro 15.6 Ryzen edition :christmas_tree:

That’s a great ultrabook, and have almost zero problems with EndeavourOS, except problem with touchpad…Sometimes on boot (random probability) it just doesn’t work at all, so i have to use keyboard to reboot etc until it do…

So far i have found Arch wiki article https://wiki.archlinux.org/title/Xiaomi_Mi_Notebook_Pro_15.6 which mentions to try i8042.noaux kernel parameter, i’ve tried adding it to /etc/default/grub and have rebuilt grub, but it doesn’t help - still happens sometimes…

Any help to try out solving this problem is appreciated! :smiley:

inxi -Fxxxz --no-host

System:
  Kernel: 5.10.88-2-lts x86_64 bits: 64 compiler: gcc v: 11.1.0
    Desktop: KDE Plasma 5.23.4 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM
    Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Laptop System: TIMI product: A35S v: N/A serial: <superuser required>
    Chassis: type: 10 serial: <superuser required>
  Mobo: TIMI model: TM2031 v: 014 serial: <superuser required> UEFI: TIMI
    v: XMACZ5B1P0605 date: 05/20/2021
Battery:
  ID-1: BAT0 charge: 33.5 Wh (49.1%) condition: 68.2/66.0 Wh (103.3%)
    volts: 7.5 min: 7.7 model: SUNWODA R15B03W type: Li-ion serial: <filter>
    status: Discharging cycles: 27
CPU:
  Info: 6-core model: AMD Ryzen 5 5600H with Radeon Graphics bits: 64
    type: MT MCP smt: enabled arch: Zen 3 rev: 0 cache: L1: 384 KiB L2: 3 MiB
    L3: 16 MiB
  Speed (MHz): avg: 1555 high: 3391 min/max: 1200/4795:4280:4666:4538:4409
    boost: enabled cores: 1: 1197 2: 1197 3: 3391 4: 2625 5: 1195 6: 1182
    7: 1397 8: 1397 9: 1197 10: 1197 11: 1197 12: 1492 bogomips: 79045
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Cezanne vendor: Xiaomi driver: amdgpu v: kernel
    bus-ID: 03:00.0 chip-ID: 1002:1638 class-ID: 0300
  Device-2: IMC Networks XiaoMi Webcam type: USB driver: uvcvideo
    bus-ID: 3-2:2 chip-ID: 13d3:5471 class-ID: 0e02
  Display: x11 server: X.org 1.21.1.2 compositor: kwin_x11 driver:
    loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa
    resolution: <missing: xdpyinfo>
  Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
  Device-1: AMD vendor: Xiaomi driver: snd_hda_intel v: kernel
    bus-ID: 03:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
    vendor: Xiaomi driver: snd_rn_pci_acp3x v: kernel bus-ID: 03:00.5
    chip-ID: 1022:15e2 class-ID: 0480
  Device-3: AMD Family 17h HD Audio vendor: Xiaomi driver: snd_hda_intel
    v: kernel bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403
  Sound Server-1: ALSA v: k5.10.88-2-lts running: yes
  Sound Server-2: JACK v: 1.9.19 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.42 running: no
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 01:00.0
    chip-ID: 8086:2723 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 3-3:3 chip-ID: 8087:0029 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: see --recommends
Drives:
  Local Storage: total: 476.94 GiB used: 127.85 GiB (26.8%)
  ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNV512G KIOXIA
    size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: AEXA0102 temp: 38.9 C scheme: GPT
Partition:
  ID-1: / size: 468.09 GiB used: 127.85 GiB (27.3%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 296 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 54.0 C mobo: 30.0 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 269 Uptime: 1m wakeups: 181 Memory: 15.05 GiB
  used: 2.36 GiB (15.7%) Init: systemd v: 250 Compilers: gcc: 11.1.0
  Packages: pacman: 1032 Shell: Bash v: 5.1.12 running-in: konsole
  inxi: 3.3.11

journalctl -p3 -xb (after normal boot, when touchpad works, will have to catch moment when it doesn’t again and post it)

Jan 02 21:19:31 new-pc kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Jan 02 21:19:33 new-pc kernel: acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517
Jan 02 21:19:33 new-pc kernel: acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517
Jan 02 21:19:35 new-pc systemd-backlight[884]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
Jan 02 21:19:35 new-pc systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
-- Subject: A start job for unit systemd-backlight@backlight:acpi_video0.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit systemd-backlight@backlight:acpi_video0.service has finished with a failure.
-- 
-- The job identifier is 437 and the job result is failed.

did you already tried : https://wiki.archlinux.org/title/Xiaomi_Mi_Notebook_Pro_15.6#Touchpad_troubles

? and add : i8042.noaux to the kernel line ?

2 Likes

Yes, he’ve mentioned it in OP :wink:

P.S. Jeez, i need coffee…why in the hell i’ve identified as another user?! :rofl: :coffee:

btw, welcome aboard @happty_dog2022 ! :enos: :rocket:

2 Likes

but, does it show the touchpad under lspci , which chipset does it use ?

@ringo
Thanks for fast answer! :slight_smile:
Yes, i’ve tried i8042.noaux haven’t helped issue it seems - still randomly happens on some boots… :slightly_frowning_face:

Here is lspci looks like it doesn’t show, unless i’ve missed it (right now i use that i8042.noaux parameter still, should i try without it?)

lspci

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166a
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166b
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166c
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166d
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166e
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 166f
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1670
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1671
01:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
02:00.0 Non-Volatile memory controller: KIOXIA Corporation Device 0001
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne (rev c6)
03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637
03:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor
03:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
03:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
03:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01)
03:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller
03:00.7 Signal processing controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/Renoir Sensor Fusion Hub
04:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)
04:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 81)

@keybreak
Thank you for welcome! :slight_smile:
Also it’s she :wink:

1 Like

got clearly no idea :slight_smile:

time wil tell…; only saw also on that link Fn+F9 is to enable/disable touchpad

general review it should work with the latest kernel…

but wil see :slight_smile:

1 Like

Oh yes, i know about it, but when it boots without touchpad working - this button ain’t helping either… :laughing:

I’ve tried latest Kernel after installation, it’s was same.
So you think it’s just very new hardware and only way is to just wait until Kernel will have support for it?

Weird thing is that when it works it works just great, all buttons and all of those scroll, taps and multi-finger gestures… :dancer:

Looks like some blocker happens on some boots…

If it helps, I have a similar issue with my USB wireless mouse. it works most of the time, but occasionally, it will not work at login at all, so I need to unplug it and plug it back again.

Since both the mouse and (in your case) the touch pad are pointing devices and the issue happens sporadically on login in both cases, I’m thinking it could be the same problem. I wasn’t able to identify the reason, but given that I was able to use the unplugging/re-plugging workaround I didn’t bother too much with it. I suspect the device is not properly initialized for some reason.

Bottom line, if you cant solve the issue, try identifying the device and resetting it with modprobe (which should be the equivalent of unplugging and plugging the touchpad back in):

  • first identify the driver by using inxi -J --no-host
  • then use modprobe -r [drivername] followed by modprobe [drivername]

Without being a proper fix this might help get the touchpad back in working order when it doesn’t work at login.

2 Likes

Did you add the kernel parameter i8042.noaux properly and update grub?

1 Like

@ricklinux
I think so…why everyone keep asking me same thing which was answered in op? :sweat_smile:

What i did from arch wiki was that:

  1. Add option to grub settings

/etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=3 nowatchdog i8042.noaux"
  1. Update grub
grub-mkconfig -o /boot/grub/grub.cfg
  1. Reboot

Have i missed something from wiki?

@nate
Thank you, it makes sense actually!

inxi -J --no-host

USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
  Hub-2: 2-0:1 info: Super-speed hub ports: 2 rev: 3.1
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0
  Device-1: 3-2:2 info: IMC Networks XiaoMi Webcam type: Video rev: 2.0
  Device-2: 3-3:3 info: Intel AX200 Bluetooth type: Bluetooth rev: 2.0
  Device-3: 3-4:4 info: Shenzhen Goodix FingerPrint type: <vendor specific>
    rev: 2.0
  Hub-4: 4-0:1 info: Super-speed hub ports: 2 rev: 3.1

I don’t think touchpad is listed here?

Friend of mine was right when he said there might be some “untouchable” hidden setting enabled by default, like Fast boot inside Xiaomi bios, he said sometimes when this is enabled computer can skip some hardware initialization steps on boot, which can lead to not properly working things…

Xiaomi’s bios have only Secure boot, which i have disabled already since it is advised for Linux as i’ve read.

1 Like

Fast boot is also setting in Windows which should be disabled. At least if you are dualbooting.

2 Likes

I’d like to try and disable it, but Xiaomi bios only have very few options at all, like: time, password, Secure boot and that’s pretty much it.

Windows…? Dualbooting?
Disgusting! No thanks, it’s enough of that for me! :penguin_face:

4 Likes

Could journal errors in op be connected to that issue somehow?
That watchdog thingy maybe?

Backlight seems to be something else…

That’s the spirit! Welcome to the forum!

party_72

3 Likes

Yes, I’ve noticed this too, with a wireless mouse. Sometimes it just doesn’t register at all on boot, and unplugging and plugging makes it work. I’ve always thought it was a hardware issue with the mouse, but now this makes me think about it again. I’ve had this happening for years, on various Linux distros…

I’ll try resetting it with modprobe -r the next time I notice it (it happens fairly rarely, maybe once a month or so). So If that works, one can easily make a custom keybinding to run a script that resets it.

Yeah I think some companies just make the bios have the basic stuff like boot order etc. Lenovo/hp etc at least have the features enabled and shown in BIOS.

Can you think of a method to debug and identify the problem? It would be great if a bug report were to be filed in for this. I didn’t even know where to start looking for the source of this issue. And yes this happens rarely like once or twice a month, depending on the number of reboots. This is a Logitech Unifying receiver. Next time i’ll have a look to see if the receiver is at all detected (and not a pairing issue).

In my case, it’s a cheap wireless mouse branded “Trust” (model 23804, to be precise).

I always assumed it was a pairing issue… I have no idea how to reliably reproduce it.

Hey! Thank you! :slight_smile:
You might be the froggiest person i have ever seen! :laughing: :frog:

Welcome @happty_dog2022 :enos:

LET US ALL LOVE LAIN

1 Like