iwl3945 unable to connect to WPA personal without linux-backports-modules being installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I found I am unable to connect to a WPA-personal secured wireless network using an iwl3945-based card, unless the linux-backport-
Prior to installing the backports package, any attempts to connect using NetworkManager would end up spamming the debug logs with the following (1 every few seconds):
Mar 24 08:05:38 mach4 kernel: [ 851.021878] wlan0: authenticate with AP 00:0f:b5:e7:6f:96
Mar 24 08:05:38 mach4 kernel: [ 851.021895] wlan0: authenticated
Mar 24 08:05:38 mach4 kernel: [ 851.021901] wlan0: associate with AP 00:0f:b5:e7:6f:96
Mar 24 08:05:38 mach4 kernel: [ 851.027643] wlan0: RX ReassocResp from 00:0f:b5:e7:6f:96 (capab=0x431 status=0 aid=1)
Mar 24 08:05:38 mach4 kernel: [ 851.027649] wlan0: associated
Mar 24 08:05:38 mach4 kernel: [ 851.030674] wlan0: disassociating by local choice (reason=3)
I then tried with wpa_supplicant, but that displayed the following errors during logging, and would keep disconnecting itself:
ioctl[SIOCSIWEN
Driver did not support SIOCSIWENCODEEXT
After browsing around a bit through some other bugs, I decided to try installing the backport-modules package, which ended up fixing the problem.
I have the following packages and versions installed:
linux-restricte
linux-backports
wpasupplicant: 0.6.6-2
Thanks for your bug report. Unfortunately, because this bug is not reported against any package, it didn't get any attention during a long time. Fortunately, your bug description says that your card worked with backports, that means that this bug is now fixed in Karmic because Karmic use more recent drivers. According to this, I'm marking this bug report as Fix Released.