Tl wn823n linux mint

Tl wn823n linux mint

26 фев 2017, 23:10

Недавно купил себе в Связном WIFI адаптер TP-LINK TL-WN823N . Купил для своего системника, с тем, чтобы избавить квартиру от ещё одного провода к роутеру. Однако под Линукс Минт 18.1 Циннамон устройство работало не корректно. Периодически скорость и уровень сигнала адаптера падали почти до нуля. А иногда и вообще Линукс отказывался определять данное устройство в usb порту.
Первое решение найденное в сети было таковым:

(Комментарий от меня. По какой-то причине сделать копирование в терминале у меня не вышло. Происходила какая то ошибка. Поэтому я сделал это так, как сделал бы это в винде. Зашёл в папку /etc/modprobe.d/ как администратор и через правую клавишу мыши скопировал файлы из одного окна в другое).

Перезагружаем компьютер. Вот и всё. У меня это сработало. Надеюсь, поможет и вам.
В конце авторы материала по данной проблеме предлагают проверить какой драйвер активен.
Набираем:
lsmod | grep 8192

Если в окне терминала вы видите драйвер 8192cu — то всё в норме. Если вы видите драйвер rtl8192cu — значит у вас по-прежнему работает старый драйвер.
Авторы данного материала не рекомендуют обновлять ядро Линукса. Правильный драйвер тогда придётся устанавливать заново.
Даю ссылку на сайт статьи, которую использовал. https://sites.google.com/site/easylinux . /reserve-7
На данной странице можно отыскать инструкции для других чипсетов Realtek
Realtek RTL8188CUS and RTL8192CU chipsets (0bda:8176 and 0bda:8178), Realtek RTL8723BE chipset, Realtek RTL8723AU chipset (0bda:b720), Realtek RTL8188EU chipset (0bda:8179), Realtek RTL8192EU chipset (0bda:818b), Realtek RTL8812AU chipset, (0bda:8812)Realtek RTL8723BU chipset (0bda:b720).

Уважаемые мэтры, комментарии приветствуются.

Источник

Arch Linux

You are not logged in.

#1 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

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

3)After $ip link:

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

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

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

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)

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

#2 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)

#3 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

$ dmesg | grep 8192eu

dmesg | grep xxxu

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

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

Читайте также:  Pdf printing mac os

#5 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?)

#6 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.

#7 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?

#8 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.

#9 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)

#10 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.

#11 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.

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing

How to Ask Questions the Smart Way

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

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:

2) If I run again dhcpcd:

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

4) But when I ping archlinux.org:

(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)

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

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

Читайте также:  Как загрузить куст реестра другой windows

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

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

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?)

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

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

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 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 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 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 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 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.

Источник

Sorry to bother you with this, but I’m not really an expert and it may be the most stupid thing you’ll see. I have ubuntu 19.04 (kernel: 5.0.0-13-generic; gcc version: 8.3.0) installed on an old pc that has a broken wifi card. So I replaced it with an external tp link wireless usb adapter. But I cannot follow the instructions:

I already downloaded these files and sent to the pc from another one, as it has no internet connection:

It may be a really stupid thing, but if I have, fe, to compile (I don’t even know what it means) the driver, I don’t know what it means » go to the driver directory and run the following commands «.

I really appreciate anyone and anything that helps me to solve this.

2 Answers 2

If you have internet access by any other means (wired or through USB tethering), you can installed the RTL8192EU drivers for your TP-LINK TL-WN823N wireless adapter from Mange’s GitHub repo. Here are the steps as described on the GitHub page:

Building and installing using DKMS

(1) Install DKMS and other required tools:

(2) Clone this repository and change your directory to cloned path.

Читайте также:  Restarting server in linux

(3) Add the driver to DKMS. This will copy the source to a system directory so that it can used to rebuild the module on kernel upgrades.

(4) Build and install the driver.

(5) Distributions based on Debian & Ubuntu have RTL8XXXU driver present & running in kernelspace. To use our RTL8192EU driver, we need to blacklist RTL8XXXU.

(6) Force RTL8192EU Driver to be active from boot.

