Description of problem: nmcli refuses to bring up my wireless device in Fedora 21 beta. I can't test with the NetworkManager applet due to a video driver issue that causes GNOME to not work. Version-Release number of selected component (if applicable): $ nmcli --version nmcli tool, version 0.9.10.0-10.git20140704.fc21 How reproducible: always Steps to Reproduce: $ nmcli device DEVICE TYPE STATE CONNECTION em1 ethernet connected enp2s1 lo loopback unmanaged -- wlp2s2 wifi unmanaged -- $ nmcli device wifi list ifname wlp2s2 Error: Device 'wlp2s2' is not a Wi-Fi device. Expected results: wlp2s2 clearly is a Wi-Fi device and worked fine in Fedora 19 Additional info: $ lspci |grep Network 02:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
Note the device had a different name in Fedora 19, I forget what it was though.
This might be due to missing NetworkManager-wifi package. Please check if it is installed (and install if it is not). $ rpm -q NetworkManager-wifi
Installing NetworkManager-wifi has fixed the issue! (I had some package conflict and had to swap NetworkManager-14.git20140704.fc21 for NetworkManager-13.git20140704.fc21 before I could install it). Thanks for your help!
Re-opening the bug for better indication in nmcli of the possible not-installed-wifi-plugin problem. See a patch in http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=jk/nm-plugin-missing&id=0cefe02acbb2e3e945308309e65ce86c7e2caeb9 The problem of missing Wi-Fi plugin may occur, for example, when installing minimal Fedora installation on ARM, that doesn't install NetworkManager-wifi by default.
The patch has been committed upstream: e304f04 cli: better indicate when a Wi-Fi plugin might not be available (rh #1168573) - nm-0-9-10 70f375b cli: better indicate when a Wi-Fi plugin might not be available (rh #1168573) - nm-1-0 823df33 cli: better indicate when a Wi-Fi plugin might not be available (rh #1168573) - master
NetworkManager-1.0.2-1.fc22,network-manager-applet-1.0.2-1.fc22,NetworkManager-openconnect-1.0.2-1.fc22,NetworkManager-openvpn-1.0.2-1.fc22,NetworkManager-vpnc-1.0.2-1.fc22,NetworkManager-openswan-1.0.2-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/NetworkManager-1.0.2-1.fc22,network-manager-applet-1.0.2-1.fc22,NetworkManager-openconnect-1.0.2-1.fc22,NetworkManager-openvpn-1.0.2-1.fc22,NetworkManager-vpnc-1.0.2-1.fc22,NetworkManager-openswan-1.0.2-1.fc22
NetworkManager-0.9.10.2-4.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/FEDORA-2015-7623/NetworkManager-0.9.10.2-4.fc21
Package NetworkManager-1.0.2-1.fc22, NetworkManager-openconnect-1.0.2-1.fc22, NetworkManager-vpnc-1.0.2-1.fc22, network-manager-applet-1.0.2-1.fc22, NetworkManager-openvpn-1.0.2-1.fc22, NetworkManager-openswan-1.0.2-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-1.0.2-1.fc22 NetworkManager-openconnect-1.0.2-1.fc22 NetworkManager-vpnc-1.0.2-1.fc22 network-manager-applet-1.0.2-1.fc22 NetworkManager-openvpn-1.0.2-1.fc22 NetworkManager-openswan-1.0.2-1.fc22' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-7767/NetworkManager-1.0.2-1.fc22,network-manager-applet-1.0.2-1.fc22,NetworkManager-openconnect-1.0.2-1.fc22,NetworkManager-openvpn-1.0.2-1.fc22,NetworkManager-vpnc-1.0.2-1.fc22,NetworkManager-openswan-1.0.2-1.fc22 then log in and leave karma (feedback).
NetworkManager-1.0.2-1.fc22, NetworkManager-openconnect-1.0.2-1.fc22, NetworkManager-vpnc-1.0.2-1.fc22, network-manager-applet-1.0.2-1.fc22, NetworkManager-openvpn-1.0.2-1.fc22, NetworkManager-openswan-1.0.2-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
NetworkManager-0.9.10.2-5.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1195792 has been marked as a duplicate of this bug. ***