Public bug reported:

This is a Lenovo IdeaPad S206.
Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN 
Controller (rev 01)

Current behavior is: 
WiFi will operate pretty well -- quite stable.  
Then I suspend the system, move to another WiFi hotspot, and wake the system up.
It will see the other hotspot, but keep prompting me for a password which it 
already has.
This happens about half the time... In fact, maybe exactly half the time I wake 
the system up.
I have also seen it happen when the system is shut down and re-started.
It will never again authenticate once it gets into this state.

Work-around:
Hardware reset: shut system down, hold power button while the splash-screen is 
displayed, until the machine shuts down (about 5 sec.)
Then re-start.  VoilĂ , WiFi authenticates and works fine, until the problem 
occurs again.

History:
WiFi on this machine has always been problematic.  It did not function after a 
clean install of the system.
(For all I know, it was already the inconsistent state problem.)
I had to fiddle around a great deal to get it working even this well... 

Also:
The same system running off a stick with Ubuntu 13.04 Beta is *unusably* flaky 
regarding WiFi.

----------------------------------------------------------
$ lsmod |grep wl
wl                   2906499  0 
cfg80211              175574  1 wl
lib80211               14041  2 lib80211_crypt_tkip,wl

How can we debug this?
(How to look directly at the WiFi hardware state?)

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171145

Title:
  Broadcom WiFi left in inconsistent state after suspend, shutdown in
  12.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171145/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to