Bugzilla – Bug 503757
NetworkManager - wireless not working
Last modified: 2009-07-07 03:19:38 UTC
NetworkManager (NetworkManager-0.7.0.r4359-16.16) does not work with wireless card. I tried both access from kde4 applet and from cnetworkmanager cli, but no wireless networks are found. cnetworkmanager shows, that wlan0 is in state UNAVAILABLE: $ cnetworkmanager -a cnetworkmanager 0.8.4 - Command Line Interface for NetworkManager State: CONNECTED Wifi enabled: 1 Wifi HW enabled: 1 Device: /org/freedesktop/Hal/devices/net_00_1a_6b_d0_9c_a7 Udi: /org/freedesktop/Hal/devices/net_00_1a_6b_d0_9c_a7 Interface: eth0 Driver: e1000e Ip4Address: 10.20.1.107 Capabilities: NM_SUPPORTED,CARRIER_DETECT Dev State: ACTIVATED Ip4Config: /org/freedesktop/NetworkManager/IP4Config/0 Addresses: 10.20.1.107/21.0.0.0 via 10.20.0.1 Nameservers: 10.20.0.2 10.20.0.8 Domains: suse.cz suse.de Dev Type: 802_3_ETHERNET HwAddress: 00:1A:6B:D0:9C:A7 Speed: 1000 Carrier: 1 Device: /org/freedesktop/Hal/devices/net_00_13_e8_8c_65_47 Udi: /org/freedesktop/Hal/devices/net_00_13_e8_8c_65_47 Interface: wlan0 Driver: iwlagn Ip4Address: 0.0.0.0 Capabilities: NM_SUPPORTED Dev State: UNAVAILABLE Dev Type: 802_11_WIRELESS Dev Mode: INFRA Wifi Capabilities: CIPHER_WEP40,CIPHER_WEP104,CIPHER_TKIP,CIPHER_CCMP,WPA,RSN HwAddress: 00:13:E8:8C:65:47 Bitrate: 0 ActiveAccessPoint: / Access Points but if I do 'iwlist scan', I can see all available networks, so this really seems like a bug in NM and not in driver/whatever. Attaching complete list of packages, hwinfo, and logs
Created attachment 292077 [details] hwinfo
Created attachment 292078 [details] /var/log/massages
Created attachment 292079 [details] NM log
Created attachment 292080 [details] rpm -qa
Just from the symptoms this could be a duplicate of bug 502957
Lukas, From the log I found you can connect the wireless successfully on 10 Apr. ======================================== Apr 10 21:57:40 hex NetworkManager: <info> Activation (wlan0/wireless): connection 'midgrad' has security, and secrets exist. No new secrets needed ..... Apr 10 21:57:58 hex NetworkManager: <info> Policy set 'midgrad' (wlan0) as default for routing and DNS. Apr 10 21:57:58 hex NetworkManager: <info> Activation (wlan0) successful, device activated. Apr 10 21:57:58 hex NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complet ======================================== Until 12 May, I found it failed. I thought it should be at below lines. May 12 10:39:41 hex NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add(): Sucess May 13 20:15:04 hex NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed The mgr_state have two state: * DOWN: supplicant manager has been created, but cannot be used; the supplicant * is either not running or has not yet been fully initialized. * IDLE: supplicant manager is ready for use So I guess the status should DOWN. And from the log I can't see below line afer 12 May. (wlan0): supplicant manager state: down -> idle So what's your change after May, do you upgrade some new package? What's you libnl's version?
I have no idea, the NM is working again and I really don't remember what was the configuration at time when I wrote this bugreport. But since it works now, I suggest closing as FIXED
->Fixed. Feel free to reopen it if any issue.