[regression-potential] Intel WiFi Link 5150ABG can't connect to Access Point if "802.11N-Only Mode" enabled

Bug #560230 reported by RussianNeuroMancer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux
Invalid
High
linux (Ubuntu)
Invalid
Medium
Unassigned
Nominated for Maverick by RussianNeuroMancer

Bug Description

I install linux-backports-modules-wireless-lucid-generic package for test another issue https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554832 with fresh driver, but found another problem. If in Access Point settings "802.11N-Only Mode" enabled Intel WiFi Link 5150AGN can't connect to AP.
If I change mode to "Mixed" or "802.11G-Only Mode" Intel WiFi Link 5150AGN can connect to AP.

Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :

I test this issue with this AP: Linksys 320N (DD-WRT v24-sp2 (build 14144 - 03/24/10) firmware, latest), Linksys 610N (DD-WRT v24-sp2 (build 14144 - 03/24/10) firmware, latest) and TP-LINK TL-WR941ND (090821 firmware, latest, official).

summary: - Intel WiFi Link 5150ABN can't connect to Access Point if "802.11N-Only
- Mode" enabled
+ [regression-potential ] Intel WiFi Link 5150ABN can't connect to Access
+ Point if "802.11N-Only Mode" enabled
summary: - [regression-potential ] Intel WiFi Link 5150ABN can't connect to Access
+ [regression-potential] Intel WiFi Link 5150ABN can't connect to Access
Point if "802.11N-Only Mode" enabled
tags: added: regression-potential
Revision history for this message
Leann Ogasawara (leannogasawara) wrote : Re: [regression-potential] Intel WiFi Link 5150ABN can't connect to Access Point if "802.11N-Only Mode" enabled

I'm removing the regression-proposed tag as this already is appropriately tagged regression-potential. Additionally there is no kernels in -proposed for Lucid so the regression-proposed tag doesn't apply here.

tags: removed: regression-proposed
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi RussianNeuroMancer,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :

Tested with 2.6.34rc5 - still an issue.

Changed in linux (Ubuntu):
status: Incomplete → Triaged
importance: Undecided → Medium
Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :

Also this bug is present in 2.6.33.

Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :
summary: - [regression-potential] Intel WiFi Link 5150ABN can't connect to Access
+ [regression-potential] Intel WiFi Link 5150AGN can't connect to Access
Point if "802.11N-Only Mode" enabled
description: updated
summary: - [regression-potential] Intel WiFi Link 5150AGN can't connect to Access
+ [regression-potential] Intel WiFi Link 5150ABG can't connect to Access
Point if "802.11N-Only Mode" enabled
Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :

My problem is result of incorrect detection of WiFi adapter. My adpater is 5150ABG, but iwlagn driver from 2.6.32 kernel detect it like 5150AGN, and allow connect to 802.11N-Mode enabled networks. In 2.6.33 and 2.6.34 detection problem is fixed.

Changed in linux (Ubuntu):
status: Triaged → Invalid
Changed in linux:
status: Unknown → Invalid
Changed in linux:
importance: Unknown → High
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.