2.6.19-rc2 ipw2200 breakage with wpa_supplicant
Something changed between 2.6.18-mm1 and 2.6.19-rc2 to cause my laptop's ipw2200 to be unable to associate with the access point using NetworkManager and wpa_supplicant. I keep seeing this kind of thing over and over in the wpa_supplicant output:
Trying to associate with (removed) (SSID='Robman' freq=0 MHz) CTRL_IFACE monitor send - hexdump(len=43): (removed) Cancelling scan request
WPA: clearing own WPA/RSN IE
Automatic auth_alg selection: 0x1
RSN: using IEEE 802.11i/D9.0
WPA: Selected cipher suites: group 16 pairwise 16 key_mgmt 2
WPA: clearing AP WPA IE
WPA: set AP RSN IE - hexdump(len=22): (removed)
WPA: using GTK CCMP
WPA: using PTK CCMP
WPA: using KEY_MGMT WPA-PSK
WPA: Set own WPA IE default - hexdump(len=22):(removed) p key clearinger_wext_set_drop_unencrypted
State: ASSOCIATING -> ASSOCIATING wpa_driver_wext_associate
Setting authentication timeout: 15 sec 0 usec
EAPOL: External notification - EAP success=0
EAPOL: External notification - EAP fail=0
EAPOL: External notification - portControl=Auto
RSN: Ignored PMKID candidate without preauth flag Wireless event: cmd=0x8b06 len=8
Wireless event: cmd=0x8b1a len=15
Wireless event: cmd=0x8b19 len=8
Received 1373 bytes of scan results (6 BSSes)
Scan results: 6
Selecting BSS from priority group 0
0: (removed) ssid='Robman' wpa_ie_len=0 rsn_ie_len=22 caps=0x11
selected based on RSN IE
Trying to associate with (removed) (SSID='Robman' freq=0 MHz)
and iwevent keeps showing this repeatedly:
20:52:32.303911 eth1 Scan request completed 20:52:32.303945 eth1 Set Mode:Managed 20:52:32.303962 eth1 Set ESSID:"Robman" 20:52:32.671509 eth1 Scan request completed 20:52:32.671542 eth1 Set Mode:Managed 20:52:32.671560 eth1 Set ESSID:"Robman" 20:52:33.034063 eth1 Scan request completed
Replacing ipw2200.c from 2.6.18-mm1 (adapted for the irq changes) fixes the problem.
I do notice that I keep seeing those "Scan request completed" messages from iwevent when nothing is going on with the 2.6.19-rc2 driver but not the 2.6.18-mm1 driver.
Anyone else seeing this?
Signature · 3 lines
Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [email protected] Home Page: http://www.roberthancock.com/
Quoted 1 line · Robert Hancock
Something changed between 2.6.18-mm1 and 2.6.19-rc2 to cause my laptop's ipw2200 to be unable to associate with the access point using NetworkManager and
wpa_supplicant. I keep seeing this kind of thing over and over in thewpa_supplicantoutput:
It looks like the bad patch is this one. Reverting it makes it work again. Either there's a bug in here or it's a change breaking working userspace, either way, no good:
[PATCH] WE-21 for ipw2200
author Jean Tourrilhes <[email protected]>
Wed, 30 Aug 2006 01:01:40 +0000 (18:01 -0700) committer John W. Linville <[email protected]> Mon, 25 Sep 2006 20:52:16 +0000 (16:52 -0400)
commit 919ee6ddcd3fcff09dee90c11af17a802196ad1f
tree c45e35201d7a3f2c998fc316898f902fd85fdfd2
parent b978d0278c3a4c41bda806743c6ef5dca86b4c61
[PATCH] WE-21 for ipw2200
Signature · 3 lines
Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [email protected] Home Page: http://www.roberthancock.com/
Quoted 11 lines · On Fri, 20 Oct 2006 21:33:53 -0600 Robert Hancock <[email protected]> wrote:
Quoted 4 lines · Robert Hancock
Something changed between 2.6.18-mm1 and 2.6.19-rc2 to cause my laptop's ipw2200 to be unable to associate with the access point using NetworkManager and
wpa_supplicant. I keep seeing this kind of thing over and over in thewpa_supplicantoutput:It looks like the bad patch is this one. Reverting it makes it work again. Either there's a bug in here or it's a change breaking working userspace, either way, no good:
[PATCH] WE-21 for ipw2200
Please try 2.6.19-rc2-mm2, or git-wireless.patch therefrom.
Quoted 16 lines · Robert Hancock
Quoted 4 lines · Robert Hancock
Something changed between 2.6.18-mm1 and 2.6.19-rc2 to cause my laptop's ipw2200 to be unable to associate with the access point using NetworkManager and
wpa_supplicant. I keep seeing this kind of thing over and over in thewpa_supplicantoutput:It looks like the bad patch is this one. Reverting it makes it work again. Either there's a bug in here or it's a change breaking working userspace, either way, no good:
[PATCH] WE-21 for ipw2200
author Jean Tourrilhes <[email protected]>
Wed, 30 Aug 2006 01:01:40 +0000 (18:01 -0700) committer John W. Linville <[email protected]> Mon, 25 Sep 2006 20:52:16 +0000 (16:52 -0400)
Quoted 8 lines
commit
919ee6ddcd3fcff09dee90c11af17a802196ad1f
treec45e35201d7a3f2c998fc316898f902fd85fdfd2
parentb978d0278c3a4c41bda806743c6ef5dca86b4c61[PATCH] WE-21 for ipw2200
Signed-off-by Jean Tourrilhes <[email protected]>Signed-off-by John W. Linville <[email protected]>
This is a wpa_supplicant WE-21 incompatibility problem. Using iwconfig directly works. Don't know if upgrading wpa_supplicant helps.
Thanks,
-yi