Comment 7 for bug 35633

Hi Paul,

here the requested information:

Perfect, just what I needed. The rest is a bit overkill! :)
:-D You never know ....

> received event "hotkey ATKD 00000034 00000000"
> received event "hotkey ATKD 00000033 00000000"
These two keys are actually only one. The key toggles the LCD-backlight and it is working very well.
> received event "hotkey ATKD 00000061 00000000"
This key is meant to toggle between LCD and CRT. It does not work at all
> received event "hotkey ATKD 0000006b 00000003"
This one should toggle the mouse-pad on/off when an external mouse is attached.

There are still two keys missing - which this time actually are two keys - and also do not work. They are meant to in-/decrease the display-brightness and use a range of hotkey-event-codes as follows:

increase brightness:
hotkey ATKD 00000026 0000000b
hotkey ATKD 00000025 00000008
hotkey ATKD 00000024 00000009
hotkey ATKD 00000023 00000006
hotkey ATKD 00000022 00000006
hotkey ATKD 00000021 00000006
hotkey ATKD 00000020 00000045

decrease brightness:
hotkey ATKD 00000011 00000011
hotkey ATKD 00000012 00000006
hotkey ATKD 00000013 00000006
hotkey ATKD 00000014 00000006
hotkey ATKD 00000015 00000009
hotkey ATKD 00000016 00000008
hotkey ATKD 00000017 00000029

Which special-keys to these four match up to? And do they currently work?

> [Tue Mar 21 20:20:08 2006] received event "hotkey ATKD 00000051 00000003"
> [Tue Mar 21 20:20:08 2006] executing action "/etc/acpi/webbtn.sh"

I think I've worked out why it's currently doing the wrong
thing---gnome-power-manager is currently grabbing that keycode when it
shouldn't be!

Sorry for the delayed reply!

Best regards,

Thomas