FS#27581 - 3.1.5 kernel breaks iwlagn compatibility with 802.11n wifi access points

Attached to Project: Arch Linux
Opened by Yan-Fa Li (yanfali) - Thursday, 15 December 2011, 06:22 GMT
Last edited by Thomas Bächler (brain0) - Monday, 09 January 2012, 17:26 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 13
Private No

Details

Description:
iwlagn driver is stops connect to 802.11n access points after this release. Interesting 802.11g access works fine. kernel 3.1.4 worked. After upgrade to 3.1.5 it stopped working. Fedora has the same bug reported. With an apparent fix:

https://bugzilla.redhat.com/show_bug.cgi?id=767173

Additional info:
core/linux 3.1.5-1 (base) [installed]
The Linux Kernel and modules



Steps to reproduce:
Try and connect to an 802.11n access point using the iwlagn driver.
This task depends upon

Closed by  Thomas Bächler (brain0)
Monday, 09 January 2012, 17:26 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.1.8
Comment by sinister99 (sinister99) - Friday, 16 December 2011, 02:16 GMT
Same problem here, downgraded to 3.1.4 and it works fine again.
Comment by Mister Fred (MisterFred) - Friday, 16 December 2011, 16:45 GMT
Same here, and downgrading does the trick.
Comment by badboy (badboy) - Friday, 16 December 2011, 17:02 GMT
Looks like the same problem for me.
wpa_supplicant gives no error, but no ping goes through. Works fine on 3.1.4.
Had no time to test with 802.11g connections
Comment by Ezekiel Sulastin (ZekeSulastin) - Sunday, 18 December 2011, 16:59 GMT
Same problem using both core/3.1.5-1 and aur/linux-ck-3.1.5-2; the user-visible error from netcfg was a DHCP failure. Recompiling linux-ck with the fedora patch fixed the issue; I'll post more exact dmesg and such from the non-working kernel later.
Comment by Pierre Buard (Gilrain) - Friday, 30 December 2011, 16:05 GMT
The problem persists with testing/3.1.6-1
As suggested, recompiling kernel 3.1.5 with attached patch restores functionality.
Comment by Ezekiel Sulastin (ZekeSulastin) - Saturday, 31 December 2011, 20:38 GMT
The problem now persists with core 3.1.6-1, and recompiling 3.1.6 with the patch from redhat/linked by Pierre Buard fixes the issue.

Also, someone might want to add [linux] to the title so it shows up when someone clicks the bug reports link from the Packages site ;)
Comment by fakefur (fakefur) - Tuesday, 03 January 2012, 14:32 GMT
same here ... i went back to 3.1.4-1 from 3.1.5 and hoped 3.1.6-1 would fix it but it doesn't
Comment by Konstantin (kstep) - Thursday, 05 January 2012, 13:09 GMT
Tried 3.1.7-1, bug still persists.
Comment by Thomas Bächler (brain0) - Thursday, 05 January 2012, 14:07 GMT
A fix is in the stable queue (I think), should be in 3.1.8, which is scheduled to be released Friday night or Saturday morning.
Comment by Tim Boundy (Gigaplex) - Monday, 09 January 2012, 12:58 GMT
3.1.8 is out and resolved the issue for me.
Comment by badboy (badboy) - Monday, 09 January 2012, 13:03 GMT
3.1.8 resolved the issue atleast on one of my laptops. Will test it later on my main laptop.

// Edit: Works on both laptops just fine.
Comment by fakefur (fakefur) - Monday, 09 January 2012, 13:14 GMT
i'm having no luck still even with 3.1.8 ... my main laptop is a Thinkpad T500 with the 5100 wireless card ... even going back to 3.1.4 doesn't fix it anymore

my other laptop (a Thinkpad T41p) on sitting next to the T500 has no issues whatsoever in either arch or debian testing

*sigh*
Comment by Yan-Fa Li (yanfali) - Monday, 09 January 2012, 16:17 GMT
Works for me. As of 3.1.8 I can now connect to N access points again. Thanks.

Loading...