[b43] Intrepid upgrade/can't connect to wpa network

Bug #292368 reported by Keith Moseley
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Hi, I've just upgraded from Hardy to Intrepid from the official release on a laptop with a Broadcom 4311 wireless card. With Hardy, it worked fine using the b43-fwcutter driver on a WPA-PSK network, but when the STA driver came out, I just had endless prompts for the password and a spinning circle. I reverted to the old driver and assumed when Intrepid came out it would be fixed.

Move forward to present: yesterday I upgraded using 'update-manager -d' and had a working wireless connection still using the b43 driver for a couple hours while I was trying to figure out a separate issue with logging onto my Gnome desktop. I then decided to try the STA driver to see if it was working, but I got the same behaviour as before, so I again reverted to the old driver, only this time it did the same password prompt/spinning circle loop with it as well. I tried wicd and connecting manually, but neither worked. A wired connection works fine, however, as does an unencrypted wireless one.

Here's where it gets weird. I downloaded and burned the livecd to see if it was because of some corrupted config file from the upgrade. I booted from it and set the b43 driver up and it connected to my wireless network first time. I then spent the next few hours looking for similar problems on the forums to see if I could figure out what had gone wrong before doing a fresh install, as I didn't want the hassle of having to download the extra programs and redoing all my settings, but after trying a bunch of different things, I still hadn't solved it. So I put the livecd back in planning on doing an install, but wanted to quickly check something online before I did so. Set up the b43 driver again, watched the spinning circle and several password prompts later figured out that the cd that worked a few hours before now doesn't work.

Maybe it's my card, but I don't think so. The reason being that I've since done a fresh install anyways on the offchance that it would work (it didn't, but it fixed a couple other things so oh well) but discovered by trial and error that setting my router to WPA2 works for some reason. (Also the new STA driver works really well compared to the old one. I've got about ten different networks showing up on my scan where before it struggled to pick up two and my home router was less than 50% unless I was sitting next to it. But I digress...)

I'm attaching my syslog from today. The successful connection at the end is just after I changed to WPA2. All the unsuccessful ones before then were with WPA. Also, I've added the ppa network manager archive to my repositories, so I've got the most recent NM packages.

Revision history for this message
Keith Moseley (xantham1) wrote :
Revision history for this message
Keith Moseley (xantham1) wrote :

Oh yeah, I forgot to mention I'm running the 64 bit version.

Regards.

Revision history for this message
geb (georgeeb) wrote :

i am running 32 bit intrepid, same problem...recurring password screen for a wpa enterprise network. I think something is wrong with my card(bcm4311, STA driver). Card is detected fine by lspci but iwconfig produces strange results...

george@toast:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11 Nickname:""
          Access Point: Not-Associated

pan0 no wireless extensions.

Revision history for this message
Keith Moseley (xantham1) wrote :

I forgot about iwconfig. I've just looked at it on my working wpa2 system. Here's the output:

lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11 Nickname:""
          Access Point: Not-Associated
          Link Quality:5 Signal level:218 Noise level:163
          Rx invalid nwid:0 invalid crypt:231 invalid misc:0

pan0 no wireless extensions.

Curiouser and curiouser. There's another thread about wpa enterprise here:

I forgot about iwconfig. I've just looked at it on my working wpa2 system. Here's the output:

lo no wireless extensions.

eth0 no wireless extensions.

eth1 IEEE 802.11 Nickname:""
          Access Point: Not-Associated
          Link Quality:5 Signal level:218 Noise level:163
          Rx invalid nwid:0 invalid crypt:231 invalid misc:0

pan0 no wireless extensions.

Curiouser and curiouser, as obviously I am associated. Maybe Network Manager preempts iwconfig in some way? There's another thread about wpa enterprise here: Bug #272185

My network is wpa personal. I don't know if that means mine and your problems are different. Does resetting your security to WPA2 work (assuming you have access to settings)?

Regards.

Revision history for this message
geb (georgeeb) wrote :

Could you clarify what you mean by "resetting your security to wpa2 work (assuming you have access to settings)?"
Thank you

Revision history for this message
Keith Moseley (xantham1) wrote :

Sorry. If you change the settings on your router to wpa2 from wpa, does network manager then connect to the internet? That is what happened to me when I changed mine. Mine also connects to an unprotected network.

Regards.

Revision history for this message
geb (georgeeb) wrote :

Sorry I cannot do this. My connection problems are for my schools network, and thus no access to settings. Many other people in the forums are having this same problem, and while I have not tried to connect to an unprotected network, many other people can. Encrypted networks appear to be the problem.

Here are two topics for your references, no real solutions have been found yet(as far as I know):
http://ubuntuforums.org/showthread.php?t=963379
http://ubuntuforums.org/showthread.php?t=964837

nikolaz (nikolazius)
Changed in linux:
status: New → Confirmed
Revision history for this message
jeremy-list (quick-dudley) wrote :

I have the same problem trying to login to a WPA Personal encrypted network. Like the original reporter of this bug, I could connect fine under hardy.
Here's what my windows machine says about the network: (it's using an identical wireless card)
Network-Authentication: WPA-PSK
Data Encryption: TKIP

