WPA doesn't work
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ndiswrapper (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
I'm using 32bit Ubuntu (same on Ubuntu, Xubuntu and Kubuntu so nothing to do with network-
If you have a RT2500 or BCM4318 network card you should be able to replicate this... but I have a feeling that it might be possible to replicate on a lot more as the drivers work!
On BCM4318:
bcm43xx kernel module doesn't support wpa - fair enough... use Ndiswrapper...
apt-get install ndiswrapper-
ndiswrapper -i bcmwl5.inf
ndiswrapper -m
ndiswrapper -l
output reports card driver ok and hardware present
rmmod bcm43xx (remove module)
edit /etc/modprobe.
edit /etc/modules add ndiswrapper
modprobe ndiswrapper
use network-manager and try to connect - failed! network-manager recognises hardware and ability to use wpa (asks for wpa psk) but doesn't connect even finds the network
as far as i can tell using dmesg, running network-manager without a daemon and so on there are not obvious bugs!
All of the above works in Dapper!
Exacly the same for RT2500! (my other laptop)
My desktop has bcm4318 card and that doesn't work either!
The forums and everywhere says the issues are with the packages provided by Ubuntu - they don't work!
Ndiswrapper version apparently has problems and wpa_supplicant turns itself off (read UbuntuForums)
This is a major problem - how many laptops can only use wireless with Ndiswrapper + WPA!
I got one laptop to work using a script that updated Ndiswrapper and modified config files I don't understand - now if that's Linux security I'm going back to Windows!
Wireless should work - The above should work and ndisgtk should know if the hardware is present if ndiswrapper reports it is!
Please, please, please sort this out - the ndiswrapper and possibly wpa_supplicant, network-manager packages need serious bug-fixing and/or upgrading!
I can edit /etc/interfaces and have done so on my desktop - that didn't work in Feisty but did in Dapper
bcm4318 is a very, very, very common chipset and so is the rt2500 I have 7 network cards in my house I didn't buy the same brand and between them I only have 1 that isn't bcm4318 or rt2500!
This bug should be really easy to replicate!
I followed a previous thread that stated just goto the rt2500 entry in wifidocs! I found that site is useless... I don't want to have to edit the interfaces file everytime I move my laptop between 2 work places, university and home!
The reason PCLOS is beating Ubuntu in the distrowatch count is because of this! There is nothing else going for PCLOS except even the livecd works with ndiswrapper and you can connect to the network!
I don't believe that this issue is resolved in Gutsy from forum posts but I might check later and update this to let you know for sure!
| Marius Vasilescu (vegancorr) wrote | #1 |
| Marius Vasilescu (vegancorr) wrote | #2 |
| Przemek K. (azrael) wrote | #3 |
| Changed in ndiswrapper (Ubuntu): | |
| status: | Confirmed → Incomplete |
| Marius Vasilescu (vegancorr) wrote | #4 |
| Przemek K. (azrael) wrote | #5 |
| Changed in ndiswrapper (Ubuntu): | |
| status: | Incomplete → Invalid |
I can confirm this bug and reproduce it with Feisty up to date. I have "Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)" and using ndiswrapper. It's interesting that the wireless works as long as it has no security. If I try to connect with WPA / WPA2 / WEP it fails.
I installed Feisty just after it was released and the wireless network worked just fine. I don't remember if back then I installed ndiswrapper via automatix or synaptec (maybe the versions are different). I can't check with automatix because the site is still down. A few days ago I decided to reinstall ubuntu because I had stability problems with the X server and thought that it would be better just to reinstall everything. The X server stability didn't dissapear, but I couldn't make the wireless work again, although my system is up to date!
I also tried to use Wicd, but it seems that it's not a Network Manager issue.
I attached the daemon log, maybe it helps. I will boot with an older kernel to see what it happens, because I didn't check that.