From: Chiefdome <chiefdome@googlemail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
george0505@realtek.com, linux-wireless@vger.kernel.org
Subject: Re: Alfa AWUS036NHR with RTL8188RU chipset
Date: Wed, 21 Sep 2011 11:43:44 +0200 [thread overview]
Message-ID: <4E79B1D0.7090602@googlemail.com> (raw)
In-Reply-To: <4E792994.1080809@lwfinger.net>
On 09/21/2011 02:02 AM, Larry Finger wrote:
> On 09/20/2011 04:38 PM, Chiefdome wrote:
>> I tried at least wireless-next but the adapter isn't showing up.
>> Where to get more log files and stuff?
>> Isnt this adapter good supported by the rtl8192cu driver or where is
>> the problem?
>
> For the mainline kernel to work with 802.11n-only APs and to reconnect
> after an initial try, your kernel needs the following patches:
>
> commit bac2555c6d86387132930af4d14cb47c4dd3f4f7
> Author: George <george0505@realtek.com>
> Date: Sat Sep 3 10:58:48 2011 -0500
>
> rtlwifi: Fix problem when switching connections
>
> The driver fails to clear encryption keys making it impossible
> to switch connections.
>
> Signed-off-by: George <george0505@realtek.com>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Stable <stable@kernel.org> [2.6.39+]
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
> commit 3401dc6eba788ebc7c14ce51018d775b1c263399
> Author: George <george0505@realtek.com>
> Date: Sat Sep 3 10:58:47 2011 -0500
>
> rtlwifi: rtl8192su: Fix problem connecting to HT-enabled AP
>
> The driver fails to connect to 802.11n-enabled APs. The patch fixes
> Bug #42262.
>
> Signed-off-by: George <george0505@realtek.com>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Stable <stable@kernel.org> [2.6.39+]
> Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
> Both of these are in wireless-testing, and were just merged into the
> mainline kernel. In addition, they were merged with the 3.0 stable
> tree today.
>
> Both should be in wireless-next, but as I recall, you were not able to
> test with that tree.
>
> With the updated mainline kernel, the link is stable and performance
> is acceptible with netperf TCP_STREAM (TX) at 20.5 +/- 4.8 Mbps and
> TCP_MAERTS (RX) of 21.7 +/- 3.8 Mbps. These numbers are not
> spectacular, but they will do.
>
> Larry
>
I tried the latest git repo from
git://git.infradead.org/users/linville/wireless-next.
Same story here.
After disconnecting to the network, I have to reload the module only
then networks are seen.
Chiefdome
next prev parent reply other threads:[~2011-09-21 9:43 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 2:10 Alfa AWUS036NHR with RTL8188RU chipset Chiefdome
2011-09-20 2:27 ` Chiefdome
2011-09-20 3:05 ` Larry Finger
2011-09-20 9:32 ` Chiefdome
2011-09-20 21:38 ` Chiefdome
2011-09-20 22:32 ` Larry Finger
2011-09-21 0:02 ` Larry Finger
2011-09-21 9:43 ` Chiefdome [this message]
2011-09-21 14:45 ` Larry Finger
2011-09-21 19:19 ` Chiefdome
2011-09-21 20:03 ` Larry Finger
2011-09-21 20:28 ` Chiefdome
2011-09-21 20:37 ` Larry Finger
2011-09-21 20:39 ` Chiefdome
2011-09-21 20:41 ` Chiefdome
2011-09-21 21:09 ` Larry Finger
2011-09-30 14:20 ` v4mp
2011-09-30 15:18 ` Larry Finger
2011-09-30 18:14 ` v4mp
2011-10-06 16:25 ` Toddy
2011-10-06 22:06 ` Larry Finger
2011-10-08 16:24 ` Toddy
2011-10-08 16:52 ` Larry Finger
2011-10-08 23:29 ` Gábor Stefanik
2011-10-09 14:21 ` v4mp
2011-10-09 14:47 ` Larry Finger
2011-10-15 14:22 ` v4mp
2011-10-16 2:49 ` Larry Finger
2011-10-17 10:07 ` v4mp
2011-10-17 14:59 ` Larry Finger
2011-10-17 17:09 ` v4mp
2011-10-17 18:38 ` Larry Finger
2011-10-18 3:23 ` Larry Finger
2011-10-18 12:44 ` v4mp
2011-10-18 13:07 ` v4mp
2011-10-18 15:20 ` Larry Finger
2011-10-18 21:50 ` v4mp
2011-10-18 23:01 ` Larry Finger
2011-10-19 8:17 ` v4mp
2011-10-19 12:08 ` Larry Finger
2011-10-19 14:37 ` v4mp
2011-10-20 3:38 ` Larry Finger
2011-10-20 9:47 ` v4mp
2011-10-20 13:35 ` Larry Finger
2011-10-26 15:49 ` Chiefdome
2011-10-26 16:12 ` Larry Finger
2011-10-26 19:39 ` Chiefdome
2011-10-26 21:20 ` Larry Finger
2011-10-26 21:31 ` Larry Finger
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=4E79B1D0.7090602@googlemail.com \
--to=chiefdome@googlemail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=george0505@realtek.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;
as well as URLs for NNTP newsgroup(s).