linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: vishnu <vishnu.kopparapu@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing
Date: Mon, 18 Mar 2013 18:20:09 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130318T191350-236@post.gmane.org> (raw)
In-Reply-To: 5144A184.1060900@iki.fi

Jussi Kivilinna <jussi.kivilinna@...> writes:

> 
> On 15.03.2013 15:29, vishnu wrote:
> > Hello all,
> > 
> > driver used : rtl8192cu
> > 
> > When I tested with my linux kernel 3.0 , I didn't have any problems 
connecting 
> > to AP. But with kernel 3.6.8 , I had a problem . When I tested with 3.7.8 
also I 
> > am facing the same problem. This is the latest kernel used by latest release 
of 
> > buildroot , so I didn't test any kernels after that version.
> > 
> > The authentication and association are fine but from some reason it is 
> > disassociating after that and it keeps repeating it and it never connects to 
the 
> > AP.
> > 
> 
> Have you tested this patch: http://marc.info/?l=linux-
wireless&m=136318849815054&w=2
> 
> It solves re-association issues that rtl8192cu had.
> 
> -Jussi
> 
> 

Hello Jussi,

I have applied the patch to kernel 3.7.8 and it doesn't fix my issue. I have 
started testing the latest 3.9.0-rc2 version. I will let you know once I have 
tested.

Thanks,
Vishnu.





  reply	other threads:[~2013-03-18 18:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 13:29 problem connecting to AP on new kernel (disassociating continuously after associating ) . Can some one please comment on the issue I am facing vishnu
2013-03-16 16:44 ` Jussi Kivilinna
2013-03-18 18:20   ` vishnu [this message]
2013-03-18 18:29     ` Larry Finger
2013-03-18 18:44       ` vishnu
2013-03-19 15:40       ` vishnu
2013-03-19 18:14         ` Larry Finger
2013-03-20 12:56           ` vishnu

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=loom.20130318T191350-236@post.gmane.org \
    --to=vishnu.kopparapu@gmail.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).