linux-kernel - Keyboard dead for a bunch of LG laptops

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <52E29310.1040600@saunalahti.fi>
Date:	Fri, 24 Jan 2014 18:21:36 +0200
From:	Joonas Saarinen <jza@...nalahti.fi>
To:	linux-kernel@...r.kernel.org
CC:	shawnn@...omium.org
Subject: Keyboard dead for a bunch of LG laptops

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/