Keyboard uunresponsive after resume from suspend
up vote
0
down vote
favorite
If I suspend my laptop to RAM and wake it back up both keyboard and mouse are stuck for a few seconds (external USB mouse works fine when connected.) after which mouse starts working. The keyboard either wont work at all or rarely gets stuck on same input repeatedly sending same character. Ive had this issue for last 3 ubuntu releases before which it worked fine.
I've tried solutions here, and here. My command line includes atkbd.reset=1 i8042.direct i8042.dumbkbd none of them seems to help. What i have tried:
atkbd.reset=1 i8042.nomux=1 i8042.reset=1 i8042.nopnp=1 i8042.dumbkbd=1 i8042.direct
dmesg | grep i8042 output:
[ 1.495444] i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[ 1.498084] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.498089] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.648255] input: AT Raw Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[ 2.364299] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5
[ 225.155223] i8042: Can't write CTR while closing AUX port
[ 225.671941] i8042: Can't reactivate AUX port
[ 226.236540] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input15
[ 226.889445] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input17
[ 260.835043] i8042: Can't write CTR while closing AUX port
[ 261.351775] i8042: Can't reactivate AUX port
[ 261.908339] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input19
[ 262.480772] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input21
[ 286.021240] i8042: Can't write CTR while closing AUX port
[ 286.537976] i8042: Can't reactivate AUX port
[ 287.088777] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input23
[ 287.643256] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input25
Looks like it is initializing kbd and mouse as new devices but isn't setting up the keyboard correctly.
keyboard 18.04 mouse suspend
add a comment |
up vote
0
down vote
favorite
If I suspend my laptop to RAM and wake it back up both keyboard and mouse are stuck for a few seconds (external USB mouse works fine when connected.) after which mouse starts working. The keyboard either wont work at all or rarely gets stuck on same input repeatedly sending same character. Ive had this issue for last 3 ubuntu releases before which it worked fine.
I've tried solutions here, and here. My command line includes atkbd.reset=1 i8042.direct i8042.dumbkbd none of them seems to help. What i have tried:
atkbd.reset=1 i8042.nomux=1 i8042.reset=1 i8042.nopnp=1 i8042.dumbkbd=1 i8042.direct
dmesg | grep i8042 output:
[ 1.495444] i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[ 1.498084] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.498089] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.648255] input: AT Raw Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[ 2.364299] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5
[ 225.155223] i8042: Can't write CTR while closing AUX port
[ 225.671941] i8042: Can't reactivate AUX port
[ 226.236540] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input15
[ 226.889445] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input17
[ 260.835043] i8042: Can't write CTR while closing AUX port
[ 261.351775] i8042: Can't reactivate AUX port
[ 261.908339] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input19
[ 262.480772] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input21
[ 286.021240] i8042: Can't write CTR while closing AUX port
[ 286.537976] i8042: Can't reactivate AUX port
[ 287.088777] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input23
[ 287.643256] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input25
Looks like it is initializing kbd and mouse as new devices but isn't setting up the keyboard correctly.
keyboard 18.04 mouse suspend
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
If I suspend my laptop to RAM and wake it back up both keyboard and mouse are stuck for a few seconds (external USB mouse works fine when connected.) after which mouse starts working. The keyboard either wont work at all or rarely gets stuck on same input repeatedly sending same character. Ive had this issue for last 3 ubuntu releases before which it worked fine.
I've tried solutions here, and here. My command line includes atkbd.reset=1 i8042.direct i8042.dumbkbd none of them seems to help. What i have tried:
atkbd.reset=1 i8042.nomux=1 i8042.reset=1 i8042.nopnp=1 i8042.dumbkbd=1 i8042.direct
dmesg | grep i8042 output:
[ 1.495444] i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[ 1.498084] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.498089] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.648255] input: AT Raw Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[ 2.364299] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5
[ 225.155223] i8042: Can't write CTR while closing AUX port
[ 225.671941] i8042: Can't reactivate AUX port
[ 226.236540] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input15
[ 226.889445] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input17
[ 260.835043] i8042: Can't write CTR while closing AUX port
[ 261.351775] i8042: Can't reactivate AUX port
[ 261.908339] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input19
[ 262.480772] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input21
[ 286.021240] i8042: Can't write CTR while closing AUX port
[ 286.537976] i8042: Can't reactivate AUX port
[ 287.088777] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input23
[ 287.643256] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input25
Looks like it is initializing kbd and mouse as new devices but isn't setting up the keyboard correctly.
keyboard 18.04 mouse suspend
If I suspend my laptop to RAM and wake it back up both keyboard and mouse are stuck for a few seconds (external USB mouse works fine when connected.) after which mouse starts working. The keyboard either wont work at all or rarely gets stuck on same input repeatedly sending same character. Ive had this issue for last 3 ubuntu releases before which it worked fine.
I've tried solutions here, and here. My command line includes atkbd.reset=1 i8042.direct i8042.dumbkbd none of them seems to help. What i have tried:
atkbd.reset=1 i8042.nomux=1 i8042.reset=1 i8042.nopnp=1 i8042.dumbkbd=1 i8042.direct
dmesg | grep i8042 output:
[ 1.495444] i8042: PNP: PS/2 Controller [PNP030b:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[ 1.498084] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.498089] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.648255] input: AT Raw Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[ 2.364299] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input5
[ 225.155223] i8042: Can't write CTR while closing AUX port
[ 225.671941] i8042: Can't reactivate AUX port
[ 226.236540] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input15
[ 226.889445] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input17
[ 260.835043] i8042: Can't write CTR while closing AUX port
[ 261.351775] i8042: Can't reactivate AUX port
[ 261.908339] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input19
[ 262.480772] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input21
[ 286.021240] i8042: Can't write CTR while closing AUX port
[ 286.537976] i8042: Can't reactivate AUX port
[ 287.088777] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input23
[ 287.643256] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input25
Looks like it is initializing kbd and mouse as new devices but isn't setting up the keyboard correctly.
keyboard 18.04 mouse suspend
keyboard 18.04 mouse suspend
asked Aug 1 at 21:33
Roh_mish
1013
1013
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
I have a laptop with the i8042 device, too. I noticed that when the machine resumed after a suspend, that the dmesg
command showed log entries with
rfkill: input handler
which is supposed to enable and disable wireless.
Since the keyboard is also an input device, I wondered if rfkill
might be impacting the keyboard in some way. So I disabled rfkill
by doing:
sudo mv /usr/sbin/rfkill /usr/sbin/rfkill.disabled
After rebooting, the problem with the keyboard has gone away for the past 2 days, despite multiple tests over many hours, to reproduce the problem. However, control over turning WiFi on/off is gone from the desktop.
If you see rfkill
in your dmesg
output, you might give this a try.
New contributor
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
I have a laptop with the i8042 device, too. I noticed that when the machine resumed after a suspend, that the dmesg
command showed log entries with
rfkill: input handler
which is supposed to enable and disable wireless.
Since the keyboard is also an input device, I wondered if rfkill
might be impacting the keyboard in some way. So I disabled rfkill
by doing:
sudo mv /usr/sbin/rfkill /usr/sbin/rfkill.disabled
After rebooting, the problem with the keyboard has gone away for the past 2 days, despite multiple tests over many hours, to reproduce the problem. However, control over turning WiFi on/off is gone from the desktop.
If you see rfkill
in your dmesg
output, you might give this a try.
New contributor
add a comment |
up vote
1
down vote
I have a laptop with the i8042 device, too. I noticed that when the machine resumed after a suspend, that the dmesg
command showed log entries with
rfkill: input handler
which is supposed to enable and disable wireless.
Since the keyboard is also an input device, I wondered if rfkill
might be impacting the keyboard in some way. So I disabled rfkill
by doing:
sudo mv /usr/sbin/rfkill /usr/sbin/rfkill.disabled
After rebooting, the problem with the keyboard has gone away for the past 2 days, despite multiple tests over many hours, to reproduce the problem. However, control over turning WiFi on/off is gone from the desktop.
If you see rfkill
in your dmesg
output, you might give this a try.
New contributor
add a comment |
up vote
1
down vote
up vote
1
down vote
I have a laptop with the i8042 device, too. I noticed that when the machine resumed after a suspend, that the dmesg
command showed log entries with
rfkill: input handler
which is supposed to enable and disable wireless.
Since the keyboard is also an input device, I wondered if rfkill
might be impacting the keyboard in some way. So I disabled rfkill
by doing:
sudo mv /usr/sbin/rfkill /usr/sbin/rfkill.disabled
After rebooting, the problem with the keyboard has gone away for the past 2 days, despite multiple tests over many hours, to reproduce the problem. However, control over turning WiFi on/off is gone from the desktop.
If you see rfkill
in your dmesg
output, you might give this a try.
New contributor
I have a laptop with the i8042 device, too. I noticed that when the machine resumed after a suspend, that the dmesg
command showed log entries with
rfkill: input handler
which is supposed to enable and disable wireless.
Since the keyboard is also an input device, I wondered if rfkill
might be impacting the keyboard in some way. So I disabled rfkill
by doing:
sudo mv /usr/sbin/rfkill /usr/sbin/rfkill.disabled
After rebooting, the problem with the keyboard has gone away for the past 2 days, despite multiple tests over many hours, to reproduce the problem. However, control over turning WiFi on/off is gone from the desktop.
If you see rfkill
in your dmesg
output, you might give this a try.
New contributor
edited 2 days ago
zx485
1,43831114
1,43831114
New contributor
answered Nov 19 at 22:39
Glen
111
111
New contributor
New contributor
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1061565%2fkeyboard-uunresponsive-after-resume-from-suspend%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown