Description of problem: After resume from STR NetowrkManager displays message "device not ready" under Wireless Networks. I have to rmmod b43 and ssb and them modprobe b43 to be able to use wifi again. It used to work, unfortunately i do not remember when it stopped working. Probably it is not related to NM but i could not distinguish what might cause this issue. Version-Release number of selected component (if applicable): NetowrkManager-0.8.0-4.git20100325.fc12.x86_64 my wifi: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 02) How reproducible: Suspend to ram and resume. S
I am seeing the same thing starting with NetworkManager-0.8.0-4.git20100325.fc12.x86_64 and ath5k WiFi. Restarting the NetworkManager service fixes things instantly, no need to reload the kernel module. The prior release of NetworkManager did not have this issue, so this is a regression.
Yes Robert. You are right. Restart of NM fixes problem, no need to reload modules.
Intel 4965abgn chip. Same problem. This started happening after NetworkManager-0.8.0-4.git20100325.fc12.x86_64 update was applied. A new kernel was also updated at the same time, but I tested with the older kernel (2.6.32.9-70.fc12.x86_64) and it exhibits the same problem with the new NetworkManager. So it seems that the NetworkManager update is at fault here. Flipping the wifi killswitch off/on also restores the connection, as does manually unchecking/rechecking Enable Wireless from nm-applet.
Same problem with F13 beta with ath5k [Atheros AR5212 802.11abg] on a ThinkPad X60s. Relavent packages: kernel-PAE-2.6.33.1-19.fc13.i686 NetworkManager-0.8.0-0.4.git20100211.fc13.i686 Workarrounds: - restart NetworkManager [sudo service NetworkManager restart] - Fn-F5 [twice] - Toggle the manual switch for wireless rf on/off Downgrading to NetworkManager-glib-0.8.0-4.git20100325.fc13.i686 also resolves the issue. yum downgrade NetworkManager NetworkManager-gnome NetworkManager-glib
Sorry - got the versions mixed-up in the previous post. works: NetworkManager-0.8.0-0.4.git20100211.fc13.i686 breaks: NetworkManager-0.8.0-4.git20100325.fc13.i686
Snippet of /var/log/messages after resume from suspend: Apr 3 18:58:36 localhost kernel: Restarting tasks ... done. Apr 3 18:58:37 localhost NetworkManager: <info> Waking up... Apr 3 18:58:37 localhost NetworkManager: <info> (eth0): now managed Apr 3 18:58:37 localhost NetworkManager: <info> (eth0): device state change: 1 -> 2 (reason 2) Apr 3 18:58:37 localhost NetworkManager: <info> (eth0): bringing up device. Apr 3 18:58:37 localhost NetworkManager: <info> (eth0): preparing device. Apr 3 18:58:37 localhost NetworkManager: <info> (eth0): deactivating device (reason: 2). Apr 3 18:58:37 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Apr 3 18:58:37 localhost NetworkManager: <info> (wlan0): now managed Apr 3 18:58:37 localhost NetworkManager: <info> (wlan0): device state change: 1 -> 2 (reason 2) Apr 3 18:58:37 localhost NetworkManager: <info> (wlan0): bringing up device. Apr 3 18:58:37 localhost NetworkManager: <info> (wlan0): deactivating device (reason: 2). Apr 3 18:58:38 localhost ntpd[1650]: Deleting interface #17 wlan0, fe80::21d:e0ff:fe00:c305#123, interface stats: received=0, sent=0, dropped=0, active_time=2 secs Apr 3 18:58:38 localhost ntpd[1650]: Deleting interface #18 wlan0, 192.168.1.106#123, interface stats: received=0, sent=0, dropped=0, active_time=2 secs Here I toggled the wifi kill switch: Apr 3 18:58:46 localhost kernel: iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio. Apr 3 18:58:46 localhost NetworkManager: <info> WiFi now disabled by radio killswitch Apr 3 18:58:46 localhost kernel: iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio. Apr 3 18:58:46 localhost NetworkManager: <info> WiFi now disabled by radio killswitch Apr 3 18:58:46 localhost NetworkManager: <info> (wlan0): bringing up device. Apr 3 18:58:47 localhost kernel: Registered led device: iwl-phy0::radio Apr 3 18:58:47 localhost kernel: Registered led device: iwl-phy0::assoc Apr 3 18:58:47 localhost kernel: Registered led device: iwl-phy0::RX Apr 3 18:58:47 localhost kernel: Registered led device: iwl-phy0::TX Apr 3 18:58:47 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Apr 3 18:58:47 localhost NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready Apr 3 18:58:47 localhost NetworkManager: <info> (wlan0): device state change: 2 -> 3 (reason 42) Apr 3 18:58:47 localhost NetworkManager: <info> Activation (wlan0) starting connection 'Auto Sanctuary' Apr 3 18:58:47 localhost NetworkManager: <info> (wlan0): device state change: 3 -> 4 (reason 0) Apr 3 18:58:47 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Apr 3 18:58:47 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Apr 3 18:58:47 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Apr 3 18:58:47 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Apr 3 18:58:47 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Apr 3 18:58:47 localhost NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0) Apr 3 18:58:47 localhost NetworkManager: <info> (wlan0): preparing device. Apr 3 18:58:47 localhost NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto Sanctuary' requires no security. No secret s needed. Apr 3 18:58:47 localhost NetworkManager: <info> Config: added 'ssid' value 'Sanctuary' Apr 3 18:58:47 localhost NetworkManager: <info> Config: added 'scan_ssid' value '1' Apr 3 18:58:47 localhost NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' Apr 3 18:58:47 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Apr 3 18:58:47 localhost NetworkManager: <info> Config: set interface ap_scan to 1 Apr 3 18:58:47 localhost NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected Apr 3 18:58:47 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associating Apr 3 18:58:47 localhost kernel: iwlagn 0000:03:00.0: RF_KILL bit toggled to disable radio. Apr 3 18:58:47 localhost NetworkManager: <info> WiFi now disabled by radio killswitch Apr 3 18:58:47 localhost NetworkManager: <info> (wlan0): device state change: 5 -> 2 (reason 0) Apr 3 18:58:47 localhost NetworkManager: <info> (wlan0): deactivating device (reason: 0). Apr 3 18:58:47 localhost kernel: iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio. Apr 3 18:58:47 localhost NetworkManager: <info> WiFi now disabled by radio killswitch Apr 3 18:58:47 localhost NetworkManager: <info> (wlan0): bringing up device. Apr 3 18:58:48 localhost kernel: Registered led device: iwl-phy0::radio Apr 3 18:58:48 localhost kernel: Registered led device: iwl-phy0::assoc Apr 3 18:58:48 localhost kernel: Registered led device: iwl-phy0::RX Apr 3 18:58:48 localhost kernel: Registered led device: iwl-phy0::TX Apr 3 18:58:48 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready Apr 3 18:58:48 localhost NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready Apr 3 18:58:48 localhost NetworkManager: <info> (wlan0): device state change: 2 -> 3 (reason 42) Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) starting connection 'Auto Sanctuary' Apr 3 18:58:48 localhost NetworkManager: <info> (wlan0): device state change: 3 -> 4 (reason 0) Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Apr 3 18:58:48 localhost NetworkManager: <info> (wlan0): device state change: 4 -> 5 (reason 0) Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0/wireless): connection 'Auto Sanctuary' requires no security. No secret s needed. Apr 3 18:58:48 localhost NetworkManager: <info> Config: added 'ssid' value 'Sanctuary' Apr 3 18:58:48 localhost NetworkManager: <info> Config: added 'scan_ssid' value '1' Apr 3 18:58:48 localhost NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Apr 3 18:58:48 localhost NetworkManager: <info> Config: set interface ap_scan to 1 Apr 3 18:58:48 localhost NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected Apr 3 18:58:48 localhost NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> associating Apr 3 18:58:48 localhost dnsmasq[1807]: no servers found in /etc/resolv.conf, will retry Apr 3 18:58:48 localhost kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Apr 3 18:58:48 localhost NetworkManager: <info> (wlan0): supplicant connection state: associating -> associated Apr 3 18:58:48 localhost NetworkManager: <info> (wlan0): supplicant connection state: associated -> completed Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Sanctuary'. Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Apr 3 18:58:48 localhost NetworkManager: <info> (wlan0): device state change: 5 -> 7 (reason 0) Apr 3 18:58:48 localhost NetworkManager: Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds) Apr 3 18:58:48 localhost NetworkManager: <info> running: /sbin/dhclient -d -4 -sf /usr/libexec/nm-dhcp-client.action -pf /var/run/dhclient-wlan0.pid -lf /var/lib/dhclient/dhclient-af10dc8e-57ba-4aae-8518-99b2c715658a-wlan0.lease -cf /var/run/nm-dhclient-wlan0.conf wlan0 Apr 3 18:58:48 localhost NetworkManager: <info> dhclient started with pid 31550 Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) scheduled... Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) started... Apr 3 18:58:48 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) complete. Apr 3 18:58:48 localhost dhclient[31550]: Internet Systems Consortium DHCP Client 4.1.1 Apr 3 18:58:48 localhost dhclient[31550]: Copyright 2004-2010 Internet Systems Consortium. Apr 3 18:58:48 localhost dhclient[31550]: All rights reserved. Apr 3 18:58:48 localhost dhclient[31550]: For info, please visit https://www.isc.org/software/dhcp/ Apr 3 18:58:48 localhost dhclient[31550]: Apr 3 18:58:48 localhost NetworkManager: DHCPv4: device wlan0 state changed nbi -> preinit Apr 3 18:58:48 localhost dhclient[31550]: Listening on LPF/wlan0/00:1d:e0:00:c3:05 Apr 3 18:58:48 localhost dhclient[31550]: Sending on LPF/wlan0/00:1d:e0:00:c3:05 Apr 3 18:58:48 localhost dhclient[31550]: Sending on Socket/fallback Apr 3 18:58:50 localhost dhclient[31550]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67 Apr 3 18:58:50 localhost dhclient[31550]: DHCPACK from 192.168.1.1 Apr 3 18:58:50 localhost dhclient[31550]: bound to 192.168.1.106 -- renewal in 38932 seconds. Apr 3 18:58:50 localhost NetworkManager: DHCPv4: device wlan0 state changed preinit -> reboot Apr 3 18:58:50 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled... Apr 3 18:58:50 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started... Apr 3 18:58:50 localhost NetworkManager: address 192.168.1.106 Apr 3 18:58:50 localhost NetworkManager: prefix 24 (255.255.255.0) Apr 3 18:58:50 localhost NetworkManager: gateway 192.168.1.1 Apr 3 18:58:50 localhost NetworkManager: nameserver '68.87.71.226' Apr 3 18:58:50 localhost NetworkManager: nameserver '68.87.73.242' Apr 3 18:58:50 localhost NetworkManager: domain name 'hsd1.ma.comcast.net.' Apr 3 18:58:50 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled... Apr 3 18:58:50 localhost NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete. Apr 3 18:58:50 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started... Apr 3 18:58:50 localhost avahi-daemon[1439]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.106. Apr 3 18:58:50 localhost avahi-daemon[1439]: New relevant interface wlan0.IPv4 for mDNS. Apr 3 18:58:50 localhost avahi-daemon[1439]: Registering new address record for 192.168.1.106 on wlan0.IPv4. Apr 3 18:58:50 localhost avahi-daemon[1439]: Registering new address record for fe80::21d:e0ff:fe00:c305 on wlan0.*. Apr 3 18:58:51 localhost NetworkManager: <info> (wlan0): device state change: 7 -> 8 (reason 0) Apr 3 18:58:51 localhost NetworkManager: <info> Policy set 'Auto Sanctuary' (wlan0) as default for routing and DNS. Apr 3 18:58:51 localhost NetworkManager: <info> Activation (wlan0) successful, device activated. Apr 3 18:58:51 localhost NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
When stuff doesn't work after resume, before toggling the rfkill switch, can you grab the output of these 3 commands: rfkill cat /sys/class/rfkill/*/type cat /sys/class/rfkill/*/state thanks!
[root@localhost michal]# rfkill bash: rfkill: command not found [root@localhost michal]# cat /sys/class/rfkill/*/type wlan bluetooth wlan bluetooth [root@localhost michal]# cat /sys/class/rfkill/*/state 1 1 1 1
After installing rfkill [root@localhost michal]# rfkill Usage: rfkill [options] command Options: --version show version (0.3) Commands: help event list block {<idx>,all,wifi,bluetooth,uwb,wimax,wwan,gps} unblock {<idx>,all,wifi,bluetooth,uwb,wimax,wwan,gps} You have new mail in /var/spool/mail/michal [root@localhost michal]# cat /sys/class/rfkill/*/type wlan bluetooth bluetooth wlan [root@localhost michal]# cat /sys/class/rfkill/*/state 1 1 1 1
Sorry, 'rfkill list' Thanks, Dan
#uname -a Linux l 2.6.32.9-70.fc12.x86_64 #1 SMP Wed Mar 3 04:40:41 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux #rfkill list 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no #cat /sys/class/rfkill/*/type bluetooth wlan #cat /sys/class/rfkill/*/state 0 1 # now toggle kill switch #rfkill list 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 15: hci0: Bluetooth Soft blocked: no Hard blocked: no #cat /sys/class/rfkill/*/type bluetooth bluetooth wlan #cat /sys/class/rfkill/*/state 1 1 1
[root@localhost michal]# rfkill list 0: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: no 1: hp-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no 13: hci0: Bluetooth Soft blocked: no Hard blocked: no
*** Bug 579202 has been marked as a duplicate of this bug. ***
NetworkManager-0.8.0-6.git20100408.fc13,ModemManager-0.3-8.git20100408.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-6.git20100408.fc13,ModemManager-0.3-8.git20100408.fc13
NetworkManager-0.8.0-6.git20100408.fc12,ModemManager-0.3-8.git20100408.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-6.git20100408.fc12,ModemManager-0.3-8.git20100408.fc12
NetworkManager-0.8.0-6.git20100408.fc13, ModemManager-0.3-8.git20100408.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 579495 has been marked as a duplicate of this bug. ***
ModemManager-0.3-9.git20100409.fc12, NetworkManager-0.8.0-6.git20100408.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update ModemManager NetworkManager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/NetworkManager-0.8.0-6.git20100408.fc12,ModemManager-0.3-9.git20100409.fc12
I have upgraded to NetworkManager-0.8.0-6.git20100408.fc12.x86_64 and am no longer experiencing this problem on resume.
ModemManager-0.3-9.git20100409.fc12, NetworkManager-0.8.0-6.git20100408.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.