Can't connect to my Kubuntu laptop to my WPA enabled network.

[TFrog]

I'm running a Compaq Presario R4125US laptop with a Broadcom BCM4318 chipset. The repository debs for ndiswrapper-utils and ndiswrapper don't work at all. I searched the net for others with similar issues. Others are having this issue as well. seems those packages are broken. I did however, download and compile the ndiswrapper version 1.23 from source code. From there my system recognized my chipset and was able to see it in the network settings in the system settings. Afterward, I downloaded and installed Knetworkmanager like I did with Dapper. I attempted to connect to my home network and was not prompted to enter a password for KDE Wallet and Knetworkmanager didn't seem to keep my passkey. Knetworkmanager hung at 28% while trying to configure my network access. The laptop works fine wired but this is the ONLY issue I got with the new Edgy. My desktop works fabulous and I'd love to personally thank the person who put in the extra effort into doing the mouse drivers. My wireless mouse on my desktop no longer freezes to the point of hard reset. CONGRATS. Otherwise a fine effort on all your parts.

[Sarah Kowalik (hobbsee-deactivatedaccount)]

odd. can you give us the output of:

apt-cache policy knetworkmanager

if it doesnt show:

knetworkmanager:
  Installed: 0.1-0ubuntu1
  Candidate: 0.1-0ubuntu1

please update, and try again.

[TFrog (stgparris)]

Dear Ms., Mz., Miss, or Mrs. Hobbs,

The current version of knetworkmanager I'm running is 0.1-0ubuntu1. Current
version of knworkconf is 3.5.4-0ubuntu3. I'm currently running Kubuntu Edgy
Eft 6.10 with all the updates. The repository version of ndiswrapper-utils
didn't work when atempting to load the Windows drivers. ndiswrapper -i
reported no ndiswrapper from three different drivers. After that I went to
the ndiswrapper project page, downloaded 1.23 source code tarball from
SourceForge and compiled. From that point on my Broadcom BCM4318 was
recognized by Kubuntu as being Enabled in System Settings/Network
Connections. It was at that point I installed the Edgy repository
knetworkmanager. It shows the networks in the neighborhood (as I live in an
apartment complex with a lot of wireless networks). However, when trying to
connect to the one in my home which has WPA security enabled, it brings up
the Connect to Wireless Network window for me to fill in the WPA Personal
password. After typing in my password, it goes to Configuring Device and
sticks at 28%. Never do I see KDE Wallet to save the passkey or ask me for
a login to let knetworkmanager use the wallet for the passkey.

When using Dapper Drake, the first thing it would do no matter the settings
in Security, it would pop up the wallet login before providing the password
to knetworkmanager. For some reason it fails to do this in Edgy Eft. Also,
this was a clean install from a freshly burned disc image bit torrented down
to my desktop with ktorrent which is also running Edgy Eft Beta at the
moment (installed from the same disc image). Both installs were done late
last night and early this morning. Should you know who wrote the Xorg mouse
driver for Eft, please thank him/her for me. This is the first time I've
had my Microsoft wireless mouse work without a total system hang every 30
minutes. Matter of fact, I have yet to have it hang the system.

I'm a very satisfied Ubuntu/Kubuntu user. Almost six months ago I switched
from Fedora Core. I've not looked back yet. If you are able to provide me
with more help with this issue from the above prescribed symtoms I greatly
appreciate it. By the way, I may be new to Ubuntu/Kubuntu, but I'm a
CompTIA A+ certified tech. I am very good at spotting troubles and
hopefully I provided you with a thorough enough accounting of the issue to
help you resolve this. I've seen another post on the Ubuntu forums saying
ndiswrapper was currently broken, but I didn't go out immediately and
compile the SourceForge project code till after trying the packages to
verify what was heard. I however need the ndiswrapper for the WPA security
till either the Broadcom project completes its work or Linux in general
adopts the Dreamscape driver model that I've been hearing about and
following with great interest.

Sincerely,
Terry L. Parris (IRC nick TFrog)

