Cannot get Network Adapter to Work

rabbit307 · 2019-02-06 04:21:47

Hello I can't get my network adapter to work. It is AWUS036NEH which seems to use the rt2800usb driver.

systemctl list-unit-files --state=enabled
UNIT FILE                                   STATE  
autovt@.service                             enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
display-manager.service                     enabled
getty@.service                              enabled
NetworkManager-dispatcher.service           enabled
NetworkManager-wait-online.service          enabled
NetworkManager.service                      enabled
sddm.service                                enabled
ufw.service                                 enabled
remote-fs.target                            enabled

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp31s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether 70:85:c2:ae:38:39 brd ff:ff:ff:ff:ff:ff
4: wlp21s0f0u9: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 82:a9:af:cd:1c:0f brd ff:ff:ff:ff:ff:ff

When I attempt any sort of scan it cannot find any networks but does not give an error besides that.

When I do journalctl -b | grep NetworkManager:

Feb 05 22:31:17 archpc NetworkManager[547]: <info>  [1549423877.8123] NetworkManager (version 1.14.5dev+17+gba83251bb-2) is starting... (for the first time)

Feb 05 22:31:17 archpc NetworkManager[547]: <info>  [1549423877.8124] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)

Feb 05 22:31:17 archpc NetworkManager[547]: <info>  [1549423877.8188] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"

Feb 05 22:31:17 archpc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Feb 05 22:31:17 archpc NetworkManager[547]: <info>  [1549423877.8202] manager[0x559dceae9060]: monitoring kernel firmware directory '/lib/firmware'.

Feb 05 22:31:17 archpc dbus-daemon[545]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1' (uid=0 pid=547 comm="/usr/bin/NetworkManager --no-daemon ")

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0058] hostname: hostname: using hostnamed

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0058] hostname: hostname changed from (none) to "archpc"

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0060] dns-mgr[0x559dceaf5930]: init: dns=default, rc-manager=symlink

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0064] manager[0x559dceae9060]: rfkill: WiFi hardware radio set enabled

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0064] manager[0x559dceae9060]: rfkill: WWAN hardware radio set enabled

Feb 05 22:31:18 archpc dbus-daemon[545]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.1' (uid=0 pid=547 comm="/usr/bin/NetworkManager --no-daemon ")

Feb 05 22:31:18 archpc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0267] settings: Loaded settings plugin: NMSKeyfilePlugin (internal)

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0275] settings: Loaded settings plugin: NMSIbftPlugin ("/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-2/libnm-settings-plugin-ibft.so")

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0291] keyfile: new connection /etc/NetworkManager/system-connections/Wired connection 1.nmconnection (520324e5-c8c4-38dd-90a9-4be72a3caaa8,"Wired connection 1")

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0304] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0305] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0306] manager: Networking is enabled by state file

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0308] dhcp-init: Using DHCP client 'internal'

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0365] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-2/libnm-device-plugin-bluetooth.so)

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0375] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-2/libnm-device-plugin-wifi.so)

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0386] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-2/libnm-device-plugin-ovs.so)

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0391] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-2/libnm-device-plugin-wwan.so)

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0398] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-2/libnm-device-plugin-adsl.so)

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0513] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.14.5dev+17+gba83251bb-2/libnm-device-plugin-team.so)

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0523] device (lo): carrier: link connected

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0526] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0535] manager: (enp31s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.0544] device (enp31s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')

Feb 05 22:31:18 archpc dbus-daemon[545]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service' requested by ':1.1' (uid=0 pid=547 comm="/usr/bin/NetworkManager --no-daemon ")

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.1612] ovsdb: Could not connect: No such file or directory

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.7362] wifi-nl80211: (wlan0): using nl80211 for WiFi device control

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.7364] device (wlan0): driver supports Access Point (AP) mode

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.7373] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3)

Feb 05 22:31:18 archpc dbus-daemon[545]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.1' (uid=0 pid=547 comm="/usr/bin/NetworkManager --no-daemon ")

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.7394] rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:01.2/0000:15:00.0/usb1/1-9/1-9:1.0/ieee80211/phy0/rfkill0) (driver rt2800usb)

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.7591] supplicant: wpa_supplicant running

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.7819] device (wlan0): interface index 3 renamed iface from 'wlan0' to 'wlp21s0f0u9'

