I have Secure Boot disabled in the BIOS, I assume that’s what you mean with fastboot? However, there is a fastboot option in Windows.
I’ll dig into the kernel parameter subject later, although I am losing faith in a positive outcome
I regularly read, e.g on the Arch wiki, that sometimes the touchpad stops working, and it also gets detected with dmesg. In my case it never ever worked even once.
I checked dmesg, with 'grep i -touchpad or grep “SYN” it doesn´t find anything at all.
I do get some results with 'sudo dmesg | grep i2c, but as you can see, nothing related to that cursed touchpad.
4.325031] input: WACF2200:00 056A:5218 Touchscreen as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input13
[ 4.356647] input: WACF2200:00 056A:5218 as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input14
[ 4.356679] input: WACF2200:00 056A:5218 as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input15
[ 4.356716] input: WACF2200:00 056A:5218 as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input16
[ 4.356746] input: WACF2200:00 056A:5218 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input17
[ 4.356794] hid-generic 0018:056A:5218.0005: input,hidraw4: I2C HID v1.00 Mouse [WACF2200:00 056A:5218] on i2c-WACF2200:00
[ 4.601284] input: Wacom HID 5218 Pen as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input25
[ 4.601441] input: Wacom HID 5218 Finger as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input26
[ 4.601582] wacom 0018:056A:5218.0005: hidraw2: I2C HID v1.00 Mouse [WACF2200:00 056A:5218] on i2c-WACF2200:00
I also was hoping that it showed some life, but when pressing/touching the touchpad with journalctl -f active, it doesn’t detect anything related to the touchpad at all, although the keyboard lights up. It only detects input from my external mouse. I also tried to disconnect the external one, no succes either.
It’s getting pretty late now, but I’m quite familiar with the terminal, so I will dive in your last suggestion. And before I forget, thanks for the great help!
No.
Fastboot in both Windows and BIOS.
If it is enabled and being used (Windows settings, find it), it’s the most probable reason to your issue. That’s why it was 1st in my list
I took a quick look at these udev and udevadm pages, but it’s gonna take me a bit more time to dive into it.
I did notice that where it showed you -
/70-touchpad.rules:KERNELS=="input - , in my case it didn’t show ‘=="input’, it showed ‘!="input’.
About the Fast boot Options, in Windows I was able to disable it after I enabled hibernation (with hibernation disabled the option was greyed out or not even available at all). When it comes to Fast boot options in the BIOS, i haven’t been able to locate that option yet.
My other notebook, a Lenovo Silm 7 14ARE05, has a hacked BIOS, and has so much more configuration options. I’m almost tempted to do the same with my Flex 5 14ARE05, I own an SPI Flasher and a SOCI8 clip. I can create a dump of the current BIOS, so if something would go wrong, it’s pretty easy to revert the changes.
Then once I got the dump of the original BIOS, I can patch it and flash the ROM chip with the modified BIOS, which adds many more options, also quite a few that are related to the touchpad settings.
Of course I prefer getting the touchpad to work without any of this, but to be honest, I am not very confident that there will be a proper solution anytime soon. And the main reason that I bought this laptop, was Linux ;(.
It seems that I am one of the very few people that never even got the touchpad detected, let alone having it in a working state.
This is a systemd provided file. You can’t have it differ.
Check complete file
$ cat /usr/lib/udev/rules.d/70-touchpad.rules
# do not edit this file, it will be overwritten on update
ACTION=="remove", GOTO="touchpad_end"
ENV{ID_INPUT}=="", GOTO="touchpad_end"
ENV{ID_INPUT_TOUCHPAD}=="", GOTO="touchpad_end"
KERNEL!="event*", GOTO="touchpad_end"
# touchpad:<subsystem>:v<vid>p<pid>:name:<name>:*
KERNELS=="input*", ENV{ID_BUS}!="", \
IMPORT{builtin}="hwdb 'touchpad:$env{ID_BUS}:v$attr{id/vendor}p$attr{id/product}:name:$attr{name}:'", \
GOTO="touchpad_end"
LABEL="touchpad_end"
I’ve never read that! Go away devil!..
You may report to the kernel tracker for such hardware driver issues. It is more productive
It could be a simple kernel parameter, or module option…
If not necessary, I´d rather don´t do stuff like that either, but my Yoga Slim 7’s BIOS got a huge amount of extra options. For example, it’s possible to allocate more than the 512MB to the integrated GPU. RAID 0 with 2 Nvme drives became an option, S3 sleep state became available (which wasn´t present in the original BIOS , without that there were some serious issues when running linux, e.g. not being able to wake it up ;). And many more options that might be interesting for some people.
Anyway, I have been fiddling with Garuda again, I don´t want to abandon the eye-candy Arch distro, so I am motivated to keep trying to get the touchpad to work.
Finally I made some progress, it’s for the first time that it actually got recognized!
dmesg | grep i2c
[] × sudo dmesg |grep i2c
[ 6.289834] i2c_hid_acpi i2c-MSFT0001:00: hid_descr_cmd failed
[ 6.289839] i2c_hid_acpi i2c-MSFT0001:00: Failed to fetch the HID Descriptor
[ 6.460265] input: WACF2200:00 056A:5218 Touchscreen as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/i
nput/input13
[ 6.499720] input: WACF2200:00 056A:5218 as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input14
[ 6.499917] input: WACF2200:00 056A:5218 as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input15
[ 6.500148] input: WACF2200:00 056A:5218 as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input16
[ 6.500284] input: WACF2200:00 056A:5218 Mouse as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/i
nput17
[ 6.500422] hid-generic 0018:056A:5218.0005: input,hidraw4: I2C HID v1.00 Mouse [WACF2200:00 056A:5218] on i2c-WACF2200:00
[ 7.380376] input: Wacom HID 5218 Pen as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input30
[ 7.380454] input: Wacom HID 5218 Finger as /devices/platform/AMDI0010:00/i2c-0/i2c-WACF2200:00/0018:056A:5218.0005/input/input31
[ 7.380511] wacom 0018:056A:5218.0005: hidraw4: I2C HID v1.00 Mouse [WACF2200:00 056A:5218] on i2c-WACF2200:00
Unfortunately I have to go to work now, so I can´t dig deeper in this issue right now. When I’ll be back home later, I will continue trouble shooting, but maybe someone here is already familiar with that issue
I'm glad you found a working kernel. As best I understand, 5.14-rc is not full of radical changes, mostly it's additional (and newer) hardware support. On my old baytrail 2-in-1, I waited over a year for sound support... These days, many of the prepatch(-rc) kernels are pretty stable. The "mainline" kernel will be officially stable in about another month.
I'm new to garuda and linux in general , but was thinking of trying it out when I buy this specific laptop. Does anybody know if this touchpad "bug" has been fixed by the release of the latest kernel?Also nice to see a fellow greek in these forums @petsam
In this topic is reported fixed in the linux-mainline kernel.
chaotic-aur/linux-mainline 5.14rc4-1
In Garuda, you can install this kernel like any other kernel in repos.
It is not yet released from kernel upstream devs as stable, so it’s a per user/system decision to install it when/if your HW needs it.
Of course, sometime it will be released and archlinux will ship it as default linux package.
Btw, does anyone of you having issues using tthe built in kernel installer?
Some kernels installed properly, but another kernel I installed the traditional way by downloading the tarball, extract, generate/modify the .config file and then compile it (and all the rest that is needed to boot that kernel).
I thought I might as well show the touchpad settings now that I'm on my lunch break and told my boss I'll continue working from home for the rest of the day.
All options that I've tested, worked perfectly. And luckily the touchscreen also works as intented, although that's something I'd probably use more with some Windows applications.