--- Comment #27 from Takashi Iwai email@example.com --- (In reply to Artyom from comment #24)
(In reply to Takashi Iwai from comment #23)
Hrm, my kernel merely changed the suspend/resume functions and nothing else, so the behavior change except for suspend/resume isn't expected. And, it doesn't change the binding, so the blacklist is still necessary. It was asked only for testing the suspend/resume problem.
You should install only kernel-default.rpm, nothing else. At easiest, download kernel-default-5.15*.rpm from the URL and install it manually via zypper install.
Oh, my bad... My current fix is disabling touchpad service on startup (backgroud services on kde) - then it doesn't disable after suspend :) but fix for that would be too cool because in my case touchpad is enabled in suspend mode (it still consume electricity), also it's not possible to run this service manually (failed to start touchpad service) Also there strange enabled status when it broken For fixing after suspend/resume needs (maybe your kernel unbind elan_i2c?) # echo -n "i2c-ELAN0000:00" > /sys/bus/i2c/drivers/i2c_hid_acpi/unbind # echo -n "i2c-ELAN0000:00" > /sys/bus/i2c/drivers/i2c_hid_acpi/bind Maybe problem with touchpad service ?
Is this behavior (jumping pointer?) with the unpatched kernel? I expected that the patch may influence on this.
In anyway, if not done yet, please check the following with the patched kernel: - Boot with the blacklist - Try suspend / resume without re-binding and let me know which problem is present.
FWIW, Fedora kernel "works" because the device is bound with i2c-hid, not elantech. Maybe they have some workaround in it or it's just a matter of device binding order that casually worked. But the suspend/resume problem should remain with them unless any fix is applied.