I'm seeing a lot of problems associating with APs when using a Toshiba
NB505 with RTL8188CE wireless. The situation seems to have improved
quite a bit when I moved from 3.0 to 3.2-rc2, but I still see a good
number of failed associations. This card doesn't seem to like my Linksys
E2000 router in particular; I rarely see a successful association with
this router.
I'm attaching logs from the kernel and wpa_supplicant from some failed
associations with the E2000 along with the wpa_supplicant configuration
I used. I loaded rtl8192ce with debug=3, but if more verbosity or any
other information is needed, please let me know.
Thanks,
Seth
On 11/21/2011 12:13 PM, Seth Forshee wrote:
>
> I've uploaded the capture along with the logs to
> http://people.canonical.com/~sforshee/rtl8188ce/.
Unfortunately, I do not have permission to access the pcap file. The other two
are OK, but not the one of interest.
Larry
On 11/18/2011 04:54 PM, Seth Forshee wrote:
> I'm seeing a lot of problems associating with APs when using a Toshiba
> NB505 with RTL8188CE wireless. The situation seems to have improved
> quite a bit when I moved from 3.0 to 3.2-rc2, but I still see a good
> number of failed associations. This card doesn't seem to like my Linksys
> E2000 router in particular; I rarely see a successful association with
> this router.
>
> I'm attaching logs from the kernel and wpa_supplicant from some failed
> associations with the E2000 along with the wpa_supplicant configuration
> I used. I loaded rtl8192ce with debug=3, but if more verbosity or any
> other information is needed, please let me know.
Would it be possible for you to have a separate computer log the transaction
between the AP with ESSID 'Kailia' and the RTL8188CE using wireshark or Kismet?
Chaoming may see something in the logs that I do not, but the request for
authentication is timing out. With wireshark, we can see what is actually on the
air.
Larry
On 11/21/2011 12:56 PM, Seth Forshee wrote:
> On Mon, Nov 21, 2011 at 12:34:52PM -0600, Larry Finger wrote:
>> On 11/21/2011 12:13 PM, Seth Forshee wrote:
>>>
>>> I've uploaded the capture along with the logs to
>>> http://people.canonical.com/~sforshee/rtl8188ce/.
>>
>> Unfortunately, I do not have permission to access the pcap file. The
>> other two are OK, but not the one of interest.
>
> Sorry about that, didn't notice the lack of permissions. Fixed now.
I got it now. I would like one other piece of information - what is the MAC
address of your RTL8188CE device? It is not found in any of the dmesg logs that
I have.
Larry
On Sat, Nov 19, 2011 at 11:25:44PM -0600, Larry Finger wrote:
> On 11/18/2011 04:54 PM, Seth Forshee wrote:
> >I'm seeing a lot of problems associating with APs when using a Toshiba
> >NB505 with RTL8188CE wireless. The situation seems to have improved
> >quite a bit when I moved from 3.0 to 3.2-rc2, but I still see a good
> >number of failed associations. This card doesn't seem to like my Linksys
> >E2000 router in particular; I rarely see a successful association with
> >this router.
> >
> >I'm attaching logs from the kernel and wpa_supplicant from some failed
> >associations with the E2000 along with the wpa_supplicant configuration
> >I used. I loaded rtl8192ce with debug=3, but if more verbosity or any
> >other information is needed, please let me know.
>
> Would it be possible for you to have a separate computer log the
> transaction between the AP with ESSID 'Kailia' and the RTL8188CE
> using wireshark or Kismet? Chaoming may see something in the logs
> that I do not, but the request for authentication is timing out.
> With wireshark, we can see what is actually on the air.
I've uploaded the capture along with the logs to
http://people.canonical.com/~sforshee/rtl8188ce/.
Thanks,
Seth
On Mon, Nov 21, 2011 at 08:01:50PM -0600, Larry Finger wrote:
> On 11/21/2011 12:56 PM, Seth Forshee wrote:
> >On Mon, Nov 21, 2011 at 12:34:52PM -0600, Larry Finger wrote:
> >>On 11/21/2011 12:13 PM, Seth Forshee wrote:
> >>>
> >>>I've uploaded the capture along with the logs to
> >>>http://people.canonical.com/~sforshee/rtl8188ce/.
> >>
> >>Unfortunately, I do not have permission to access the pcap file. The
> >>other two are OK, but not the one of interest.
> >
> >Sorry about that, didn't notice the lack of permissions. Fixed now.
>
> I got it now. I would like one other piece of information - what is
> the MAC address of your RTL8188CE device? It is not found in any of
> the dmesg logs that I have.
7c:4f:b5:c7:a5:53
Thanks for taking a look.
Seth
On Mon, Nov 21, 2011 at 08:20:08PM -0600, Seth Forshee wrote:
> On Mon, Nov 21, 2011 at 08:01:50PM -0600, Larry Finger wrote:
> > On 11/21/2011 12:56 PM, Seth Forshee wrote:
> > >On Mon, Nov 21, 2011 at 12:34:52PM -0600, Larry Finger wrote:
> > >>On 11/21/2011 12:13 PM, Seth Forshee wrote:
> > >>>
> > >>>I've uploaded the capture along with the logs to
> > >>>http://people.canonical.com/~sforshee/rtl8188ce/.
> > >>
> > >>Unfortunately, I do not have permission to access the pcap file. The
> > >>other two are OK, but not the one of interest.
> > >
> > >Sorry about that, didn't notice the lack of permissions. Fixed now.
> >
> > I got it now. I would like one other piece of information - what is
> > the MAC address of your RTL8188CE device? It is not found in any of
> > the dmesg logs that I have.
>
> 7c:4f:b5:c7:a5:53
>
> Thanks for taking a look.
Hi Larry,
Just wondering if you've gotten a chance to take a look at the trace
yet.
Thanks,
Seth
On Mon, Nov 21, 2011 at 12:34:52PM -0600, Larry Finger wrote:
> On 11/21/2011 12:13 PM, Seth Forshee wrote:
> >
> >I've uploaded the capture along with the logs to
> >http://people.canonical.com/~sforshee/rtl8188ce/.
>
> Unfortunately, I do not have permission to access the pcap file. The
> other two are OK, but not the one of interest.
Sorry about that, didn't notice the lack of permissions. Fixed now.
On Tue, Dec 13, 2011 at 10:57:42PM -0600, Larry Finger wrote:
> Seth,
>
> On 12/13/2011 03:26 PM, Seth Forshee wrote:
> >
> >The capture files are available at:
> >
> >http://people.canonical.com/~sforshee/rtl8188ce/
>
> The major difference is that the "bad" AP implements 802.11n HT40
> technology, but the "good" one does not.
>
> There was a period when rtl8192ce and rtl8192cu had a bug that
> prevented them from associating with 802.11n APs, but that was fixed
> a long time ago. I can communicate with my Netgear WNDR3300 AP that
> implements full 802.11 capabilities.
>
> What kernel are you running? If you implement the bleeding-edge
> compat-wireless release, does that help.
I'm running 3.2-rc5 currently. The results are the same with
bleeding-edge compat-wireless.
Seth
Seth,
As expected, my RTL8188SE came right up.
The lspci -nnv details for my card are
06:00.0 0280: 10ec:8176 (rev 01)
Subsystem: 10ec:8176
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 21
Region 0: I/O ports at 4000 [size=256]
Region 2: Memory at f8000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: rtl8192ce
Does yours also have 10ec:8176 as the PCI ID?
Larry
On 12/15/2011 12:41 PM, Tim Gardner wrote:
> On 12/14/2011 05:50 PM, Larry Finger wrote:
>> Tim,
>>
>> I did the live test with the Dec. 14 build of 12.04 (64 bit). It
>> connected with my WNDR3300 with no difficulty. I tested all 4 modes
>> supported by the AP. All worked.
>>
>> I assume that an installation would work the same as the live version,
>> but that is easy for you to test.
>>
>> Larry
>>
>
> Here are the 3 modes I was able to successfully test on my WNDR3300 as an open AP:
>
> * Up to 270Mbps at 2.4Ghz
> 11N Channel: 03/2.422Ghz
> in this mode only the 11N SSID is beaconed.
> iperf: 11.2 Mbps average over 120 seconds, high of 26.2 Mbps, low of 6.71
>
> * Up to 270Mbps at 5Ghz & 54Mbps at 2.4Ghz
> 11N Channel: 36 / 5.180Ghz
> 11G Channel: auto
> in this mode only the G beacon can be seen (which makes sense)
> iperf: 14.3 Mbps average over 120 seconds, high of 28.5 Mbps, low of 8.97
>
> * Up to 130Mbps at 2.4Ghz
> 11N Channel: 03/2.422Ghz
> in this mode only the 11N SSID is beaconed.
> iperf: 16.0 Mbps average over 120 seconds, high of 28.9 Mbps, low of 7.44
>
> This mode would not acquire a beacon using the rtl8192ce:
>
> * Up to 130Mbps at 5Ghz & 54Mbps at 2.4Ghz
> 11N Channel: 36 / 5.180Ghz
> 11G Channel: auto
> in this mode no beacon can be seen.
>
> I verified using a MacBook Air under OS/X that the N SSID was appearing on the 5
> Ghz channel, but couldn't see the G beacon. Maybe its a bug in the WNDR3300.
I had never used the "auto" channel setting before. When I set my AP to the same
configuration as yours (130/54 and 36/auto), it sent the 802.11n beacon in the
2.4GHz channel. The 11G SSID was not seen; however, I could connect to the AP on
channel 1. When I switched to 11G channel 1, rather than auto, then I saw the
11G SSID in the beacon. I then tested the 5G band using a Dell DW1450 (p54usb)
dual-band device. The 11N SSID was present on channel 36 using auto or channel 1.
There may be a bug in the WNDR3300 firmware. Sometimes when I switched from
channel 1 to auto for the 2G band, that band would beacon the 11G SSID, and
other times, it would beacon the 11N SSID. I have not determined a pattern. The
11N SSID is always shown on the selected 5G channel. I could, however, connect
the RTL8188CE to whatever SSID the AP was sending on the 2.4GHz band.
Curiouser and curiouser,
Larry
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
On Wed, Dec 14, 2011 at 11:43:17AM -0600, Larry Finger wrote:
> Seth,
>
> As expected, my RTL8188SE came right up.
>
> The lspci -nnv details for my card are
>
> 06:00.0 0280: 10ec:8176 (rev 01)
> Subsystem: 10ec:8176
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR+ FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin A routed to IRQ 21
> Region 0: I/O ports at 4000 [size=256]
> Region 2: Memory at f8000000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: <access denied>
> Kernel driver in use: rtl8192ce
>
> Does yours also have 10ec:8176 as the PCI ID?
Yes.
07:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8184]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 17
Region 0: I/O ports at 2000 [size=256]
Region 2: Memory at f0100000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: rtl8192ce
Kernel modules: rtl8192ce
On 12/14/2011 09:49 AM, Seth Forshee wrote:
> On Wed, Dec 14, 2011 at 10:39:44AM -0600, Larry Finger wrote:
>> On 12/14/2011 10:23 AM, Seth Forshee wrote:
>>>
>>> I'm running 3.2-rc5 currently. The results are the same with
>>> bleeding-edge compat-wireless.
>>
>> I'm running 3.2-rc5 from wireless-testing, but I should test the one
>> from mainline. I'll also retest an RTL8188CE with my 802.11n AP.
>>
>> What model is that Cisco AP? Perhaps Realsil has one in their lab. I
>> do not have access to any Cisco hardware.
>
> It's a Linksys E2000.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
I ordered a refurb Linksys E3000. Should be here Friday. My Lenovo x120e
has the identical adapter. It seems to work pretty well except that it
won't show up the WNDR3300 11N SSID in the list. I've tested thusly:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/902557/comments/52
rtg
--
Tim Gardner [email protected]
On 12/14/2011 10:49 AM, Seth Forshee wrote:
> On Wed, Dec 14, 2011 at 10:39:44AM -0600, Larry Finger wrote:
>> On 12/14/2011 10:23 AM, Seth Forshee wrote:
>>>
>>> I'm running 3.2-rc5 currently. The results are the same with
>>> bleeding-edge compat-wireless.
>>
>> I'm running 3.2-rc5 from wireless-testing, but I should test the one
>> from mainline. I'll also retest an RTL8188CE with my 802.11n AP.
>>
>> What model is that Cisco AP? Perhaps Realsil has one in their lab. I
>> do not have access to any Cisco hardware.
>
> It's a Linksys E2000.
If matters come to worse, I can buy a used E2000 for $30 on E-bay.
Larry
On 12/16/2011 10:06 AM, Larry Finger wrote:
> On 12/16/2011 10:53 AM, Tim Gardner wrote:
>>
>> Yep - specifying a _fixed_ channel for 'Up to 130Mbps at 5Ghz & 54Mbps at
>> 2.4Ghz' allowed a connection using the G beacon. I have not verified
>> using a
>> 5Ghz capable adapter that its also beaconing on channel 36.
>
> Do you want to report this to Netgear, or should I?
>
> Larry
>
Please, be my guest :) I'll go back to working on Intel wifi issues.
rtg
--
Tim Gardner [email protected]
Seth,
On 12/13/2011 03:26 PM, Seth Forshee wrote:
>
> The capture files are available at:
>
> http://people.canonical.com/~sforshee/rtl8188ce/
The major difference is that the "bad" AP implements 802.11n HT40 technology,
but the "good" one does not.
There was a period when rtl8192ce and rtl8192cu had a bug that prevented them
from associating with 802.11n APs, but that was fixed a long time ago. I can
communicate with my Netgear WNDR3300 AP that implements full 802.11 capabilities.
What kernel are you running? If you implement the bleeding-edge compat-wireless
release, does that help.
Larry
On 12/16/2011 10:53 AM, Tim Gardner wrote:
>
> Yep - specifying a _fixed_ channel for 'Up to 130Mbps at 5Ghz & 54Mbps at
> 2.4Ghz' allowed a connection using the G beacon. I have not verified using a
> 5Ghz capable adapter that its also beaconing on channel 36.
Do you want to report this to Netgear, or should I?
Larry
On Mon, Nov 21, 2011 at 08:20:08PM -0600, Seth Forshee wrote:
> On Mon, Nov 21, 2011 at 08:01:50PM -0600, Larry Finger wrote:
> > On 11/21/2011 12:56 PM, Seth Forshee wrote:
> > >On Mon, Nov 21, 2011 at 12:34:52PM -0600, Larry Finger wrote:
> > >>On 11/21/2011 12:13 PM, Seth Forshee wrote:
> > >>>
> > >>>I've uploaded the capture along with the logs to
> > >>>http://people.canonical.com/~sforshee/rtl8188ce/.
> > >>
> > >>Unfortunately, I do not have permission to access the pcap file. The
> > >>other two are OK, but not the one of interest.
> > >
> > >Sorry about that, didn't notice the lack of permissions. Fixed now.
> >
> > I got it now. I would like one other piece of information - what is
> > the MAC address of your RTL8188CE device? It is not found in any of
> > the dmesg logs that I have.
>
> 7c:4f:b5:c7:a5:53
Larry,
I've been trying to look into this myself over the last couple of days,
but I'm still trying to learn all of this 802.11 stuff. I've kind of hit
the limit of what knowledge I've acquired so far, so I'd appreciate it
if you could look at my findings and offer suggestions.
What I'm doing is running wpa_supplicant manually to try and initiate a
connection while monitoring the traffic with wireshark on a separate
machine. What I'm seeing is that when the rtl8192ce device sends a
probe request or authentication request, the majority of the time the AP
sends a response but the adapter fails to ack the response (I don't see
the ack in the wireshark capture, and the AP resends the probe response
several times). The logs show timeouts that correspond to the types of
responses that aren't being acked. It's as if the adapter doesn't see
the responses at all.
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).
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?
Thanks,
Seth
On Wed, Dec 14, 2011 at 10:39:44AM -0600, Larry Finger wrote:
> On 12/14/2011 10:23 AM, Seth Forshee wrote:
> >
> >I'm running 3.2-rc5 currently. The results are the same with
> >bleeding-edge compat-wireless.
>
> I'm running 3.2-rc5 from wireless-testing, but I should test the one
> from mainline. I'll also retest an RTL8188CE with my 802.11n AP.
>
> What model is that Cisco AP? Perhaps Realsil has one in their lab. I
> do not have access to any Cisco hardware.
It's a Linksys E2000.
On 12/14/2011 05:50 PM, Larry Finger wrote:
> Tim,
>
> I did the live test with the Dec. 14 build of 12.04 (64 bit). It
> connected with my WNDR3300 with no difficulty. I tested all 4 modes
> supported by the AP. All worked.
>
> I assume that an installation would work the same as the live version,
> but that is easy for you to test.
>
> Larry
>
Here are the 3 modes I was able to successfully test on my WNDR3300 as
an open AP:
* Up to 270Mbps at 2.4Ghz
11N Channel: 03/2.422Ghz
in this mode only the 11N SSID is beaconed.
iperf: 11.2 Mbps average over 120 seconds, high of 26.2 Mbps, low of 6.71
* Up to 270Mbps at 5Ghz & 54Mbps at 2.4Ghz
11N Channel: 36 / 5.180Ghz
11G Channel: auto
in this mode only the G beacon can be seen (which makes sense)
iperf: 14.3 Mbps average over 120 seconds, high of 28.5 Mbps, low of 8.97
* Up to 130Mbps at 2.4Ghz
11N Channel: 03/2.422Ghz
in this mode only the 11N SSID is beaconed.
iperf: 16.0 Mbps average over 120 seconds, high of 28.9 Mbps, low of 7.44
This mode would not acquire a beacon using the rtl8192ce:
* Up to 130Mbps at 5Ghz & 54Mbps at 2.4Ghz
11N Channel: 36 / 5.180Ghz
11G Channel: auto
in this mode no beacon can be seen.
I verified using a MacBook Air under OS/X that the N SSID was appearing
on the 5 Ghz channel, but couldn't see the G beacon. Maybe its a bug in
the WNDR3300.
rtg
--
Tim Gardner [email protected]
On Wed, Dec 14, 2011 at 10:58:09AM -0600, Larry Finger wrote:
> On 12/14/2011 10:49 AM, Seth Forshee wrote:
> >On Wed, Dec 14, 2011 at 10:39:44AM -0600, Larry Finger wrote:
> >>On 12/14/2011 10:23 AM, Seth Forshee wrote:
> >>>
> >>>I'm running 3.2-rc5 currently. The results are the same with
> >>>bleeding-edge compat-wireless.
> >>
> >>I'm running 3.2-rc5 from wireless-testing, but I should test the one
> >>from mainline. I'll also retest an RTL8188CE with my 802.11n AP.
> >>
> >>What model is that Cisco AP? Perhaps Realsil has one in their lab. I
> >>do not have access to any Cisco hardware.
> >
> >It's a Linksys E2000.
>
> If matters come to worse, I can buy a used E2000 for $30 on E-bay.
If there's anything you'd like me to try, don't hesitate to ask. I'm
trying to come up to speed on debugging wireless problems anyway, so I'd
value the experience.
Thanks,
Seth
On 12/14/2011 03:52 PM, Tim Gardner wrote:
> On 12/14/2011 09:49 AM, Seth Forshee wrote:
>> On Wed, Dec 14, 2011 at 10:39:44AM -0600, Larry Finger wrote:
>>> On 12/14/2011 10:23 AM, Seth Forshee wrote:
>>>>
>>>> I'm running 3.2-rc5 currently. The results are the same with
>>>> bleeding-edge compat-wireless.
>>>
>>> I'm running 3.2-rc5 from wireless-testing, but I should test the one
>>> from mainline. I'll also retest an RTL8188CE with my 802.11n AP.
>>>
>>> What model is that Cisco AP? Perhaps Realsil has one in their lab. I
>>> do not have access to any Cisco hardware.
>>
>> It's a Linksys E2000.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> I ordered a refurb Linksys E3000. Should be here Friday. My Lenovo x120e has the
> identical adapter. It seems to work pretty well except that it won't show up the
> WNDR3300 11N SSID in the list. I've tested thusly:
>
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/902557/comments/52
Something is funny. My AP is an WNDR3300 and it works perfectly in 802.11n mode
with kernels from both mainline and wireless-testing.
I think trying a Live CD might be in order. I'm downloading
http://cdimage.ubuntu.com/daily-live/current/precise-desktop-amd64.iso.
If this is not the correct one, please send the better link.
Larry
Larry
Tim,
I did the live test with the Dec. 14 build of 12.04 (64 bit). It connected with
my WNDR3300 with no difficulty. I tested all 4 modes supported by the AP. All
worked.
I assume that an installation would work the same as the live version, but that
is easy for you to test.
Larry
On 12/14/2011 10:23 AM, Seth Forshee wrote:
>
> I'm running 3.2-rc5 currently. The results are the same with
> bleeding-edge compat-wireless.
I'm running 3.2-rc5 from wireless-testing, but I should test the one from
mainline. I'll also retest an RTL8188CE with my 802.11n AP.
What model is that Cisco AP? Perhaps Realsil has one in their lab. I do not have
access to any Cisco hardware.
Larry
On 12/15/2011 12:50 PM, Larry Finger wrote:
> On 12/15/2011 12:41 PM, Tim Gardner wrote:
>> On 12/14/2011 05:50 PM, Larry Finger wrote:
>>> Tim,
>>>
>>> I did the live test with the Dec. 14 build of 12.04 (64 bit). It
>>> connected with my WNDR3300 with no difficulty. I tested all 4 modes
>>> supported by the AP. All worked.
>>>
>>> I assume that an installation would work the same as the live version,
>>> but that is easy for you to test.
>>>
>>> Larry
>>>
>>
>> Here are the 3 modes I was able to successfully test on my WNDR3300 as
>> an open AP:
>>
>> * Up to 270Mbps at 2.4Ghz
>> 11N Channel: 03/2.422Ghz
>> in this mode only the 11N SSID is beaconed.
>> iperf: 11.2 Mbps average over 120 seconds, high of 26.2 Mbps, low of 6.71
>>
>> * Up to 270Mbps at 5Ghz & 54Mbps at 2.4Ghz
>> 11N Channel: 36 / 5.180Ghz
>> 11G Channel: auto
>> in this mode only the G beacon can be seen (which makes sense)
>> iperf: 14.3 Mbps average over 120 seconds, high of 28.5 Mbps, low of 8.97
>>
>> * Up to 130Mbps at 2.4Ghz
>> 11N Channel: 03/2.422Ghz
>> in this mode only the 11N SSID is beaconed.
>> iperf: 16.0 Mbps average over 120 seconds, high of 28.9 Mbps, low of 7.44
>>
>> This mode would not acquire a beacon using the rtl8192ce:
>>
>> * Up to 130Mbps at 5Ghz & 54Mbps at 2.4Ghz
>> 11N Channel: 36 / 5.180Ghz
>> 11G Channel: auto
>> in this mode no beacon can be seen.
>>
>> I verified using a MacBook Air under OS/X that the N SSID was
>> appearing on the 5
>> Ghz channel, but couldn't see the G beacon. Maybe its a bug in the
>> WNDR3300.
>
> I had never used the "auto" channel setting before. When I set my AP to
> the same configuration as yours (130/54 and 36/auto), it sent the
> 802.11n beacon in the 2.4GHz channel. The 11G SSID was not seen;
> however, I could connect to the AP on channel 1. When I switched to 11G
> channel 1, rather than auto, then I saw the 11G SSID in the beacon. I
> then tested the 5G band using a Dell DW1450 (p54usb) dual-band device.
> The 11N SSID was present on channel 36 using auto or channel 1.
>
> There may be a bug in the WNDR3300 firmware. Sometimes when I switched
> from channel 1 to auto for the 2G band, that band would beacon the 11G
> SSID, and other times, it would beacon the 11N SSID. I have not
> determined a pattern. The 11N SSID is always shown on the selected 5G
> channel. I could, however, connect the RTL8188CE to whatever SSID the AP
> was sending on the 2.4GHz band.
>
> Curiouser and curiouser,
>
> Larry
Yep - specifying a _fixed_ channel for 'Up to 130Mbps at 5Ghz & 54Mbps
at 2.4Ghz' allowed a connection using the G beacon. I have not verified
using a 5Ghz capable adapter that its also beaconing on channel 36.
rtg
--
Tim Gardner [email protected]
On 12/14/2011 11:12 AM, Seth Forshee wrote:
>
> If there's anything you'd like me to try, don't hesitate to ask. I'm
> trying to come up to speed on debugging wireless problems anyway, so I'd
> value the experience.
I have not had a chance to reboot so that I can install the RTL8188CE. In
addition, I'm building a fresh copy of mainline 3.2-rc5 for a separate test.
I'll let you know what happens.
Larry
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.
Larry
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
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.
Seth
On 01/27/2012 11:05 AM, Seth Forshee wrote:
>
> 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.
Thanks for the update. At least a mechanical problem would explain why I could
not reproduce your problem.
Larry
On Wed, Dec 14, 2011 at 11:58:04AM -0600, Seth Forshee wrote:
> On Wed, Dec 14, 2011 at 11:43:17AM -0600, Larry Finger wrote:
> > Seth,
> >
> > As expected, my RTL8188SE came right up.
> >
> > The lspci -nnv details for my card are
> >
> > 06:00.0 0280: 10ec:8176 (rev 01)
> > Subsystem: 10ec:8176
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > ParErr- Stepping- SERR+ FastB2B- DisINTx-
> > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
> > >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> > Latency: 0, Cache Line Size: 64 bytes
> > Interrupt: pin A routed to IRQ 21
> > Region 0: I/O ports at 4000 [size=256]
> > Region 2: Memory at f8000000 (64-bit, non-prefetchable) [size=16K]
> > Capabilities: <access denied>
> > Kernel driver in use: rtl8192ce
> >
> > Does yours also have 10ec:8176 as the PCI ID?
>
> Yes.
>
> 07:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
> Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:8184]
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 17
> Region 0: I/O ports at 2000 [size=256]
> Region 2: Memory at f0100000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: <access denied>
> Kernel driver in use: rtl8192ce
> Kernel modules: rtl8192ce
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
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.
Larry