Knetwork manager fails at 28% - Kubuntu Dapper

I have installed Kubuntu Dapper on my HP Pavilion ze2308 laptop. I enabled the broadcom wifi by blacklisting the bcm43xx driver and using ndiswrapper with the windows driver instead. The only way i can get it to connect is by issuing

dhclient eth1

in the console.

I have edited the file /etc/network/interfaces and commented out eth0 and eth1, my wired and wireless connections, respectively.. Upon reboot, networkmanager detects both. It works fine for plugging and unplugging my wired connection. It even detects my wireless network properly.. But, when i try to connect, it gets to 28%, stalls, then eventually gives up...

I have read that other people are having similar problems, with all of them happening at 28%. But i have not found a solution yet..

Please advise as to how i can effectively use KnetworkManager.

Thanks,
-myk

I have this problem as well, Kubuntu Dapper on Acer Ferrari 3000, got ndiswrapper working and could see interface etc but Knetwork manager stalls at 28% I've also tried using the included bcm43xx module but to no avail.

I really need network manager cos dealing with WPA_supplicant directly is too much faff for the person I am putting the box together for.

Please can anyone even just point me in the right direction?

Child

Has anyone figured out anything about this problem yet? I have the same exact problem.

I had same problem, but now wireless works fine. I have Asus A6R laptop with Broadcom 4318. Instructions will be found ubuntuforums. Sorry can`t post direct link. I need 3 posts to made link. See my signature

Cheers

-cdrw80-

I'm afraid to say I don't know exactly how I did it but I just got it working.

I think I played around with the open source bc43xx kernel drivers, failed with those and went back to the disappear. I would try playing with switching your wireless router between unencrypted and wpa, I think what happened was that when I switched it back to encrypted and tried to connect, at 28% it then asked me for the new passkey and this seemed to get it past whatever obstacle was holding it back and it worked from then on?!

I think you might need to make sure that your /etc/network/interfaces file only has the local interface in it as knetworkmanager uses a different system for managing what is available.

HTH
Child

I can confirm that this "stalling at 28%" happens. But it happens on my box only when I use the wrong parameters for my WPA connection. Let me explain:

1. I need to manually "connect to other wireless network..."
2. I specify the network name (ESSID)
3. I choose "Use encryption", "WPA personal", "WPA 2". Now the problematic part, choosing the "WPA protocol":
   1. When I choose "Automatic" or "AES-Counter Mode ..." then connecting fails (-> stalling)
   2. When I choose TKIP ("Temporary Key Integrity Protocol") the connection will be established

(Note that "TKIP" corresponds to the WPA protocol settings on my wireless router!)

Maybe this information can help some of you guys!
Peter

Originally Posted by bittner I can confirm that this "stalling at 28%" happens. But it happens on my box only when I use the wrong parameters for my WPA connection. Let me explain: I need to manually "connect to other wireless network..." I specify the network name (ESSID) I choose "Use encryption", "WPA personal", "WPA 2". Now the problematic part, choosing the "WPA protocol": When I choose "Automatic" or "AES-Counter Mode ..." then connecting fails (-> stalling) When I choose TKIP ("Temporary Key Integrity Protocol") the connection will be established (Note that "TKIP" corresponds to the WPA protocol settings on my wireless router!) Maybe this information can help some of you guys! Peter

This solved my problem yesterday but now today it won't work at all. I did do some updates and added a bunch a new programs and wonder if this messed up something?

Hello Everyone,

I'm new on this Forum. I have the same issue with my wireless card. Suse detects it but when I enter the info for the wireless router it would get stuck at 28% of the process.
If you have any solutions, please let us know!
Thanks