>From: Sarah Hobbs <email address hidden>
>Reply-To: Bug 63176 <email address hidden>
>To: <email address hidden>
>Subject: [Bug 63176] Re: Can't connect to my Kubuntu laptop to my WPA
>enablednetwork.
>Date: Sat, 30 Sep 2006 14:17:06 -0000
>
>odd. can you give u...

[Lothar (lothar-tradescape)]

I run Dapper and I experience the same behaviour. Sometimes it works though. It may be a flaw in ndiswrapper. Unfortunately the native BCM drivers don't work with more that 1G of ram, so I must use ndiswrapper. If you have less ram, try the native bcm driver. It might work for you. What annoys me more is that I have to always enter my WPA passkey and ssid, as I work with a hidden SSIS. Iwish Knetworkmanager would remember my network and allow me just to selekt it from the menu. But after every restart I have to enter it manually :-(

[Anthony Mercatante (tonio)]

This is supposed to be resolved with version 0.1
The issue can be bad integration to your wallet, so if it doesn't work even after update, can you try to remove ~/.kde/share/config/kwalletrc and ~/.kde/share/apps/kwallet, then log out/in to kde, and restart knetworkmanager ?

[Lothar (lothar-tradescape)]

I removed ~/.kde/share/config/kwalletrc and ~/.kde/share/apps/kwallet but to no avail. Evwerytime I reboot I don't see my hidden network in the menu and I always have to use "Connect to other wireless network..." and fill out the WPA passkey and the hidden SSID. And the about of knetwormanager sais it's 0.1 prerelease. I would also love if a developer could look into https://launchpad.net/bugs/50432, as it sits there since a cpuple of months without getting assigned. And I guess if it does not get assigned there's no chance to get it fixed for Edgy(+1)

[TFrog (stgparris)]

Lothar,

Thanks for the reply but the native Broadcom driver is not an option for me.
  I live in an apartment complex with as many as 5 or 6 separate networks in
the area at once. WEP encryption is just pure trash compared to the
security of WPA. I could probably walk around the apartment complex right
now if I had Dapper on here again with Airsnort and get into even the ones
around that are so called secured. However, thanks for the info. I can get
ndiswrapper working fine under Dapper and am moving the laptop back to it in
about 20 minutes. I had to do something to prove to Ubuntu staff I wasn't
lying about ndiswrapper being toasted in Edgy Eft. I've now got screenshots
to prove it. LOL.

Sincerely,
TFrog

>From: Lothar <email address hidden>
>Reply-To: Bug 63176 <email address hidden>
>To: <email address hidden>
>Subject: [Bug 63176] Re: Can't connect to my Kubuntu laptop to my WPA
>enablednetwork.
>Date: Mon, 02 Oct 2006 22:35:24 -0000
>
>I run Dapper and I experience the same behaviour. Sometimes it works
>though. It may be a flaw in ndiswrapper. Unfortunately the native BCM
>drivers don't work with more that 1G of ram, so I must use ndiswrapper.
>If you have less ram, try the native bcm driver. It might work for you.
>What annoys me more is that I have to always enter my WPA passkey and
>ssid, as I work with a hidden SSIS. Iwish Knetworkmanager would remember
>my network and allow me just to selekt it from the menu. But after every
>restart I have to enter it manually :-(
>
>--
>Can't connect to my Kubuntu laptop to my WPA enabled network.
>https://launchpad.net/bugs/63176

_________________________________________________________________
Express yourself - download free Windows Live Messenger themes!
http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://imagine-msn.com/themes/vibe/default.aspx?locale=en-us&source=hmtagline

[Anthony Mercatante (tonio)]

This is not

[Anthony Mercatante (tonio)]

This is not a knetworkmanager but a ndiswrapper one.
The solution for your problem consist in removing ndiswrapper and make usage of the native bcm43xx driver instead.
As the firmwares are not included, you have to install bcm43xx-fwcutter package and use this to extract them from the windows driver and install them in /lib/firmwares.
That'll work like a charm.

[Launchpad Janitor (janitor)]

[Expired for ndiswrapper (Ubuntu) because there has been no activity for 60 days.]