asus hotkey ATKD 0000005c (power4gear)

Many thanks for you bug.

Pliss read: https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch
--
Cristian Aravena Romero

I guess the case here is that it has a different behaviour based on the laptop model.

Can you provide the dmi strings requested in:

  https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

please and we can make the key do what it is supposed to on your particular laptop model. At the moment it is matched in:

  /etc/acpi/events/asus-lock

thanks! this is additional info:

keycode: 0x92 (obtained using keyboard shorcut)

anyway the laptop also generates an acpi event:
[Tue Mar 21 15:35:12 2006] received event "hotkey ATKD 0000005c 00000001"
[Tue Mar 21 15:35:12 2006] notifying client 3961[108:108]
[Tue Mar 21 15:35:12 2006] executing action "/etc/acpi/lockbtn.sh"
[Tue Mar 21 15:35:12 2006] BEGIN HANDLER MESSAGES
[Tue Mar 21 15:35:12 2006] END HANDLER MESSAGES
[Tue Mar 21 15:35:12 2006] action exited with status 0
[Tue Mar 21 15:35:12 2006] completed event "hotkey ATKD 0000005c 00000001"

my laptop identifiers are:
ASUSTeK Computer Inc.
M6Ne
1.0

anyway I know that also M6000 series laptops have the same identifier (at least the same ACPI event) ( http://www.openlaptops.org )

What would you like this to generate instead?

  KEY_BATTERY
  KEY_SETUP
  KEY_CONFIG

seem the closest.

I'd like to do this:

Power profile selector
Change CPU power consumption

Should select power consumption profile. (A suggested list is Full Power, High Power, Normal, DVD Playback, Presentation, and Long Life.)

I don't have an exact idea but it should be KEY_BATTERY.. shouldn't it?
also because I don't know what is KEY_SETUP and KEY_CONFIG...

No, really. It's 'acpi-support'.

Can I try to do a handler to this hotkey?

KEY_BATTERY is quite useless (when I click gnome-power-manager shows the current battery status (AC plugged in, battery is fully charged))

KEY_SETUP and KEY_CONFIG doesn't seem having any handlers if used. I'll give you my very simple implementation of what the hotkey is intended to do

this is the script launched when pressing the hotkey

This affects me on my A6U as well. The keycodes are the same. My laptop identifiers are:
ASUSTeK Computer Inc.
A6U
1.0

Yes, Nicolò, your description of what the hotkey should do matches perfectly with the description from the asus manual (yes, I read it ;)). Thanks for the implementation!

Copy the other 'dmidecode' across:

 Manufacturer: ASUSTeK Computer Inc.
 Product Name: A6Km

I can probably do something with this and remove the zenity stuff (hopefully we'll have a better system for on-screen messages in dapper+1). The other pain is the fact that it is stopping powernowd.

I think what I'd like to do in the future is to perhaps stop using powernowd and instead let the kernel grovernors take care of it; which would also get the manual speed overriddes working.

BTW, can you test a version of your script that makes no effort to actually stop 'powernowd', but which just switch the grovenor from userspace to 'performance'/'powersave'.

Because this is cosmetic and only affects one range of laptop I think I'm going to keep this for dapper+1 unless it becomes easily doable.

I'd like to add the key-mapping so that it least doesn't lock the screen.

I did stop powernowd simply because it is useless if the governor is
performance and powersave. I think we can keep it running but it vasts
resources (I don't know how much). Anyway I'll try to remove the
"stop" and i'll test if it works the same tomorrow!

Yes Paul! As you told I think that powernowd must be substituted by
kernel goversors, which in my opinion are more reactive!

remember that my dmidecode is:
ASUSTeK Computer Inc.
M6Ne
1.0

Dear Paul I want to tell you that now ALL asus laptops have this hotkey,
and don't have the lock hotkey... So I think that the new power4gear
hotkey should be the default one...

Paul, do you think that the new handler will be available for edgy?

Would be a nice handler for Asus V6J too, where the Power4Gear button is locking the screen at the moment.

Proposed script, however, is not working since Asus V6J has two cores and in that case, two cpus that can be individually scaled.

Yes! But I don't know if it does make sense to correct the error in
the script, since it will never be introduces... In my opinion this
hotkey should interact with gnome power manager, which has a checkbox
"prefer power savings over performance".
Maybe through gconf we could edable/disable that key!
Anyway other things are needed... Such as multiple configuration
schemas, that gnome-power-manager doesn't have now. Only one for
battery and one fo AC.

So nothing in edgy too :(

please can you do something similar to what you have done for thinkpad? file /etc/acpi/thinkpad-lockorbattery.sh

Upstream is interested in adding a feature in g-p-m. They asked me the keycode!

I think this bug is waiting for us to figure out what to map it to!

I'm de-assigning it for the moment, but I hope to come back to it.

Paul, what do you mean?

this might be a proposal which handles multi cores (I think, because I don't have one)
please test it. There is an unresolved issue: how to notify the change to the user (so he understands in which status is the machine)?
I tried to use notify-bin (from libnotify-bin) but it does not work in acpid. It ends with this error:
libnotify-Message: Unable to get session bus: Failed to execute dbus-launch to autolaunch D-Bus session

this error disappears if I restart acpid from an X terminal (strange)

And is libnotify supported by kde too?

It does not necessarily handle multi cores. My machine (ausus A5e) is a bog standard celeron. No multi core.

What do I need to do to test it please? (I am not geek enough to know, sorry)

I assume I put it in /etc/acpi

But do I then have to run a command so that it is recognised as being there when I press the hotkey?

Thanks.

The script I uploaded is intended to support both uniprocessors and
multiprocessors
you should edit /etc/acpi/asus-lock.sh and change the action=....

You should also restart acpid: sudo /etc/init.d/acpid restart

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

what?

This bug is valid. Still an issue with Hard Alpha 5. The button does nothing. Can we reopen this bug?

Confirmed. xev gives no output for this key.

Hello,

You mention that the key is not visible in xev. Please follow the directions in https://wiki.ubuntu.com/Hotkeys/Troubleshooting and report your results, to help us determining which package needs to be fixed for this.

Changed laptop, sorry!!

As I changed my notebook and I will no longer use Hardy, I unsubscribed from this bug report.

The original problem, that /etc/acpi/events/asus-lock triggered on this button and locked the screen, should be resolved now in karmic because this event handler has been removed - the mapping of ACPI event to hotkey is now being done by the asus-laptop driver. If the key is still being mismapped in karmic, this will need to be fixed in the kernel package rather than in acpi-support.

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 : ==

=== 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 ! ;-)

Oups, i forget to say that i am using Ubuntu 9.10 Karmic Koala. :-)

Albin,

You say you have this bug, but your message doesn't mention anything about a "power4gear" hotkey. You mention a key with the 0000005c ACPI event, but say that it should be mapped to screen lock?

Sorry, I think that it was implicit in my message. :-)

On Ubuntu, my Fn+space run like "lock screen". But it should run as "power4gear". And the real "lock screen" is Fn+Suppr. And I confirm the fact that pressing Fn+space throws event "hotkey ATKD 0000005c" in acpi_listen.

On my other OS "Win...", Fn+space run the Power4gear utility. But I think that there isn't a program doing the same thing on Linux.

Tell me, if you want more information ;-)

Ok - can you please walk through the steps in https://wiki.ubuntu.com/Hotkeys/Troubleshooting, to show how this key is being handled by the system? The mapping doesn't appear to be changed by udev, so we probably need this to be fixed in the kernel.

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!