linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: linux-wireless@vger.kernel.org
Cc: markh@compro.net, Larry Finger <Larry.Finger@lwfinger.net>,
	Johannes Berg <johannes@sipsolutions.net>,
	dmarkh@cfl.rr.com
Subject: Re: rtl8192cu problem - Re: Wireless network problem with Access Point selection using ifup
Date: Thu, 03 Jan 2013 07:52:45 -0500	[thread overview]
Message-ID: <50E57F1D.7050803@compro.net> (raw)
In-Reply-To: <50C61E16.3010404@compro.net>

On 12/10/2012 12:38 PM, Mark Hounschell wrote:
> On 12/10/2012 11:24 AM, Larry Finger wrote:
>> On 12/10/2012 06:46 AM, Johannes Berg wrote:
>>> On Mon, 2012-12-10 at 07:00 -0500, Mark Hounschell wrote:
>>>
>>>> Should I file and bug report and/or contact the author?
>>>
>>> Larry, the issue seems to be that rtl8192cu doesn't scan after having
>>> disconnected at least once, and maybe doesn't report any/good signal
>>> strength values.
>>
>> The problem is likely that rtl8192cu goes mute after a disconnect. I'm
>> not sure if it happens only with WPA/WPA2 or if all encryption methods
>> are affected. I have not yet found the problem, but this and other
>> reports have increased the priority.
>>
>
> FYI,
>
> If you look at the logs for the instance when the furthest away AP was
> selected (info-furthest-away), At least I, see no disconnections at all.
> It selected the furthest AP yet was unusable. Yet no disconnects and
> iwconfig showed good.
>

I haven't noticed any activity on this. Should I just toss out all my 
rtl8192cu devices? If so, can anyone  recommend ANY USB wireless-N 
devices that actually work as they should in Linux with Linux drivers?

Thanks and Regards
Mark

      reply	other threads:[~2013-01-03 12:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 14:10 Wireless network problem with Access Point selection using ifup Mark Hounschell
2012-12-06 15:03 ` Johannes Berg
2012-12-07 10:12   ` Mark Hounschell
2012-12-07 20:50     ` Mark Hounschell
2012-12-07 20:54       ` Johannes Berg
2012-12-07 21:06         ` Mark Hounschell
     [not found]           ` <50C5B65F.4040104@cfl.rr.com>
2012-12-10 10:26             ` Johannes Berg
2012-12-10 11:10               ` Mark Hounschell
2012-12-10 11:29                 ` Johannes Berg
2012-12-10 12:00                   ` Mark Hounschell
2012-12-10 12:46                     ` rtl8192cu problem - " Johannes Berg
2012-12-10 16:24                       ` Larry Finger
2012-12-10 17:38                         ` Mark Hounschell
2013-01-03 12:52                           ` Mark Hounschell [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=50E57F1D.7050803@compro.net \
    --to=markh@compro.net \
    --cc=Larry.Finger@lwfinger.net \
    --cc=dmarkh@cfl.rr.com \
    --cc=johannes@sipsolutions.net \
    --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).