Home Network Community > All Threads > TL-WN823N: Linux driver from tp-link.com/de/support fails
< All Threads

TL-WN823N: Linux driver from tp-link.com/de/support fails

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

TL-WN823N: Linux driver from tp-link.com/de/support fails

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TL-WN823N: Linux driver from tp-link.com/de/support fails
TL-WN823N: Linux driver from tp-link.com/de/support fails
2020-03-19 14:10:51
Model: TL-WN823N  
Hardware Version: V3
Firmware Version: ?

hello,

 

I am using Debian 10 with kernel 4.19.98.
(also tried Debian testing with kernel 5.4.19, same result):

 

I downloaded the 2018-05-08 driver for the V3:

https://www.tp-link.com/de/support/download/tl-wn823n/v3/#Driver

 

It did not compile/load, so I made these changes (first changes are for compilation,

final change is for loading (__vfs_read -> kernel_read):

 

299,300c299,301
<       ptimer->data = (unsigned long)cntx;
<       init_timer(ptimer);
---
>       //ptimer->data = (unsigned long)cntx;
>       //init_timer(ptimer);
>       timer_setup(ptimer, pfunc, 0);
diff -r rtl8192EU_WiFi_linux_v5.2.19.1_25633.20171222_COEX20171113-0047/Makefile rtl8192EU_WiFi_linux_v5.2.19.1_25633.20171222_COEX20171113-0047-modified/Makefile
21a22,23
> EXTRA_CFLAGS += -Wno-date-time
> EXTRA_CFLAGS += -Wno-incompatible-pointer-types
diff -r rtl8192EU_WiFi_linux_v5.2.19.1_25633.20171222_COEX20171113-0047/os_dep/osdep_service.c rtl8192EU_WiFi_linux_v5.2.19.1_25633.20171222_COEX20171113-0047-modified/os_dep/osdep_service.c
2003c2003,2004
<               rlen = __vfs_read(fp, buf + sum, len - sum, &fp->f_pos);
---
>               //rlen = __vfs_read(fp, buf + sum, len - sum, &fp->f_pos);
>               rlen = kernel_read(fp, buf + sum, len - sum, &fp->f_pos);


Unfortunately, when using this driver, the whole system freezes.

 

When using the 'rtl8xxxu' driver (as suggested here:
https://wiki.ubuntuusers.de/WLAN/Karten/TP-Link/), the system does not
freeze but there is another problem:

 

Mar 19 13:24:45 fujitsu NetworkManager[475]: <info>  [1584620685.0971] audit: op="statistics" arg="refresh-rate-ms" pid=860 uid=1000 result="success"
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2694] device (wlxd0374578a112): Activation: starting connection 'WLAN-Natter' (83ee82d2-9bbe-4beb-ac9e-3e3e5fcce781)
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2696] audit: op="connection-activate" uuid="83ee82d2-9bbe-4beb-ac9e-3e3e5fcce781" name="WLAN-Natter" pid=860 uid=1000 result="success"
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2699] device (wlxd0374578a112): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2748] device (wlxd0374578a112): set-hw-addr: reset MAC address to D0:37:45:78:A1:12 (preserve)
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2804] device (wlxd0374578a112): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2805] device (wlxd0374578a112): Activation: (wifi) access point 'WLAN-Natter' has security, but secrets are required.
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2806] device (wlxd0374578a112): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2807] sup-iface[0x55d9ab704a30,wlxd0374578a112]: wps: type pbc start...
Mar 19 13:24:47 fujitsu kernel: [  877.162317] IPv6: ADDRCONF(NETDEV_UP): wlxd0374578a112: link is not ready
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2881] device (wlxd0374578a112): supplicant interface state: disconnected -> scanning
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2911] device (wlxd0374578a112): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2914] device (wlxd0374578a112): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2916] device (wlxd0374578a112): Activation: (wifi) connection 'WLAN-Natter' has security, and secrets exist.  No new secrets needed.
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2916] Config: added 'ssid' value 'WLAN-Natter'
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2916] Config: added 'scan_ssid' value '1'
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2916] Config: added 'bssid' value '5C:49:79:43:B4:47'
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2916] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256'
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2916] Config: added 'psk' value '<hidden>'
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.2929] audit: op="statistics" arg="refresh-rate-ms" pid=860 uid=1000 result="success"
Mar 19 13:24:47 fujitsu kernel: [  877.182592] wlxd0374578a112: authenticate with 5c:49:79:43:b4:47
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.3055] device (wlxd0374578a112): supplicant interface state: scanning -> authenticating
Mar 19 13:24:47 fujitsu kernel: [  877.186605] wlxd0374578a112: send auth to 5c:49:79:43:b4:47 (try 1/3)
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.3156] audit: op="statistics" arg="refresh-rate-ms" pid=860 uid=1000 result="success"
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.3532] audit: op="statistics" arg="refresh-rate-ms" pid=860 uid=1000 result="success"
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.3749] audit: op="statistics" arg="refresh-rate-ms" pid=860 uid=1000 result="success"
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.3977] audit: op="statistics" arg="refresh-rate-ms" pid=860 uid=1000 result="success"
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.4381] audit: op="statistics" arg="refresh-rate-ms" pid=860 uid=1000 result="success"
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.4601] audit: op="statistics" arg="refresh-rate-ms" pid=860 uid=1000 result="success"
Mar 19 13:24:47 fujitsu kernel: [  877.389384] wlxd0374578a112: send auth to 5c:49:79:43:b4:47 (try 2/3)
Mar 19 13:24:47 fujitsu kernel: [  877.597396] wlxd0374578a112: send auth to 5c:49:79:43:b4:47 (try 3/3)
Mar 19 13:24:47 fujitsu kernel: [  877.801450] wlxd0374578a112: authentication with 5c:49:79:43:b4:47 timed out
Mar 19 13:24:47 fujitsu NetworkManager[475]: <info>  [1584620687.9618] device (wlxd0374578a112): supplicant interface state: authenticating -> disconnected
Mar 19 13:24:57 fujitsu NetworkManager[475]: <info>  [1584620697.9648] device (wlxd0374578a112): supplicant interface state: disconnected -> scanning
Mar 19 13:25:02 fujitsu NetworkManager[475]: <info>  [1584620702.7339] audit: op="statistics" arg="refresh-rate-ms" pid=860 uid=1000 result="success"
Mar 19 13:25:11 fujitsu kernel: [  901.082959] wlxd0374578a112: authenticate with 5c:49:79:43:b4:47
Mar 19 13:25:11 fujitsu NetworkManager[475]: <info>  [1584620711.2078] device (wlxd0374578a112): supplicant interface state: scanning -> authenticating
Mar 19 13:25:11 fujitsu kernel: [  901.089565] wlxd0374578a112: send auth to 5c:49:79:43:b4:47 (try 1/3)
Mar 19 13:25:11 fujitsu kernel: [  901.293455] wlxd0374578a112: send auth to 5c:49:79:43:b4:47 (try 2/3)
Mar 19 13:25:11 fujitsu kernel: [  901.497309] wlxd0374578a112: send auth to 5c:49:79:43:b4:47 (try 3/3)
Mar 19 13:25:11 fujitsu kernel: [  901.701409] wlxd0374578a112: authentication with 5c:49:79:43:b4:47 timed out
Mar 19 13:25:11 fujitsu NetworkManager[475]: <info>  [1584620711.8489] device (wlxd0374578a112): supplicant interface state: authenticating -> disconnected
Mar 19 13:25:12 fujitsu NetworkManager[475]: <warn>  [1584620712.4914] device (wlxd0374578a112): Activation: (wifi) association took too long, failing activation
Mar 19 13:25:12 fujitsu NetworkManager[475]: <info>  [1584620712.4915] device (wlxd0374578a112): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Mar 19 13:25:12 fujitsu NetworkManager[475]: <warn>  [1584620712.4929] device (wlxd0374578a112): Activation: failed for connection 'WLAN-Natter'
Mar 19 13:25:12 fujitsu NetworkManager[475]: <info>  [1584620712.4934] device (wlxd0374578a112): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Mar 19 13:25:12 fujitsu kernel: [  902.375940] IPv6: ADDRCONF(NETDEV_UP): wlxd0374578a112: link is not ready
Mar 19 13:25:12 fujitsu NetworkManager[475]: <info>  [1584620712.4990] device (wlxd0374578a112): set-hw-addr: set MAC address to 46:78:B8:96:40:5C (scanning)
Mar 19 13:25:12 fujitsu kernel: [  902.386536] IPv6: ADDRCONF(NETDEV_UP): wlxd0374578a112: link is not ready
Mar 19 13:25:21 fujitsu NetworkManager[475]: <info>  [1584620721.8549] device (wlxd0374578a112): supplicant interface state: disconnected -> inactive

 

