[Solved] Wifi TP-Link TL-WN823N doesn't work

manux-chacarita · 2019-02-08 16:31:37

Hi, I'm trying to use my Wlan adapter: TL-WN823N with no luck.
I've tried both in my laptop and in my PC.

1) The adapter seems to be detected:
$lsusb

4 Bus 001 Device 005: ID 2357:0109 TP-Link TL WN823N RTL8192EU

2) The driver seems to be loaded:
$dmesg | grep usbcore

 22 [    0.274361] usbcore: registered new interface driver usbfs
 23 [    0.274361] usbcore: registered new interface driver hub
 24 [    0.274361] usbcore: registered new device driver usb
 25 [    0.396046] usbcore: registered new interface driver usbserial_generic
 26 [    1.554273] usbcore: registered new interface driver usbhid
 27 [    5.879897] usbcore: registered new interface driver snd-usb-audio
 28 [    5.881150] usbcore: registered new interface driver uvcvideo
 29 [    6.790052] usbcore: registered new interface driver rtl8xxxu
 30 [    6.790052] usbcore: registered new interface driver rtl8xxxu

3)After $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: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
      link/ether 1c:1b:0d:52:dd:e8 brd ff:ff:ff:ff:ff:ff
 3: wlp0s20f0u8: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
      link/ether 8e:9c:94:c6:3e:0d brd ff:ff:ff:ff:ff:ff

4)Check kernel messages for the firmware:
$dmesg | grep firmware

[    0.196610] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    3.864926] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    5.814188] usb 1-8: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin

5)Check any messages for the rtl8xxxu
$checkdmesg | grep rtl8xxxu

[    5.814188] usb 1-8: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
[    6.790052] usbcore: registered new interface driver rtl8xxxu
[    6.792422] rtl8xxxu 1-8:1.0 wlp0s20f0u8: renamed from wlan0

6)When I try$wifi-menu
The networks are recognized
I chose mine, enter password
And I get:
"CONNECTING FAILED"

I've followed the following post, with the same results:
https://michaelheap.com/tp-link-tl-wn82 … rch-linux/

I've both tried in a clean installation of Arch and in my laptop where I've not installed yet, and can't do it because I don't have a inner card (either for ethernet or wifi)

Thanks!!!

Last edited by manux-chacarita (2019-02-09 11:16:40)

seth · 2019-02-08 17:35:26

The behavior is recorded for the chip.
Please do not follow random blog posts, see https://aur.archlinux.org/packages/8192eu-dkms/ and post updated outputs (because after installing 8192eu, rtl8xxxu should no longer show up)

manux-chacarita · 2019-02-08 21:22:09

Thanks for your response.
As you suggested, I've installed 8192eu and this are the outputs,
Please let me know if I'm missing any logs

$ dmesg | grep usbcore

 
[    0.275793] usbcore: registered new interface driver usbfs
[    0.275793] usbcore: registered new interface driver hub
[    0.275793] usbcore: registered new device driver usb
[    0.395704] usbcore: registered new interface driver usbserial_generic
[    1.493812] usbcore: registered new interface driver usbhid
[    5.211821] usbcore: registered new interface driver snd-usb-audio
[    5.213099] usbcore: registered new interface driver uvcvideo
[    6.118633] usbcore: registered new interface driver rtl8xxxu
[    6.133636] usbcore: registered new interface driver rtl8192eu

$ dmesg | grep 8192eu

[    4.800259] usb 1-8: rtl8192eu_parse_efuse: dumping efuse (0x200 bytes):
[    4.800304] usb 1-8: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
[    5.779866] 8192eu: loading out-of-tree module taints kernel.
[    5.780135] 8192eu: module verification failed: signature and/or required key missing - tainting kernel
[    5.789584] RTL871X: rtl8192eu v4.4.1_17696.20160509_BTCOEX20160412-0042
[    5.789585] RTL871X: rtl8192eu BT-Coex version = BTCOEX20160412-0042
[    5.789608] usbcore: registered new interface driver rtl8192eu

dmesg | grep xxxu

[    4.800304] usb 1-8:i rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
[    5.773741] usbcore: registered new interface driver rtl8xxxu
[    5.792051] rtl8xxxu 1-8:1.0 wlp0s20f0u8: renamed from wlan0

seth · 2019-02-08 21:29:50

What happens if you blacklist rtl8xxxu?
https://wiki.archlinux.org/index.php/Ke … acklisting

