Installation of a TP-Link TL-WN823N usb wifi dongle - SOLVED

[Paul..]

Kent, that looks like a much better solution...EDIT: way to go aus9, now we have possible two solutions!

[aus9]

BTW

Code: Select all

sudo su
modprobe 8192eu
root@mx1:/home/gordon# modinfo 8192eu
filename:       /lib/modules/4.7.0-0.bpo.1-amd64/kernel/drivers/net/8192eu.ko
version:        v4.3.1.1_11320.20140505
author:         Realtek Semiconductor Corp.
description:    Realtek Wireless Lan Driver
license:        GPL
srcversion:     ACD8089385F9BD51D17D5A4
alias:          usb:v2019pAB33d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2357p0109d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2357p0108d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2357p0107d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v2001p3319d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0BDAp818Cd*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v0BDAp818Bd*dc*dsc*dp*icFFiscFFipFFin*
depends:        usbcore
vermagic:       4.7.0-0.bpo.1-amd64 SMP mod_unload modversions 
parm:           rtw_ips_mode:The default IPS mode (int)
parm:           rtw_usb_rxagg_mode:int
parm:           rtw_qos_opt_enable:int
parm:           ifname:The default name to allocate for first interface (charp)
parm:           if2name:The default name to allocate for second interface (charp)
parm:           rtw_initmac:charp
parm:           rtw_channel_plan:int
parm:           rtw_chip_version:int
parm:           rtw_rfintfs:int
parm:           rtw_lbkmode:int
parm:           rtw_network_mode:int
parm:           rtw_channel:int
parm:           rtw_mp_mode:int
parm:           rtw_wmm_enable:int
parm:           rtw_vrtl_carrier_sense:int
parm:           rtw_vcs_type:int
parm:           rtw_busy_thresh:int
parm:           rtw_ht_enable:int
parm:           rtw_bw_mode:int
parm:           rtw_ampdu_enable:int
parm:           rtw_rx_stbc:int
parm:           rtw_ampdu_amsdu:int
parm:           rtw_lowrate_two_xmit:int
parm:           rtw_rf_config:int
parm:           rtw_power_mgnt:int
parm:           rtw_smart_ps:int
parm:           rtw_low_power:int
parm:           rtw_wifi_spec:int
parm:           rtw_antdiv_cfg:int
parm:           rtw_antdiv_type:int
parm:           rtw_enusbss:int
parm:           rtw_hwpdn_mode:int
parm:           rtw_hwpwrp_detect:int
parm:           rtw_hw_wps_pbc:int
parm:           rtw_max_roaming_times:The max roaming times to try (uint)
parm:           rtw_mc2u_disable:int
parm:           rtw_80211d:Enable 802.11d mechanism (int)
parm:           rtw_notch_filter:0:Disable, 1:Enable, 2:Enable only for P2P (uint)
parm:           rtw_tx_pwr_lmt_enable:0:Disable, 1:Enable, 2: Depend on efuse (int)
parm:           rtw_tx_pwr_by_rate:0:Disable, 1:Enable, 2: Depend on efuse (int)
parm:           rtw_phy_file_path:The path of phy parameter (charp)
parm:           rtw_load_phy_file:PHY File Bit Map (int)
parm:           rtw_decrypt_phy_file:Enable Decrypt PHY File (int)

the usb ids exist as this line shows alias: alias: usb:v2357p0109

[aus9]

@ kmathern

for your attention only Me thinks

I see that 4.9 kernel module depends on a certain wireless module but on my system, that new 8192eu does not have such dependency.

I am currently on a usb dongle and I have

Code: Select all

lsmod | grep 80211
cfg80211              577536  0 
rfkill                 24576  3 cfg80211,asus_wmi

your thoughts low priority I need some sleep

[texchuck]

aus9,

You guys are amazing!!!!!!!

The modules.alias file now contains the 8192 references:

Code: Select all

