From: Joonas Saarinen <jza@saunalahti.fi>
To: linux-kernel@vger.kernel.org
Cc: shawnn@chromium.org
Subject: Keyboard dead for a bunch of LG laptops
Date: Fri, 24 Jan 2014 18:21:36 +0200 [thread overview]
Message-ID: <52E29310.1040600@saunalahti.fi> (raw)
Hello, people! There's still lingering an interesting regression where
the internal keyboard of various older LG laptops is dead. It is tracked
here:
https://bugzilla.kernel.org/show_bug.cgi?id=58991
Downstream:
https://bugzilla.redhat.com/show_bug.cgi?id=969550
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243904
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256776
Late last year, I personally did a git bisect on LG LW25 which ended up
pointing at an atkbd patch:
be2d7e4233a4fe439125b825470020cef83407d5
Input: atkbd - fix multi-byte scancode handling on reconnect
Full description about that patch and some discussion:
https://groups.google.com/forum/#!topic/fa.linux.kernel/rUpZ8-HaQIM
Could it be that? The boot parameter i8042.dumbkbd=1 can be used to
still make the keyboard functional. Of course that workaround leaves the
keyboard a bit gimped (no lock LEDs, for example).
So, some questions:
1) What exactly happened? Is there something common with these LG
machines' BIOS or keyboard controller firmware which causes the problem?
2) How could this happen? I thought the i8042 keyboard was one of the
simplest devices in a PC. It's quite serious if it stops working like this.
3) Should something be done? Those are of course aging (Core 1 Duo era)
machines, but I think Linux has always strived to work well with all
sorts of hardware, old and new.
Joonas
next reply other threads:[~2014-01-24 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 16:21 Joonas Saarinen [this message]
2014-01-24 16:52 ` Shawn N
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52E29310.1040600@saunalahti.fi \
--to=jza@saunalahti.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=shawnn@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®