Am 09.09.2013 16:57, schrieb Larry Finger:
On 09/09/2013 09:16 AM, Mark Cave-Ayland wrote:
On 09/09/13 00:16, Larry Finger wrote:
On 09/08/2013 06:53 AM, Timothy Rundle wrote:
My TL-WN821N with a RTL8192CU chipsets fails to stay connected. It
appears to be disconnecting every 5-10 seconds. Since the issue
happens with the mainline kernel, the downstream maintainer ask me to
post here. Here is a section of my kernel log:
This problem has been reported before; however, I cannot duplicate it on
my openSUSE KDE system that controls the wireless using NetworkManager.
Yes, this sounds like exactly the same problem that I reported a
couple of weeks
ago. Note that I see the issue invoking wpa_supplicant manually rather
than
using NetworkManager, so I don't think that this is part of the problem.
I can also clarify that if I remove *all* entries from
wpa_supplicant.conf
except for the one AP I'm trying to associate with, then I can
generally get an
initial association within about 30-60s. However I still repeatedly see
drop-outs every 30s or so.
I think your user space is exactly the problem. As I am writing this, my
device, which lsusb reports as "ID 7392:7811 Edimax Technology Co., Ltd
EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]" has been up for
a little over 20 hours. During that time, there have been 23
deauthentications for reason 7, but 0 of the "connection to AP lost"
variety.
My system is running version 1.1 of wpa_supplicant, 0.9.6.4 of
NetworkManager, and 0.9.0.7 of the KDE applet.
None of my wireless connections are made automatically. When I select a
particular AP from the KDE applet, it is roughly 2 seconds until the
interface has gotten an IP and reports its state as connected.
I will switch my system from NM to manual control to see what happens.
Larry
Just in case:
There can be some usb issue. At least i need to fight right now with
some of them on ath9k_htc.
--
Regards,
Oleksij
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
