Hide Forgot
Description of problem: After turning wireless off and on again no wireless networks are found. manual rmmod b43; modprobe b43 solves the problem - NetworkManager displays wireless networks again. Hardware: Dell Latitude D620 0c:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01) Version-Release number of selected component (if applicable): [serek@talky ~]$ NetworkManager --version 0.8.999-2.git20110509.fc15 How reproducible: Reproduced multiple times when connected to 40-bit WEP encrypted network. Only able to reproduce once in multiple attempts when connected to unencrypted/opened network. Steps to Reproduce: 1. Connect to 40-bit WEP encrypted network 2. Click Wireless ON/OFF button in NetworkManager applet to turn wireless off 3. Click Wireless ON/OFF button in NetworkManager applet to turn wireless back on 4. 'Wireless unavailable' appears in place of Wireless ON/OFF button Actual results: Wireless networks unavailable. Expected results: All available wireless networks should be displayed and connection to known wireless network (if in range) should be established. Additional info: 'rmmod b43; modprobe b43' run as root re-enables wireless connectivity
Very probably a driver issue. Could you grab dmesg output? Also /var/log/messages and /var/log/wpa_supplicant will help debug things.
(In reply to comment #1) > Very probably a driver issue. Which would not be the first issue with this wireless I saw since I have that laptop. But it worked for me lately on Ubuntu (10.04 I think). > > Could you grab dmesg output? Also /var/log/messages and /var/log/wpa_supplicant > will help debug things. Will do so in the evening when I'm back in range of the WEP-(in)secured network and will posts results immediately. Would it be helpful if I grab some info (kernel, driver, etc.) from Ubuntu I run on this laptop before? If it worked there it may help to see what's the difference. Regards, Sergiusz
Created attachment 498620 [details] dmesg output System was freshly rebooted before recreating this, so attached full dmesg including system boot. I have added 3 empty lines to the log to point each of the breakpoints in my experiment. Timestamps are as follows: [ 142.728191] - clicked wireless OFF [ 147.720207] - clicked wireless ON (wireless remained unavailable) [ 229.339169] - unloaded & loaded b43 module (wireless reconnected after this)
Created attachment 498624 [details] /var/log/messages System was freshly rebooted before recreating this, so attached full /var/log/messages including system boot. I have added 3 empty lines to the log to point each of the breakpoints in my experiment. Timestamps are as follows: May 12 20:56:29 - clicked wireless OFF May 12 20:56:35 - clicked wireless ON (wireless remained unavailable) May 12 20:57:57 - unloaded & loaded b43 module (wireless reconnected after this)
Created attachment 498626 [details] /var/log/wpa_supplicant.log File doesn't have timestamps. No log entries were generated when wireless was switched back on (unsuccessfully), so 3 empty lines shows unload/load of b43 module.
The issue could be caused by 'dell-laptop' platform driver. What do you get on $ rfkill list If anything is blocked you can use $ rfkill unblock all If 'dell-laptop causes the problems unload it # rmmod dell-laptop Or you can blacklist it permanently in /etc/modprobe.d/blacklist.conf.
Wireless is now in unavailable state. 'rfkill list' shows nothing blocked: [root@talky ~]# rfkill list 0: dell-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: dell-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no Usual 'rmmod b43; modprobe b43' brought wireless back up. I have unloaded dell-laptop module subsequently and I cannot recreate the problem now, so seems like this does the trick. Now the question is what useful features are provided by dell-laptop module, or in other words what will not work now with no dell-laptop module loaded? Also is blocking dell-laptop recommended permanent solution or only a workaround? Regards, Sergiusz
I don't know the driver, but quickly glancing over it reveals that it handles rfkill switches (apparently wrong way) and backlight. So removing it should not cause you any problems. http://askubuntu.com/questions/41008/what-does-the-dell-laptop-kernel-module-do
I have what seems like the same problem. Restarting the NetworkManager service fixes the issue if the WirelessOff/AirlaneMode are disabled. Restarting NetworkManager whilst WirelessOff/AiplaneMode are enabled has no effect.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping