When I said: "If the card is working for a session, turning it of at any time
then back on again renders wifi inaccessible for the remainder of the session."
I was mistaken. I'm not sure why I said that.
Now as far as I can tell (and remember), if the card is in the "working" state
turning it on and off repeatedly does not cause it to go into the "not
working" state as I seemed to think.
Something else I didn't mention is that suspending the laptop (when the card is
stuck off) will return it to "working" state.
Here is a summary of the problem:
To put the card in the "not working" state can be done by rebooting, making
sure the card is in the red state (card off).
Or by surpending then resuming the laptop, once again making sure the card is
in the red state.
On reboot the card is now in the blue state, and in the "not working" state.
On resume the card is still in the red state but also in the "not working"
state.
To return the card to the "Working" state can be done the same as above but
puting the card in the blue state before rebooting or suspending.
In this case the card is in the blue state and in the "working" state after
resuming or rebooting.
When the wifi is in the "working" state this is what the
/var/lib/NetworkManager/NetworkManager.state looks like:
On (light is blue):
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Off (light is red):
[main]
NetworkingEnabled=true
WirelessEnabled=false
WWANEnabled=true
When the wifi card is in the "not working" state:
On (light is blue):
[main]
NetworkingEnabled=true
WirelessEnabled=false
WWANEnabled=true
Off (light is red):
[main]
NetworkingEnabled=true
WirelessEnabled=false
WWANEnabled=true
When the card is in "not working" state the Enable Wirless checkbox in nmapplet
is greyed out.
When the card is in "working" state the box can be checked (but not when in the
red state).
Unchecking it makes WirelessEnabled=false.
The following is an attempt by me to isolate what is causing the problem.
I have also attached a file containing log entries from syslog.
This consists of turning the card on and off in both the "working" and "not
working" states.
And also all of the entries in syslog during a suspend-resume.
When I say:
"Startup to working state"
- this includes the supending from the not working state and the resuming into
"working" state.
And When I say:
"startup into "not working" state"
- is going from working to not working.
****************************************
I figured from all of this that the problem is being caused by something other
than nmapplet?
Calling iwconfig results in the same ouptput regardless of state:
# iwconfig wlan0
wlan0 IEEE 802.11abg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
But ...
"working": (and blue)
# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:24:d6:##:##:##
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
"not working": (and blue)
# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:24:d6:##:##:##
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
so i tried to turn it on with ifconfig wlan0 up
"not working" (and blue)
# ifconfig wlan0 up
wlan0 Link encap:Ethernet HWaddr 00:24:d6:##:##:##
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Note: calling ifconfig wlan0 up when "not working" and red results in
"SIOCSIFFLAGS: Operation not possible due to RF-kill", which makes
sense.
nm-applet still doesn't see the wifi card, even though ifconfig thinks its up.
At first I though this was nm-applet's fault:
# killall nmapplet
# nmapplet
still doesn't see card
# gedit /var/lib/NetworkManager/NetworkManager.state
edit WirelessEnabled=true
still not there
# killall nmapplet
# nmapplet
still not there
I also tried unticking Enable Networking and editing, killing it etc, etc.
nm-applet still won't see the card, even though its now "UP".
But if you look at the log files just after calling ifconfig wlan0 up you see
this line (and noting else):
Apr 7 02:39:23 ian-laptop kernel: [ 4865.543006] ADDRCONF(NETDEV_UP): wlan0:
link is not ready
Note this error only occurs when I call "ifconfig wlan0 up" in the blue
and "not working" state, noting else.
Then if I turn the card off and on again (blue-red-blue)
# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:24:d6:##:##:##
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
So its not remembering the fact that I did ifconfig wlan0 up on it,
which makes sense. Since there was an error.
So this means the problem is at an even lower level than ifconfig, or in
ifconfig itself?
Anyway, the point is there are 2 things wrong:
1) The card isn't being brought into the up state properly when the RF_KILL bit
is toggled.
2) The default state of the card on bootup is RF_KILL=on. (but not after
returning from suspended where it remembers its state)
The card SHOULD be left in the state it was when the system was shut down.
I noticed this on my friends computer as well (different card), is this
something that was changed in maverick on purpose?
For the record, I don't like it, even if it did work properly.
Could you please give me ideas as to what package/program/utility you
think is causing the problem here so I can get more info about it for
you.
** Attachment added: "annotated logs.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/655530/+attachment/1991815/+files/annotated%20logs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655530
Title:
Wifi card does not turn on properly on reboot
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