The stick works fine under W10 when connecting to the same router.

 

Does anybody have an idea?

 

Many Thanks in Advance!
Felix

 

  0      
 
  0      
 
#1
Options
5 Reply
Re:TL-WN823N: Linux driver from tp-link.com/de/support fails
2020-03-19 16:52:08

This driver works:

https://github.com/jeremyb31/rtl8192eu-linux-driver.git

 

cd rtl8192eu-linux-driver

make

sudo make install

sudo modprobe -r rtlxxxu

sudo modprobe 8192eu

 

-> work :-)

  0  
  0  
#2
Options
Re:TL-WN823N: Linux driver from tp-link.com/de/support fails
2020-03-29 17:55:04

 

sorry, should be:

 

cd rtl8192eu-linux-driver

make

sudo make install

sudo modprobe -r rtl8xxxu

sudo modprobe 8192eu

  0  
  0  
#3
Options
Re:TL-WN823N: Linux driver from tp-link.com/de/support fails
2021-04-24 23:48:17

Hi @fnatter ,

I followed your instructions, but in the last step, I get the following message back:

 

 

FATAL: Module 8192eu not found in directory /lib/modules/4.19.0-16-amd64

 

If I move 8192eu to the directory above, it still does not see it. What am I doing wrong?

 

Thanks for your reply.

 

Orlando.

  0  
  0  
#4
Options
Re:TL-WN823N: Linux driver from tp-link.com/de/support fails
2021-04-25 09:49:36

@fnatter Hi Orlando,

 

using dkms worked better for me (sorry I didn't comment it here):

 

$ cd rtl8192eu-linux-driver

$ sudo dkms add ./rtl8192eu
$ sudo dkms build rtl8192eu/1.0
$ sudo dkms install rtl8192eu/1.0
reboot (might not be necessary).

 

According [1], the 2nd step might need to be

$ sudo dkms add .

 

[1] https://github.com/jeremyb31/rtl8192eu-linux-driver

 

Does this work for you?

 

Cheers and Best Regards,

Felix

  0  
  0  
#5
Options
Re:TL-WN823N: Linux driver from tp-link.com/de/support fails
2021-05-09 17:14:48

@omendez Have you been able to try this?

  0  
  0  
#6
Options

Information

Helpful: 0

Views: 1791

Replies: 5

Related Articles
TL-WN823N + 8192eu.ko driver on Kali Linux
6458 0
Driver TL-WN823N
481 0
TL-WN823N on Linux
988 0
TL-WN823N Wireless Adapter. Driver Error
641 0
TL-WN823N: No stable connection
1947 0
WN823N unable to compile driver
742 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.