Edimax EW-7811Un V2 adapter not working

ordinary.schreiber · 2022-01-15 10:01:44

Hello everyone, I am using KDE Plasma on a Desktop computer which has also Ubuntu 20.04 and Windows 10 installed (each one on a different drive).

I've been using a Edimax EW-7811Un V2 wlan adapter to connect to wifi for a whille now, and it worked equally in all three operating systems.

Although, recently the adapter "doesn't work" on Archlinux anymore. The system recognizes it correctly and it is able to connect to the wifi, but then the connection doesn't actually work. I get timeouts and contious drops and I can't really navigate.

Instead, it keeps working perfectly on Windows and Ubuntu.

What can I try here?

Last edited by ordinary.schreiber (2022-01-15 10:03:59)

Strike0 · 2022-01-15 10:41:37

Which kernel module does the adapter use? Have you installed extra packages to provide the modules for it?

ordinary.schreiber · 2022-01-15 11:01:00

No, I didn't install any extra package.

It worked straight out of the box as it was supposed to, so I figured it wasn't necessary.

Should I install extra packages to provide kernel modules? How do I do that?

In case it is useful, here is the Edimax support page for that adapter:

https://edimax.freshdesk.com/support/so … -or-higher

ordinary.schreiber · 2022-01-15 11:18:58

Another guide reports additional informations.

https://edimax.freshdesk.com/support/so … ial-driver

The instructions are for Ubuntu systems but the first issue might be the same for both Ubuntu and Arch.

One of the first steps for the installation of those modules on Linux is to verify the kernel version.
The guide says that the adapter supports kernels up to v5.3.7 only.

My output is:

$ uname -r
5.16.0-arch1-1

Does this is mean the adapter can never work on my Arch system?

Last edited by ordinary.schreiber (2022-01-15 11:24:35)

Lone_Wolf · 2022-01-15 11:26:16

edimax wrote:

However, starting from kernel v3.10, there is a built-in driver for our EW-7811Un. You don't need to install any driver, i.e. Plug-and-Play.

IF your problems are with the built-in driver, the older version they list MAY work better.

There are atleast 2 frequently occurring causes that match your symptoms (and have nothing to do with any kernel module):

- a certain NetworkManager setting
- conflicting network services

post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Last edited by Lone_Wolf (2022-01-15 11:27:31)

ordinary.schreiber · 2022-01-15 13:24:49

$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
cups.path                                | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
iwd.service                              | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-media-session.service           | pipewire.service.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
xdg-user-dirs-update.service             | default.target.wants

seth · 2022-01-15 13:48:49

iwd.service                              | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants

NM and iwd will trip over each other. Pick one, disable the other.
If you want to use iwd as NM backend, see https://wiki.archlinux.org/title/Networ … Fi_backend

Also/otherwise please post the output of "lsusb"

ordinary.schreiber · 2022-01-15 14:02:34

Any side effect disabling for example iwd?

Is there any important difference between iwd and NM?

seth wrote:

Also/otherwise please post the output of "lsusb"

$ lsusb
Bus 002 Device 006: ID 4e53:5407  USB OPTICAL MOUSE 
Bus 002 Device 005: ID 1a2c:4c5e China Resource Semico Co., Ltd USB Keyboard
Bus 002 Device 007: ID 0781:5583 SanDisk Corp. Ultra Fit
Bus 002 Device 004: ID 7392:b811 Edimax Technology Co., Ltd Edimax N150 Adapter
Bus 002 Device 003: ID 1bcf:2cb4 Sunplus Innovation Technology Inc. EKACOM-K30
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Last edited by ordinary.schreiber (2022-01-15 14:07:05)

seth · 2022-01-15 14:08:21

IWD is predominantly an alternative to wpa_supplicant, https://wiki.archlinux.org/title/Iwd
NM is a general network manager that uses wpa_supplicant or iwd to establish a wireless carrier
IWD also can configure the network, https://wiki.archlinux.org/title/Iwd#En … figuration - in this case you won't need NM (but iwd afaik won't handle wired connections)

You *must* not use concurrent network managing services because then this here happens:

ordinary.schreiber · 2022-01-15 14:17:07

Will NM handle both wireless and wired connections?

In that case I would probably like to disable iwd.

Last edited by ordinary.schreiber (2022-01-15 14:19:59)

seth · 2022-01-15 14:23:04

Will NM handle both wireless and wired connections?

Yes.

ordinary.schreiber · 2022-01-15 14:31:41

Ok, I just disabled iwd.

Now my output is:

$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
cups.path                                | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-media-session.service           | pipewire.service.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
xdg-user-dirs-update.service             | default.target.wants

Although, I keep having the exact same symptoms as before.
The connection is extremely slow and dashy and it often results in timeouts.

What else can I try?

seth · 2022-01-15 14:34:50

Did you also stop the iwd service or reboot?
If so (because otherwise just disabling the service has no impact on the running system), please post a complete system journal

sudo journalctl -b | curl -F 'f:1=<-' ix.io

ordinary.schreiber · 2022-01-15 14:50:42

For some reason that command doesn't get any output. It seems unable to complete the request.

Anyway I did reboot the system and here is another output. The service seems inactive:

$ sudo systemctl status iwd
○ iwd.service - Wireless service
     Loaded: loaded (/usr/lib/systemd/system/iwd.service; disabled; vendor preset: disabled)
     Active: inactive (dead)

Last edited by ordinary.schreiber (2022-01-15 14:51:31)

seth · 2022-01-15 14:56:22

Journal too big or no network?
Redirect it to a file and upload that somewhere.

ordinary.schreiber · 2022-01-15 15:00:06

I tried again. This time the command completed the request but returned no output at all.

To be able to do so, I temporarily connected with a wired connection from USB-tethering of my smartphone.

Last edited by ordinary.schreiber (2022-01-15 15:02:51)

seth · 2022-01-15 15:03:34

It doesn't matter how you upload the output of "sudo journalctl -b" as long as you do
Eg.

sudo journalctl -b > /tmp/journal.txt

and upload /tmp/journal.txt to a google drive.

ordinary.schreiber · 2022-01-15 15:07:05

I don't know if I got this right.

Now I have this output:

# journalctl -b > /tmp/journal.txt
# journalctl -b | curl -F 'f:1=<-' ix.io
curl: (6) Could not resolve host: ix.io

Last edited by ordinary.schreiber (2022-01-15 15:07:56)

seth · 2022-01-15 15:08:46

Skip "journalctl -b > /tmp/journal.txt"
"journalctl -b > /tmp/journal.txt" posted the output into a file /tmp/journal.txt - somehow™ upload that file, in doubt usb-walk it to a system w/ a working network connection.

ordinary.schreiber · 2022-01-15 15:38:34

Here is the journal.txt file containing that output:

https://we.tl/t-jFV74FDqBQ

seth · 2022-01-15 16:13:26

You're connected

gen 15 16:19:49 archer NetworkManager[317]: <info>  [1642259989.7192] manager: NetworkManager state is now CONNECTED_GLOBAL

and then swicthed to a TTY and somehow™ triggered a re-association

gen 15 16:20:10 archer kernel: R8188EU: INFO assoc success
gen 15 16:20:10 archer wpa_supplicant[391]: wlan0: Associated with 3c:a6:2f:37:68:7b

There's nothing that indicates interim failure/disconnect.
However:

the kernel wrote:

gen 15 16:19:35 archer kernel: r8188eu: module is from the staging directory, the quality is unknown, you have been warned.

"7392:b811" is the v2 of the device, v1 operated on a RTL8192cu chip…
Try

sudo iw dev wlan set power_save off

but the driver has a terrible track record

ordinary.schreiber · 2022-01-15 16:27:49

Here is the output:

$ sudo iw dev wlan set power_save off
command failed: No such device (-19)

seth wrote:

but the driver has a terrible track record

So is my issue related to the driver of the network adapter?

Last edited by ordinary.schreiber (2022-01-15 16:28:44)

seth · 2022-01-15 17:02:22

Sorry, I hit numlock...

sudo iw dev wlan0 set power_save off

If you search for the driver, you'll find lots of reports about "no connectio", "unstable" and "terribly slow" and I could not find a resolution

ordinary.schreiber · 2022-01-15 22:21:16

Lone_Wolf wrote:

IF your problems are with the built-in driver, the older version they list MAY work better.

Could this be a way? In that case, how do I do that?

The output did not change by the way:

$ sudo iw dev wlan0 set power_save off
command failed: No such device (-19)

Although, ifconfig shows the usb adapter with that exact name so I don't understand why that command results in "No such device".

Last edited by ordinary.schreiber (2022-01-15 22:42:06)

seth · 2022-01-16 08:55:39

Do you engage https://wiki.archlinux.org/title/Networ … face_names (because otherwise the "wlan0" device name is an error) and there's "enp3s0: renamed from eth0"

One thing I just noticed looking at the journal again:

pacman -Qs firmware

Arch Linux

#1 2022-01-15 10:01:44

Edimax EW-7811Un V2 adapter not working

#2 2022-01-15 10:41:37

Re: Edimax EW-7811Un V2 adapter not working

#3 2022-01-15 11:01:00

Re: Edimax EW-7811Un V2 adapter not working

#4 2022-01-15 11:18:58

Re: Edimax EW-7811Un V2 adapter not working

#5 2022-01-15 11:26:16

Re: Edimax EW-7811Un V2 adapter not working

#6 2022-01-15 13:24:49

Re: Edimax EW-7811Un V2 adapter not working

#7 2022-01-15 13:48:49

Re: Edimax EW-7811Un V2 adapter not working

#8 2022-01-15 14:02:34

Re: Edimax EW-7811Un V2 adapter not working

#9 2022-01-15 14:08:21

Re: Edimax EW-7811Un V2 adapter not working

#10 2022-01-15 14:17:07

Re: Edimax EW-7811Un V2 adapter not working

#11 2022-01-15 14:23:04

Re: Edimax EW-7811Un V2 adapter not working

#12 2022-01-15 14:31:41

Re: Edimax EW-7811Un V2 adapter not working

#13 2022-01-15 14:34:50

Re: Edimax EW-7811Un V2 adapter not working

#14 2022-01-15 14:50:42

Re: Edimax EW-7811Un V2 adapter not working

#15 2022-01-15 14:56:22

Re: Edimax EW-7811Un V2 adapter not working

#16 2022-01-15 15:00:06

Re: Edimax EW-7811Un V2 adapter not working

#17 2022-01-15 15:03:34

Re: Edimax EW-7811Un V2 adapter not working

#18 2022-01-15 15:07:05

Re: Edimax EW-7811Un V2 adapter not working

#19 2022-01-15 15:08:46

Re: Edimax EW-7811Un V2 adapter not working

#20 2022-01-15 15:38:34

Re: Edimax EW-7811Un V2 adapter not working

#21 2022-01-15 16:13:26

Re: Edimax EW-7811Un V2 adapter not working

#22 2022-01-15 16:27:49

Re: Edimax EW-7811Un V2 adapter not working

#23 2022-01-15 17:02:22

Re: Edimax EW-7811Un V2 adapter not working

#24 2022-01-15 22:21:16

Re: Edimax EW-7811Un V2 adapter not working

#25 2022-01-16 08:55:39

Re: Edimax EW-7811Un V2 adapter not working

Board footer