(7) Newer versions of Ubuntu has weird plugging/replugging issue (Check #94). This includes weird idling issues, To fix this:

(8) Update changes to Grub & initramfs

(9) Reboot system to load new changes from newly generated initramfs.

(10) After the reboot, you can check that your kernel has loaded the right module:

Источник

Download for TL-WN823N V3

Driver

Download Published Date: 2020-01-08 Language: Multi-language File Size: 9.74 MB

1. For Mac OS 10.15.
2. For TL-WN821N(EUUS) v6.0, TL-WN822N(EUUS) v5.0, TL-WN8200ND(UN) v2.0, TL-WN823N(EUUSRU) v3.0.

TL-WN823N(UN)_V3_Mac os x 10.14_Beta

Download Published Date: 2018-11-09 Language: English File Size: 13.93 MB

This is a beta version; unknown bugs may still exist. The formal version is coming soon.

Download Published Date: 2018-11-09 Language: English File Size: 24.95 MB

1. For TL-WN823N(US) V3.
2. For Mac 10.8

Download Published Date: 2018-11-09 Language: English File Size: 43.11 MB

1. For TL-WN823N(US) V3.
2. For WinXP/Win7/Win8/Win8.1/Win10 32bit/64bit.

Download Published Date: 2018-05-08 Language: English File Size: 3.83 MB

Published Date: 2018-03-16 Language: English File Size: 11.02MB Download Published Date: 2018-03-16 Language: English File Size: 43.10MB Download Published Date: 2018-01-18 Language: English File Size: 3.04 MB

Modifications and Bug Fixes:

Support linux(kernel 2.6.18

Setup Video

Feature Filter: All TroubleshootingUS User Application RequirementUS Q&A of functional explanation or specification parametersUS

  • Problems you may come across during the driver installation of the TP-Link wireless adapter 07-20-2021 425513
  • How to use TP-Link network adapters on Windows 8 03-26-2021 97307
  • How to install the driver manually on MAC OS? 12-17-2020 348163
  • How to improve the speed of TP-Link wireless adapters? 12-09-2019 475772
  • Why cannot I find or connect to my wireless networks? 09-24-2019 834940
  • How to find suitable driver for my network adapter 04-29-2019 144173

Subscribe TP-Link takes your privacy seriously. For further details on TP-Link’s privacy practices, see TP-Link’s Privacy Policy.

Be The First To Get Exclusive Deals & News

Get products, events and services for your region.

To provide a better experience, we use cookies and similar tracking technologies to analyze traffic, personalize content and ads. By continuing to browse this website, you agree to our use of cookies and such technologies. Learn more Don’t show again

To provide a better experience, we use cookies and similar tracking technologies to analyze traffic, personalize content and ads. By continuing to browse this website, you agree to our use of cookies and such technologies. Learn more Don’t show again

These cookies are necessary for the website to function and cannot be deactivated in your systems.

Site Selection Popup

SMB Product Selection System

tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple

__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID

VISITOR_INFO1_LIVE, YSC, LOGIN_INFO, PREF, CONSENT, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC

Analysis and Marketing Cookies

Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.

The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.

Google Analytics & Google Tag Manager & Google Optimize

_gid, _gat, _gat_global, _ga, _gaexp

Google Ads & DoubleClick

NID, IDE, test_cookie, id, 1P_JAR

fr, spin, xs, datr, c_user, sb, _fbp

_ce.s, _CEFT, _gid, cean, _fbp, ceac, _drip_client_9574608, cean_asoc

_hjKB, _fbp, ajs_user_id, _BEAMER_LAST_UPDATE_zeKLgqli17986, _hjid, _gcl_au, _ga, ajs_anonymous_id, _BEAMER_USER_ID_zeKLgqli17986, _hjAbsoluteSessionInProgress, _hjFirstSeen, _hjIncludedInPageviewSample, _hjTLDTest

Hm_lpvt_33178d1a3aad1dcf1c9b345501daa675, Hm_lvt_33178d1a3aad1dcf1c9b345501daa675, HMACCOUNT_BFESS

lms_analytics, AnalyticsSyncHistory, _gcl_au, liap

Источник

Оцените статью