Update after further testing: detaching and re-attaching atkbd alone is
not sufficient. The serio bus auto-rebinds atkbd immediately after it is
unbound, so the broken resume path still runs, and re-probing atkbd
after resume can still fail to enable the keyboard.
The reliable userspace workaround is to reinitialize the i8042
controller after resume:
echo -n i8042 > /sys/bus/platform/drivers/i8042/unbind
sleep 1
echo -n i8042 > /sys/bus/platform/drivers/i8042/bind
This reinitializes the KBD port; atkbd then enumerates the keyboard on a
new serio port and the keyboard responds again. If keyd is running, do
not restart it while user.slice is frozen: leave it running so its
inotify watch re-grabs the new input device, which also keeps the
compositor's virtual keyboard intact.
The proposed atkbd DMI quirk remains the proper fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2171389
Title:
atkbd: keyboard disabled after s2idle resume on MECHREVO WUJIE Series
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2171389/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
