linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: Nikolay Borisov <n.borisov.lkml@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Slow connection with rtl8xxxu and 8192eu chipset
Date: Tue, 28 Nov 2017 11:59:07 -0500	[thread overview]
Message-ID: <e4cd40ab-8663-e329-952f-0eb7c27cf565@gmail.com> (raw)
In-Reply-To: <12fed6ac-0e21-a137-4d7c-3bb341c4e831@gmail.com>

On 11/28/2017 11:49 AM, Nikolay Borisov wrote:
> 
> 
> On 28.11.2017 18:35, Jes Sorensen wrote:
>> On 11/28/2017 11:26 AM, Nikolay Borisov wrote:
>>>
>>>
>>> On 28.11.2017 18:16, Jes Sorensen wrote:
>>>> On 11/14/2017 05:39 AM, Nikolay Borisov wrote:
>>>>>
>>>>>
>>>>> I just tested with verbatim 4.14 and even though the wireless works, 
>>>>> iwconfig reports something strange: 
>>>>>
>>>>> iwconfig wifi1
>>>>> wifi1     no wireless extensions.
>>>>>
>>>>> However, my device works as expected (albeit still slow): 
>>>>>
>>>>> wifi1     Link encap:Ethernet  HWaddr 18:d6:c7:0d:47:3c  
>>>>>           inet addr:10.20.1.175  Bcast:10.20.1.255  Mask:255.255.255.0
>>>>>           inet6 addr: fe80::281d:5f27:eb1b:8ded/64 Scope:Link
>>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>>           RX packets:38903 errors:0 dropped:0 overruns:0 frame:0
>>>>>           TX packets:24689 errors:0 dropped:0 overruns:0 carrier:0
>>>>>           collisions:0 txqueuelen:1000 
>>>>>           RX bytes:51524413 (51.5 MB)  TX bytes:5503039 (5.5 MB)
>>>>
>>>> iwconfig has been deprecated for a decade, but maybe you could elaborate
>>>> on what you feel is strange in this output?
>>>
>>> Well there are 2 things:
>>>
>>> 1. The low bitrate - which I've confirmed doing actual data test, ie,
>>> not just the number but the fact that the speeds are low.
>>>
>>> 2. The worse signal level/link quality.
>>
>> I don't see either of those in the iwconfig output
>>
>> The low TX bitrate is a known issue. Somehow the firmware rate handling
>> doesn't seem to work (or it works differently than I assumed) similar to
>> for the 8188eu. It's something I need to figure out when I have some time.
>>
>> As for link quality is this something you measured or read out of 'iw' ?
> 
> Well there is:
> 
> Link Quality=26/70  Signal level=-84 dBm < - with rtl8xxxu driver
> 
> Link Quality=81/100  Signal level=100/100  Noise level=0/100 <-- with
> vendor's driver. Another vector was the icon of network manager had only
> 2 bars with the in-tree driver and had full bars with out (yeah, this is
> a bit subjective metric but it's the best i've got).

OK, the link reporting from rtl8xxxu isn't complete, so I wouldn't put
too much into this.

Cheers,
Jes

  reply	other threads:[~2017-11-28 16:59 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 [this message]
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=e4cd40ab-8663-e329-952f-0eb7c27cf565@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=n.borisov.lkml@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).