acpi4asus

Hi,
Could you read http://dev.iksaif.net/projects/acpi4asus/wiki/Asus-laptop_Support and send the according informations ?
Could you also join the result of tree /sys/devices/platform/asus-laptop/
If you use a 2.6.32 kernel or newer you can try the latest version of asus-laptop.c just follow http://dev.iksaif.net/projects/acpi4asus/wiki/Backport_module and run python acpi4asus.py asus-laptop asus-laptop-refactor
Thanks

Anonymous wrote:

acpi_listen

FN+F2 → hotkey ATKD 0000005f 00000002

hotkey ATKD 0000007e 00000002

(the second line appears a few seconds laterr

FN+F8 → hotkey ATKD 00000061 00000001

FN+F9 → hotkey ATKD 0000006b 00000002

FN+keypad-return → hotkey ATKD 00000055 00000002

(this should open the calculator...but it should be enough to simply send a signal that we can use for a gnome keybinding)

All these key are handled in newer asus-laptop modules.
Read http://dev.iksaif.net/projects/acpi4asus/wiki/Backport_module and try to use acpi4asus.py:

python acpi4asus.py asus-laptop backport-asus-laptop-2.6.31

Corentin Chary wrote:

Anonymous wrote:

acpi_listen

FN+F2 → hotkey ATKD 0000005f 00000002

hotkey ATKD 0000007e 00000002

(the second line appears a few seconds laterr

FN+F8 → hotkey ATKD 00000061 00000001

FN+F9 → hotkey ATKD 0000006b 00000002

FN+keypad-return → hotkey ATKD 00000055 00000002

(this should open the calculator...but it should be enough to simply send a signal that we can use for a gnome keybinding)

All these key are handled in newer asus-laptop modules.
Read http://dev.iksaif.net/projects/acpi4asus/wiki/Backport_module and try to use acpi4asus.py:
[...]

Thank you, everything works by now except the lights. :)
But there is one problem: The slideswitch now handles both wireless and bluetooth, while FN+F2 is only for wireless. That can be a bit of a mess.

Anonymous wrote:

Corentin Chary wrote:

Anonymous wrote:

acpi_listen

FN+F2 → hotkey ATKD 0000005f 00000002

hotkey ATKD 0000007e 00000002

(the second line appears a few seconds laterr

FN+F8 → hotkey ATKD 00000061 00000001

FN+F9 → hotkey ATKD 0000006b 00000002

FN+keypad-return → hotkey ATKD 00000055 00000002

(this should open the calculator...but it should be enough to simply send a signal that we can use for a gnome keybinding)

All these key are handled in newer asus-laptop modules.
Read http://dev.iksaif.net/projects/acpi4asus/wiki/Backport_module and try to use acpi4asus.py:
[...]

Thank you, everything works by now except the lights. :)
But there is one problem: The slideswitch now handles both wireless and bluetooth, while FN+F2 is only for wireless. That can be a bit of a mess.

Well, Fn+F2 should cycle. Anyway, asus-laptop only send input events, then some userspace utility (some part of gnome in your case), handle the input event and switch the device on or off. Could you send me the output of xev when pressing Fn+F2 and the slideswitch ?

The lights may be controlled by the "touchpad" led, could you try that ? (see /sys/class/leds , there should be some files, then echo 1 > brightness in the asus::touchpad directory).

Well, Fn+F2 should cycle. Anyway, asus-laptop only send input events, then some userspace utility (some part of gnome in your case), handle the input event and switch the device on or off. Could you send me the output of xev when pressing Fn+F2 and the slideswitch ?

xev for Fn+F2:
(pressed)
KeyPress event, serial 35, synthetic NO, window 0x5000001,
root 0x13f, subw 0x0, time 6736966, (694,310), root:(701,359),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 35, synthetic NO, window 0x5000001,
root 0x13f, subw 0x0, time 6736966, (694,310), root:(701,359),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

(pressed again)
KeyPress event, serial 37, synthetic NO, window 0x5000001,
root 0x13f, subw 0x0, time 6742186, (172,-18), root:(179,31),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x5000001,
root 0x13f, subw 0x0, time 6742186, (172,-18), root:(179,31),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

xev for the slideswitch:
(switch to the right -> on)
KeyPress event, serial 35, synthetic NO, window 0x5000001,
root 0x13f, subw 0x0, time 6571029, (1027,393), root:(1034,442),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 35, synthetic NO, window 0x5000001,
root 0x13f, subw 0x0, time 6571029, (1027,393), root:(1034,442),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

(switch to the left -> off)
KeyPress event, serial 37, synthetic NO, window 0x5000001,
root 0x13f, subw 0x0, time 6574538, (1027,393), root:(1034,442),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x5000001,
root 0x13f, subw 0x0, time 6574538, (1027,393), root:(1034,442),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

The lights may be controlled by the "touchpad" led, could you try that ? (see /sys/class/leds , there should be some files, then echo 1 > brightness in the asus::touchpad directory).

I tried that, but there is no reaction. If it helps you, those two led-panels seem to be connected to the power-leds in a way, when the notebook is on s3, they blink in the same way as the power-leds do, they also turn off with them and on when resuming from s3. The only strange thing is, when the notebook is booting normally, those led panels are turned off. They then turn on as soon as grub2 loads the linux kernel (in a slow, fading way).

Anonymous wrote:

Well, Fn+F2 should cycle. Anyway, asus-laptop only send input events, then some userspace utility (some part of gnome in your case), handle the input event and switch the device on or off. Could you send me the output of xev when pressing Fn+F2 and the slideswitch ?

Could you try with different values of wapf ? modprobe asus_laptop wapf=[0,1,2,3,4,5].
See http://dev.iksaif.net/projects/acpi4asus/wiki/Asus-laptop_WAPF for more informations.

The lights may be controlled by the "touchpad" led, could you try that ? (see /sys/class/leds , there should be some files, then echo 1 > brightness in the asus::touchpad directory).

I tried that, but there is no reaction. If it helps you, those two led-panels seem to be connected to the power-leds in a way, when the notebook is on s3, they blink in the same way as the power-leds do, they also turn off with them and on when resuming from s3. The only strange thing is, when the notebook is booting normally, those led panels are turned off. They then turn on as soon as grub2 loads the linux kernel (in a slow, fading way).

Hum, what kind of control do you have for these leds on windows ?

Corentin Chary wrote:

Could you try with different values of wapf ? modprobe asus_laptop wapf=[0,1,2,3,4,5].
See http://dev.iksaif.net/projects/acpi4asus/wiki/Asus-laptop_WAPF for more informations.

fn+f2 xev (pressed twice with a second delay)
wapf=0

[nothing]

wapf=1

[nothing]

wapf=2

KeyPress event, serial 35, synthetic NO, window 0x4e00001,
root 0x13f, subw 0x0, time 3039052, (-384,297), root:(293,346),
state 0x0, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 35, synthetic NO, window 0x4e00001,
root 0x13f, subw 0x0, time 3039052, (-384,297), root:(293,346),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x4e00001,
root 0x13f, subw 0x0, time 3042558, (-384,297), root:(293,346),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x4e00001,
root 0x13f, subw 0x0, time 3042558, (-384,297), root:(293,346),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

wapf=3

KeyPress event, serial 35, synthetic NO, window 0x4e00001,
root 0x13f, subw 0x0, time 3077850, (-338,153), root:(339,202),
state 0x0, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 35, synthetic NO, window 0x4e00001,
root 0x13f, subw 0x0, time 3077850, (-338,153), root:(339,202),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x4e00001,
root 0x13f, subw 0x0, time 3081421, (-338,153), root:(339,202),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x4e00001,
root 0x13f, subw 0x0, time 3081421, (-338,153), root:(339,202),
state 0x10, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

wapf=4

[nothing]

wapf=5

[nothing]

Slideswitch xev (first turned on, then off)
wapf=0

[nothing]

wapf=1

[nothing]

wapf=2

[nothing]

wapf=3

[nothing]

wapf=4

[nothing]

wapf=5

[nothing]

The lights may be controlled by the "touchpad" led, could you try that ? (see /sys/class/leds , there should be some files, then echo 1 > brightness in the asus::touchpad directory).

I tried that, but there is no reaction. If it helps you, those two led-panels seem to be connected to the power-leds in a way, when the notebook is on s3, they blink in the same way as the power-leds do, they also turn off with them and on when resuming from s3. The only strange thing is, when the notebook is booting normally, those led panels are turned off. They then turn on as soon as grub2 loads the linux kernel (in a slow, fading way).

Hum, what kind of control do you have for these leds on windows ?

Actually, on my asus driver disk there was no tool to configure these leds. But a friend of mine has a laptop that is pretty similar to mine, and he uses some kind of asus control panel software.

Anonymous wrote:

Corentin Chary wrote:

Could you try with different values of wapf ? modprobe asus_laptop wapf=[0,1,2,3,4,5].
See http://dev.iksaif.net/projects/acpi4asus/wiki/Asus-laptop_WAPF for more informations.

fn+f2 xev (pressed twice with a second delay)

Then your laptop need wapf=2, anyway this should be the default setting. Could you fill the http://dev.iksaif.net/projects/acpi4asus/wiki/Asus-laptop_WAPF with your results ?

Slideswitch xev (first turned on, then off)

Could you try with acpi_listen ? The key may not already be mapped to an input event.

Hum, what kind of control do you have for these leds on windows ?

Actually, on my asus driver disk there was no tool to configure these leds. But a friend of mine has a laptop that is pretty similar to mine, and he uses some kind of asus control panel software.

Hum.. It will be hard to find how to control these leds, there is no obious acpi interface to do it :/

Alright, here is the slideswitch data from acpi_listen:

wapf=0,1,2,3
hotkey ATKD 0000005e 00000000
hotkey ATKD 0000007d 00000000

hotkey ATKD 0000005f 00000000
hotkey ATKD 0000007e 00000000

wapf=4,5
hotkey ATKD 00000080 00000000

hotkey ATKD 00000081 00000000