acpi4asus

Hi,
On ubuntu I don't remenber who is in charge of handling this event, acpi scripts or something like g-p-m ?
Did you only upgrade the kernel ? What was the previous version ?
Thanks

On ubuntu I don't remenber who is in charge of handling this event, acpi scripts or something like g-p-m ? Did you only upgrade the kernel ? What was the previous version ?

Events were handled by acpi, but in 9.10 (latest version) it was changed.
See this bug: https://bugs.launchpad.net/bugs/451108

I could go back to acpi events and solve my problem with the commands above, but it will be against ubuntu new policy to let the kernel handle this events.
I thought this was the place to report this issue. I'm willing to enhance asus-laptop if necessary, but I really don't know where to start. I disassembled DSDTs in the past, but without understanding what they mean.

I upgraded the whole distro, it was my guess that the problem was in the kernel (maybe I'm wrong).

Hum, ok.
There is two problems here, the asus-laptop to asus_laptop was a side effect, and I didn't want that.
The other problem is that wlan file sometime handles the led, and sometime handles the device, we need to fix that and add /sys/class/leds when it handle the led, and /sys/class/rfkill when it handle the device.

Anyway currently asus-laptop should send an input event when Fn+F2 is pressed. This input event should be handled by an application (network manager or g-p-m on gnome) and switch existing rfkill interfaces. (As described in #451108, wireless drivers sometime register rfkill interfaces, so do bluetooth drivers).

- When you press Fn+F2, is an input event generated ? (you can check that using readkeys or xev)
- If not, can you use acpi_listen to check the code of the acpi_event ?
- Can you fill the wiki with information about your model:

http://dev.iksaif.net/projects/acpi4asus/wiki/Asus-laptop_WAPF
http://dev.iksaif.net/projects/acpi4asus/wiki/Asus-laptop_hardware

- When you press Fn+F2, is an input event generated ? (you can check that using readkeys or xev)

No event in xev if I press Fn+F2, but this if I press the wireless button above keyb:

KeyPress event, serial 34, synthetic NO, window 0x4a00001,
root 0x7e, subw 0x0, time 14755492, (185,381), root:(1591,600),
state 0x0, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

- If not, can you use acpi_listen to check the code of the acpi_event ?

Fn+F2:
hotkey ATKD 00000088 00000000

Wireless button:
hotkey ATKD 0000005d 00000000

- Can you fill the wiki with information about your model:

Should I to register to modify the wiki (I saw edits from anonymous)?

Anonymous wrote:

- When you press Fn+F2, is an input event generated ? (you can check that using readkeys or xev)

No event in xev if I press Fn+F2, but this if I press the wireless button above keyb:

KeyPress event, serial 34, synthetic NO, window 0x4a00001, root 0x7e, subw 0x0, time 14755492, (185,381), root:(1591,600), state 0x0, keycode 246 (keysym 0x1008ff95, XF86WLAN), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False

- If not, can you use acpi_listen to check the code of the acpi_event ?

Fn+F2: hotkey ATKD 00000088 00000000

Wireless button: hotkey ATKD 0000005d 00000000

with that patch you should be able to get an event: http://git.iksaif.net/?p=acpi4asus.git;a=commitdiff;h=583db1db20c27bc269613e132df34dbcfcf3fd81;hp=f1f6a17375be07af97c3af1428464c123c9170b0

- Can you fill the wiki with information about your model:

Should I to register to modify the wiki (I saw edits from anonymous)?

Yes please

I built the patched module, rmmod stock asus_laptop, insmod patched, but now xev doesn't get any event.
The module is loaded (I added 0.42f as proof):
asus_laptop: Asus Laptop Support version 0.42f
asus_laptop: Error calling BSTS
asus_laptop: V6V model detected
input: Asus Laptop extra buttons as /devices/virtual/input/input13
Registered led device: asus::touchpad

Even if I unload patched kmod and reload the original, xev no longer gets events. Is there anything to do to "wake up" X?

Anonymous wrote:

I built the patched module, rmmod stock asus_laptop, insmod patched, but now xev doesn't get any event. The module is loaded (I added 0.42f as proof): asus_laptop: Asus Laptop Support version 0.42f asus_laptop: Error calling BSTS asus_laptop: V6V model detected input: Asus Laptop extra buttons as /devices/virtual/input/input13 Registered led device: asus::touchpad

Even if I unload patched kmod and reload the original, xev no longer gets events. Is there anything to do to "wake up" X?

I don't know how your X is configured, and you may have to restart X. (Ctr+Alt+F1, /etc/init.d/gdm restart)
xev also need the focus.

Now it works, reproducibly. I only have compiz enabled, before it was disabled, I don't think is relevant.
Now Fn+F2 generates the same event as the wireless button.

How do we make it control both led and radio (rf_kill)?

Anonymous wrote:

Now it works, reproducibly. I only have compiz enabled, before it was disabled, I don't think is relevant. Now Fn+F2 generates the same event as the wireless button.

How do we make it control both led and radio (rf_kill)?

Currently, there is no known way to know if /sys/devices/platform/asus_laptop/wlan will control led, device or boths.
In fact, your model is worst than others because there is doesn't use WAPF, which can sometime be used to control that.

if you do : echo 0 > wlan; echo 0 > bluetooth, will this shutdown the led ?
Does wlan and bluetooth both control the devices ?

if you do : echo 0 > wlan; echo 0 > bluetooth, will this shutdown the led ?

Yes.

Does wlan and bluetooth both control the devices ?

BT works out of the box without any acpi script, the button switches on and off both led and radio.
Wlan doesn't work, the button do generate an acpi event, but ubuntu scripts are faulty. I fixed the scripts, but Steve in bug #451108 asks not to modify the scripts, but fix the kernel. That's why I tried to raise the issue here. It's not my field, I'm trying to understand. If you say that it's impossible to fix the kernel, I'll offer my revised acpi scripts to ubuntu.

Anonymous wrote:

if you do : echo 0 > wlan; echo 0 > bluetooth, will this shutdown the led ?

Yes.

Does wlan and bluetooth both control the devices ?

BT works out of the box without any acpi script, the button switches on and off both led and radio. Wlan doesn't work, the button do generate an acpi event, but ubuntu scripts are faulty. I fixed the scripts, but Steve in bug #451108 asks not to modify the scripts, but fix the kernel. That's why I tried to raise the issue here. It's not my field, I'm trying to understand. If you say that it's impossible to fix the kernel, I'll offer my revised acpi scripts to ubuntu.

Yep try to send the modified scripts to ubuntu.
I'll try to fix the kernel module, but without proper documentation / coherent bios behavior, this will be hard ...

I'll try to fix the kernel module, but without proper documentation / coherent bios behavior, this will be hard ...

Understood, thanks.
I didn't spend a lot of time trying to understand how acpi-laptop works, but with some pointers, maybe, I could help.
Dumping acpi DSDT and understanding its code is necessary?
I think to recall that in previous kernel versions the button switched off wlan radio and led.
I'll check older versions.
Any hint on what to look for?

The code didn't change a lot for that part in previous version, but you can try.
The problem is mainly that Asus do not provide any kind of documentation about their dsdt interface, and that this interface seems bugged or incomplete in a lot of models.