Public bug reported:
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.
** Affects: acpi-support (Ubuntu)
Importance: Undecided
Status: New
--
acpi-support broken on asus models
https://bugs.launchpad.net/bugs/293943
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
