Hotkeys not detected on Asus F3sv (ACPI events)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Corentin Chary |
Bug Description
Hi
Using jaunty fully updated (with live cd or with an upgraded intrepid), some hotkeys are not working on my laptop (asus f3sv).
I followed the procedure there: https:/
The hotkeys that are not working are sending ACPI events but no input event is generated. This is the list og these keys:
"hotkey ATKD 00000050 00000000" -> should launch email client
"hotkey ATKD 00000051 00000000" -> should launch web browser
"hotkey ATKD 00000061 00000000" -> switch between LCD/external monitor (Maybe this one works, I couldn't test).
"hotkey ATKD 0000005c 00000000" -> lock the screen
"hotkey ATKD 00000095 00000000" -> the manual says "Launches a multimedia application (cd/dvd, tv, video, audio)".
"hotkey ATKD 0000008a 00000000" -> the manual says "Switch between different color, brightness, sharpness and contrast presets".
"hotkey ATKD 00000082 00000000" -> should launch a webcam app (cheese for example)
"hotkey ATKD 00000099 00000000" -> the manual says "Activate or desativate "Power for Phone"", I think launching ekiga would be ok.
Other keys are working great.
Would it be possible to fix this for jaunty? It must be quite trivial to solve with the new hotkeys management architecture?
In case this couldn't be done for jaunty, is there a workaround to make these hotkeys work?
I can provide more info if needed.
Thanks.
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
MachineType: ASUSTeK Computer Inc. F3Sv
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: root=UUID=
ProcEnviron:
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: linux
Looking at asus-laptop module code in 2.6.29 (http:// git.kernel. org/?p= linux/kernel/ git/stable/ linux-2. 6.29.y. git;a=blob; f=drivers/ platform/ x86/asus- laptop. c;h=eeafc6c0160 dbe41b827a627f7 7c842d396adbd6; hb=8d7bff2d7266 0d9d60aa371ae3d 1356bbf329a09) it seems like it is solved in 2.6.29 (I didn't test it).
So is there some way to backport this module?