Feb 05 22:31:18 archpc NetworkManager[547]: <info>  [1549423878.7868] device (wlp21s0f0u9): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')

Feb 05 22:31:23 archpc NetworkManager[547]: <info>  [1549423883.3873] device (wlp21s0f0u9): set-hw-addr: set MAC address to 1A:0A:9B:EB:94:3E (scanning)

Feb 05 22:31:27 archpc systemd[1]: NetworkManager-dispatcher.service: Succeeded.

Feb 05 22:31:27 archpc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Feb 05 22:31:27 archpc kernel: audit: type=1131 audit(1549423887.898:58): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Feb 05 22:31:27 archpc NetworkManager[547]: <info>  [1549423887.9697] sup-iface[0x559dceaed980,wlp21s0f0u9]: supports 4 scan SSIDs

Feb 05 22:31:27 archpc NetworkManager[547]: <info>  [1549423887.9701] device (wlp21s0f0u9): supplicant interface state: starting -> ready

Feb 05 22:31:27 archpc NetworkManager[547]: <info>  [1549423887.9702] device (wlp21s0f0u9): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')

Feb 05 22:31:28 archpc NetworkManager[547]: <info>  [1549423888.0611] agent-manager: req[0x559dceb82560, :1.30/org.kde.plasma.networkmanagement/1000]: agent registered

Feb 05 22:31:33 archpc NetworkManager[547]: <info>  [1549423893.9518] manager: startup complete

What can I do to fix it? I haven't had an issue like this before and the adapter works out of the box on another Arch installation.

Last edited by rabbit307 (2019-02-06 04:49:43)

seth · 2019-02-06 08:27:57

You've no carrier, ie. no cable in the ethernet port and wpa_supplicant/iwd cannot associate w/ an AP.
Please post a complete journal ("sudo journalctl -b")
Also shutdown ufw.service for the moment to rule out interference by a borked firewall rule.

Lone_Wolf · 2019-02-06 09:51:46

Feb 05 22:31:18 archpc NetworkManager[547]: <info> [1549423878.0058] hostname: hostname changed from (none) to "archpc"

Why did you skip the network configuration part of the installation guide ?

rabbit307 · 2019-02-06 14:16:28

.

Last edited by rabbit307 (2019-02-08 14:00:50)

seth · 2019-02-06 14:59:45

There's no attempt to connect any AP at all in that log.
Do you want to use the ethernet or the wifi device and where do you struggle? Did you ever configure a connection??

qinohe · 2019-02-06 15:12:16

Lone_Wolf wrote:

Feb 05 22:31:18 archpc NetworkManager[547]: <info> [1549423878.0058] hostname: hostname changed from (none) to "archpc"
Why did you skip the network configuration part of the installation guide ?

He didn't, it's how NetworkManager initializes itself when you use it the first time.
Yesterday I needed to test something I needed NM for, these lines were in my journal too.

rabbit307 · 2019-02-06 15:25:53

seth wrote:

There's no attempt to connect any AP at all in that log.
Do you want to use the ethernet or the wifi device and where do you struggle? Did you ever configure a connection??

Ethernet works fine, I want to use the wifi device. The problem is that it doesn't show any networks either in network manager or when scanning using something else.

I'm kind of confused because it works out of box on my other arch install...

seth · 2019-02-06 15:27:29

Drop NM (stop and disable the service) and do a manual scan. You can also try wifi-menu before.
https://wiki.archlinux.org/index.php/Wi … uration#iw

rabbit307 · 2019-02-06 15:54:04

seth wrote:

Drop NM (stop and disable the service) and do a manual scan. You can also try wifi-menu before.
https://wiki.archlinux.org/index.php/Wi … uration#iw

When I scan with sudo iw dev wlp21s0f0u9 scan it does not respond with anything, and wifi-menu also says no networks found.

seth · 2019-02-06 16:01:39

Please post full commands and outputs of your attempt. Also ensure "rfkill" that the interface isn't blocked.

