From: Seth Forshee <seth.forshee@canonical.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Chaoming Li <chaoming_li@realsil.com.cn>,
Tim Gardner <tim.gardner@canonical.com>,
linux-wireless@vger.kernel.org
Subject: Re: Problems associating with RTL8188CE
Date: Fri, 27 Jan 2012 11:05:49 -0600 [thread overview]
Message-ID: <20120127170549.GB2251@ubuntu-macmini> (raw)
In-Reply-To: <20120127030623.GA26774@ubuntu-macmini>
On Thu, Jan 26, 2012 at 09:06:23PM -0600, Seth Forshee wrote:
> On Thu, Jan 26, 2012 at 05:50:39PM -0600, Larry Finger wrote:
> > On 01/26/2012 03:33 PM, Seth Forshee wrote:
> > >Sorry for the long silence on this, I was busy with some other things.
> > >But I've been playing with it again this week and uncovered some new
> > >information regarding the failures.
> > >
> > >I noticed the other day that the rtl8188ce was no longer having trouble
> > >associating with this AP. After playing around in the router settings I
> > >discovered that it works fine so long as the router isn't on channel 1.
> > >So then I configured my other router to use channel 1, and then I
> > >started seeing problems with that router as well.
> > >
> > >I also tried the rtl8192ce driver from Realtek's website, and I'm having
> > >better luck with that driver.
> >
> > Seth,
> >
> > Are those AP's 802.11n devices that allow HT features on channel 1?
> > I do not know if we support that or not. On my 802.11n device, it
> > automatically switches to channel 3 when I enable HT, and that
> > works.
> >
> > I can connect to an 802.11g AP on channel 1 with no trouble.
>
> Whether or not HT is enabled makes no difference. One is an older
> 802.11g router, and on the other I see the same problems with or without
> HT enabled.
I decided to remove the card from the netbook and test it in another
machine, and it worked flawlessly. A different card in the netbook works
fine as well.
But then after reinstalling the rtl8188ce in the netbook I'm not seeing
any problems associating. None at all. So perhaps the issue was
mechanical in nature.
I'll keep testing it for a while to see if the problems resurface, but
for now everything seems fine. Thanks for your help.
Seth
next prev parent reply other threads:[~2012-01-27 17:05 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
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 [this message]
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=20120127170549.GB2251@ubuntu-macmini \
--to=seth.forshee@canonical.com \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=linux-wireless@vger.kernel.org \
--cc=tim.gardner@canonical.com \
/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