Red Hat Bugzilla – Bug 462167
kernel-126.96.36.199-29.fc9 and IWL4965 break WPA
Last modified: 2008-11-11 14:32:56 EST
Description of problem:
Since updating to kernel-188.8.131.52-29.fc9.x86_64, i cannot connect to WPA protected networks. I have WPA both at work and at home, so it is quite a problem, now.
Version-Release number of selected component (if applicable):
update to said kernel
Steps to Reproduce:
2. Reboot in the new kernel
3. Try connecting to a wpa encrypted wifi network
Unable to connect, /var/log/messages ends with
iwl4965: Error sending TX power (-22)
correct connection to the network
I can confirm flakiness with iwl4965, WPA and this kernel. I actually got a connection once, but lost it later. (First boot attempt: unable to connect entirely, second boot attempt: able to connect, transfer some files over SFTP, then lost connection while downloading updates and failed to reconnect.) I don't see any error messages which look useful to me in /var/log/messages. I ended up booting into the previous kernel, but this obviously isn't a fix.
Same problem here with kernel-184.108.40.206-29.fc9.x86_64. When I boot kernel-220.127.116.11-108.fc9.x86_64 I can connect without problem.
I've seen this behavior as well. If I boot 18.104.22.168 everything is working properly. Using 22.214.171.124 I am unable to connect to any wireless networks.
$ rpm -q kernel
I'll be happy to provide any debugging assistance I can given direction.
I can confirm this problem as well. However, I can't connect to *any* networks including:
* Unsecured WiFI network
* WEP network
* WPA2 secured network
Booting back to 126.96.36.199-108.fc9.x86_64 and they all work.
Right, it's not just WPA, I tried the university's 802.1x LEAP network yesterday and had the same problem. (I actually was able to connect, but then lost the connection after a few minutes and couldn't reconnect.)
Created attachment 317148 [details]
egrep wlan0 /var/log/messages
WHen i added attachment bugzilla deleted my comments - trying again (see attachment above)
I confirm this with kernel-188.8.131.52-14.fc8 - totally unable to use the wireless.
I tried to connect a couple of times - even shutdown NM and nm-applet - then removed the iwl4965 module - turned off the radio kill switch and back on (this used to help a few months ago when I cud not connect then) - didnt help at all this time.
It appeared to connect - but I could not actually use the network.
I do have this in log (rest of log is above) :
kernel: wlan0 (WE) : Wireless Event too big (342)
Also with older kernel even - a large fraction of time - while it connects ok - it refuses to connect to the AP 6 inches from the laptop but chooses an alternate AP 100 feet away .. which is very odd.
Reverting to kernel-184.108.40.206-69.fc8 all works.
hope this is helpful
I am not using x64 kernel- just i686.
Quick update - Still not working using 220.127.116.11 kernel.
Confirm: with latest update (18.104.22.168-45), no solution for the issue. Is anybody looking at it?
The same issue (i.e. unable to connect to WPA networks) seems to occur on F8, F9, and rawhide. I have mostly concentrated on rawhide kernels so far, but not solution yet. This does not seem to be confined to iwl4965 but instead seems to affect all mac80211-based drivers.
FWIW, a clean 2.6.27-rc8 kernel built w/ the rawhide kernel configuration does _NOT_ exhibit this problem (at least not for me), while the rawhide and F9 kernels clearly do (for me). I do not see any wireless-related (or even crypto-related) difference between the rawhide kernels and the plain upstream kernels that would account for this behavior (or even suggest a link to it).
*** This bug has been marked as a duplicate of bug 458972 ***
WPA is WORKING with rt2x00's rt73usb (with the matching hardware, of course) on kernel-22.214.171.124-14.fc8. So it can't be all mac80211-based drivers.
Comment 12 is an interesting datapoint -- I'll try to confirm. Nevertheless, it seems unlikely that we somehow broke WPA in multiple mac80211-based drivers simultaneously (and only in Fedora) in unrelated ways...
Any updates on this? Current Fedora kernels not working with one of the most common wireless chipsets is really bad. I'm still stuck on kernel-126.96.36.199-108.fc9 on my laptop and I'm sure there are many more people with this problem. (And this is not just WPA - as I said, at least 802.1x LEAP is similarly broken.)
Oops, I see there are some updates (but unfortunately still no solution) in bug 458972.
I have been following this thread for some time - clearly some people have had very serious wireless connection issues with IWL4965 - however I have been running F9 for many months now with IWL4965 under F9 in Gnome using NetworkManager connecting with WPA2-PSK encryption - with not a single wireless problem all through the kernel changes from the 2.6.25 through to the current 2.6.26 kernels in F9.
The AP I am using is a Linksys WRT54GL and the encryption was until recently set to use "TKIP + AES". At the weekend I switched to "AES" only and the wireless remains solid. My laptop in this case is a Dell M4300, and at all stages I have been running with fully updated F9. The AP is set to use BG Mixed mode.
There must be something to hook into in giving the information that my system works perfectly well whereas other combinations of hardware seem not to. Why should different combinations give different results?
Would it be related to which AP is being used I wonder? I see a lot of people using the T61 and having problems. Are there any people running T61 who can connect using WPA?
Anyone with the same combination as mine who see these issues? My install was clean and I have made no adjustments at all to the networking setup - it connected first time without any special effort.
From comment #11 there is a suggestion that this may affect other mac8011-based drivers, but I have also been running an old laptop with F9 using the RT73usb in kernel driver to the same AP without issue also. Does this help?
In addition another machine using IWL3945 in kernel driver in F8 has been connecting to the same AP without any issues as well.....
Would be nice to know if there is some information that might give a lead in finding where the problem really lies?