rabbit307 · 2019-02-06 16:23:29

seth wrote:

Please post full commands and outputs of your attempt. Also ensure "rfkill" that the interface isn't blocked.

I ran this

john@archPC ~ % sudo iw dev
[sudo] password for john: 
phy#0
        Interface wlp21s0f0u9
                ifindex 3
                wdev 0x1
                addr 00:c0:ca:5f:af:bd
                type managed
                txpower 0.00 dBm
john@archPC ~ % sudo iw dev wlp21s0f0u9 link
Not connected.
john@archPC ~ % sudo ip link set wlp21s0f0u9 up
john@archPC ~ % ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp31s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 70:85:c2:ae:38:39 brd ff:ff:ff:ff:ff:ff
3: wlp21s0f0u9: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:c0:ca:5f:af:bd brd ff:ff:ff:ff:ff:ff
john@archPC ~ % sudo iw dev wlp21s0f0u9 scan
john@archPC ~ % sudo wifi-menu
Scanning for networks... failed
No networks found

john@archPC ~ % sudo wpa_supplicant -B -i wlp21s0f0u9 -c /etc/wpa_supplicant/wpa_supplicant.conf 
Successfully initialized wpa_supplicant
john@archPC ~ % sudo wpa_cli
wpa_cli v2.6
Copyright (c) 2004-2016, Jouni Malinen <j@w1.fi> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.


Selected interface 'wlp21s0f0u9'

Interactive mode

> scan
OK
<3>CTRL-EVENT-SCAN-STARTED 
> scan_results
bssid / frequency / signal level / flags / ssid
<3>CTRL-EVENT-SCAN-RESULTS 
<3>CTRL-EVENT-NETWORK-NOT-FOUND 
>

Rfkill shows it's not blocked too

seth · 2019-02-06 16:40:23

