As a solution (until the binding of this device is fixed in the linux kernel), I blacklisted this driver in the kernel command line, as described in https://unix.stackexchange.com/a/474552/4319 :
First, find function names which look like initialization functions of this module: # fgrep elants /boot/System.map-5.8.0-23-generic | fgrep init ffffffff818f3430 t elants_i2c_initialize ffffffff818f40bf t elants_i2c_initialize.cold ffffffff829253f5 t elants_i2c_driver_init ffffffff82af7a30 t __initcall_elants_i2c_driver_init6 # The last one (__initcall*) doesn't look like the one we are looking for. Then add them to the kernel parameters in /etc/default/grub (on Ubuntu) GRUB_CMDLINE_LINUX_DEFAULT="... initcall_blacklist=elants_i2c_initialize initcall_blacklist=elants_i2c_initialize.cold initcall_blacklist=elants_i2c_driver_init" and run update-grub. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900254 Title: fails to suspend unless I unbind a device from elants_i2c driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1900254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
