| 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
| ||
|
Date: Sat, 15 Sep 2012 07:48:44 -0700 (PDT) From: Chris Rankin <rankincj@...oo.com> To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Cc: "linux-input@...r.kernel.org" <linux-input@...r.kernel.org> Subject: [BUG][3.5.4] No keyboard without i8042_nokbd=1 parameter Hi, I have recently upgraded my oldest PC from 3.4.8 to 3.5.4, but was puzzled to discover that the keyboard no longer worked unless I also added the i8042_nokbd=1 boot parameter. It turns out that 3.4.8 didn't use the i8042 keyboard device anyway: >From 3.4.8: ... i8042 aux: probe of 00:07 failed with error -16 i8042: PNP: PS/2 Controller [PNP0303] at 0x60,0x64 irq 1 i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp serio: i8042 KBD port at 0x60,0x64 irq 1 mousedev: PS/2 mouse device common for all mice TCP: cubic registered Registering the dns_resolver key type Using IPI Shortcut mode Freeing unused kernel memory: 268k freed Write protecting the kernel text: 1628k Write protecting the kernel read-only data: 580k input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 ... Hence adding the i8042_nokbd=1 parameter merely forces the kernel to do again what it used to do automatically.Does anyone have any theories as to why the 3.5.x kernel now needs help to set the keyboard up correctly, please? Thanks, Chris -- 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/
Powered by blists - more mailing lists