Comment 52 for bug 352150

One more guess: In the last days I learned that there are quite strong interferences between bluetooth and wireless LAN since they both use the ISM band (2.4 to 2.4835 GHz) – see bug #219057.

Try to send a big file to your mobile phone and at the same time try to watch a movie online – at least for me this doesn't work; the data rate of my WLAN connection will be much slower than without using bluetooth at the same time & the connection will even be interrupted several times. My syslog then looks like this:

Aug 27 03:10:15 rosa wpa_supplicant[952]: CTRL-EVENT-DISCONNECTED bssid=00:1a:4f:93:9b:52 reason=0
Aug 27 03:10:15 rosa NetworkManager[870]: <info> (eth1): supplicant connection state: completed -> disconnected
Aug 27 03:10:15 rosa NetworkManager[870]: <info> (eth1): supplicant connection state: disconnected -> scanning
Aug 27 03:10:16 rosa wpa_supplicant[952]: Trying to associate with 00:1a:4f:93:9b:52 (SSID='wg-floragasse' freq=2417 MHz)
Aug 27 03:10:16 rosa NetworkManager[870]: <info> (eth1): supplicant connection state: scanning -> associating
Aug 27 03:10:16 rosa wpa_supplicant[952]: Associated with 00:1a:4f:93:9b:52
Aug 27 03:10:16 rosa wpa_supplicant[952]: CTRL-EVENT-CONNECTED - Connection to 00:1a:4f:93:9b:52 completed (reauth) [id=0 id_str=]
Aug 27 03:10:16 rosa NetworkManager[870]: <info> (eth1): supplicant connection state: associating -> associated
Aug 27 03:10:16 rosa NetworkManager[870]: <info> (eth1): supplicant connection state: associated -> completed
Aug 27 03:10:16 rosa wpa_supplicant[952]: CTRL-EVENT-DISCONNECTED bssid=00:1a:4f:93:9b:52 reason=0
Aug 27 03:10:16 rosa NetworkManager[870]: <info> (eth1): supplicant connection state: completed -> disconnected
Aug 27 03:10:16 rosa NetworkManager[870]: <info> (eth1): supplicant connection state: disconnected -> scanning
Aug 27 03:10:16 rosa wpa_supplicant[952]: Trying to associate with 00:1a:4f:93:9b:52 (SSID='wg-floragasse' freq=2417 MHz)
Aug 27 03:10:16 rosa NetworkManager[870]: <info> (eth1): supplicant connection state: scanning -> associating

I just took some lines out of the logfile, but I think you get the idea. Now, since nothing has been changed in the ipw2200-firmware over the last year but at the same time the behavior of the WLAN adapter changed radically (the number of firmware errors decreased enormously), I make a guess: maybe it's because bluetooth (bluez) works much better now and the interferences decreased?

BTW; in the meantime I had only _one_ firmware error with a connection problem after the firmware-restart and it even happens that I don't get a single "Firmware error detected"-message for several days. Great! :)