Hi everyone, glad to be part of community, what a great OS!
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
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!
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.
Oh yes, i know about it, but when it boots without touchpad working - this button ain’t helping either…
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…
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.
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.
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).