From: Seth Forshee <seth.forshee@canonical.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Chaoming Li <chaoming_li@realsil.com.cn>, linux-wireless@vger.kernel.org
Subject: Re: Problems associating with RTL8188CE
Date: Tue, 13 Dec 2011 15:26:06 -0600 [thread overview]
Message-ID: <20111213212606.GB30788@thinkpad-t410> (raw)
In-Reply-To: <4EE7B85E.3070802@lwfinger.net>
On Tue, Dec 13, 2011 at 02:41:02PM -0600, Larry Finger wrote:
> On 12/13/2011 01:42 PM, Seth Forshee wrote:
> >I have another AP that the rtl8192ce doesn't have any problems
> >associating with, so I also captured a trace with wireshark when
> >associating to that AP. I didn't see much that differed except that the
> >probe response frame with the problematic AP is about 350 bytes longer
> >(due to additional information elements).
>
> The extra IE entries must be the clue.
>
> >Something else that I noticed is that with the problematic AP, inactive
> >power save seems to kick in shortly afer sending the
> >probe/authentication requests. I wondered if this might be behind the
> >issues, but loading the module with ips=0 makes no difference.
> >
> >Any suggestions on what might be going wrong or next steps for
> >debugging?
>
> With ips=0, all power save should be eliminated. Please take the two
> capture files, and filter all but the probe and probe response
> frames. I'll try to find some time to analyze them.
The capture files are available at:
http://people.canonical.com/~sforshee/rtl8188ce/
Thanks,
Seth
next prev parent reply other threads:[~2011-12-13 21:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 22:54 Problems associating with RTL8188CE Seth Forshee
2011-11-20 5:25 ` Larry Finger
2011-11-21 18:13 ` Seth Forshee
2011-11-21 18:34 ` Larry Finger
2011-11-21 18:56 ` Seth Forshee
2011-11-22 2:01 ` Larry Finger
2011-11-22 2:20 ` Seth Forshee
2011-11-29 18:55 ` Seth Forshee
2011-12-13 19:42 ` Seth Forshee
2011-12-13 20:41 ` Larry Finger
2011-12-13 21:26 ` Seth Forshee [this message]
2011-12-14 4:57 ` Larry Finger
2011-12-14 16:23 ` Seth Forshee
2011-12-14 16:39 ` Larry Finger
2011-12-14 16:49 ` Seth Forshee
2011-12-14 16:58 ` Larry Finger
2011-12-14 17:12 ` Seth Forshee
2011-12-14 17:25 ` Larry Finger
2011-12-14 17:43 ` Larry Finger
2011-12-14 17:58 ` Seth Forshee
2012-01-26 21:33 ` Seth Forshee
2012-01-26 23:50 ` Larry Finger
2012-01-27 3:06 ` Seth Forshee
2012-01-27 17:05 ` Seth Forshee
2012-01-27 18:14 ` Larry Finger
2011-12-14 21:52 ` Tim Gardner
2011-12-14 22:54 ` Larry Finger
2011-12-15 0:50 ` Larry Finger
2011-12-15 18:41 ` Tim Gardner
2011-12-15 19:50 ` Larry Finger
2011-12-16 16:53 ` Tim Gardner
2011-12-16 17:06 ` Larry Finger
2011-12-16 17:11 ` Tim Gardner
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=20111213212606.GB30788@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--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