asus eee 1000h Fn and extra buttons (hotkeys) not working

[Γουργιώτης Γιώργος (aka Gourgi)]

Binary package hint: hal-info

i've attached a tar.gz with as much info i could get about the Fn buttons in my Asus EEE 1000H.
i've tested them against 2.6.30-rc6 kernel (and rc8 too).

The archive includes information according the links below
https://wiki.ubuntu.com/Hotkeys/Troubleshooting
http://martinpitt.wordpress.com/2009/05/08/devicekit-update-future-handling-of-fn-key-maps/

Here is a screenshot of the keyboard
http://img15.imageshack.us/img15/2141/asuseeepc1000h.jpg

------------- Summary ------------------
= default configuration 2.6.30-rc6 mainline kernel =

    * [Works=Yes] Fn+F1 Hibernate
    * [Works=NO] Fn+F2 WLAN-toggle
    * [Works=Yes] Fn+F5 Brightness Up
    * [Works=Yes] Fn+F6 Brightness Down
    * [Works=NO] Fn+F7 Lock screen
    * [Works=NO] Fn+F8 VGA-toggle --> runs Volume Up instead
    * [Works=NO] Fn+F9 Taskmanager --> runs ??? instead (i think it disables power manager!)
    * [Works=Yes] Fn+F10 Mute Volume
    * [Works=Yes] Fn+F11 Volume Down
    * [Works=Yes] Fn+F12 Volume Up
    * [Works=Yes] 1. hotkey Suspend
    * [Works=NO] 2. hotkey
    * [Works=NO] 3. hotkey
    * [Works=NO] 4. hotkey

= default configuration (2.6.30-rc6 mainline kernel) (udev-extras installed from Martin Pitt's PPA) =
  the test results was the same as aboce, no difference at all (at least this is good for Martin's udev switch :-D)

Currently i use elmurato's scripts from http://forum.eeeuser.com/viewtopic.php?id=65606 to do what the above buttons supposed to do.
If it is helpful, you can download his scripts from here http://www.informatik.uni-bremen.de/~elmurato/EeePC/Jaunty_Eeeasy-Scripts.tar.gz to see how he is doing it.

Below i post the default configuration from the the Eeeasy scripts:

    * Fn+F1 Standby
    * Fn+F2 WLAN-toggle
    * Fn+F5/F6 Brightness
    * Fn+F7 Lock screen
    * Fn+F8 VGA-toggle
    * Fn+F9 Taskmanager
    * Fn+F10/F11/F12 Volume
    * 1. hotkey Lock screen
    * 2. hotkey Bluetooth-toggle or user-defined
    * 3. hotkey Webcam-toggle or user-defined
    * 4. hotkey CPU frequency control or user-defined

Other Fn buttons on the keyboard that worked on both HAL and udev-extras tests:

    * [Works=Yes] Fn+Ins NumLock
    * [Works=Yes] Fn+Ins ScrollLock
    * [Works=Yes] Fn+LeftArrow Home
    * [Works=Yes] Fn+RightArrow End
    * [Works=Yes] Fn+UpArrow PageUp
    * [Works=Yes] Fn+UpArrow PageDown
    * [Works=Yes] Fn+7 7
    * [Works=Yes] Fn+8 8
    * [Works=Yes] Fn+9 9
    * [Works=Yes] Fn+0 *
    * [Works=Yes] Fn+U 4
    * [Works=Yes] Fn+I 5
    * [Works=Yes] Fn+O 6
    * [Works=Yes] Fn+P - # the minus symbol
    * [Works=Yes] Fn+J 1
    * [Works=Yes] Fn+K 2
    * [Works=Yes] Fn+L 3
    * [Works=Yes] Fn+: + # the plus symbol
    * [Works=Yes] Fn+M 0
    * [Works=Yes] Fn+> , # the comma symbol
    * [Works=Yes] Fn+? / # the slash symbol

If more info is needed, please ask! I'm willing to make this buttons work!
If more testing is needed please quide me.

And one last thing: as far as i can undestand there are different teams/packages that are responsible for the different Fn Buttons states. (xev-udev-hal-gnome power management-kernel)
Can the bug-triage team subscribe those teams too in my bug-report? i don't know exactly who to add here...

ProblemType: Bug
Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: hal-info 20090407-0ubuntu1
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: hal-info
Uname: Linux 2.6.30-020630rc8-generic i686

[Martin Pitt (pitti)]

I'm afraid these scripts aren't very helpful for a permanent solution, since they use ACPI codes. For udev-extras I need proper input events. Can you please exercise the "Fixing broken keys" procedure in /usr/share/doc/udev-extras/README.keymap.txt ? Thank you!

[Martin Pitt (pitti)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!