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/soc@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' [root@localhost ~]#
On 09/12/2017 05:02 PM, Peter Robinson wrote:
On Tue, Sep 12, 2017 at 9:57 PM, Robert Moskowitz rgm@htt-consult.com wrote:
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
What make/model/chipset/driver? You need to provide more information that "usb dongle"
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.
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
thanks
Bob
On 09/08/2017 10:33 AM, Peter Robinson wrote:
On Thu, Sep 7, 2017 at 6:26 PM, Robert Moskowitz rgm@htt-consult.com 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
-
Robert Moskowitz