Discussion:
[fedora-arm] Fedora-Server-armhfp-26-1.5-sda nmcli wili problems
Robert Moskowitz
2017-09-07 17:26:24 UTC
Permalink
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

(CoboFree is the SSID I am using here on my notebook)

# nmcli connection show

NAME UUID TYPE DEVICE

cobo d9e7a648-0d48-4353-856f-7c3a3dd3db3b 802-11-wireless --

eth0 9699134e-a93c-32fb-b518-a0dc17cc78a3 802-3-ethernet --



I then try to bring the connection up:

# nmcli con up cobo
Error: Connection activation failed: No suitable device found for this
connection.

nmcli device wifi list

is an empty list

What am I missing here. I have used mncli on other builds in the past.
This is my first try with this image.

thanks

Bob
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedoraproject.
Peter Robinson
2017-09-08 14:33:14 UTC
Permalink
Post by Robert Moskowitz
I took my F26 cubieboard to a hackathon where all they have here is
wireless.
# nmcli device status
DEVICE TYPE STATE CONNECTION
eth0 ethernet unavailable --
lo loopback unmanaged --
wlan0 wifi unmanaged --
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 -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-leave
Robert Moskowitz
2017-09-08 20:31:58 UTC
Permalink
Post by Peter Robinson
Post by Robert Moskowitz
I took my F26 cubieboard to a hackathon where all they have here is
wireless.
# nmcli device status
DEVICE TYPE STATE CONNECTION
eth0 ethernet unavailable --
lo loopback unmanaged --
wlan0 wifi unmanaged --
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
Is this with minimal server? Perhaps I am missing something?


[***@C2 8021ARintermediate]$ [19412.644618] usb 1-1: new high-speed USB
device number 2 using ehci-platform
[19412.781778] usb 1-1: New USB device found, idVendor=148f, idProduct=7601
[19412.788666] usb 1-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[19412.795933] usb 1-1: Product: 802.11 n WLAN
[19412.800299] usb 1-1: Manufacturer: MediaTek
[19412.804635] usb 1-1: SerialNumber: 1.0
[19413.509622] usb 1-1: reset high-speed USB device number 2 using
ehci-platform
[19413.637694] mt7601u 1-1:1.0: ASIC revision: 76010001 MAC revision:
76010500
[19413.654471] mt7601u 1-1:1.0: Firmware Version: 0.1.00 Build: 7640
Build time: 201302052146____
[19414.058900] mt7601u 1-1:1.0: Warning: unsupported EEPROM version 0d
[19414.065401] mt7601u 1-1:1.0: EEPROM ver:0d fae:00
[19414.501327] usbcore: registered new interface driver mt7601u
nmcli dev status
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected eth0
lo loopback unmanaged --
wlan0 wifi unmanaged --
[***@C2 8021ARintermediate]$ nmcli device wifi list
[***@C2 8021ARintermediate]$ nmcli device wifi connect HTTNET password
mypassword
Error: No Wi-Fi device found.

_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedoraproject.or
Robert Moskowitz
2017-09-11 18:09:13 UTC
Permalink
I really think there is something wrong/missing with this F26 minimal
server for wifi support.

With my F26-Xfce image:

