Peter,
I just put down a fresh image:
fedora-arm-image-installer
--image=/home/rgm/arm/Fedora-Server-armhfp-26-1.5-sda.raw.xz
--target=Cubieboard2 --media=/dev/sdb --norootpass --selinux=ON --addconsole
booted up via a USBTTY dongle, set the timezone, hostname, and root
password. Continued and logged in.
No dnf update. This is the software levels shipped.
After logging in, inserted the wifi USB dongle and and same bad
results. So I believe there is some key component missing for wifi
support via nmcli in the minimal server. It works just fine with the
F26-Xfce image and the Centos7-arm image.
So please give me some idea of what may be missing. I am happy to test
installing and getting this working. In fact I really NEED to get this
working by Nov 5 when I leave for pre-IETF travel...
thanks
Bob
On 09/08/2017 10:33 AM, Peter Robinson wrote:
On Thu, Sep 7, 2017 at 6:26 PM, Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote:
I took my F26 cubieboard to a hackathon where all they have here is
wireless.
So I put in a wifi usb dongle and see wlan0 available:
# nmcli device status
DEVICE TYPE STATE CONNECTION
eth0 ethernet unavailable --
lo loopback unmanaged --
wlan0 wifi unmanaged --
I create a connection:
nmcli con add con-name cobo ifname wlan0 type wifi ssid CoboFree
I use "nmcli device wifi connect SSID-Name password wireless-password"
regularly on F-26 without issue to connect to wireless networks
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
