can't use keyboard after resume from suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Many times (around ~60% of them), resuming my laptop from suspend results in a not-working keyboard.
Solution/Workaround is: close lid, let it suspend again, and try to resume until keyboard gets working again.
Another solution is: plug an usb keyboard, and run something like "modprobe usbhid" or "modprobe hid", and this unblocks also the laptop keyboard.
Probably this is a bug in the kernel, but I have not enough knowledge to understand where it is located (maybe we can add some systemd hooks in /lib/systemd to catch such events and reload the kernel modules?)
G.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu12
ProcVersionSign
Uname: Linux 4.4.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Dec 15 16:15:08 2016
InstallationDate: Installed on 2016-05-11 (217 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Acer Aspire V3-772G
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.13
dmi.board.
dmi.board.name: VA70_HW
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.name: Aspire V3-772G
dmi.product.
dmi.sys.vendor: Acer
Changed in systemd (Ubuntu): | |
status: | New → Won't Fix |
I seem to have fixed this by adding `atkbd.reset` to my boot parameters.
You can add them to `GRUB_CMDLINE_ LINUX` and `GRUB_CMDLINE_ LINUX_DEFAULT` in `/etc/default/grub` then `sudo update-grub` for them to apply on every boot.