Description of problem: I have a fine working wireless connection with kernel-2.6.25.6-55.fc9.i686 here (sending this report over it right now). After upgrading the kernel I cannot get a valid ip via dhcp and after a while my wireless connection disassociates (reason=7 or =3). Steps to Reproduce: 1. Use NetworkManager to connect to Network 2. wait for association 3. wait for ip Actual results: timeout Expected results: waiting for ip should finish successfull after a while.
It happens for me with intel 3945. I have two access points, one at home and one at work, and the behaviour is the same. Authentication is WPA-PSK.
Created attachment 310905 [details] Log of the Networkmanager session This is the log of the connection failures. I tried 3/4 times. There are thousands of the following messages: wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7) iwl3945: No space for Tx iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28 wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7) iwl3945: No space for Tx iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28 wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7) iwl3945: No space for Tx iwl3945: Error sending REPLY_LEDS_CMD: iwl3945_enqueue_hcmd failed: -28 wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7) wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7) wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7) wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7) wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7) wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7) wlan0: RX deauthentication from 00:16:e0:04:fa:c0 (reason=7)
Me too on a Dell Vostro 1700 with iwl3945. Interestingly, connecting to access point with no encryption worked with no Rx/Tx errors, and transferred a 15MB file no problem.
*** This bug has been marked as a duplicate of 453390 ***