NetworkManager hangs after first login (bcm43xx)

Bug #110459 reported by Sb
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-network (Ubuntu)
Invalid
Undecided
Unassigned
knetworkmanager (Ubuntu)
Invalid
Undecided
Unassigned
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hi,

I have Kubuntu 7.04 on a Dell Inspiron B130 (1300) laptop with a bcm43xx WiFi card. It works well enough with Ndiswrapper and also with the native bcm43xx driver, but KNetworkManager is giving me trouble.

Every time I boot up my system, KNetworkManager tries to connect, but then it hangs at "28% Configuring Device". Sometimes it gets to the IP configuration stage if I am using the native bcm43xx driver. But no matter what, it won't connect the first time. I have to power-cycle my WiFi radio to get it to connect. In subsequent logins, it is already connected when I login, it's only the first connection after bootup that is broken.

I tried booting up my system and logging in to failsafe, and I pinged a website and found that my connection is loading at boot, as I want it to. But I need KnetworkManager to work for the signal strength graph, etc. I also tried the gnome variant nm-applet and it behaves exactly the same.

Thanks for your help!

Revision history for this message
Sb (sb56637) wrote :

sudo lspci -vvnn (attached)

Revision history for this message
Sb (sb56637) wrote :

I just tried Kubuntu 6.10, and Knetworkmanager works perfectly. This is definitely a regression.

Changed in knetworkmanager:
status: Unconfirmed → Confirmed
Changed in gnome-network:
status: Unconfirmed → Confirmed
Revision history for this message
patrick (styx493) wrote :

same story here.

other scenario: after wakeing up from suspend2ram, knm alsways tries to connect to eth0 instead of the wlan device. you can either wait until it fails, or select proper device manually, thus hanging at 28%
sometimes unloading and reloading of ndsiwrapper AND knm helps, often it doesn't.

some people mention a connection to the chars used as a wpa-secret, whereas extra signs like &!/" may cause problems.

Revision history for this message
Alexander Sack (asac) wrote :

network-manager and the broadcom drivers have improved in gutsy. So I assume this is fixed. Please reopen if you still see this bug in gutsy (ubunt 7.10).

Thanks,
 - Alexander

Changed in network-manager:
status: Confirmed → Fix Released
Revision history for this message
Alexander Sack (asac) wrote :

definitly not a knetworkmanager bug.

Changed in knetworkmanager:
status: Confirmed → Invalid
Revision history for this message
Alexander Sack (asac) wrote :

same for gnome-network

Changed in gnome-network:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.