Created attachment 908830 [details] dmesg output Description of problem: NetworkManager doesn't show wifi connections on the built-in interface, which was switched on, of course. Edit Networks did not show wifi. iwlist scan says network is down. Version-Release number of selected component (if applicable): https://kojipkgs.fedoraproject.org//work/tasks/5145/7045145/Fedora-Live-Xfce-x86_64-rawhide-20140614.iso How reproducible: Always Steps to Reproduce: 1. Download, burn and boot the DVD 2. Optionally, select Troubleshooting, Test and Start, use TAB to remove rhgb and quiet, and add debug 3. Boot Actual results: System behaves as if there were not built-in wifi. Expected results: Wifi should be usable. Additional info:
Created attachment 908831 [details] /var/log/messages /var/log/messages just after successful boot. Network Manager version is NetworkManager-0.9.9.95-1.git20140609.fc21.x86_64 . Kernel version is kernel-3.16.0-0.rc0.git10.1.fc21.x86_64 .
Did a custom spin with: kernel-3.16.0-0.rc0.git11.1.fc21.x86_64 NetworkManager-0.9.9.95-1.git20140609.fc21.x86_64 wicd-1.7.2.4-9.fc21.x86_64 NetworkManager still doesn't show WIFI. If I add a WIFI connection in Edit Connections, it doesn't show when I click on the applet. wicd with wicd-gtk works.
Running Fedora-Live-Xfce-x86_64-rawhide-20140620.iso from koji. I have: NetworkManager-openconnect-0.9.8.4-3.fc21.x86_64 NetworkManager-glib-0.9.9.95-1.git20140609.fc21.x86_64 NetworkManager-openvpn-0.9.9.0-0.2.git20140128.fc21.x86_64 NetworkManager-vpnc-0.9.9.0-5.git20140428.fc21.x86_64T NetworkManager-vpnc-gnome-0.9.9.0-5.git20140428.fc21.x86_64 NetworkManager-l2tp-0.9.8.6-3.fc21.x86_64 NetworkManager-pptp-0.9.8.2-5.fc21.x86_64 NetworkManager-0.9.9.95-1.git20140609.fc21.x86_64 NetworkManager-wifi-0.9.9.95-1.git20140609.fc21.x86_64 I can see the networks around me with iwlist scan, but NetworkManager allows turning on wifi (it was on by default), but I don't see the available networks.
For the record, the card is Atheros AR9285, driver ath9k: Jun 14 10:09:15 localhost kernel: [ 246.163589] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc90001b80000, irq=17 Jun 14 10:09:15 localhost kernel: ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xffffc90001b80000, irq=17 Jun 14 10:09:16 localhost systemd-udevd[636]: renamed network interface wlan0 to wlp2s0 The device seems to be correctly recognized end exported by NetworkManager. Would you grab output of these command to see the device status: $ nmcli gen status $ nmcli dev $ nmcli dev wifi You could try 'nmcli dev wifi rescan' to force NM start a scan for Wi-Fi networks.
I could not see the nearby AP's in NM's applet. I was able to get a connection with nmcli d wifi connect <AP> password <password> as root. When I reissued this command as a user, I got an "unknown error". When I reissued as root, I also got the unknowd error. After disconnecting with "nmcli d disconnect wlp3s0", I was able to reconnect as root. I didn't try user mode again. Still did not see AP's in NM applet, but Edit Connections showed several with the above AP and a dotted numberical suffix, reflecting a number of (deliberate) attempts to connect with an incorrect password. Entering the passowrd on a command line is a security risk. Fortunately, I have discovered "nmcli -a d wifi connect <AP>". The NM applet changes appropriately to reflect what nmcli has done. The problem is I can't see the surrounding AP's from the applet, but I can from nmcli. Indeed, here is the requested output, with my succesful connection in place: "# nmcli g s STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected full enabled enabled enabled enabled # nmcli d DEVICE TYPE STATE CONNECTION wlp3s0 wifi connected <AP> 4 p33p1 ethernet unavailable -- lo loopback unmanaged -- # nmcli d wifi * SSID MODE CHAN RATE SIGNAL BARS SECURITY <other AP's> * <AP> Infra 6 54 Mbit/s 84 ▂▄▆█ WPA1 WPA2 <other AP's> " With the nmcli workaround, I won't need to use wicd.
So the Wi-Fi device is correctly recognized and NM scans APs. nmcli can get the info from NetworkManager. If you have problems that nm-applet icon doesn't react on left-click, it seems to be a bug in GTK3 - https://bugzilla.gnome.org/show_bug.cgi?id=731612. I've filed a Fedora bug for it - bug 1112650.
Thanks. I've put myself on the CC list for bug 112650, and I'll try a custom built of an Xfce with gtk3-3.12.1-1.
Oops, bug 1112650.
Because of dependencies, regressing gtk3 I used the following command: "rpm --oldpkg -iUv gtk3-3.12.1-1.fc21.x86_64.rpm gtkmm30-3.12.0-1.fc21.x86_64.rpm gtk3-immodule-xim-3.12.1-1.fc21.x86_64.rpm" . The resulting DVD worked fine. I no longer wicd as a backup (comment 2). To execute the command, I used the '-l' switch option in livecd-creator. To get the rpms into the chroot environment the -l switch provides, I used the technique described in http://billauer.co.il/blog/2012/06/livedvd-kickstart-modified/, where it says: "The liveCD’s root is visible to the “outside world” at something like /var/tmp/imgcreate-q2Hvwg/install_root". In my case, I like to specify an explicit temporary directory, so I can copy the rpms into a place visible to the chroot shell and execute the rpm command. I mention the technique here because it can be used in situations where it's necessary to perform a few rpm updates before burning the CD.
Works with gtk3-3.13.3-2.fc21.x86_64 .
I'm seeing this with current Fedora 21: NetworkManager-0.9.10.0-1.git20140704.fc21.1 kernel-3.16.0-0.rc7.git0.1.fc21.x86_64 03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 3e) The system behaves as though Wi-Fi is disabled. [tim@localhost ~]$ nmcli dev DEVICE TYPE STATE CONNECTION virbr0 bridge connected virbr0 em1 ethernet unavailable -- lo loopback unmanaged -- wlp3s0 wifi unmanaged -- [tim@localhost ~]$ nmcli dev wifi [tim@localhost ~]$ nmcli dev wifi rescan Error: No Wi-Fi device found. The same system runs Fedora 20 without problems.
Configuring the wifi interface manually with wpa_passphrase/wpa_supplicant/dhclient works fine. Why would NetworkManager think wlp3s0 is 'unmanaged'?
(In reply to Tim Waugh from comment #12) > Configuring the wifi interface manually with > wpa_passphrase/wpa_supplicant/dhclient works fine. > > Why would NetworkManager think wlp3s0 is 'unmanaged'? Most probably by configuration either supplied by the administrator or through some configuration package. You should look for "unmanaged-devices" in /etc/NetworkManager files.
(In reply to Pavel Šimerda (pavlix) from comment #13) > > Why would NetworkManager think wlp3s0 is 'unmanaged'? > > Most probably by configuration either supplied by the administrator or > through some configuration package. You should look for "unmanaged-devices" > in /etc/NetworkManager files. This is a fresh install (clean install of Fedora 20, wifi configured, updates installed, then 'yum distro-sync --releasever=21'). 'find /etc/NetworkManager -type f | xargs grep managed' gave no output.
Wi-Fi support in NetworkManager has been separated to a plugin and it is contained in NetworkManager-wifi package on Fedora. The package should be pulled in automatically on update. However, it may be the update didn't go properly (due to missing keys or something) and NetworkManager-wifi package was not installed. Tim, please check that you have the package installed.
(In reply to Jirka Klimes from comment #15) > Tim, please check that you have the package installed. Thanks, it was not installed. After installing it, the problem is fixed.
Great. For the record, NM spec in F21 for NetworkManager-wifi contains: %define obsoletes_nmver 1:0.9.9.95-1 Obsoletes: NetworkManager < %{obsoletes_nmver} which should install NetworkManager-wifi on updates from the old NM versions.
*** Bug 1134055 has been marked as a duplicate of this bug. ***