Either a driver bug or a wrong ACPI DSTD, which in the end the elants_i2c must work around :-(Īnd I already had decompiled the ACPI DSTD to have a look. The elants_i2c wrongly claims the device. Now I'm wondering, what people with a notebook with an Elan touchscreen would do. Just add some startup script doing:Įcho "i2c-ELAN0001:00" > /sys/bus/i2c/drivers/elants_i2c/unbindĮcho "i2c-ELAN0001:00" > /sys/bus/i2c/drivers/i2c_hid/bind Instead of a kernel rebuild, you can simply unbind the device for the built-in module. And didn't register the messages were created by the touchpad actually, since this is the touchscreen driver.Īnd since I managed to brick my HW, I had other things to do ( ), so I could just test this now. I saw these error messages and assumed some larger problem. i2c_hid i2c-ELAN0001:00: supply vddl not found, using dummy regulator i2c_hid i2c-ELAN0001:00: supply vdd not found, using dummy regulator The Touchpad/screen is connected via dmesg | grep ELAN The driver is no longer loaded as built in, but as a module.
Elan input device windows 10 gateway drivers#
I fetched a kernel from (5.6.14 and 5.7.0-rc7).ĭevice Drivers -> Input device support -> Touchscreens -> Elan eKTH I2C touchscreen -> set to m
Same beheaviour for kernel 5.4.xx and 5.6.xx When booting a test Windows10 (sorry.), it works so a HW fault can be excluded. elants_i2c i2c-ELAN0001:00: unknown packet 00 00 ff ff
elants_i2c i2c-ELAN0001:00: Failed to read fw id: -121 elants_i2c i2c-ELAN0001:00: invalid 'hello' packet: 00 00 ff ff elants_i2c i2c-ELAN0001:00: software reset failed: -121 elants_i2c i2c-ELAN0001:00: i2c-ELAN0001:00 supply vccio not found, using dummy regulator elants_i2c i2c-ELAN0001:00: i2c-ELAN0001:00 supply vcc33 not found, using dummy regulator The Elantech Touchscreen is not working in Lenovo Ideapad 5 15.
0 kommentar(er)
