From: Nikolay Borisov <n.borisov.lkml@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Slow connection with rtl8xxxu and 8192eu chipset
Date: Tue, 14 Nov 2017 14:50:09 +0200 [thread overview]
Message-ID: <c1ef2d69-a30a-ceb2-d258-cca023117e07@gmail.com> (raw)
In-Reply-To: <87inedkp5h.fsf@purkki.adurom.net>
On 14.11.2017 14:42, Kalle Valo wrote:
> Nikolay Borisov <n.borisov.lkml@gmail.com> writes:
>
>> (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.
>
> iwconfig is old and not really properly supported anymore. Instead use
> iw and specifically 'iw wlan0 link' to check the transmit rate. And then
> testing speed it's best to use tools like iperf to verify the real
> speed, not just rely on what tools report.
To measure the speed I actually used a proper internet transfer. So in
reality I could hardly get more than 10 megabits with the built-in
adapter, whereas I'm getting 70-80 megabits otherwise. Of course the
test was performed to the same location everytime to reduce noise.
>
prev parent reply other threads:[~2017-11-14 12:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 9:26 Slow connection with rtl8xxxu and 8192eu chipset Nikolay Borisov
2017-11-14 10:39 ` 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 [this message]
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=c1ef2d69-a30a-ceb2-d258-cca023117e07@gmail.com \
--to=n.borisov.lkml@gmail.com \
--cc=kvalo@codeaurora.org \
--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