(To be sure: it still doesn't work, does it?)

manux-chacarita · 2019-02-08 22:18:25

Hi, thank you very much Seth!
It was dead, but after blacklisting the old driver, it started working.

One more thing:
wifi-menu is still not working, I can use it through Network Manager inside my Window Manager.
Any ideas?

(Should I close this post and open a new one with the last question?)

Thanks again!

seth · 2019-02-08 22:23:18

From your initial post, something (probably networkmanager?) is bringing the interface up and wifi-menu will refuse to operate it.
Pick and use only one network managing service (in case of wifi-menu it's netctl) per interface.

manux-chacarita · 2019-02-09 10:33:18

Thanks again, yes, I could connect directly after booting through the network manager cli.
Now that I have the solution for the desk pc (ethernet helped me downloading the drivers) I would like to use the same drivers in a new fresh installation on a laptop with no ethernet or wifi card, just USB and the same wlan adapter. Should I remaster the arch iso with the 8192eu drivers before installation?

seth · 2019-02-09 10:45:13

You'll have to get the kernel module onto that system - whether you remaster an iso or just usb-walk it over doesn't matter.
Notice that the dkms package will attempt to build the module, what's likely not going to work (I've no idea, but don't think there's a compiler in the iso) - so you have to bring a precompiled module !!!for the kernel version in the iso!!!

If you're facing more issues, you'd better open a new thread on topic.

progandy · 2019-02-09 10:45:24

You can remaster it or you could build the module with the same kernel version as the ISO, put the built package on a USB drive and install it on the booted iso.

Edit: As seth said, a dkms won't work of course. Then you'd have to copy and install dkms with all its dependencies as well.

Edit: You could use the dkms package and let it build the module after installing it on the host with the correct kernel version, and then copy it manually to the position in /usr/lib/modules. Then "rmmod" the original module and then load the new one.

Last edited by progandy (2019-02-09 10:53:57)

manux-chacarita · 2019-02-09 10:51:29

Thank you guys, as you suggested I will try out and if I have any issues in the process I'll open a new thread.

ewaller · 2019-02-09 16:17:47

Is tethering a phone by USB an option? They show up as a wired Ethernet. Just plug it it, turn on tethering, and run dhcpcd as root.

manux-chacarita · 2019-02-10 21:33:02

ewaller wrote:

Is tethering a phone by USB an option?

Hi Ewaller! It's a great option that I haven't thought about before.
I've tried it in my pc with arch installed and it worked perfectly.
When I try in the laptop with the arch ISO:

1) # dhcpcd

dlopen: /usr/lib/dhcpcd/dev/udev.so: cannot read file data: Input/output error
script_runreason: /usr/lib/dhcpcd/dhcpcd-run-hooks: Input/output error
script_runreason: /usr/lib/dhcpcd/dhcpcd-run-hooks: Input/output error
DUID 00:04:5c:46:06:fa:19:2f:45:3a:b2:99:7b:08:8c:63:bb:9b
enp0s20u1: IAID 49:a7:a1:c6
enp0s20u1: soliciting an IPv6 router
enp0s20u1: rebinding lease of 192.168.42.139
enp0s20u1: leased 192.168.42.139 for 3600 seconds
enp0s20u1: adding route to 192.168.42.0/24
enp0s20u1: adding default route via 192.168.42.129
script_runreason: /usr/lib/dhcpcd/dhcpcd-run-hooks: Input/output error
forked to background, child pid 847

2) If I run again dhcpcd:

sending commands to master dhcpcd process

3) ping 8.8.8.8 works fine, same thing with for example archlinux.org ip

4) But when I ping archlinux.org:

ping: archlinux.org: Temporary failure in name resolution

