wireless broken on asus P35 (setLEDAsusWireless)

Bug #293943 reported by Torsten Krah
2
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)
High
Unassigned

Bug Description

Using my wlan key i can't get it on again - so i've looked deeper in the scripts and found following errors / wrong assumptions.

The /etc/acpi/events/asus-wireless-on does trigger on 0000005f, but this should be 0000005e.
The /etc/acpi/events/asus-wireless-off does trigger on 0000005e, but this should be 0000005f.

So both events are "swapped" - at least on my P35 modell here (monitored using acpi_listen and asus_laptop modul).

And the next things which breaks all is the state function setLEDAsusWireless.
These function does only work if, and only if, the call to /sys/devices/platform/asus-laptop/wlan does control the LED - but thats not true for a P35/P35.
Echoing 0 or 1 to this device, you are controling the real hardware kill switch,not only the led. This can be monitored by watching the rf_kill device and watching the state become "3" = hardware kill when echoing a 0 do the wlan device.
So this call should never be done, because the led does itself "knows" if wlan is toggled on or off (if you don't use the softkill rf_kill variant - but from a hardware perspective this is true).

The solution to me is - to completly comment out the script calls for now as it would break my wlan if i ever use this button - but that can't be a real solution.

Steve Langasek (vorlon)
summary: - acpi-support broken on asus models
+ wireless broken on asus P35 (setLEDAsusWireless)
Changed in acpi-support (Ubuntu):
status: New → Triaged
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package acpi-support - 0.132

---------------
acpi-support (0.132) lucid; urgency=low

  * lib/state-funcs, start.d/60-asus-wireless-led.sh, asus-wireless.sh:
    eliminate setLEDAsusWireless altogether; this needs to be handled
    directly by the kernel when the kill switch is toggled, not in a racy
    and inconsistently-applied manner by acpi-support; and in at least some
    cases we know this already *does* happen because of reports that
    /sys/devices/platform/asus-laptop/wlan, used for toggling "the LED" with
    the current kernel module, is actually an interface for toggling *the
    antenna* that happens to also toggle the LED. Likewise, we should not
    be responsible for bringing up the antenna at boot, so get rid of the
    file in the start.d directory. LP: #293943, #204378, #334368.
  * Now that the last script is gone from start.d, kill off the directory
    and the init script handling too.
  * Remove the asus-wireless-2 event handler, which is completely redundant
    with the pre-existing asus-wireless-{off,on} handlers. LP: #207871.

  [ Erik Andrén ]
  * Add support for ATKD 00000037 to events/asus-touchpad.
    This makes the disable touchpad buttons (!) on the EeePc 1005HA work as
    intended. LP: #502720.
 -- Steve Langasek <email address hidden> Mon, 04 Jan 2010 15:52:56 -0800

Changed in acpi-support (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers