[Debian-eeepc-devel] [Fwd: Re: Bug#485236: eeepc-acpi-scripts: Fn+F2 sometimes fails to switch wireless on]

Trevor trevor.chart at gmail.com
Fri Aug 7 09:13:13 UTC 2009


Oops! Replied to sender instead of to the list. Damyan, sorry for the 
duplicate.

Trevor

-------- Original Message --------
Subject: Re: [Debian-eeepc-devel] Bug#485236: eeepc-acpi-scripts: Fn+F2 
sometimes fails to switch wireless on
Date: Thu, 06 Aug 2009 11:38:59 -0700
From: Trevor <trevor.chart at gmail.com>
To: Damyan Ivanov <dmn at debian.org>
References: <4A7A31EE.5090108 at gmail.com> 
<20090806070432.GI8146 at pc1.creditreform.bg>

Damyan Ivanov wrote:
> -=| Trevor, Wed, Aug 05, 2009 at 06:29:18PM -0700 |=-
>> This is a constant bug for me on 900a. Fn+F2 will switch wireless
>> off, but not back on. Running the wireless scripts manually results
>> in:
>> off:
>> trevor at Myri:/etc/acpi/actions$ sudo sh wireless.sh off
>> Detected eeepc-wlan as rfkill /sys/class/rfkill/rfkill0
>> Detected WLAN module ath5k on wlan0
>>
>> On:
>> trevor at Myri:/etc/acpi/actions$ sudo sh wireless.sh on
>> Detected eeepc-wlan as rfkill /sys/class/rfkill/rfkill0
>> Detected WLAN module ath5k on wlan0
>> wlan0: ERROR while getting interface flags: No such device
>> exec: 51: wireless.sh: not found
> 
> these last two lines are strange. Please run the command with shell 
> echo (-x):
> 
>   $ sudo sh -x /etc/acpi/actions/wireless.sh on
> 
> and post the output.

trevor at Myri:~$ sudo sh -x /etc/acpi/actions/wireless.sh on
+ . /usr/share/eeepc-acpi-scripts/functions.sh
+ detect_rfkill eeepc-wlan
+ local _rfkill
+ [ -f /sys/class/rfkill/rfkill0/name ]
+ cat /sys/class/rfkill/rfkill0/name
+ [ eeepc-wlan = eeepc-wlan ]
+ echo Detected eeepc-wlan as rfkill /sys/class/rfkill/rfkill0
Detected eeepc-wlan as rfkill /sys/class/rfkill/rfkill0
+ RFKILL=/sys/class/rfkill/rfkill0/state
+ return
+ wlan_control=/sys/class/rfkill/rfkill0/state
+ [ -n /sys/class/rfkill/rfkill0/state -a -e
/sys/class/rfkill/rfkill0/state ]
+ [ -e /sys/class/rfkill/rfkill0/state ]
+ cat /sys/class/rfkill/rfkill0/state
+ STATE=0
+ cmd=on
+ [ on = toggle ]
+ [ 0 = 0 ]
+ echo 1
+ detect_wlan
+ grep -i network controller
+ + lspci
grep -q RaLink
+ + grep -i atheros
lspci+ grep -q -i wireless
+ + grep -q -i ath_pci
lspci -v
+ WLAN_IF=wlan0
+ WLAN_MOD=ath5k
+ echo Detected WLAN module ath5k on wlan0
Detected WLAN module ath5k on wlan0
+ [ ath5k = ath_pci ]
+ [ ath5k = ath5k ]
+ modprobe ath5k
+ sleep 1
+ ifconfig wlan0 up
SIOCSIFFLAGS: Input/output error
+ exec /etc/acpi/actions/wireless.sh off
Detected eeepc-wlan as rfkill /sys/class/rfkill/rfkill0
Detected WLAN module ath5k on wlan0

After running this time, I got a new behavior in which thee led also
shut itself off - makes sense given that the script is calling itself to
do just that. The last bit of dmesg gives

trevor at Myri:~$ dmesg | tail
[ 8017.333303] 	(5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 8017.333316] 	(5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 8017.333350] cfg80211: Calling CRDA for country: US
[ 8017.393215] ath5k 0000:01:00.0: enabling device (0000 -> 0002)
[ 8017.393250] ath5k 0000:01:00.0: PCI INT A -> GSI 17 (level, low) ->
IRQ 17
[ 8017.393289] ath5k 0000:01:00.0: setting latency timer to 64
[ 8017.393453] ath5k 0000:01:00.0: registered as 'phy0'
[ 8017.403576] ath5k phy0: failed to wakeup the MAC Chip
[ 8017.403674] ath5k 0000:01:00.0: PCI INT A disabled
[ 8017.403716] ath5k: probe of 0000:01:00.0 failed with error -5

hmm...noticing the "ifconfig up" stanza...I'm going to try commenting it
out to see what that does.

commenting this line

#                if ! ifconfig $WLAN_IF up; then exec $0 off; fi

results in duplication of the old behavior (hardware indications are
that wifi should work, software doesn't read anything). Interestingly, a
call to lspci seemss to indicate that I have a "Atheros Communications
Inc. AR5001 Wireless Network Adapter". Isn't the hardware actually an
AR242X or some such thing?

> 
> Also, I am not sure how the script interacts with 2.6.30 kernel you 
> are using; the kernel shall turn on rfkill on Fn+F2 before the script 
> kicks in.
> 

I had the same issue with 2.6.29 when it was the backport too, I just
never used the toggle enough to care and didn't have enough time to go
poking around for fun.




More information about the Debian-eeepc-devel mailing list