[Jaunty] Bad /etc/acpi/start.d/60-asus-wireless-led.sh file

Bug #334368 reported by Mathieu Marquer
This bug affects 1 person
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)

Bug Description

Binary package hint: acpi-support

According to the report from an user of ubuntu-fr.org forum (http://forum.ubuntu-fr.org/viewtopic.php?pid=2450270#p2450270) :

On Ubuntu Jaunty, using a ASUS-F5RL AP336C laptop (but other Asus laptops seems concerned), the wifi card can't be used : when you turns the wifi switch on, the LED turns on then off, and the wifi connexion can't be used.

This can be fixed by changing /etc/acpi/start.d/60-asus-wireless-led.sh from :

. /usr/share/acpi-support/state-funcs
if isAnyWirelessPoweredOn ; then
    setLEDAsusWireless 1
    setLEDAsusWireless 0


. /usr/share/acpi-support/state-funcs
if isAnyWirelessPoweredOn ; then
    setLEDAsusWireless 0
    setLEDAsusWireless 1

After that small change, the WiFi can be use normally.

Please let me know if you need additionnal informations.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: acpi-support 0.119 [modified: usr/bin/acpi_fakekey]
SourcePackage: acpi-support
Uname: Linux 2.6.28-8-generic i686

Revision history for this message
Mathieu Marquer (slasher-fun) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

what happens if you remove this file completely? Does wifi still work in that case (including toggling of the wireless LED)?

Steve Langasek (vorlon)
Changed in acpi-support (Ubuntu):
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: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers