* Slow connection with rtl8xxxu and 8192eu chipset
@ 2017-11-14 9:26 Nikolay Borisov
2017-11-14 10:39 ` Nikolay Borisov
2017-11-14 12:42 ` Kalle Valo
0 siblings, 2 replies; 9+ messages in thread
From: Nikolay Borisov @ 2017-11-14 9:26 UTC (permalink / raw)
To: linux-wireless
(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 ?
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Slow connection with rtl8xxxu and 8192eu chipset
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-14 12:42 ` Kalle Valo
1 sibling, 1 reply; 9+ messages in thread
From: Nikolay Borisov @ 2017-11-14 10:39 UTC (permalink / raw)
To: linux-wireless; +Cc: Jes.Sorensen
On 14.11.2017 11:26, Nikolay Borisov wrote:
> (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 ?
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)
dmesg output:
[вт ное 14 12:30:38 2017] usb 1-1.1: This Realtek USB WiFi dongle (0x2357:0x0108) is untested!
[вт ное 14 12:30:38 2017] usb 1-1.1: Please report results to Jes.Sorensen@gmail.com
[вт ное 14 12:30:39 2017] usb 1-1.1: Vendor: Realtek
[вт ное 14 12:30:39 2017] usb 1-1.1: Product: \x03802.11n NI
[вт ное 14 12:30:39 2017] usb 1-1.1: Serial:
[вт ное 14 12:30:39 2017] usb 1-1.1: rtl8192eu_parse_efuse: dumping efuse (0x200 bytes):
[вт ное 14 12:30:39 2017] usb 1-1.1: 00: 29 81 00 7c 01 40 03 00
[вт ное 14 12:30:39 2017] usb 1-1.1: 08: 40 74 04 50 14 00 00 00
[вт ное 14 12:30:39 2017] usb 1-1.1: 10: 2b 2b 2c 2d 2d 2d 2c 2c
[вт ное 14 12:30:39 2017] usb 1-1.1: 18: 2d 2e 2e f2 ef ef ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 20: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 28: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 30: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 38: ff ff 29 29 29 29 29 29
[вт ное 14 12:30:39 2017] usb 1-1.1: 40: 2a 2a 29 29 29 f2 ef ef
[вт ное 14 12:30:39 2017] usb 1-1.1: 48: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 50: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 58: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 60: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 68: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 70: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 78: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 80: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 88: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 90: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 98: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: a0: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: a8: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: b0: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: b8: a1 3e 23 00 00 00 ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: c0: ff 01 00 10 00 00 00 ff
[вт ное 14 12:30:39 2017] usb 1-1.1: c8: 00 00 ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: d0: 57 23 08 01 e7 47 02 18
[вт ное 14 12:30:39 2017] usb 1-1.1: d8: d6 c7 0d 47 3c 0a 03 52
[вт ное 14 12:30:39 2017] usb 1-1.1: e0: 65 61 6c 74 65 6b 20 0e
[вт ное 14 12:30:39 2017] usb 1-1.1: e8: 03 38 30 32 2e 31 31 6e
[вт ное 14 12:30:39 2017] usb 1-1.1: f0: 20 4e 49 43 20 00 00 ff
[вт ное 14 12:30:39 2017] usb 1-1.1: f8: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 100: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 108: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 110: ff ff ff ff ff ff ff 0d
[вт ное 14 12:30:39 2017] usb 1-1.1: 118: 03 00 05 00 30 00 00 00
[вт ное 14 12:30:39 2017] usb 1-1.1: 120: 00 93 ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 128: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 130: f6 a8 98 2d 03 92 98 00
[вт ное 14 12:30:39 2017] usb 1-1.1: 138: fc 8c 00 11 9b 44 02 0a
[вт ное 14 12:30:39 2017] usb 1-1.1: 140: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 148: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 150: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 158: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 160: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 168: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 170: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 178: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 180: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 188: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 190: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 198: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1a0: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1a8: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1b0: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1b8: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1c0: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1c8: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1d0: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1d8: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1e0: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1e8: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1f0: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: 1f8: ff ff ff ff ff ff ff ff
[вт ное 14 12:30:39 2017] usb 1-1.1: RTL8192EU rev B (SMIC) 2T2R, TX queues 3, WiFi=1, BT=0, GPS=0, HI PA=0
[вт ное 14 12:30:39 2017] usb 1-1.1: RTL8192EU MAC: 18:d6:c7:0d:47:3c
[вт ное 14 12:30:39 2017] usb 1-1.1: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
[вт ное 14 12:30:39 2017] usb 1-1.1: Firmware revision 19.0 (signature 0x92e1)
[вт ное 14 12:30:40 2017] usbcore: registered new interface driver rtl8xxxu
[вт ное 14 12:30:40 2017] rtl8xxxu 1-1.1:1.0 wifi1: renamed from wlan0
[вт ное 14 12:30:40 2017] IPv6: ADDRCONF(NETDEV_UP): wifi1: link is not ready
[вт ное 14 12:30:40 2017] IPv6: ADDRCONF(NETDEV_UP): wifi1: link is not ready
[вт ное 14 12:30:40 2017] IPv6: ADDRCONF(NETDEV_UP): wifi1: link is not ready
[вт ное 14 12:30:40 2017] Ebtables v2.0 registered
[вт ное 14 12:30:48 2017] random: crng init done
[вт ное 14 12:30:51 2017] wifi1: authenticate with 30:b5:c2:75:a4:cd
[вт ное 14 12:30:51 2017] wifi1: send auth to 30:b5:c2:75:a4:cd (try 1/3)
[вт ное 14 12:30:51 2017] wifi1: authenticated
[вт ное 14 12:30:51 2017] wifi1: associate with 30:b5:c2:75:a4:cd (try 1/3)
[вт ное 14 12:30:51 2017] wifi1: RX AssocResp from 30:b5:c2:75:a4:cd (capab=0x431 status=0 aid=1)
[вт ное 14 12:30:51 2017] usb 1-1.1: rtl8xxxu_bss_info_changed: HT supported
[вт ное 14 12:30:51 2017] wifi1: associated
>
>
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Slow connection with rtl8xxxu and 8192eu chipset
2017-11-14 10:39 ` Nikolay Borisov
@ 2017-11-28 16:16 ` Jes Sorensen
2017-11-28 16:26 ` Nikolay Borisov
0 siblings, 1 reply; 9+ messages in thread
From: Jes Sorensen @ 2017-11-28 16:16 UTC (permalink / raw)
To: Nikolay Borisov, linux-wireless
On 11/14/2017 05:39 AM, Nikolay Borisov wrote:
>
>
> On 14.11.2017 11:26, Nikolay Borisov wrote:
>> (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 ?
>
> 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?
The 8192eu driver has some issues, it looks like firmware rate support
isn't working and it therefore transmits everything at low rates. I have
to find some time to look into this.
Jes
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Slow connection with rtl8xxxu and 8192eu chipset
2017-11-28 16:16 ` Jes Sorensen
@ 2017-11-28 16:26 ` Nikolay Borisov
2017-11-28 16:35 ` Jes Sorensen
0 siblings, 1 reply; 9+ messages in thread
From: Nikolay Borisov @ 2017-11-28 16:26 UTC (permalink / raw)
To: Jes Sorensen, linux-wireless
On 28.11.2017 18:16, Jes Sorensen wrote:
> On 11/14/2017 05:39 AM, Nikolay Borisov wrote:
>>
>>
>> On 14.11.2017 11:26, Nikolay Borisov wrote:
>>> (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 ?
>>
>> 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.
>
> The 8192eu driver has some issues, it looks like firmware rate support
> isn't working and it therefore transmits everything at low rates. I have
> to find some time to look into this.>
> Jes
>
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Slow connection with rtl8xxxu and 8192eu chipset
2017-11-28 16:26 ` Nikolay Borisov
@ 2017-11-28 16:35 ` Jes Sorensen
2017-11-28 16:49 ` Nikolay Borisov
0 siblings, 1 reply; 9+ messages in thread
From: Jes Sorensen @ 2017-11-28 16:35 UTC (permalink / raw)
To: Nikolay Borisov, linux-wireless
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:
>>>
>>>
>>> On 14.11.2017 11:26, Nikolay Borisov wrote:
>>>> (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 ?
>>>
>>> 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' ?
Thanks,
Jes
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Slow connection with rtl8xxxu and 8192eu chipset
2017-11-28 16:35 ` Jes Sorensen
@ 2017-11-28 16:49 ` Nikolay Borisov
2017-11-28 16:59 ` Jes Sorensen
0 siblings, 1 reply; 9+ messages in thread
From: Nikolay Borisov @ 2017-11-28 16:49 UTC (permalink / raw)
To: Jes Sorensen, linux-wireless
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:
>>>>
>>>>
>>>> On 14.11.2017 11:26, Nikolay Borisov wrote:
>>>>> (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 ?
>>>>
>>>> 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).
>
> Thanks,
> Jes
>
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Slow connection with rtl8xxxu and 8192eu chipset
2017-11-28 16:49 ` Nikolay Borisov
@ 2017-11-28 16:59 ` Jes Sorensen
0 siblings, 0 replies; 9+ messages in thread
From: Jes Sorensen @ 2017-11-28 16:59 UTC (permalink / raw)
To: Nikolay Borisov, linux-wireless
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Slow connection with rtl8xxxu and 8192eu chipset
2017-11-14 9:26 Slow connection with rtl8xxxu and 8192eu chipset Nikolay Borisov
2017-11-14 10:39 ` Nikolay Borisov
@ 2017-11-14 12:42 ` Kalle Valo
2017-11-14 12:50 ` Nikolay Borisov
1 sibling, 1 reply; 9+ messages in thread
From: Kalle Valo @ 2017-11-14 12:42 UTC (permalink / raw)
To: Nikolay Borisov; +Cc: linux-wireless
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.
--
Kalle Valo
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Slow connection with rtl8xxxu and 8192eu chipset
2017-11-14 12:42 ` Kalle Valo
@ 2017-11-14 12:50 ` Nikolay Borisov
0 siblings, 0 replies; 9+ messages in thread
From: Nikolay Borisov @ 2017-11-14 12:50 UTC (permalink / raw)
To: Kalle Valo; +Cc: linux-wireless
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.
>
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2017-11-28 16:59 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 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).