"eeepc_wmi: Unknown key XX pressed" when pressing Fn+F keys on Asus Eee Pc 1016p

For WLAN key, someone has dealt with that in bug 662365.

Besides the wifi toggle, could you try the upstream version of eeepc-wmi I put in http://people.canonical.com/~lexical/bugs/lp689393/ and try if other keys work.

Download the files there and execute commands like these:
`make`
`sudo rmmod eeepc-wmi`
`sudo insmod ./eeepc-wmi.ko`

It interests me more if Fn+F3 (disable touchpad) works. Please report if the hotkey works.

This bug is found on 3 eeepc laptops I can reach. Upstream already contains most of the fix. Worth (and *needs*) carrying in Maverick.

A dkms package with the patched eeepc-wmi driver should fix this bug: https://launchpad.net/~lexical/+archive/eeepc

Tested on a 1015PX model, Fn + F7 still not work as expected. It gives the following error in the syslog:

Mar 3 00:09:22 ubuntu-1015PX kernel: [ 634.256677] keyboard: can't emulate rawmode for keycode 245
Mar 3 00:09:22 ubuntu-1015PX kernel: [ 634.256725] keyboard: can't emulate rawmode for keycode 245

As for the Fn + F4 & Fn + F9 which needs to be define in the Keyboard Shortcut by the user, so everything else works as expected.

SRU Justification

Impact: Several hotkey key codes are not added in the keymap of eeepc-wmi
driver. This makes these hotkeys unusable.

Fix: This bug can be fixed by adding the correct mapping in the keymap.
Three patches are carried from upstream. There is a sauce patch made by me
to make the touchpad toggle hotkey and OSD work in Maverick user space.

Testcase: Tested on Asus EEE PC 1011PX

@shang
  Fn+F7 is the hotkey to turn off the monitor. With the SRU, the key code is gotten but xev shows no ksym assigned.
  After looking at /usr/share/X11/xkb/symbols/inet, the related key codes are not assigned to a ksym.

// key <I252> { [ ] }; // KEY_BRIGHTNESS_ZERO -- brightness off
// key <I253> { [ ] }; // KEY_DISPLAY_OFF -- turn off display

  I wonder if X or gnome (most probably g-p-m) has dealt with this function (monitor off).

  However, I will suggest to report this as another bug for a user space expert to investigate.

I used the dkms module at https://launchpad.net/~lexical/+archive/eeepc and I can confirm that all keys are now seen from userspace. Fn+F3 toggles the touchpad and is the only functionality that "just works". For Fn+F7, I see the same output as Shang Wu.

`xev` sees the following ksyms:
Fn+F2 as XF86WLAN
Fn+F4 as XF86Launch5
Fn+F7 as NoSymbol
Fn+F9 as XF86Launch1

I noticed that the XF86WLAN keysym issue has been reported as bug 385646.

This bug was fixed in the package linux - 2.6.38-6.33

---------------
linux (2.6.38-6.33) natty; urgency=low

  [ Andy Whitcroft ]

  * d-i -- enable speakup-modules udeb
    - LP: #672699
  * rebase to 493f3358cb289ccf716c5a14fa5bb52ab75943e5
  * [Config] debian PPC64 configuration
  * [Config] cleanup powerpc config fixing unexpected inconsistancies
  * [Config] resync ppc64 configuration
  * SAUCE: match up ENTRY/END naming for 32/64 bit
  * rebase to fb62c00a6d8942775abc23d1621db1252e2d93d1
  * [Config] update configs after rebase to
    fb62c00a6d8942775abc23d1621db1252e2d93d1
  * [Config] pps_gen_parport no longer built

  [ Corentin Chary ]

  * SAUCE: (drop after 2.6.38) eeepc-wmi: reorder keymap
    - LP: #689393
  * SAUCE: (drop after 2.6.38) eeepc-wmi: add wlan key found on 1015P
    - LP: #689393

  [ John Johansen ]

  * SAUCE: Fix aufs calling of security_path_mknod
    - LP: #724456

  [ Kees Cook ]

  * SAUCE: proc: hide kernel addresses via %pK in /proc/<pid>/stack

  [ Tim Gardner ]

  * rebase to 2.6.38-rc7

  [ Upstream Kernel Changes ]

  * Revert "drm/i915: fix corruptions on i8xx due to relaxed fencing"

  [ Major Kernel Changes ]

  * rebase from v2.6.38-rc6 to v2.6.38-rc7 +
    fb62c00a6d8942775abc23d1621db1252e2d93d1
    - LP: #721389
    - LP: #722925
    - LP: #723672
    - LP: #723676
    - LP: #715318
 -- Andy Whitcroft <email address hidden> Mon, 07 Mar 2011 15:33:17 +0000

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed' to 'verification-done'.

If verification is not done by one week from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

The -proposed kernel fixed this bug. I verified on the EEEPC model Ax 1015PX.

This bug was fixed in the package linux - 2.6.35-28.50

---------------
linux (2.6.35-28.50) maverick-proposed; urgency=low

  [ Brad Figg ]

  * Release Tracking Bug
    - LP: #734399

  [ Corentin Chary ]

  * SAUCE: (drop after 2.6.38) eeepc-wmi: reorder keymap
    - LP: #689393
  * SAUCE: (drop after 2.6.38) eeepc-wmi: add wlan key found on 1015P
    - LP: #689393

  [ Keng-Yu Lin ]

  * SAUCE: eeepc-wmi: set the touchpad toggle key code to F22
    - LP: #689393

  [ Tim Gardner ]

  * [Config] CONFIG_BOOT_PRINTK_DELAY=y
    - LP: #733191

  [ Upstream Kernel Changes ]

  * Revert "drm/radeon/bo: add some fallback placements for VRAM only
    objects."
    - LP: #652934
  * eeepc-wmi: add additional hotkeys
    - LP: #689393
  * xen: don't bother to stop other cpus on shutdown/reboot
    - LP: #727814
  * Yama: use thread group leader when creating match
    - LP: #729839
  * mmc: sdhci-pci: add ricoh e822 pci id with device specific quirks
    - LP: #730820
 -- Brad Figg <email address hidden> Sun, 13 Mar 2011 07:01:39 -0700