In Intrepid, I am getting the same response regardless of whether I use linux atheros driver or ndiswrapper, so this is probably not a driver problem. Unfortunately I don't have a copy of Hardy anymore and I'm not sure which package to downgrade, or even how to convince dpkg to downgrade a package.

Revision history for this message
jeremy-list (quick-dudley) wrote :

Here's the output from wpa_supplicant.

Revision history for this message
bquenin (bquenin) wrote :

Hi guys,

  I had the exact same problem for several weeks... Reading your post about WPA2 working but not WPA, I started to tweak my router WIFI setup (WRT54GS with tomato firmware). I tried several configuration with WPA2/WPA/WEP, and only WEP was working. Then I switch back to WPA (my initial setup) and I just changed the channel from 13 to 1 (I was using channel 13 to be alone on my channel) and boom, it worked ...
  So, it sounds like a workaround, but if you have the hand on the wifi AP, try switching to another channel, it worked for me so maybe it'll work for you ...
  Another thing, I think there's a bug somewhere in Ubuntu since I have a dual boot with Windows/Ubuntu, and under Windows everything works fine (even with the channel #13) and it's obviously the same hardware stuff ...

Please give me feedback if changing the channel worked for you.

Thanks.

Revision history for this message
jeremy-list (quick-dudley) wrote :

Well this bug is marked as a duplicate. The original bug actually gives a solution and tells you where to get a "fixed" version of network manager. Quotation marks there because it's no different from the buggy one in terms of connecting to my flatmate's AP. I solved this problem by completely uninstalling network-manager and installing wicd instead.

Revision history for this message
Fabián Rodríguez (magicfab) wrote :

@jeremy-list: care to marke the appropriate duplicate or giving our it's # ?

Revision history for this message
shadowcreeper (shadowcreeper) wrote :

Similar problem here using latest intrepid packages.

Success:
Can connect to unencrypted networks.
Can connect to my work's WPA network (not sure if WPA or WPA2).

Failure:
Cannot connect to my personal WEP 128bit box.

Or rather it connects but after a little while disconnects and fails to reconnect with an endless password prompt. How long the "little while" is depends on the traffic (the more traffic, the shorter the time between connect and utter failure). After failure, the only thing that makes it work again (since at this point it cannot even connect to an unsecured system) is to rmmod the drivers (b43) and then modprobe them.

I do not consider making changes to the AP to be a valid solution (although I would like to move it over to WPA for security reasons, my NintendoDS would then not be able to connect).

Revision history for this message
shadowcreeper (shadowcreeper) wrote :

Update from my previous post:

Now works flawlessly with my WEP box. I am using the b43 driver with firmware cut from the R202477.EXE download (from Dell's support site) in the DRIVER_US/bcmwl5.inf file.

Not sure what file I was using before. But that is the file I used this time (since I got a new larger hard drive and re-installed Ubuntu and re-did the fwcutter stuff).

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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