Kernel Bug Tracker – Bug 58991
[BISECTED]Notebook keyboard not working after update to 3.9.4
Last modified: 2014-10-14 09:40:46 UTC
After updating the kernel to 3.9.4-200 no input is accepted from the integrated notebook keyboard at any init level or in rescue mode.
The keyboard only works if I fall back to 3.8.11-200.fc18.i686.
Excerpt from /etc/default/grub:
GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm.lv=vg_mercury/lv_swap rd.dm=0 rd.lvm.lv=vg_mercury/lv_root KEYMAP=us FONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8"
vendor: LG Electronics Inc.
version: Not Applicable
width: 32 bits
capabilities: smbios-2.31 dmi-2.31
[ 2.426475] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4
As of kernel 3.10.5-201.fc19.i686 this has still not been resolved. I refer to
Where there are many reports of this problem.
This bug has been around for awhile guys.
I have a hard time believing that nobody in kernel land thinks that this is not important enough to bother with.
Please fix it.
The kernel bugzilla is just used to track problem. You need to discuss fixing it with whoever your support partner or distribution is.
It is being tracked at:
The problem, as you can see has been round since the end May this year with kernel 3.9.4 and the kernel has gone through 2 major revisions since then with no fix in sight. The problem still persists with 3.11.8
We lowly users (bow bow - just kidding) have no ability fix this ourselves. Distributors have no way to fix this.
Whose gonna fix this???
Your distribution if you are only running distribution kernels.
If you can verify the workaround and also build some kernels to bisect the problem then it may get more direct involvement.
Right now there is insufficient info to even guess why some random laptop with a load of out of tree drivers in it is breaking
Thanks for your postive response.
I realize that getting to every laptop in the whole world would be difficult, but it would seem that this is a whole family of laptops. The problem appeared at at a specific juncture.
Kernels prior to 3.9.4-200.fc18.i686 worked. That is kernel-3.9.3-201.fc18 and previous kernels worked just fine. After 3.9.4-200.fc18.i686 and consquently 3.9.4-200.fc19.i686 the problem appears and persists to the current kernel build available. And the dmesg output is available over several kernel build in the redhat bugzilla bug report mentioned above.
It would be difficult to go back to fc18, as such, if you really do need a bisection with this info I will do what I can to get it done, provided I have some hand holding on how to go about doing it.
I'm looking forward to your response :)
Oh.... I will see if the workaround allows for the keyboard to work. With the limitations mentioned in the redhat bugzilla bug report and get back to you within a day or so.
Just tested the workaround.
Indeed i8042.dumbkbd=1 allows me type with the built in keyboard, but, as reported, the [fn] key is disfuntional
Ok thats very helpful as a starting point and playing "guess where the bug might be"
You shouldn't need to drop a release to test different kernels built for bisecting the problem - especially as it seems you just need to boot to a command line and press a few keys to check.
As you are running Fedora I think the relevant document and guide on bisection is
also has some discussion on doing it in Fedora
is a general howto with more detail
Roughly speaking the idea is that you find a good kernel and a bad kernel and git bisect then does the minimal number of in betwen kernel builds to find which specific change to the kernel caused the problem.
*** Bug 65791 has been marked as a duplicate of this bug. ***
> After updating the kernel to 3.9.4-200 no input is accepted from the integrated notebook keyboard at any init level or in rescue mode.
BTW as I noted in that duplicate bug, 3.9.0 seems to be the exact version where the bug appears, at least for my LG LW25 laptop.
A kernel bisect suggests that the first bad commit is:
Input: atkbd - fix multi-byte scancode handling on reconnect
it's not just LG.
HP ProBook 4730s has the same problem.
Debian Testing amd64 with 3.12.6-2 kernel
$ dmesg|grep keyboard
[ 1.076507] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 4104.610482] atkbd serio0: Failed to enable keyboard on isa0060/serio0
[17396.052022] atkbd serio0: Failed to deactivate keyboard on isa0060/serio0
[17396.360274] atkbd serio0: Failed to enable keyboard on isa0060/serio0
[34176.156200] atkbd serio0: Failed to enable keyboard on isa0060/serio0
I am working on a fix on the issue.
If you see a similar keyboard issue,
could you collect the output of "sudo dmidecode" from your labtop/computer?
I am not sure the issue you saw is the same issue that Joonas reported.
Could you cherry-pick changes from here and help me to verify it on HP ProBook 4730s?
Created attachment 132981 [details]
i'm also starting to think that it's not the same bug.
actually at the moment the onboard keyboard is working. since i'm using an
USB keyboard i didnt notice when it started working again.
so you can remove my laptop form the atkbd_deactivate_rst_fixup
ill get with you in touch if it happens again.
On Fri, Apr 18, 2014 at 11:32 PM, <firstname.lastname@example.org>wrote:
> --- Comment #15 from Shengliang Song <email@example.com> ---
> Hi Davor,
> I am not sure the issue you saw is the same issue that Joonas reported.
> Could you cherry-pick changes from here and help me to verify it on HP
> Shengliang Song
> You are receiving this mail because:
> You are on the CC list for the bug.
Created attachment 139841 [details]
Result of command dmidecode on HP Probook 4730s
I have a similar issue on my laptop HP Probook 4730s with mint 17.
Hope it helps
I'm actually searching for a solution for the keyboard malfunction of my LG S1 Pro Express Dual. The problem occurred after system upgrade from OpenSuse 12.3 to 13.1, which included the Kernel upgrade from 3.7.10-1 to 3.11.10-7.
I found that Shengliang did a correction with Kernel 126.96.36.199 (Input: atkbd - fix keyboard not working on some LG laptops).
Unfortunately, even with the actual Kernel of OpenSuse 3.11.10-21 it doesn't work.
Is there still anybody working on this issue?
I found now in other threads (Fedora, Ubuntu) a workaround
'quiet splash i8042.dumbkbd=1' which works for me as well.
Besides some functionality is still missing, I'd really appreciate to solve this problem.
Release of OpenSuse 13.2 is planned shortly (in 32 Days).
The problem on LG laptops should be fixed with:
Author: Dmitry Torokhov <firstname.lastname@example.org>
Date: Wed Sep 10 13:50:37 2014 -0700
Input: atkbd - do not try 'deactivate' keyboard on any LG laptops
We are getting more and more reports about LG laptops not having
functioning keyboard if we try to deactivate keyboard during probe.
Given that having keyboard deactivated is merely "nice to have"
instead of a hard requirement for probing, let's disable it on all
LG boxes instead of trying to hunt down particular models.
This change is prompted by patches trying to add "LG Electronics"/"ROCKY"
and "LG Electronics"/"LW60-F27B" to the DMI list.
Reported-by: Jaime Velasco Juan <email@example.com>
Reported-by: Georgios Tsalikis <firstname.lastname@example.org>
Tested-by: Jaime Velasco Juan <email@example.com>
Signed-off-by: Dmitry Torokhov <firstname.lastname@example.org>
for all others please open a new issue.
Created attachment 153731 [details]
Javi:: vrućeadd e f cd obii čovićk grbv.d p::vkbtv
On Apr 16, 2014 2:40 AM, <email@example.com> wrote:
> Shengliang Song <firstname.lastname@example.org> changed:
> What |Removed |Added
> CC| |email@example.com
> --- Comment #14 from Shengliang Song <firstname.lastname@example.org> ---
> I am working on a fix on the issue.
> If you see a similar keyboard issue,
> could you collect the output of "sudo dmidecode" from your labtop/computer?
> You are receiving this mail because:
> You are on the CC list for the bug.