Bug 225604

Created attachment 107985 [details]
dmesg

Created attachment 107986 [details]
lspci output

Created attachment 107988 [details]
relevant /var/log/messages output when modprobing ipw3945

Created attachment 107989 [details]
relevant NM log when trying to connect to my wifi network

This is a bit strange, there are no messages from wpa_supplicant in the NM log. Maybe RC1 had some dbus related problems. Does this still happen with 10.2 final?

I dont know. Is there a delta DVD iso available somewhere for x86?

OK. I am on GM now, and pretty much the same behavior occurs. I still have to modprobe -r and modprobe again on the ipw3945 module.
On my other laptop (using madwifi with atheros chipset), I have the exact same config for NM (on GM as well). Works fine.
a ps reveals that wpa_supplicant is running once I input the key.

Here, I input the key, it says, after stage 2 is complete:

Activation (eth1/wireless): disconnected during association, asking for new key.
eth1: link timed out
eth1: link timed out

etc... I do not have any MAC restrictions on, just that 128 WEP key.

Or depending on I dont know what, when I try again, the same message as in comment #4 appears.

I am having the same issue. On boot, if I was succesfully connected to my network (with WPA PSK) then it connects. If not, it doesn't.

If I am connected and I try to reconnect, it keeps asking me for the password but never gets past stage 2 of the connection process.

This works fine under ifup.

The only thing that works is modprobe -r ipw3945; modprobe ipw3945

I have attached my Network Manager and message logs while I did the following:
 - boot (without prev successful connection, and with  no key stored in the keyring manager) (FAILED)
 - login and try to connect (FAILED)
 - click connect to other wireless network (SUCCEEDED)
 - click on the network to reconnect (FAILED)
 - delete key and click connect to other wireless network (FAILED)
 - delete key and click connect to other wireless network (FAILED)
 - reload ipw3945 module with modprobe
 - click connect to other network (SUCCEEDED)

Not in the logs, but reloading ipw3945 and clicking on the network also succeeds.

Also, there is an error from dhcpd about not understanding the lease time - I changed that on my router and it didn't affect anything

Occassionally, I also get these errors in my log:
getafix kernel: CCMP: decrypt failed: STA=00:12:a9:cb:66:40

Created attachment 110010 [details]
NetworkManager log while trying to connect

Created attachment 110011 [details]
messages log while trying to connect

Created attachment 110012 [details]
hwinfo for my wireless car

Created attachment 110013 [details]
hwinfo for my wireless card

(In reply to comment #9)
> Occassionally, I also get these errors in my log:
> getafix kernel: CCMP: decrypt failed: STA=00:12:a9:cb:66:40
> 

This was related to a bug in the ieee80211 stack when used on SMP machines.  I have installed the latest version, and that error has disappeared, but network manager still doesn't work

I have simila behaviour with ipw2200 (which drives my Tecra A2 notebooks wlan):
 - After fresh boot the card operates but 
 - after suspend to disk and resume cycle it does not come up again.
 - Suspend to RAM is no proplem: the network connection is setup
   automatically. 
 - Also deactivating and activating the card (there is a small switch)
   is no problem
This is not a problem of NetworkManager (which seems have matured compared with 10.1) since after rmmod "ipw2200; modprobe ipw2200" NetworkmManager spontaneously connects.


Before upgrading from 10.1 to 10.2 I never had this problem.

> This is not a problem of NetworkManager (which seems have matured compared with
> 10.1) since after rmmod "ipw2200; modprobe ipw2200" NetworkmManager
> spontaneously connects.
> 

but it works without problem with iflpugd.  No reload of the module required.  So it might not be NetworkManager itself, but something in the process it uses that differs from ifplugd.

I actually don't know what NM does different than ifplugd in that case. Tambet?

The reason why this this changed with 10.2 is most probably that on 10.1, ipw2200 was unloaded by default on suspend. This in not the case for 10.2 anymore. To reload the module again, you can add it to /etc/pm/config (variable SUSPEND_MODULES), but it shouldn't be necessary.

Please install the packages from http://primates.ximian.com/~tambet/NetworkManager/ (wpa_supplicant as well) so that we can see exactly why the wpa association fails. The only change from 10.2 is additional wpa_supplicant debug spew in the log file.

I'm having similar issues with my ipw3945 network card. Sometimes it connects fine, other times I spent several reboots, modprobes, using Yast to change the method of bringing the card up manually with ifup, to  ifplugd, to NetworkManager and back to manual before I get a connection. iwlist eth1 scanning always sees my AP (801.11b network with WEP encryption) but when using ifup the dhcp client does not seem to be able to get an IP address. I don't suspend this laptop at all but always shut it down properly but it does not connect reliably.
Having said that when using NetworkManager, it connects usually without any problems to my neighbour's network which is a 801.11g network and not protected at all.

Created attachment 112789 [details]
NetworkManager log of  failed connection attempt

Hope that helps

Luckily it happened again.
I added attachment #112789 [details]: NetworkManager log of a failed connect (I did not
yet install the packages from ~tambet).
The notebook was more then 24 hours suspended and the WLAN router was fresh
booted before resuming the notebook.

Note: after another suspend (to RAM) and resume cycle NetworkManager connected
successfully (neither "rmmod ipw2200; modprobe ipw2200" or "rcnetwork restart"
needed).

Please note that the initial problem stated "upon bootup". I still incur this behavior, be it from fresh boot, or s2ram/s2disk. 

I still can't connect to WEP networks, no matter the way I try to do it, be it NM, traditional method, from the command line... nothing does. 

