Complete system freeze when trying to connect to WPA2 network

Bug #305907 reported by thegizmoguy
22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-restricted-modules (Ubuntu)
Fix Released
Medium
Andy Whitcroft

Bug Description

(Sorry I'm a noob with Ubuntu)

Ok so I'm trying to connect to my university network which uses WPA2 PEAP and TKIP (this is done easily in Windows XP). Every time I try and connect to it on my broadcom card I get the prompt for username and password, hit OK, and then the entire system freezes requiring a hard reboot. I can connect to the unsecured wifi network fine.

-Ubuntu 8.10
-Pavilion dv6646us
-Broadcom bcm4328? wifi card (on the drivers that ubuntu defaults to)

Others at my school have gotten it to work outlined here: http://forum.oscr.arizona.edu/showthread.php?t=2917

I've tried the wpa_supplicant.conf suggestion in post number 12 but that didn't help (no .conf file even existed in /etc/ until i created it.

description: updated
Revision history for this message
Miloš Mandarić (mandzo18) wrote :

sudo lspci -nnvv > lspci_nnvv.log
and attach that file here

Revision history for this message
thegizmoguy (thegizmoguy) wrote :

I'll get around to it as soon as possible. In the process of fixing another bug i reported yesterday I modified 1 config line and now Ubuntu won't even boot at all.....so I'm going to try out Fedora before I reinstall Ubuntu and try again.

Revision history for this message
thegizmoguy (thegizmoguy) wrote :

Where did that command put the log file? Anyways I cd to Desktop to get it:

description: updated
Revision history for this message
madman (sandro-moscati) wrote :

Hello,

I have exact the same problem, when trying to connect to my wpa2 entreprise (peap) network, everytime my system freezes and the only solution is hard reset (capslock/scrollock blinks). I didn't check other access points. The same machine can connect using a zd1211 wnic.
System: Packard bell notebook igo 2000 with Ubuntu 8.10
Wireless network interface: Cardbus Usrobotics 5412 NDX (in fact it is a broadcom bcm4321)(802.11b/g/n)
As requested above for the other user I also send you the result of lspci -nnvv
I had a quick look at the lspci and whats strange (I think) is the "kernel modules : wl,ssb", but when I do rmmod ssb I get "ERROR: module ssb doesn't exist in /proc/modules.
Can you please advise to get this working

Thanks

Revision history for this message
thegizmoguy (thegizmoguy) wrote :

I've installed Arch Linux on my computer and have a working native-broadcom driver so when I get back to my school tomorrow, I'll test out the wpa2 network again. Hopefully the logs from 2 OSes should provide enough comparison to determine the problem.

Revision history for this message
thegizmoguy (thegizmoguy) wrote :

Oh and I forgot to mention: clarification, my card is a 4321 broadcom as well...b/g/n...not a 4328 as I mentioned originally.

Revision history for this message
thegizmoguy (thegizmoguy) wrote :

Yes, this bug exists in Arch Linux as well meaning its a driver bug or somewhere else upstream.

Revision history for this message
madman (sandro-moscati) wrote :

Okay, thanks for you input.
This weekend I'm gonna try to disable native-broadcom driver and use the ndiswrapper.
Greetings

Revision history for this message
madman (sandro-moscati) wrote :

Hello,

I tried to use the broadcom drivers from the broadcom website and I disabled to "restricted ubuntu drivers", but the result is the same.
What I also found out, using a wrong password gets logged on my radius server and I get another shot to enter the credentials, the pc hangs at the same time that the radius successfully authenticiate the ubuntu pc/user.
Damn, I realy would like to use my broadcom together with ubuntu and WPA2 enterprise.
I will keep you updated if I found something else.

Revision history for this message
kiara (kiara999) wrote :

Hello,
I have the same problem (hardware Broadcom BCM4312) in establishing a connection with the wpa2-enterprise network of my university. While trying to connect the whole system breaks down and I must do an hard reset.
The network-administratiors said that the authentification is successfull but I am not requesting for an IP-adress (perhaps does it help).
greetings

Revision history for this message
Michael Brown (michaelbrown2009) wrote :

Attached is the requested file. I have the same issue. My Ubuntu freezes with WPA2 Enterprise networks.

I have a Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller

Revision history for this message
Iain Buclaw (iainb) wrote :

Three days ago, it appears that a patch was supplied on the main Broadcom site.
http://www.broadcom.com/support/802.11/linux_sta.php

I recommend that this gets pushed into the upstream in time for the Jaunty release.

Regards
Iain

Revision history for this message
Michael Brown (michaelbrown2009) wrote :

Iain Buclaw, I am unfamiliar how to use that patch. Do you have any suggestions?

Revision history for this message
SeungCheol Han (sfeone) wrote :

Use the latest Broadcom driver at the site: http://www.broadcom.com/support/802.11/linux_sta.php
and its patch. At the 2393th row, change
count = pmkcandlist->npmkid_cand;
to
count = ntoh32(pmkcandlist->npmkid_cand);
and then rebuild it to get the new wl.ko module.

Follow the file Readme.txt and all done!!

I am also connecting the setting of WPA & WPA2 Enterprise, Protected EAP (PEAP), MSCHAPv2 with BCM4328 chip.
No CA Certificate was chosen. Provide your login information.

All Done!! I am free of Ndiswrapper finally.

Revision history for this message
thegizmoguy (thegizmoguy) wrote :

Alternately you can wait for the repos to be update with the new driver...been waiting 3 months now whats a bit longer heh? I'm no longer with Ubuntu, but the Arch Linux package has already been updated (http://aur.archlinux.org/packages.php?ID=19514) and I'll test it out over there to see if I can finally use my university's secure wireless network instead of the unsecure one.

Revision history for this message
Michael Brown (michaelbrown2009) wrote :

Will this be fixed in the 9.04 final release?

Revision history for this message
Andy Whitcroft (apw) wrote :

Had a quick look at the driver in LRM, and this seems to have the code mentioned in comment #14 (unpatched) so there is potential that just applying that fragment would be sufficient to fix this use case.

Revision history for this message
Andy Whitcroft (apw) wrote :

Actually as of March the 23rd linux-restricted-modules was updated to contain the driver specified, ie 5.10.79.10 with the patch applied. This is being done as part of fixes for crashes in the WL driver. This is being done as part of bug #292450. This will release after the beta freeze.

Changed in linux-restricted-modules:
assignee: nobody → apw
status: New → Fix Committed
importance: Undecided → Medium
Revision history for this message
Michael Brown (michaelbrown2009) wrote :

this fix works great. it is working now!

Przemek K. (azrael)
Changed in linux-restricted-modules (Ubuntu):
status: Fix Committed → Fix Released
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.