Since all indicators show OK, one question is: how have you plugged the device in? Do you have an extension cable, and if so, is it really working properly? Or have you tried all of the USB ports?
So maybe changing some physical stuff could make the difference?
I’ll have to try some physical stuff, I have tried in various USB ports (version 2.0 and 3.0) but I have not tried uninstalling the PCI adapter entirely (physically).
Do you stay in CN ? may this needs to be setup to your country in some way… looks like some settings inside EEPROM of the device…
No, I’m in the U.S., however those messages are for the PCI adapter which is hard-coded to use CN regdomain settings (I haven’t found any way to change the regdomain for it, but it at least works reasonably well even with that regdomain). The reason I know that is due to the following output:
# iw reg get global country US: DFS-FCC (2402 - 2472 @ 40), (N/A, 30), (N/A) (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS (5735 - 5835 @ 80), (N/A, 30), (N/A) (57240 - 63720 @ 2160), (N/A, 40), (N/A) phy#0 country CN: DFS-FCC (2402 - 2482 @ 40), (N/A, 20), (N/A) (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW (5735 - 5835 @ 80), (N/A, 30), (N/A) (57240 - 59400 @ 2160), (N/A, 28), (N/A) (59400 - 63720 @ 2160), (N/A, 44), (N/A) (63720 - 65880 @ 2160), (N/A, 28), (N/A)
Which, I can confirm by running
phy#0is the PCI adapter.
According to this, that should be “ath9k_htc.conf” and
options ath9k_htc nohwcrypt=1, respectively. I’ll have to try that.
The store page (including specifications) for the ThinkPenguin Wireless N USB Adapter for GNU/Linux (TPE-N150USB) can be found here: https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb
I currently already have a similar PCI wireless adapter installed (and it seems to work O.K.) but I’d like this USB adapter to show some sign of functioning as well. I didn’t need to do anything for the USB adapter to be recognized correctly (according to
lsusb), and it shows up as not being soft blocked nor hard blocked, but when I try to scan for available networks (using
iw, or even NetworkManager) I get absolutely no results (even though I know there are at least 4 or 5 networks in range, all of which the PCI adapter picks up normally). No errors, always a return code of 0, but just no output. If I try to connect using
wpa_supplicantagrees that there are “no good candidates” when scanning, and tries to rescan every 5 seconds to no avail.
I noticed that the store page specifies USB 2.0, so I’ve done most of the testing on 2.0, but I tried 3.0 as well and the results were identical.
Here are the “usual” system logs:
…and here are some more specific results pertinent to the problem:
# rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no
phy0is the PCI adapter and
phy1is the USB in question.
The results of running
lsusb -vas root are here: https://pastebin.com/ycXf4NXd
# dmesg | grep usbcore [ 0.413342] usbcore: registered new interface driver usbfs [ 0.413342] usbcore: registered new interface driver hub [ 0.413346] usbcore: registered new device driver usb [ 0.640940] usbcore: registered new interface driver usbserial_generic [ 1.273737] usbcore: registered new interface driver usbhid [ 1.403328] usbcore: registered new interface driver usb-storage [ 1.404922] usbcore: registered new interface driver uas [ 10.946677] usbcore: registered new interface driver snd_usb_toneport [ 11.024689] usbcore: registered new interface driver ath9k_htc
# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether bc:5f:f4:d9:26:90 brd ff:ff:ff:ff:ff:ff 3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether ec:08:6b:fd:ef:72 brd ff:ff:ff:ff:ff:ff 4: wlp0s26u1u5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether 28:24:ff:1a:03:6b brd ff:ff:ff:ff:ff:ff
# iw dev phy#1 Interface wlp0s26u1u5 ifindex 4 wdev 0x100000001 addr 28:24:ff:1a:03:6b type managed txpower 20.00 dBm phy#0 Interface wlp2s0 ifindex 3 wdev 0x1 addr ec:08:6b:fd:ef:72 type managed txpower 16.00 dBm multicast TXQ: qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets 0 0 0 0 0 0 0 0 0
wlp0s26u1u5) is the USB and
wlp2s0) is the PCI.
# iw dev wlp0s26u1u5 scan # echo $? 0