Tp-link TL-WN823N V3

I bought this wireless adapter but I can't get it to work on linux because Tp-link hasn't released the driver for kernel 5.3.
I found the chipset of Tl-WN823N V2 on the manjaro forums but that doesn't help me at all.
I don't know what chipset this adapter uses.

Connect your adapter to your system and run

inxi -SMNxxz
1 Like

The system recognizes the adapter and I am shown a list of available wi-fi networks in my area but when I try to connect to any network it doesn't want to connect.

Are there any reasons why you did not post the output of the inxi command?

let's try it again. post the complete output of

inxi -Fxxxza --no-host

and use the </> code button to format it for readability.

I have kernel 5.3.18-1 installed.

[francois@francois-pc ~]$ inxi -SMNxxz
System:
Host: francois-pc Kernel: 5.3.11-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0
Desktop: KDE Plasma 5.17.3 tk: Qt 5.13.2 wm: kwin_x11 dm: SDDM
Distro: Manjaro Linux
Machine:
Type: Desktop System: Gigabyte product: N/A v: N/A serial: Chassis:
type: 3 serial:
Mobo: Gigabyte model: H61M-S2PV REV 2.2 serial:
UEFI: American Megatrends v: Fce date: 03/03/2014
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte
driver: r8169 v: kernel port: e000 bus ID: 02:00.0 chip ID: 10ec:8168
Device-2: TP-Link TL WN823N RTL8192EU type: USB driver: rtl8xxxu bus ID: 2-1.1:3
chip ID: 2357:0109

[francois@francois-pc ~]$ inxi -Fxxxza --no-host
System:
Kernel: 5.3.11-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.3-x86_64
root=UUID=28e17c27-2a85-4a19-86a9-2bf36de3ba08 rw quiet apparmor=1
security=apparmor resume=UUID=ae6d4361-18de-480c-8f81-3d276d534825
udev.log_priority=3
Desktop: KDE Plasma 5.17.3 tk: Qt 5.13.2 wm: kwin_x11 dm: SDDM
Distro: Manjaro Linux
Machine:
Type: Desktop System: Gigabyte product: N/A v: N/A serial: Chassis:
type: 3 serial:
Mobo: Gigabyte model: H61M-S2PV REV 2.2 serial:
UEFI: American Megatrends v: Fce date: 03/03/2014
CPU:
Topology: Single Core model: Intel Celeron G465 bits: 64 type: MT
arch: Sandy Bridge family: 6 model-id: 2A (42) stepping: 7 microcode: 2F
L2 cache: 1536 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 7584
Speed: 1596 MHz min/max: 1600/1900 MHz Core speeds (MHz): 1: 1598 2: 1596
Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0102
Display: x11 server: X.Org 1.20.5 driver: intel unloaded: modesetting
alternate: fbdev,vesa compositor: kwin_x11 resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Sandybridge Desktop v: 3.3 Mesa 19.2.4
compat-v: 3.0 direct render: Yes
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1b.0
chip ID: 8086:1c20
Sound Server: ALSA v: k5.3.11-1-MANJARO
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte
driver: r8169 v: kernel port: e000 bus ID: 02:00.0 chip ID: 10ec:8168
IF: enp2s0 state: down mac:
Device-2: TP-Link TL WN823N RTL8192EU type: USB driver: rtl8xxxu bus ID: 2-1.1:3
chip ID: 2357:0109 serial:
IF: wlp0s29u1u1 state: down mac:
Drives:
Local Storage: total: 698.65 GiB used: 30.71 GiB (4.4%)
ID-1: /dev/sda vendor: Seagate model: ST3250318AS size: 232.88 GiB block size:
physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm
serial: rev: CC38 scheme: GPT
ID-2: /dev/sdb vendor: Toshiba model: DT01ACA050 size: 465.76 GiB block size:
physical: 4096 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm
serial: rev: A750 scheme: GPT
Partition:
ID-1: / raw size: 215.51 GiB size: 211.13 GiB (97.97%) used: 30.71 GiB (14.5%)
fs: ext4 dev: /dev/sda2
ID-2: swap-1 size: 17.08 GiB used: 0 KiB (0.0%) fs: swap swappiness: 60 (default)
cache pressure: 100 (default) dev: /dev/sda3
Sensors:
System Temperatures: cpu: 39.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 151 Uptime: 6m Memory: 15.53 GiB used: 755.4 MiB (4.8%) Init: systemd
v: 242 Compilers: gcc: 9.2.0 Shell: bash v: 5.0.11 running in: konsole
inxi: 3.0.36

Did you not reboot? Do a full update and reboot. Then check the inxi again.
This will not fix your wifi, but it is very important that the installed and the running kernel match.

Because you need to install 8192eu-dkms from AUR. But do that after the reboot. Since it is a DKMS package you have to install the matching Kernel headers.
Also do not forget to blacklist the inline Kernel driver ( rtl8xxxu ).

1 Like

Thank you very much. Can you give me instructions on installing the dkms and blacklist ing the inline kernel driver?

My installed kernel is my running kernel.

Generally searching your adapter chip (now that it is known) will usually turn up any info you require. Most of these issues have been covered many times before on the forum.

Here is a post dealing with this topic from a few days ago:

1 Like

I followed the instructions exactly of the post above and all packages installed successfully. My adapter still doesn't work. It tries to connect and says "configuring interface" but then simply disconnects.

Disable MAC Address Randomization in NetworkManager.

Disable MAC Address Randomization with the following command:

echo -e "[device]\nwifi.scan-rand-mac-address=no" | sudo tee /etc/NetworkManager/conf.d/disable-random-mac.conf

After creating the new conf file, reboot both your router and your computer.

1 Like

The adapter now works 100%!
Thank you all for your helping hand.

I figured that's what it might be. For some reason that adapter is really flaky if MAC randomization is enabled.

Glad you got it working.

Forum kindly sponsored by