I had the exact same problems with my Mx master 3 mouse when used in Bluetooth mode. But with the USB dongle it works fine
Are you using package solaar? That might help.
I’m only using solaar to pair the device initially to the receiver. It then stays paired for good. there’s no need for a special software for wireless mice. I mean the keyboard at least runs perfectly even in BIOS, so i assume the peripheral is seen by the system as a wired device.
Anyway, my intention was not to hijack the thread. I simply wanted to point out that these kinds of occurrences happen with other pointing devices, so this might not be a hardware specific thing.
1 Like
The opptopic stil here? 
1 Like
Here’s some coffee 
2 Likes
Thank you, i only have xf86-input-libinput actually, should i try xf86-input-evdev and reboot?
1 Like
The touchpad should be listed as “ELAN Microelectronics”
Either
lsusb
Or
lspci
Ok, so i had installed + reboot, don’t see touchpad listed still, other than that it works exactly the same…Will have to see if that package changed random behavior on boot, need some time 
lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 27c6:581a Shenzhen Goodix Technology Co.,Ltd. FingerPrint
Bus 003 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 003 Device 002: ID 13d3:5471 IMC Networks XiaoMi Webcam
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
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)
For the backlight issue try one of the following kernel parameters.
acpi_backlight=video
acpi_backlight=vendor
acpi_backlight=native
2 Likes
@happty_dog2022
I looked at the Arch wiki for the Xiaomi Notebook Air and it say’s using xf86-input-evdev makes the touchpad act like a touchscreen so you might not want that. So maybe uninstall that and try the xorg file.
xorg file
/etc/X11/xorg.conf.d/20-touchpad.conf
Section "InputClass"
Identifier "libinput touchpad"
Driver "libinput"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "Tapping" "on"
Option "ClickMethod" "clickfinger"
Option "NaturalScrolling" "true"
EndSection
https://wiki.archlinux.org/title/Xiaomi_Mi_Notebook_Air_13.3_(2018_Global_version)#Input
stil hard to find which type of touchpad… my old laptop (just junk) need i2c-tools and setup in bios as it can recognized atleast. it a option to install i2c-tools
It is probably run on i2c
I think i would try some of the other kernel parameters also such as
i8042.nopnp
i8042.reset
i8042.noloop
i8042.nomux
in my cursed acer only make it work in bios to on or off… and installing i2c-tools from repo… but is a bit guess.
I think on the Xiaomi Mi some other hardware is hogging the bus for the trackpad? Maybe?
Found something that might help: https://unix.stackexchange.com/questions/28736/what-does-the-i8042-nomux-1-kernel-option-do-during-booting-of-ubuntu
Also this provides information about kernel parameters like i8042: https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt
Maybe adding kernel parameter i8042.reset helps? Worth looking at the kernel parameters.
3 Likes
I assume this one you mean for those errors?
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.
It’s not that i had problems with backlight, it worked perfectly fine, however when i’ve tried acpi_backlight=video there are no errors listed in journal anymore, so it had to be good, right? 
I’m sorry, but i’ll ignore advises from https://wiki.archlinux.org/title/Xiaomi_Mi_Notebook_Air_13.3_(2018_Global_version)#Input it doesn’t look logical to follow, because my model has very different hardware https://wiki.archlinux.org/title/Xiaomi_Mi_Notebook_Pro_15.6, in fact to all other Xiaomi models as far as my searching ability goes.
@manuel
Thank you, i will try that and see if it helps, again will need some time to check because it’s random 
2 Likes