# nmcli dev status
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected Wired connection 1
wlan0 wifi disconnected --
lo loopback unmanaged --
[***@cubie2 ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
HTTNET Infra 11 54 Mbit/s 100 ▂▄▆█ WPA2

Then I put in my Centos7-arm image:

# nmcli dev status
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected eth0
wlan0 wifi disconnected --
lo loopback unmanaged --
[***@z9m9z ~]# nmcli device wifi list
* SSID MODE CHAN RATE SIGNAL BARS SECURITY
HTTNET Infra 11 54 Mbit/s 100 **** WPA2

So it is not the hardware. It is the server minimal image. What do I
need to add to it?

thanks
Post by Peter Robinson
Post by Robert Moskowitz
I took my F26 cubieboard to a hackathon where all they have here is
wireless.
# nmcli device status
DEVICE TYPE STATE CONNECTION
eth0 ethernet unavailable --
lo loopback unmanaged --
wlan0 wifi unmanaged --
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 -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm
Robert Moskowitz
2017-09-12 20:57:03 UTC
Permalink
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
Post by Peter Robinson
Post by Robert Moskowitz
I took my F26 cubieboard to a hackathon where all they have here is
wireless.
# nmcli device status
DEVICE TYPE STATE CONNECTION
eth0 ethernet unavailable --
lo loopback unmanaged --
wlan0 wifi unmanaged --
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 -- ***@lists.fedoraproject.org
To unsubscribe send an e
Robert Moskowitz
2017-09-13 15:24:37 UTC
Permalink
Oh, here is what I found in /var/log/messages for the TP-Link:

Sep 12 17:09:22 localhost kernel: usb 1-1: new high-speed USB device
number 4 using ehci-platform
Sep 12 17:09:22 localhost kernel: usb 1-1: New USB device found,
idVendor=0cf3, idProduct=9271
Sep 12 17:09:22 localhost kernel: usb 1-1: New USB device strings:
Mfr=16, Product=32, SerialNumber=48
Sep 12 17:09:22 localhost kernel: usb 1-1: Product: USB2.0 WLAN
Sep 12 17:09:22 localhost kernel: usb 1-1: Manufacturer: ATHEROS
Sep 12 17:09:22 localhost kernel: usb 1-1: SerialNumber: 12345
Sep 12 17:09:22 localhost kernel: usb 1-1: ath9k_htc: Firmware
ath9k_htc/htc_9271-1.4.0.fw requested
Sep 12 17:09:22 localhost kernel: usbcore: registered new interface
driver ath9k_htc
Sep 12 17:09:23 localhost kernel: usb 1-1: ath9k_htc: Transferred FW:
ath9k_htc/htc_9271-1.4.0.fw, size: 51008
Sep 12 17:09:23 localhost kernel: ath9k_htc 1-1:1.0: ath9k_htc: HTC
initialized with 33 credits
Sep 12 17:09:23 localhost kernel: ath9k_htc 1-1:1.0: ath9k_htc: FW
Version: 1.4
Sep 12 17:09:23 localhost kernel: ath9k_htc 1-1:1.0: FW RMW support: On
Sep 12 17:09:23 localhost kernel: ieee80211 phy1: Atheros AR9271 Rev:1
Sep 12 17:09:23 localhost NetworkManager[765]: <info> [1505250563.8303]
manager: (wlan0): 'wifi' plugin not available; creating generic device
Sep 12 17:09:23 localhost systemd: Starting Load/Save RF Kill Switch
Status...
Sep 12 17:09:23 localhost NetworkManager[765]: <info> [1505250563.8859]
manager: (wlan0): new Generic device
(/org/freedesktop/NetworkManager/Devices/4)
Sep 12 17:09:24 localhost systemd-udevd: link_config: autonegotiation is
unset or enabled, the speed and duplex are not writable.
Sep 12 17:09:24 localhost crda: setting regulatory domain to US based on
timezone (America/New_York)
Sep 12 17:09:24 localhost NetworkManager[765]: <info> [1505250564.2765]
rfkill1: found WiFi radio killswitch (at
/sys/devices/platform/***@01c00000/1c14000.usb/usb1/1-1/1-1:1.0/ieee80211/phy1/rfkill1)
(driver ath9k_htc)
Sep 12 17:09:24 localhost audit: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Sep 12 17:09:24 localhost systemd: Started Load/Save RF Kill Switch Status.
Sep 12 17:09:29 localhost audit: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Post by Robert Moskowitz
Peter,
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
What make/model/chipset/driver? You need to provide more information
that "usb dongle"
Post by Robert Moskowitz
I believe there is some key component missing for wifi support via nmcli in
There isn't, I use it literally on dozens of different ARM devices
exactly as you define above, there might well be with your specific
version USB dongle but it's not generally got an issue.
Post by Robert Moskowitz
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...
I don't see what the travel has to do with this bug report
Post by Robert Moskowitz
thanks
Bob
Post by Peter Robinson
Post by Robert Moskowitz
I took my F26 cubieboard to a hackathon where all they have here is
wireless.
# nmcli device status
DEVICE TYPE STATE CONNECTION
eth0 ethernet unavailable --
lo loopback unmanaged --
wlan0 wifi unmanaged --
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 -- ***@lists.fedoraproject.org
To unsubscribe send an email to a

Loading...