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#17670 - [kernel26] wrong keycode with Fn-key on kernel 2.6.32, no acpi event triggered
Attached to Project:
Arch Linux
Opened by badboy (badboy) - Friday, 01 January 2010, 18:17 GMT
Last edited by Dan Griffiths (Ghost1227) - Saturday, 27 February 2010, 23:12 GMT
Opened by badboy (badboy) - Friday, 01 January 2010, 18:17 GMT
Last edited by Dan Griffiths (Ghost1227) - Saturday, 27 February 2010, 23:12 GMT
|
DetailsDescription:
Fn+F8 sends wrong keycode on my laptop. with Kernel 2.6.31 I get the following output with xev: keycode 235 (keysym 0x1008ff59, XF86Display) on Kernel 2.6.32 the output is keycode 33 (keysym 0x70, p) acpi_listen puts out the following when pressing Fn+F8 on Kernel 2.6.31 video GFX0 00000080 00000000 on 2.6.32 nothing happens, no acpi event is triggered I don't know if this is a upstream bug or related to Arch's default kernel config Additional info: * package version(s) $ uname -a Linux harmless 2.6.32-ARCH #1 SMP PREEMPT Sat Dec 26 09:02:58 CET 2009 x86_64 Intel(R) Core(TM)2 Duo CPU T6670 @ 2.20GHz GenuineIntel GNU/Linux $ pacman -Q kernel26 kernel26 2.6.32.2-2 Steps to reproduce: update kernel26 to latest core package (2.6.32.2-2) |
This task depends upon
Closed by Dan Griffiths (Ghost1227)
Saturday, 27 February 2010, 23:12 GMT
Reason for closing: No response
Additional comments about closing: No response in +1 month. Please reopen if necessary with a link to upstream.
Saturday, 27 February 2010, 23:12 GMT
Reason for closing: No response
Additional comments about closing: No response in +1 month. Please reopen if necessary with a link to upstream.
anyone knows if this is a upstream bug or related to arch's default config?
If it's upstream maybe I can ask on some Linux Kernel Mailing List ;)