You've to bring the interface down in order to run wifi-menu in a meaningful way.
I guess "txpower: 0.00 dBm" could be a problem… probably some power saving mechanism or a HW switch (though you said it's not blocked)
Can you set it? (see "iw help | grep txpower")

rabbit307 · 2019-02-06 17:00:25

seth wrote:

You've to bring the interface down in order to run wifi-menu in a meaningful way.
I guess "txpower: 0.00 dBm" could be a problem… probably some power saving mechanism or a HW switch (though you said it's not blocked)
Can you set it? (see "iw help | grep txpower")

I brought it down and it still says nothing besides no networks found. As for the txpower I'm not sure what happened at first when it said 0 but I ran iw dev again and it's saying it's 20dBm now(still no change from the lack of scan results prior)

Last edited by rabbit307 (2019-02-06 17:02:02)

rabbit307 · 2019-02-07 01:28:46

bump

ewaller · 2019-02-07 04:43:56

rabbit307 wrote:

bump

Please do not do that. https://wiki.archlinux.org/index.php/Co … ct#Bumping

These are extremely active forums. If no one responded, that might be an indication that you need to provide more information. If nothing else, tell us what you have tried and/or learned since your last post rather than digging it back up and throwing it on the heap.

seth · 2019-02-07 08:29:54

If the interface is up, unblocked, powered and scanning w/o results or errors, there's obviously simply no AP to discover.
Unexepcted reasons can be disjunct frequency/protocol support (if you're only scanning on 2.4GHz, you're not gonna find any 5GHz networks) or mismatching regulatory domains (ie. the AP operates on a channel deemed illegal by the interface)

Compare "iw dev wlp21s0f0u9 link" and "iw dev wlp21s0f0u9 station dump" w/ scan results from another interface.
Try the lts kernel to rule out weird kernel bugs.

Sanity check: did you ever open the notebook case?

Lone_Wolf · 2019-02-07 10:22:14

Some notebooks have physical switches to disable wifi radio , what's the brand and model of this one ?

seth · 2019-02-07 11:07:28

Those would typically remove the device or block it and in the latter case you'd get a "network down" error from the scan.
At least I'm unaware of a system that silently impedes the signal (as it wouid be impossible to determine the state)

One more thing: parallel windows installation?

rabbit307 · 2019-02-07 14:30:08

seth wrote:

If the interface is up, unblocked, powered and scanning w/o results or errors, there's obviously simply no AP to discover.
Unexepcted reasons can be disjunct frequency/protocol support (if you're only scanning on 2.4GHz, you're not gonna find any 5GHz networks) or mismatching regulatory domains (ie. the AP operates on a channel deemed illegal by the interface)
Compare "iw dev wlp21s0f0u9 link" and "iw dev wlp21s0f0u9 station dump" w/ scan results from another interface.
Try the lts kernel to rule out weird kernel bugs.
Sanity check: did you ever open the notebook case?

Gives nothing somehow, this is a new pc build (desktop) and the adapter works flawlessly on my other two arch installs (Old desktop and Thinkpad) with just out of box configuration which is the strangest part. Is there some way I can compare the two, as from what I've seen everything is identical but maybe I'm missing some hidden config file? It sees access points and connects well with nothing additional on the other installs.

I'm starting to think it may be a motherboard issue if that's possible as this doesn't make any sense and things that have made it work for others are not helping me at all.

seth wrote:

Those would typically remove the device or block it and in the latter case you'd get a "network down" error from the scan.
At least I'm unaware of a system that silently impedes the signal (as it wouid be impossible to determine the state)
One more thing: parallel windows installation?

No it is a desktop and no other OS installed except for Arch.

Last edited by rabbit307 (2019-02-07 14:31:46)

seth · 2019-02-07 14:55:23

What do you mean by "gives nothing somehow" - these commands produce no output either?
Can you try a different usb port or move the desktop around (ie. to another location in the room)

rabbit307 · 2019-02-08 03:14:42

seth wrote:

What do you mean by "gives nothing somehow" - these commands produce no output either?
Can you try a different usb port or move the desktop around (ie. to another location in the room)

Linking the device says it is not connected (to an AP of course) and the station dump command returns nothing.

seth · 2019-02-08 07:51:07

Ok, re-reading my post it seems my brain was kinda detached from my fingers when I typed it.
The idea is to compare the devices capabilities ("iw list" or "iw phy phy0 info", assuming phy0) of the disfunctional device w/ scan results and actual connections from the working ones. Sorry.

Arch Linux

#1 2019-02-06 04:21:47

Cannot get Network Adapter to Work

#2 2019-02-06 08:27:57

Re: Cannot get Network Adapter to Work

#3 2019-02-06 09:51:46

Re: Cannot get Network Adapter to Work

#4 2019-02-06 14:16:28

Re: Cannot get Network Adapter to Work

#5 2019-02-06 14:59:45

Re: Cannot get Network Adapter to Work

#6 2019-02-06 15:12:16

Re: Cannot get Network Adapter to Work

#7 2019-02-06 15:25:53

Re: Cannot get Network Adapter to Work

#8 2019-02-06 15:27:29

Re: Cannot get Network Adapter to Work

#9 2019-02-06 15:54:04

Re: Cannot get Network Adapter to Work

#10 2019-02-06 16:01:39

Re: Cannot get Network Adapter to Work

#11 2019-02-06 16:23:29

Re: Cannot get Network Adapter to Work

#12 2019-02-06 16:40:23

Re: Cannot get Network Adapter to Work

#13 2019-02-06 17:00:25

Re: Cannot get Network Adapter to Work

#14 2019-02-07 01:28:46

Re: Cannot get Network Adapter to Work

#15 2019-02-07 04:43:56

Re: Cannot get Network Adapter to Work

#16 2019-02-07 08:29:54

Re: Cannot get Network Adapter to Work

#17 2019-02-07 10:22:14

Re: Cannot get Network Adapter to Work

#18 2019-02-07 11:07:28

Re: Cannot get Network Adapter to Work

#19 2019-02-07 14:30:08

Re: Cannot get Network Adapter to Work

#20 2019-02-07 14:55:23

Re: Cannot get Network Adapter to Work

#21 2019-02-08 03:14:42

Re: Cannot get Network Adapter to Work

#22 2019-02-08 07:51:07

Re: Cannot get Network Adapter to Work

Board footer