Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12086 - atbkd.c reporting turned off
Attached to Project:
Arch Linux
Opened by H.Gökhan SARI (hsa2) - Tuesday, 11 November 2008, 13:27 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 08 April 2009, 07:43 GMT
Opened by H.Gökhan SARI (hsa2) - Tuesday, 11 November 2008, 13:27 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 08 April 2009, 07:43 GMT
|
DetailsDescription:
Before kernel update, when a button which is unrecognized by kernel is pushed, it was available to see info on 'dmesg' output. Message was something like; atkbd.c: Unknow key pressed (translated set2, code 0xd9 on isa0060/serio0) atkbd.c: Use 'setkeycodes e059 <keycode>' to make it know Now, dmesg gives no such outputs. But it is possible to set these unreported keys' key codes by 'setkeycodes e*** <keycode>' command. What if i didn't know my unidentified keys' signals? Additional info: * i think it's about kernel26 2.6.27.5-1 Steps to reproduce: Push an unrecognized button, and give dmesg command. You won't see anything about this unrecognized button, but, in fact, you should :) |
This task depends upon
Comment by H.Gökhan SARI (hsa2) -
Tuesday, 11 November 2008, 13:29 GMT
Sorry, title should be "atkbd.c".
Comment by Tobias Powalowski (tpowa) -
Monday, 06 April 2009, 17:34 GMT
Is this still an issue?