[Karmic] Intel Pro/Wireless 3945BG (driver: iwl3945) disconnects frequently at random

Thank you for your report.

Could you please attach the following that can help the developers identify the issue.

sudo lspci -nnvv > lspci_nnvv.log
sudo iw event -t > iw_event_t.log

And can you try to identify whether or not this is an issue with NetworkManager, wpa_supplicant, or mac80211 ?
See here for more details: http://wireless.kernel.org/en/users/Documentation/Reporting_bugs#Identifying_the_bug

Regards
Iain

Thank you for a quick reply, Iain Bucław.

I couldn't run the exact command you asked, but I've adapted it the best I could. I ran iwevent instead.
I don't know how to attach more than one file, so here are the contents:

Output of iwevent:

20:31:26.858076 wlan0 Scan request completed
20:32:27.106692 wlan0 Scan request completed
20:33:47.076380 wlan0 Scan request completed
20:34:35.098698 wlan0 New Access Point/Cell address:Not-Associated
20:34:35.139631 wlan0 New Access Point/Cell address:Not-Associated
20:34:35.938540 wlan0 Set Mode:Managed
20:34:46.648602 wlan0 Scan request completed
20:34:46.649479 wlan0 Set Mode:Managed
20:34:46.649519 wlan0 Set Frequency:2.437 GHz (Channel 6)
20:34:46.664809 wlan0 Custom driver event:ASSOCINFO(ReqIEs=000f6e69636b656c6261636b5f77696669010802040b160c12182432043048606c RespIEs=010482848b9632080c1218243048606c)
20:34:46.671076 wlan0 New Access Point/Cell address:00:04:ED:58:6A:FE
20:34:56.857356 wlan0 Scan request completed
20:35:37.181558 wlan0 Scan request completed

