From: Nikolay Borisov <n.borisov.lkml@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Slow connection with rtl8xxxu and 8192eu chipset
Date: Tue, 14 Nov 2017 11:26:58 +0200 [thread overview]
Message-ID: <1195e649-c57f-1247-a0dc-2f0cc0732a00@gmail.com> (raw)
(Please CC as I'm not subscribed)
Hello,
I have the tp-link tl-wn822N usb wifi dongle. lsbusb reports it as
Bus 001 Device 003: ID 2357:0108
Unfortunately with the in-kernel rtl8xxxu driver I don't get very good
results:
wifi1 IEEE 802.11 ESSID:"HOME"
Mode:Managed Frequency:2.462 GHz Access Point:
30:B5:C2:75:A4:CD
Bit Rate=1 Mb/s Tx-Power=20 dBm
Retry short limit:7 RTS thr=2347 B Fragment thr:off
Power Management:off
Link Quality=26/70 Signal level=-84 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:165 Missed beacon:0
At the same time if I use an out of tree driver acquired from github:
https://github.com/Mange/rtl8192eu-linux-driver I get the following:
wifi1 IEEE 802.11bgn ESSID:"HOME" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency:2.462 GHz Access Point:
30:B5:C2:75:A4:CD
Bit Rate:144.4 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=81/100 Signal level=100/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Clearly this is a software problem of the in-kernel driver. I'm using
v4.10.17 with commit c14239f23adb ("rtl8xxxu: Add another 8192eu device
to the USB list") so that my device is recognised. Latest commit for
that driver in my kernel is: c59f13bbead4 ("rtl8xxxu: Work around issue
with 8192eu and 8723bu devices not reconnecting").
Any ideas what I can do to further debug this, I'd really like to use
the in-kernel driver ?
next reply other threads:[~2017-11-14 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 9:26 Nikolay Borisov [this message]
2017-11-14 10:39 ` Slow connection with rtl8xxxu and 8192eu chipset Nikolay Borisov
2017-11-28 16:16 ` Jes Sorensen
2017-11-28 16:26 ` Nikolay Borisov
2017-11-28 16:35 ` Jes Sorensen
2017-11-28 16:49 ` Nikolay Borisov
2017-11-28 16:59 ` Jes Sorensen
2017-11-14 12:42 ` Kalle Valo
2017-11-14 12:50 ` Nikolay Borisov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1195e649-c57f-1247-a0dc-2f0cc0732a00@gmail.com \
--to=n.borisov.lkml@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox