On Fri, Jun 10, 2016 at 3:34 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > On Fri, Jun 10, 2016 at 3:28 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: >> Here we go again! >> >> Fedora 23 Server, no GUI, running on an Intel NUC which has Intel >> Corporation Wireless 3165. The problem is, despite the radio being on >> and no obvious complaints, no APs are listed with nmcli d list. >> >> # nmcli r >> WIFI-HW WIFI WWAN-HW WWAN >> enabled enabled enabled enabled >> [root@f23s ~]# nmcli c >> NAME UUID TYPE DEVICE >> virbr0-nic 9b346e45-60a4-48d4-a4d2-b5452946093b generic virbr0-nic >> virbr0 a4bc029b-716c-41d7-82a1-71af8f2a045e bridge virbr0 >> enp3s0 5cfa14cc-0d22-4c12-ae08-d61d8f47a011 802-3-ethernet enp3s0 >> [root@f23s ~]# nmcli d >> DEVICE TYPE STATE CONNECTION >> virbr0 bridge connected virbr0 >> enp3s0 ethernet connected enp3s0 >> virbr0-nic tap connected virbr0-nic >> lo loopback unmanaged -- >> wlp2s0 wifi unmanaged -- >> [root@f23s ~]# nmcli d wifi list >> [root@f23s ~]# >> >> That's not expected. A laptop sees many APs for this same command, but >> it's running Workstation so I wonder if there's something Server needs >> that it doesn't get by default (other than firmware and wpa_supplicant >> which I installed afterward). >> >> Also suspicious: >> >> # journalctl -b | grep iwlwifi >> https://paste.fedoraproject.org/377327/ >> >> It's a model 3165 but it wants 7265D firmware, which it finds and uses >> without complaint. But the Carrier: OFF is curious, not sure what that >> means. >> >> Although this is Fedora 23, it is the Fedora 24 kernel and firmware >> files being used which could be related. But it's the first time I've >> tried to use this wifi. > > Fedora 23 Server > [chris@f23s ~]$ rpm -qa | grep NetworkManager > NetworkManager-1.0.12-2.fc23.x86_64 > NetworkManager-libnm-1.0.12-2.fc23.x86_64 > > Fedora 24 Workstation > [chris@f24m Downloads]$ rpm -qa | grep NetworkManager > NetworkManager-wifi-1.2.2-2.fc24.x86_64 > NetworkManager-pptp-1.2.2-1.fc24.x86_64 > NetworkManager-openvpn-gnome-1.2.2-1.fc24.x86_64 > NetworkManager-1.2.2-2.fc24.x86_64 > NetworkManager-bluetooth-1.2.2-2.fc24.x86_64 > NetworkManager-pptp-gnome-1.2.2-1.fc24.x86_64 > NetworkManager-adsl-1.2.2-2.fc24.x86_64 > NetworkManager-openvpn-1.2.2-1.fc24.x86_64 > NetworkManager-wwan-1.2.2-2.fc24.x86_64 > NetworkManager-libnm-1.2.2-2.fc24.x86_64 > NetworkManager-vpnc-gnome-1.2.2-1.fc24.x86_64 > NetworkManager-vpnc-1.2.2-1.fc24.x86_64 > NetworkManager-config-connectivity-fedora-1.2.2-2.fc24.x86_64 > NetworkManager-team-1.2.2-2.fc24.x86_64 > NetworkManager-openconnect-1.2.2-1.fc24.x86_64 > NetworkManager-glib-1.2.2-2.fc24.x86_64 > > > OK! So I'm gonna guess it wants at least NetworkManager-wifi... That did it. It needed some other things also, ModemManager and a few libraries. But now the command works. And I've connected. -- Chris Murphy -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