Output of sudo lspci -nnvv is attached. I added `sudo' because I saw "Access denied" in the output.

I'll try to identify the bug further.

Perhaps this should also go into 'linux'.

I also experience this bug on karmic using an intel BCM4311 wireless card.
Same issue, the wireless connection is randomly reset every 5 - 10 minutes.
I've tried the various wireless drivers for my chipset, and all except ndiswrapper have this problem.
I also tried the upstream linux modules with the same effect.
In the system log, I get this message at the time of the reset:

Sep 22 17:11:01 jacob-laptop NetworkManager: <info> Wireless now disabled by radio killswitch
Sep 22 17:11:01 jacob-laptop NetworkManager: <info> (wlan0): device state change: 8 -> 2 (reason 0)
Sep 22 17:11:01 jacob-laptop NetworkManager: <info> (wlan0): deactivating device (reason: 0).
Sep 22 17:11:01 jacob-laptop NetworkManager: <info> (wlan0): canceled DHCP transaction, dhcp client pid 2715
Sep 22 17:11:01 jacob-laptop NetworkManager: <WARN> check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess#012
Sep 22 17:11:01 jacob-laptop NetworkManager: <info> (wlan0): taking down device.
Sep 22 17:11:01 jacob-laptop wpa_supplicant[1580]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Sep 22 17:11:02 jacob-laptop NetworkManager: <info> Wireless now enabled by radio killswitch
Sep 22 17:11:02 jacob-laptop NetworkManager: <info> (wlan0): bringing up device.
Sep 22 17:11:02 jacob-laptop NetworkManager: <info> (wlan0): device state change: 2 -> 3 (reason 0)
Sep 22 17:11:02 jacob-laptop NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready

dmesg also gives me this message:

[ 852.116129] wlan0: associated
[ 1329.237592] wlan0: deauthenticating by local choice (reason=3)
[ 1330.160107] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[ 1330.240907] Registered led device: b43-phy0::tx
[ 1330.241646] Registered led device: b43-phy0::rx
[ 1330.242285] Registered led device: b43-phy0::radio
[ 1330.252921] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1330.264413] wlan0: direct probe to AP 00:16:9d:cd:84:f0 try 1
[ 1330.464098] wlan0: direct probe to AP 00:16:9d:cd:84:f0 try 2
[ 1330.465190] wlan0 direct probe responded
[ 1330.465193] wlan0: authenticate with AP 00:16:9d:cd:84:f0
[ 1330.467201] wlan0: authenticated

I don't know what else I should attach...

I have this very exact situation, in a fully updated Karmic.

I experience exactly the same on my Thinkpad T60. Wifi is unusable, even with very strong signal. Karmic - fully updated, post-beta.

Replacing NM with WICD helps, so in my case it seems to be NM issue.

Hi,

yesterday i upgraded my 9.04 to karmic, everything worked. today morning i did an update/-grade via wlan (Linux vaio4 2.6.31-13-generic #43-Ubuntu SMP Fri Oct 9 17:41:46 UTC 2009 x86_64 GNU/Linux)

today afternoon my wlan does not work anymore.

stopping "network-manager" and entering the wpa-connection data in "/etc/network/interfaces" and a "ifup eth0" works perfectly.

it is a workaround.

Thanks Ulrich, for the workaround. I hope it gets fixed before Karmic gets released.

Someone please tell me what I have to do as the bug reporter to notify the developers of nm to help get it fixed. Thanks.

same here with an acer 4736z

Using wicd also works as a workaround for me, but I would still really like this problem to be fixed.
I prefer nm-applet.

hi,

the latest update/upgrade solved the problem (for me). now it works with nm again

no i just had the same problem on fully updated karmic its not fixed

I can confirm this on an updated install as of an hour ago. Can anyone here describe how they manually connected with WPA, using /etc/network/interfaces ?

Just got back to a wired connection to check if the problem persisted with an updated install and it did. I attached additional information to help diagnose the problem. Let me know if any further information is required.

A few more data points on this one:
* i'm having the same problem with wicd, but it works *better* with wicd - with nm this problem occurred so much it prevented me from getting anything useful done, now it's just a really big PITA
* this is on a Lenovo X300,

A few more data points on this one:
* i'm having the same problem with wicd, but it works *better* with wicd - with nm this problem occurred so much it prevented me from getting anything useful done, now it's just a really big PITA
* this is on a Lenovo X300, with a pro/wireless 4965 (lspci -vvv output attached)
* it started happening when i switched my AP to WPA1/TKIP/PSK - it wasn't happening at all with WEP; the AP is a WRT54GL, stock up-to-date firmware
* this is also happening on an Inspiron 8600 with an intel pro/wireless 2100 card, also started happening only when i switched the AP to WPA, was also working fine with WEP
* i used the laptop on another AP (some D-Link, don't remember which one) with WPA and it worked fine
I'll try manually configuring the card in /etc/network/interfaces, but that would be annoying as i move a lot with the laptop.

While we are collecting data points, here's my hardware:

  Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05) with ipw2200 Network Driver

I use WPA2 Personal on a D-Link router. My problems range from random connection drops, to randomly failing to connect, to sometimes totally failing to connect after many attempts.

During all attempts, it seems that authentication happens fine, but DHCP fails.

After switching to wicd I was able again to connect to networks successfully. Might I also say that I am using a Intel Corporation Wireless WiFi Link 5100 and it would fail to connect with network-manager.

Maybe this is a larger issue then originally thought. It will be interesting to see if other wireless drivers are also affected as it seems to be some sort of problem with network-manager.

* going with manual config didn't help; there's definitely an underlying problem here
* if i'm *right by* the AP, i don't have the problem, but the connection degrades extremely rapidly with distance, and i never had that problem when configured with WEP

I installed the latest iwlwifi drivers (from http://linuxwireless.org/en/users/Download, not by installing a new kernel), and am getting *vastly* improved wireless connection stability. I didn't change anything else, and it's still in WPA. I'm still on Wicd (which i know much prefer to nm, actually - much more granular in its settings, and uses the underlying tools - it's more geeky and less magic, if you will).

Others with this problem should also try to install newer drivers.

I compiled the drivers from source, but you can also get a modules-backport package which in theory should be just as recent; see http://linuxwireless.org/en/users/Download#Getting_compat-wireless_on_Ubuntu

Same for me:

I have installed the 9.10 beta in a Thinkpad T60p with wireless card Intel 3945abg.

the wireless connection has this strange behaviour:

1>>> wireless connect, loose and reconnect to the line every minute

2>>> as soon as my wireless is working, it causes other two pc in the room loosing their wireless signal (another laptop with ubuntu and a macbook)

Driver installed is iwl3945

When running windows, no problems at all.

My router's and wireless card's channels are both set on 6.

wiswaud,

Great find! I can now actually connect to networks and download at speeds that are acceptable.

I would suggest that anyone coming across this bug follow as wiswaud suggested in the above post and install the wireless backport package.

wiswaud didnt work for me.. i tried installing the compiled packages no results (doesnt even connect)..and i cant compile the wireless for my kernel for some kinda reason (error 2) ... i would have to recompile the all kernel according to some forums to fix that i dont really feel like... hows the situation for the final release of karmic?by the way im using release candidate with all updates and a fresh install... hope it gets fixed for the final release

psychok7 - this particular bug is about the ipw* and iwlwifi drivers being able to connect to a network, but suffering from frequent disconnections, with this message appearing regularly in the logs:
wlan0: link is not ready

(wlan0 might be different for you).
I think you have a different bug, if you can't even connect.

Everyone else reading this, i upgraded my other laptop to 2.6.28-16-generic (which is what's most recent in 9.04 atm), and this problem got fixed (this is the laptop with ipw2100). Perhaps the bugfix in the compat-wireless drivers made its way through and is now in the kernel.

AFAIC, this bug should perhaps be closed if we can get a few people to confirm that the newer ubuntu kernel packages fix it.

i have this same bug on acer aspire one when using ubuntu moblin remix. on desktop version its fine

wiswaud - after a fresh install i did have the same problem as evryone else (frequent disconnections) but i tried ur workaround (installed the backport packages for karmic) and with that it doesnt even connect..You say the latest kernel update works?should i remove those backport packages then?

I realized the problem is at least with Wpa/Wpa2 .. it connects and works without any problem when the theres no protection (at least that i tried)

psychok7 - yep, on my second laptop which has an ipw2100 card (ipw2100 driver):
* installing the compat-wireless drivers (which should be equivalent to installing the backport modules packages) made the card work perfectly
* and then upgrading the kernel to 2.6.28-16-generic (this is on a xubuntu 9.04 machine), also worked fine, with no need to install the backport drivers

On my main, Ubuntu 9.04 laptop, which has an intel 4965 (iwlwifi driver), the backport drivers made it work perfectly (i have had *no* dropped connections *at all* since). I haven't had time to reboot to the newer kernel to see if that worked.

As for WPA/WPA2: that was my original comment, and i think that's what everybody's problem is: there's no problem with an unencrypted or a WEP AP, but the connection will drop very often with a WPA/WPA2 AP. Then again, i didn't get that behavior at all on another (Dlink-something) AP (i.e., on that AP, upgrading to WPA and not upgrading my drivers still worked fine). I do get that behavior with my WRT54GL AP. The bug seems to triggered with a combination of:
* certain APs, not all
* WPA/WPA2, neither clear nor WEP
* certain Intel cards
* not just the iwlwifi driver

Unfortunately, no one else is coming back to confirm or infirm that information...

This is also what I see.
* Intel card
* WPA/WPA2
* Not all cards have this problem.
* And as well as iwlifi drivers, it happens on bcm/ssb drivers

I'm trying now with an unencrypted connection and it still disconnects, but not as frequently.

Scratch that, it's still frequent.

wiswaud - im using karmic so i have the 2.6.31 kernel...never had any problem back in jaunty

maybe this problem popped out in recent jaunty kernels - in recent kernels, period, in fact. It's probably an upstream problem.

still having the same problem with the final version of karmic... anyways im trying to use wicd and its not working (with and without the backports enabled in the repos) can anyone give me their settings? i it authenticates by the way but doesnt get an Ip.. i tried setting it static but cant really figure out the DNS part.. i also cant compile the wireless drivers for my kernel it gives me error 2

Can you also try setting static IP in NetworkManager/Wicd? Make sure it matches the one you set in the router for your MAC address.

i was able to fix my problem by changing my router's encryption to wpa2 (AES)....im using network manager...so the problem is related to wpa only i guess

I have the same issue with up-to-date karmic, WRT54GL router, and WEP encryption (using WEP passphrase).

I'm now going to enable karmic-backports, and see what happens...

No change after installing the backports modules, unfortunately.

I get the same issue in both jaunty and karmic (up-to-date)
my laptop: acer, iwl3945, router WR541G/542G
And #26 really work for me
Just synaptic linux-backports-modules-karmic then synaptic wicd
Thanks wouterla :)

I have the same problem with karmic, after update from 9.04.
Wireless LAN randomly restarts on my laptop Acer TravelMate.
Using WPA-PSK/TKIP, ath5k.

Nov 2 20:40:57 moon NetworkManager: <info> Wireless now disabled by radio killswitch
Nov 2 20:40:57 moon NetworkManager: <info> (wlan0): device state change: 8 -> 2 (reason 0)
Nov 2 20:40:57 moon NetworkManager: <info> (wlan0): deactivating device (reason: 0).
Nov 2 20:40:57 moon NetworkManager: <info> (wlan0): canceled DHCP transaction, dhcp client pid 3429
Nov 2 20:40:57 moon NetworkManager: <WARN> check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess#012
Nov 2 20:40:57 moon NetworkManager: <info> (wlan0): removing resolv.conf from /sbin/resolvconf
Nov 2 20:40:57 moon wpa_supplicant[670]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Nov 2 20:40:57 moon kernel: [ 4656.214269] wlan0: deauthenticating from 00:1a:92:b0:eb:5b by local choice (reason=3)
Nov 2 20:40:57 moon kernel: [ 4656.214358] wlan0: deauthenticating from 00:1a:92:b0:eb:5b by local choice (reason=3)
Nov 2 20:40:58 moon NetworkManager: <info> (wlan0): taking down device.

Nov 2 20:40:58 moon NetworkManager: <info> Wireless now enabled by radio killswitch
Nov 2 20:40:58 moon NetworkManager: <info> (wlan0): bringing up device.

update #45:
linux-backports-modules-karmic get crash with kernel
then i remove it, everything still be ok :)
so i think the problem belong to NetworkManager, just replace it by Wicd

Same problem here. I was having 'Mac in deep sleep!' message the most times when I booted. So I put the 'noapic' kernel parameter and I get this issue. Also I tried to install the linux-backports-modules-wireless-karmic-generic package and my system became unstable and kernel crashed several times.

I can confirm this same problem with Dell xps-1530, intel 4965agn, and clean install of Karmic. However, I can also confirm the exact same problem in Mandriva free 2010 and in Fedora 12 (just tried it tonight). This definitely seems to be an upstream problem. WICD on Karmic seemed to fix the problem.

BTW, all these tests were on x64 platform.

On my T60 with Intel 3945 I am experiencing the problem with all WPA-TKIP secrured APs. All WPA2-AES APs work fine. I am using fully upgraded Karmic.

On TKIP secured APs I also see the kicking of other users - whenever my machine connects, the outher users are kicked out. After few seconds my machine disconnects and this repeats all the time. WPA2-AES works very well.

So probably there is something bad in TKIP handling code. I don't know how to debug this. It may finally be an wpa-supplicant issue...

same with me,
disconnecting, reconnecting ,

using karmic , with intel wif . and WPA.

dmesg shows same messages as posted earlier.

same notebook connected fine with 9.04

oh 64bit here as well.

also effects ubuntu 10.04 64bit alpha 1

[ 532.832617] wlan0: direct probe to AP 00:08:a1:a4:8b:82 (try 1)
[ 532.835262] wlan0: direct probe responded
[ 532.835269] wlan0: authenticate with AP 00:08:a1:a4:8b:82 (try 1)
[ 532.837075] wlan0: authenticated
[ 532.837112] wlan0: associate with AP 00:08:a1:a4:8b:82 (try 1)
[ 532.839389] wlan0: RX ReassocResp from 00:08:a1:a4:8b:82 (capab=0x411 status=12 aid=1)
[ 532.839396] wlan0: AP denied association (code=12)
[ 532.839423] wlan0: associate with AP 00:08:a1:a4:8b:82 (try 1)
[ 532.841162] wlan0: RX ReassocResp from 00:08:a1:a4:8b:82 (capab=0x411 status=12 aid=1)
[ 532.841168] wlan0: AP denied association (code=12)
[ 532.841187] wlan0: deauthenticating from 00:08:a1:a4:8b:82 by local choice (reason=3)
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 2.6.32-7-generic #10-Ubuntu SMP Sun Dec 6 13:54:12 UTC 2009 x86_64 GNU/Linux

I have an XPS 1530 running 10.04 Alpha2 using intel 4965agn and the problem still persists. This is a really bad bug it effects soo many people.

Had a similar problem with Ubuntu 9.10, Lenovo T60, intel 3945Aabg, iwl3945 driver. It worked with 9.04, I suppose because Network Manager was disabled (and I think this was by default). I know I had tried to enable NM with 9.04 but it didn't work so I just shut it back off. I think it sort of worked with NM sometime prior to 9.04, but I always had to re-enter the WPA key every time I rebooted.

Upgraded to 9.10 and discovered NM was re-enabled and I could not get wireless working (using WPA2-PSK). I was getting this:

Jan 30 19:47:38 davisj-laptop wpa_supplicant[2169]: CTRL-EVENT-SCAN-RESULTS
Jan 30 19:47:38 davisj-laptop wpa_supplicant[2169]: Trying to associate with 00:16:01:91:d2:67 (SSID='JDNET' freq=2412 MHz)
Jan 30 19:47:38 davisj-laptop wpa_supplicant[2169]: Association request to the driver failed
Jan 30 19:47:38 davisj-laptop wpa_supplicant[1263]: CTRL-EVENT-SCAN-RESULTS
Jan 30 19:47:38 davisj-laptop kernel: [ 645.444256] wlan0: authenticate with AP 00:16:01:91:d2:67
Jan 30 19:47:38 davisj-laptop kernel: [ 645.450565] wlan0: authenticated
Jan 30 19:47:38 davisj-laptop kernel: [ 645.450569] wlan0: associate with AP 00:16:01:91:d2:67
Jan 30 19:47:38 davisj-laptop wpa_supplicant[2169]: Associated with 00:16:01:91:d2:67
Jan 30 19:47:38 davisj-laptop wpa_supplicant[1263]: No network configuration found for the current AP
Jan 30 19:47:38 davisj-laptop wpa_supplicant[2169]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jan 30 19:47:38 davisjs-laptop kernel: [ 645.452836] wlan0: RX AssocResp from 00:16:01:91:d2:67 (capab=0x411 status=0 aid=2)
Jan 30 19:47:38 davisj-laptop kernel: [ 645.452840] wlan0: associated
Jan 30 19:47:38 davisj-laptop kernel: [ 645.455624] wlan0: disassociating by local choice (reason=3)
Jan 30 19:47:38 davisj-laptop wpa_supplicant[1263]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jan 30 19:47:38 davisj-laptop wpa_supplicant[1263]: WPA: No SSID info found (msg 1 of 4).

To make a long story short, I installed wicd and life was good. No muss, no fuss, just installed, rebooted, and wireless linked right up. My Lenovo wireless never had anything but problems with NM. To be fair, I never really dug into what might be causing the issue. It is possible that had I gotten into the NM config files I might have gotten it working, but I really didn't have the time or inclination to do so.

Same problems (even worth) for my Thinkpad T60 2007CB5 (Intel 3945abg).

1, freeze a lot while using network-manager (every 2-5 minutes with WIFI on, never with WIFI off)
2, freeze every 10-20 minutes while using WICD1.62 with the default WPA supplier
  2.1 By checking log iw event -t, will reconnect every 60-75 seconds. (deauthenticated (Reason: 3))
  2.2 Before freezing, there are some log as(now frozen, has to type it out):
       [813. 069493] e1000e 0000:02:00.0 irq 20 for MSI/MSI-X
       [813. 125177] e1000e 0000:02:00.0 irq 20 for MSI/MSI-X
       [813. 126030] ADDRCONF(NETDEV_UP): eth0:link is not ready
....
       [813. 757091] ADDRCONF(NETDEV_UP): wlan0:link is not ready

some update:

I disable internal modem of my T60 in bios, now it seems stable, no reconnection anymore

Thats interesting but I don't have an internal modem. The only way I was able to fix this was to install 9.04 and upgrade to 9.10.

Just for the heck of it I used EXT3 and no home drive encryption.

Also before I did the 9.04 upgrade to 9.10.

When using 9.10 from a fresh install. Setting the BSSID seamed to help a lot. I think the issue is the wireless is frequently scanning the wireless and getting an unexpected result from the driver and dropping the connection.

This does not present itself now that I upgraded from 9.04.

Maybe some of the drivers that got blacklisted in 9.10?