alias pci:v000080EEd0000CAFEsv00000000sd00000000bc*sc*i* vboxguest
alias usb:v2019pAB33d*dc*dsc*dp*ic*isc*ip*in* 8192eu
alias usb:v2357p0109d*dc*dsc*dp*ic*isc*ip*in* 8192eu
alias usb:v2357p0108d*dc*dsc*dp*ic*isc*ip*in* 8192eu
alias usb:v2357p0107d*dc*dsc*dp*ic*isc*ip*in* 8192eu
alias usb:v2001p3319d*dc*dsc*dp*ic*isc*ip*in* 8192eu
alias usb:v0BDAp818Cd*dc*dsc*dp*icFFiscFFipFFin* 8192eu
alias usb:v0BDAp818Bd*dc*dsc*dp*icFFiscFFipFFin* 8192eu

My list of Ethernet devices has not changed:

Code: Select all

root@mx1-2:/lib/modules/4.7.0-0.bpo.1-amd64# inxi -Nxxx
Network:   Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller
           driver: r8169 v: 2.3LK-NAPI port: 3000
           bus-ID: 02:00.0 chip-ID: 10ec:8136
           Card-2: Broadcom BCM43142 802.11b/g/n
           driver: wl bus-ID: 03:00.0 chip-ID: 14e4:4365

I am not sure how close we are to getting the TL-WN823N to work. Perhaps I need to reboot? Still a lost soul on this!!

Thanks.

[kmathern]

I'd try a reboot first.

If you're going to try the 4.9 kernel I mentioned, make sure you also upgrade firmware-realtek to the 20161130-2mx150+1 version. It has the rtl8192eu_nic.bin firmware file in it, that file isn't included in the 20160824-1mx150+1 version of firmware-realtek.

[tascoast]

Network: Card-1: Marvell 88E8057 PCI-E Gigabit Ethernet Controller driver: sky2
IF: eth0 state: down mac: 00:01:6c:48:1a:77
Card-2: Realtek RTL8191SU 802.11n WLAN Adapter driver: r8712u
IF: wlan0 state: N/A mac: N/A

My TP-Link must be slightly older but it does work OOTB.

[texchuck]

OOTB would be nice!

I don't know anything about migrating to a newer kernel. I am using the 4.7 kernel that came with the MX-16 distro I installed. I made the suggested changes with the existing kernel, but things still don't work. However, the dongle has a little green light that flashed while the system was coming up. I haven't noticed that behavior before (though may have missed it, as it is a bit subtle). It still doesn't show up in the listings, though:

Code: Select all

$ inxi -Nxxx
Network:   Card-1: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller
           driver: r8169 v: 2.3LK-NAPI port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8136
           Card-2: Broadcom BCM43142 802.11b/g/n driver: wl bus-ID: 03:00.0 chip-ID: 14e4:4365

Code: Select all

$ lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 04f2:b52d Chicony Electronics Co., Ltd 
Bus 002 Device 004: ID 0a5c:216d Broadcom Corp. 
Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 002: ID 2357:0109  
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The dongle light just flashed a couple of times again. That is definitely new behavior. Perhaps I need to disable the Broadcom chip? I will try that after sending this.

[texchuck]

I disabled the Broadcom chip (quarantined the wl driver) and the TP-Link device is now WORKING!!

Many thanks to aus9 and the other Linux geniuses who helped! It it my understanding that this chip will now work with kernel 4.9 ootb. That will be great. I am getting a stronger signal on my home router. Will now test it in the building where I had so much trouble.

Again, thank you to everyone!! I would certainly give a "thumbs up," but don't know how to do it. Someone who know how this web page works can mark it "solved."

[Paul..]

Fabulous news, texchuck. aus9 has gone to sleep, but will read about I am sure. You can mark the thread [SOLVED] by adding that word to the title of your original post.

[Stevo]

I see that the rtl8xxxu driver in the 4.9 Liquorix kernel we have available supports that USB ID

Code: Select all

alias:          usb:v2357p0109d*dc*dsc*dp*icFFiscFFipFFin*

but reports are from a couple Stretch users in the Debian forums that their 4.9 kernel broke their wifi--however, it might be that they had competing drivers loaded and did not give the new kernel driver a fair test with the out-of-tree rtl8192eu module unloaded.