Comment 23 for bug 121439

I'm also having this problem, 2.6.22-7-generic, network-manager_0.6.5-0ubuntu4, using ipw3945 on a thinkpad T60. On boot the startup scripts get a connection to any open AP properly, ifup and ifdown work fine, device names are normal (eth0 copper, eth1 wifi). After using KNetworkManager things go "awry." There is play-by-play in the attached logfile.

I have always had occasional random troubles with ipw3945 flying south on Feisty (I chalk it up to that aggravating reg daemon, will be happy when iwlwifi makes it in), but removing and re-modprobing the module has always fixed it. This did not help in this case. RF kill does not seem to affect it.

Also of note, the first time this happened, the link would be fine on boot, as above, but after NM frobbed it, ip link would show it being NO-CARRIER. I couldn't reproduce this last symptom for this report.

HTH,
Kyle