asus-laptop module has incomplete support for hotkeys on Asus

I can confirm this bug.

Unmarking as duplicate since acpi-support is no longer part of Jaunty and it also is still broken in Jaunty.

Can you please walk through https://wiki.ubuntu.com/Hotkeys/Troubleshooting and check whether this key produces a key code as well? Please also do "lshal > /tmp/hal.txt" and attach /tmp/hal.txt here. Thank you!

There is no output for this key in xev.

Right, I meant installing input-utils and checking input-events in a VT (Ctrl+Alt+F1). This needs a hal-info mapping, but we need to find out which scan code it produces.

input-events doesn't register any keypress

Can you please go further down the troubleshooting list then, and check whether the key produces an ACPI event?

That's in the original report, but I'll copy and paste it down into this comment...
ACPI event registered:
"hotkey ATKD 00000051 0000000e"

Ah, indeed, sorry.

So this leaves it to acpi-support to convert this ACPI event to a keypress. And indeed it already makes an attempt to do so in events/asus-internet, with the correct keycode:

event=hotkey (ATKD|HOTK) 00000051
action=/etc/acpi/webbtn.sh

and webbtn.sh uses "acpi_fakekey $KEY_WWW".

Debugged with Mackenzie that the trigger works (by running acpid in foreground), and apparently acpi_fakekey is broken.

Debugged further with Mackenzie. acpi_fakekey opens the correct /dev/input/ device, but it doesn't actually work.

I confirmed this on my system:

  sudo acpi_fakekey 150

it also opens the right /dev/input/event4, and write()s to it, but I do not get any actual event back (with input-events).

acpi_fakekey is supposed to be eliminated in jaunty altogether, in favor of getting kernel acpi drivers in place that generate input events. See https://wiki.ubuntu.com/HotkeyArchitectureSpec.

Steve:
After you said that in the other bug, I un-duped this one from the fakekey bug. I would *like* to do whatever debugging is necessary to get it working in kernelspace, but Martin said he doesn't know how things work in kernelspace and this was as far as he could get me.

Mackenzie,

Given the work required to get acpi_fakekey to work reliably in jaunty, I think it would actually be easier to get an ACPI kernel driver for your platform. There are several existing examples of this available: thinkpad_acpi and sony-laptop appear to work for people, and there is already an asus-laptop module in the kernel that probably just needs to be extended to handle this case.

So I can I make this a kernel bug about the asus-laptop module? I've
got 2 hotkeys that need to be added to that module.

Doing that...

 summary "asus-laptop module has incomplete support for hotkeys on Asus
Z37E"
 affects ubuntu/linux

Disassembled DSDT: http://launchpadlibrarian.net/23017437/dsdt.dsl

marking invalid for acpi-support, since this should be handled in the kernel module.

Hello,

There is the same mater on my Asus F3JV. The real hot key for Screen Lock is Fn+Suppr.

== There is also a lot of bugs with all my hot-keys : ==

=== Config ===
* PC : Asus F3JV (alias Z53JV-AP030M)
* OS : Ubuntu 9.10 Karmic Koala

=== No event in xev ===
* Fn+F2 (Wifi on/off)
* Fn+F5 (Brightness down)
* Fn+F6 (Brightness up)
* Fn+F9 (Touchpad on/off)

=== Errors in log file ===
* Fn+F2
no error message

* Fn+F5
kernel: [ 2569.550813] ACPI Error (psargs-0359): [\_SB_.PCI0.P0P2.VGA_.LCDD] Namespace lookup failure, AE_NOT_FOUND
kernel: [ 2569.550831] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_._Q0E] (Node f701acf0), AE_NOT_FOUND

* Fn+F6
kernel: [ 2656.167994] ACPI Error (psargs-0359): [\_SB_.PCI0.P0P2.VGA_.LCDD] Namespace lookup failure, AE_NOT_FOUND
kernel: [ 2656.168036] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_._Q0F] (Node f701ad08), AE_NOT_FOUND

* Fn+F9
no error message

=== acpi_listen events ===
* Fn+F1 (Zzzz) : button/sleep SLPB 00000080
* Fn+F2 (wifi on/off) : nothing
* Fn+F3 (mail) : hotkey ATKD 00000050
* Fn+F4 (internet) : hotkey ATKD 00000051
* Fn+F5 (Brightness down) : nothing
* Fn+F6 (Brightness up) : nothing
* Fn+F7 (screen light off) : hotkey ATKD 00000034
* Fn+F7 (screen light on) : hotkey ATKD 00000033
* Fn+F8 (LCD/CRT) : hotkey ATKD 00000061
* Fn+F9 (touchpad on/off) : hotkey ATKD 0000006b
* Fn+F10 (mute) : hotkey ATKD 00000032
* Fn+F11 (volume down) : hotkey ATKD 00000031
* Fn+F12 (volume up) : hotkey ATKD 00000030
* Fn+espace (screen lock) : hotkey ATKD 0000005c
* Fn+← (previous) : hotkey ATKD 00000040
* Fn+→ (next) : hotkey ATKD 00000041
* Fn+↑ (stop) : hotkey ATKD 00000043
* Fn+↓ (play/pause) : hotkey ATKD 00000045

== Question ==

Do i have to create a new bug in launchpad ? Please answer me by mail. Also if you can help me, i never report a bug on launchpad.

Thanks ! ;-)

Can somebody affected by this bug please report it upstream to http://bugzilla.kernel.org/

I don't think Ubuntu can fix this bug as fast as upstream can. Please test the steps lined out in https://wiki.ubuntu.com/Hotkeys/Troubleshooting against a lucid live CD. Let me know if you need help.

When you've done that, please post the link to the ticket here.

Mackenzie Morgan, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]