But it seems connect fine to WPA networks?

Forget me. It works now. I actually had changed laptops in between, and actually had MAC filtering enabled. No wonder it didn't work...

I had the same problems plus some others and I resolved upgrading ipw3945d and the   ipw3945-ucode (http://bughost.org/ipw3945/)

See my bug report #259005 for additional info.

Antenore.

(In reply to comment #25)
> I had the same problems plus some others and I resolved upgrading ipw3945d and
> the   ipw3945-ucode (http://bughost.org/ipw3945/)
> 
> See my bug report #259005 for additional info.
> 
> Antenore.
> 

I have already upgraded to:
Microcode: ipw3945-ucode-1.14.2
Regulatory daemon: ipw3945d-1.7.22

also, I have upgraded to:
 ieee80211-1.2.15

The ieee upgrade helped with stability, but my connection (WPA personal) still goes every now and again, and then it asks me for the password, and won't get past that.

The only way to reconnect is to do a:
modprobe -r ipw3945; modprobe ipw3945

and then reconnect

I have attached new firmware and ipw3945d packages to bug 225604. Anybody with ipw3945 problems, please give these a try. Clinton, how often does this happen? Could you attach /var/log/NetworkManager after it occured again?

(In reply to comment #27)
> I have attached new firmware and ipw3945d packages to bug 225604. Anybody with
> ipw3945 problems, please give these a try. Clinton, how often does this happen?
> Could you attach /var/log/NetworkManager after it occured again?
> 


Joachim, do you mean a different bug number?  I don't see any new packages attached to this one.

Clint

I'm sorry, I mean bug 259005. Was actually a cut-and-past accident.

Created attachment 132500 [details]
syslog and NetworkManager log post upgrade of packages

(In reply to comment #27)
> I have attached new firmware and ipw3945d packages to bug 225604. Anybody with
> ipw3945 problems, please give these a try. Clinton, how often does this happen?
> Could you attach /var/log/NetworkManager after it occured again?
> 

OK - I installed the new ipw3945 packages and rebooted.  The issue is exactly the same as before, in order to reconnect to a network, I need to modprobe -r and then modprobe the driver again.

Full log attached.

Also, I compiled my own ieee80211 driver (version 1.2.15) - before I did this, I still had the above problem, but when my network did connect, it would drop after any heavy use.

i have since tried installing ieee80211 version 1.2.16, but it complains during compilation, and I don't have enough experience to figure out what is wrong with it.

Created attachment 132730 [details]
Spontaneous disconnect

(In reply to comment #27)
> I have attached new firmware and ipw3945d packages to bug 225604. Anybody with
> ipw3945 problems, please give these a try. Clinton, how often does this happen?
> Could you attach /var/log/NetworkManager after it occured again?
> 

This morning, after I woke up, my network had disconnected itself - this attached file is the log og the event.

I have this problem too. I just downloaded and installed the new driver from #259005.

i had the same problems with networkmanager:

- need to connect about 10-15 times to get a finished connection (i guess there is also a problem with hidden ssid. maybe you should install a newer version of wpa_supplicant, because there was a version where a problem with hidden ssid got fixed)
- instable connection especially during transfers with huge amount of data and/or huge number of connections (e.g. torrent)
- also had a problem with the wlan in my university, where i couldn't connect to the open network (i guess it was a problem with dhcp)
- another bug caused by the bugs above refers to #268277: the connection is very instable (e.g. during a skype-call), after that NM isn't able to reconnect to the network und asks for another keyphrase, in case it's wrong. 

somewhere i read, that there is a conflict between NM 0.6.4 and ipw3945 so i tried to install version 0.6.3, but i wasn't able to because of a rpm-conflict. also i updated dhclient.

after getting frustrated too much i switched to wpa_supplicant and i got a fast and VERY stable connection. (wpa_supplicant v. 0.5.8). so the problem MUST be NM and not device-driver or something else.

-----------

today i'll give NM 0.6.3 source a try.

greetings
NH

now i tried 0.6.5:

i think it's "a bit" better but i'll keep testing. for best results use wpa_supplicant.

I am also having this problem with my ipw3945 in a Lenovo X60T:

-sometimes wifi won't come up on boot, sometimes for several reboots
-often wifi will just die when I am not looking, e.g. run a backup overnight, come back in the morning and the network died half way through
-some network environments are much less reliable than others, works great at my house, not so good some other places

Work-around: hit the network kill switch. Wait. Re-enable the network kill switch. Wait. "rcnetwork restart". *Sometimes* this fixes it. Sometimes only reboot fixes it.

Ubuntu Gutsy was showing what I think was the same problem (the "wifi killswitch trick" had to be used and is mentioned in the bug). I believe that an Ubuntu dev went on to fix the issue before release as I don't see this issue in later Gutsy releases which are still use the ipw3945 driver - https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/121566 .

I forgot to say that this bug is occurring for me on a fresh OpenSUSE 10.3 install with a Lenovo Thinkpad T60.

Sitsofe, can you please try iwlwifi instead of ipw3945 (which is no longer maintained)?

Helmut:
It's certainly true that iwlwifi doesn't suffer this problem. The initial release of iwlwifi with openSUSE 10.3 was problematic but later versions have been more reliable. If ipw3945 is deprecated and iwlwifi has all the same functionality then I think this bug should be closed.

(clear needinfo)

Closing as WONTFIX.

Please switch to iwlwifi and open new bugs for it if you have problems with it. Thanks.