Comment 2 for bug 128498

The bcm43xx module included in ubuntu's -generic kernel (with firmware cut of course)

I've tested it with ndiswrapper as well, which does work as expected. Both bcm43xx and ndiswrapper seem to configure fine from the terminal.

I have also tested it with a 64bit build of ubuntu installed. No noticeable change with the bcm43xx module in use, save perhaps a slightly higher probability than any given time I attempt to connect it fails (though I've never had much luck with wireless on 64 bit). Ndiswrapper also works fine on a 64 bit install, which surprised me, as I had never successfully used ndiswrapper and network manager on a 64 bit install.

All and all it's a relatively minor annoyance to me, but if someone with the same problem didn't know how to use a terminal it could be a show stopper, so to speak. I've yet to get a chance to examine a friend's connection but he says he is having what essentially sounds to be same problem, but on his Feisty install (and with kubuntu's knetworkmanager) and with a broadcom 4300 series card.

At the moment I am testing kubuntu in a 64 bit install and ndiswrapper at least works as expected. I haven't tested the bcm43xx driver with this kernel yet and knetworkmanager has updated once but last I checked it too had a problem connecting wirelessly with the manager unless a wired connection was present until dhcp finished.

If I figure anything else out I'll post here. I do know other people with bcm4318 cards and I'd say about half of them work perfectly through network manager.