(If I am going out of the thread let me know and I'll do a new post about this issue probably in newbies section)
Thanks!

Last edited by manux-chacarita (2019-02-10 22:22:25)

manux-chacarita · 2019-02-11 21:23:05

I was missing to add a name server in the /etc/resolv.conf :
For example:

 nameserver 8.8.8.8

After this I could ping any url.
Thanks again guys!

akxninja · 2019-09-15 08:37:51

manux-chacarita wrote:

Hi, thank you very much Seth!
It was dead, but after blacklisting the old driver, it started working.
One more thing:
wifi-menu is still not working, I can use it through Network Manager inside my Window Manager.
Any ideas?
(Should I close this post and open a new one with the last question?)
Thanks again!

Hi,
I am facing the same problem. would you mind sharing how this got fixed for you?

$ lsusb
Bus 001 Device 002: ID 2357:0109 TP-Link TL WN823N RTL8192EU

This is my networkctl output:

$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eno1 ether no-carrier unmanaged
3 wlp0s20u2 wlan no-carrier configuring
5 enp0s20u3 ether routable unmanaged

The 3rd interface (wlp0s20u2) is my tplink tl823n.
Its always showing 'configuring'

$ sudo dmesg | grep usbcore
[ 0.728638] usbcore: registered new interface driver usbfs
[ 0.728638] usbcore: registered new interface driver hub
[ 0.728638] usbcore: registered new device driver usb
[ 1.020327] usbcore: registered new interface driver usbserial_generic
[ 13.282545] usbcore: registered new interface driver usbhid
[ 14.036185] usbcore: registered new interface driver uvcvideo
[ 14.863032] usbcore: registered new interface driver rtl8xxxu
[ 420.318702] usbcore: registered new interface driver snd-usb-audio
[ 427.076834] usbcore: registered new interface driver cdc_ether
[ 427.089387] usbcore: registered new interface driver rndis_host

$ sudo dmesg | grep firmware
[ 0.236770] Spectre V2 : Enabling Restricted Speculation for firmware calls
[ 13.434323] usb 1-2: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin

$dhcpcd
sending commands to master dhcpcd process

I have installed the drivers from the link above (https://aur.archlinux.org/packages/8192eu-dkms/) and it got completed without any errors.
I can see the SSIDs available and upon connecting i get an error connection to 'BSSID' is deactivated. i tried with wpa_supplicant and systemd.

$ cat /etc/wpa_supplicant/wpa_supplicant-wlp0s20u2.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
update_config=1
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="GNXS-43DC98"
psk="password"

}

systemctl status wpa_supplicant
● wpa_supplicant.service - WPA supplicant
Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: disabled)
Active: active (running) since Sun 2019-09-15 13:24:44 IST; 34min ago
Main PID: 2560 (wpa_supplicant)
Tasks: 1 (limit: 4915)
Memory: 1.6M
CGroup: /system.slice/wpa_supplicant.service
└─2560 /usr/bin/wpa_supplicant -u
Sep 15 13:50:47 ninjabox wpa_supplicant[2560]: wlp0s20u2: CTRL-EVENT-SSID-REENABLED id=0 ssid="GNXS-43DC98"
Sep 15 13:50:47 ninjabox wpa_supplicant[2560]: wlp0s20u2: SME: Trying to authenticate with 34:e3:80:43:dc:98 (SSID='GNXS-43DC98' freq=2432 MHz)
Sep 15 13:50:48 ninjabox wpa_supplicant[2560]: wlp0s20u2: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="GNXS-43DC98" auth_failures=2 duration=20 reason=CONN_FAILED
Sep 15 13:50:58 ninjabox wpa_supplicant[2560]: wlp0s20u2: CTRL-EVENT-SCAN-FAILED ret=-16
Sep 15 13:56:14 ninjabox wpa_supplicant[2560]: wlp0s20u2: SME: Trying to authenticate with 34:e3:80:43:dc:98 (SSID='GNXS-43DC98' freq=2432 MHz)
Sep 15 13:56:14 ninjabox wpa_supplicant[2560]: wlp0s20u2: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="GNXS-43DC98" auth_failures=1 duration=10 reason=CONN_FAILED
Sep 15 13:56:26 ninjabox wpa_supplicant[2560]: wlp0s20u2: CTRL-EVENT-SSID-REENABLED id=0 ssid="GNXS-43DC98"
Sep 15 13:56:26 ninjabox wpa_supplicant[2560]: wlp0s20u2: SME: Trying to authenticate with 34:e3:80:43:dc:98 (SSID='GNXS-43DC98' freq=2432 MHz)
Sep 15 13:56:27 ninjabox wpa_supplicant[2560]: wlp0s20u2: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="GNXS-43DC98" auth_failures=2 duration=20 reason=CONN_FAILED
Sep 15 13:56:36 ninjabox wpa_supplicant[2560]: wlp0s20u2: Reject scan trigger since one is already pending

I tried blacklisting the old driver like the following.

$ sudo cat /etc/modprobe.d/nobeep.conf
blacklist rtl8xxxu

and i then rebooted. but nothing worked.

any pointers would be highly appreciated.
Thanks

diogobaeder · 2019-12-30 19:05:58

Hi folks!

I got to this thread trying to find out why the device was not working for me, and installing "8192eu-dkms", blacklisting "rtl8xxxu" and then rebooting worked perfectly for me, thanks a lot! :-)

This is my current kernel, in case someone sees the above and wonders if it would work for them:

$ uname -a
Linux diogobaeder-desktop 5.4.6-arch3-1 #1 SMP PREEMPT Tue, 24 Dec 2019 04:36:53 +0000 x86_64 GNU/Linux

keto · 2021-03-25 15:59:43

Have the same problem, diogobaeder answer solved for me.

V1del · 2021-03-25 16:27:26

Glad to hear however please don't necrobump 2 year old threads for what is effectively a "me too" post.

Closing this old thread.

Arch Linux

#1 2019-02-08 16:31:37

[Solved] Wifi TP-Link TL-WN823N doesn't work

#2 2019-02-08 17:35:26

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#3 2019-02-08 21:22:09

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#4 2019-02-08 21:29:50

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#5 2019-02-08 22:18:25

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#6 2019-02-08 22:23:18

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#7 2019-02-09 10:33:18

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#8 2019-02-09 10:45:13

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#9 2019-02-09 10:45:24

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#10 2019-02-09 10:51:29

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#11 2019-02-09 16:17:47

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#12 2019-02-10 21:33:02

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#13 2019-02-11 21:23:05

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#14 2019-09-15 08:37:51

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#15 2019-12-30 19:05:58

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#16 2021-03-25 15:59:43

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

#17 2021-03-25 16:27:26

Re: [Solved] Wifi TP-Link TL-WN823N doesn't work

Board footer