linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Alan Pater <alan.pater@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	'George0505' <george0505@realtek.com>,
	'georgia' <georgia@realtek.com>
Subject: Re: rtl8192cu - fails to maintain connection to some Access Points
Date: Thu, 20 Oct 2011 22:59:34 -0500	[thread overview]
Message-ID: <4EA0EE26.8010107@lwfinger.net> (raw)
In-Reply-To: <CAN4ACka-egrr=GnBomT0Yc_r_mzS-+v8OE=D0vBoH+jFQJwX8w@mail.gmail.com>

On 10/20/2011 06:02 PM, Alan Pater wrote:
> Hi folks
>
> Several people over on Ubuntu Launchpad are reporting that this USB WiFi
> adaptor has issues connecting to certain access points. In my case, I cannot
> connect to a Meraki mesh network, but have no trouble when using my Android
> phone as a WiFi Access Point.
>
> The launchpad bugs are:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/852190
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/869530
> https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-3.0.0/+bug/862684
>
> ~$ uname -a
> Linux crow 2.6.38-11-generic #50-Ubuntu SMP Mon Sep 12 21:18:14 UTC 2011
> i686 i686 i386 GNU/Linux
> ~$ lsusb
> Bus 001 Device 004: ID 0bda:8176 Realtek Semiconductor Corp.
>
> Note that I have tried newer kernels, including 3.1.0 without it making a
> difference.
>
> Is there some other steps we could be taking to figure out what is going on
> here?

You need to run wireshark on a different computer and capture the attempt to 
connect. The device works with my 3 APs, but none are Meraki.

Larry


  reply	other threads:[~2011-10-21  3:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20 23:02 rtl8192cu - fails to maintain connection to some Access Points Alan Pater
2011-10-21  3:59 ` Larry Finger [this message]
2011-10-21  7:28   ` Sedat Dilek
2011-10-21 13:23     ` Alan Pater

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=4EA0EE26.8010107@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=alan.pater@gmail.com \
    --cc=george0505@realtek.com \
    --cc=georgia@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).