Hi Graziano,
Bart Samwel wrote:
> graziano wrote:
>> I"m sorry to be a spammer today, but I found out that commenting out the
>> asus-wireless even brought back my wireless. Now Fn+F2 works for
>> bluetooth, but not wlan (which suits me better than the previous
>> behaviour). So I think it is a problem with a double toggling the status
>> of the wireless, which makes it impossible to turn it on again.
If I am correct, the problem is caused by the code in
/etc/acpi/start.d/60-asus-wireless-led.sh. There are two possible scenarios:
* isAnyWirelessPoweredOn incorrectly returns false for your hardware
* setLEDAsusWireless also toggles the hardware, not only the LED
We should add some logging to find out what's happening here. I
personally suspect that it may be the second one, but we should make
sure. Could you try modifying the last function in
/usr/share/acpi-support/state-funcs as follows:
# Pass '1' to light LED and '0' to dark LED
setLEDAsusWireless()
{
action=`test "$1" -ne 0 && echo 1 || echo 0`
# Log what we do.
logger -s "setLEDAsusWireless: parameter is $1, action is $action"
# (Older) asus-acpi module
test -w /proc/acpi/asus/wled && echo -n "$action" > /proc/acpi/asus/wled
# (Newer) asus-laptop module
test -w /sys/devices/platform/asus-laptop/wlan && echo -n "$action"
> /sys/devices/platform/asus-laptop/wlan
}
And then boot your system, and see what that outputs / logs?
Cheers,
Bart
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
