driver cannot associate, why?

Asked by Paulo Matos on 2012-07-11

Following bug 994255, in precise I installed mainline kernel 3.4.0-030400rc6-generic followed by the deb in post 2 of referred bug which correctly installed wl. However, as I restart the pc it doesn't connect to the router.

syslog has:
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Activation (eth2) starting connection 'MatosSorge'
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> (eth2): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled...
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) started...
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) scheduled...
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Activation (eth2) Stage 1 of 5 (Device Prepare) complete.
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) starting...
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> (eth2): device state change: prepare -> config (reason 'none') [40 50 0]
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Activation (eth2/wireless): connection 'MatosSorge' has security, and secrets exist. No new secrets needed.
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Config: added 'ssid' value 'MatosSorge'
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Config: added 'scan_ssid' value '1'
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Config: added 'auth_alg' value 'OPEN'
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Config: added 'psk' value '<omitted>'
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Activation (eth2) Stage 2 of 5 (Device Configure) complete.
Jul 11 22:26:11 jupiter NetworkManager[924]: <info> Config: set interface ap_scan to 1
Jul 11 22:26:12 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: disconnected -> scanning
Jul 11 22:26:13 jupiter wpa_supplicant[1024]: Trying to associate with f4:55:9c:63:2e:51 (SSID='MatosSorge' freq=2462 MHz)
Jul 11 22:26:14 jupiter wpa_supplicant[1024]: Association request to the driver failed
Jul 11 22:26:14 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: scanning -> associating
Jul 11 22:26:16 jupiter wpa_supplicant[1024]: Associated with f4:55:9c:63:2e:51
Jul 11 22:26:16 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: associating -> associated
Jul 11 22:26:16 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: associated -> 4-way handshake
Jul 11 22:26:24 jupiter wpa_supplicant[1024]: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jul 11 22:26:24 jupiter wpa_supplicant[1024]: CTRL-EVENT-DISCONNECTED bssid=f4:55:9c:63:2e:51 reason=0
Jul 11 22:26:24 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: 4-way handshake -> disconnected
Jul 11 22:26:24 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: disconnected -> scanning
Jul 11 22:26:26 jupiter wpa_supplicant[1024]: Authentication with 00:00:00:00:00:00 timed out.
Jul 11 22:26:26 jupiter wpa_supplicant[1024]: Trying to associate with f4:55:9c:63:2e:51 (SSID='MatosSorge' freq=2462 MHz)
Jul 11 22:26:26 jupiter wpa_supplicant[1024]: Association request to the driver failed
Jul 11 22:26:26 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: scanning -> associating
Jul 11 22:26:28 jupiter wpa_supplicant[1024]: Associated with f4:55:9c:63:2e:51
Jul 11 22:26:28 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: associating -> associated
Jul 11 22:26:28 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: associated -> 4-way handshake
Jul 11 22:26:36 jupiter wpa_supplicant[1024]: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
Jul 11 22:26:36 jupiter wpa_supplicant[1024]: CTRL-EVENT-DISCONNECTED bssid=f4:55:9c:63:2e:51 reason=0
Jul 11 22:26:36 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: 4-way handshake -> disconnected
Jul 11 22:26:37 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: disconnected -> scanning
Jul 11 22:26:38 jupiter wpa_supplicant[1024]: Authentication with 00:00:00:00:00:00 timed out.
Jul 11 22:26:39 jupiter wpa_supplicant[1024]: Trying to associate with f4:55:9c:63:2e:51 (SSID='MatosSorge' freq=2462 MHz)
Jul 11 22:26:39 jupiter wpa_supplicant[1024]: Association request to the driver failed
Jul 11 22:26:39 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: scanning -> associating
Jul 11 22:26:41 jupiter wpa_supplicant[1024]: Associated with f4:55:9c:63:2e:51
Jul 11 22:26:41 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: associating -> associated
Jul 11 22:26:41 jupiter NetworkManager[924]: <info> (eth2): supplicant interface state: associated -> 4-way handshake
Jul 11 22:26:49 jupiter wpa_supplicant[1024]: WPA: 4-Way Handshake failed - pre-shared key may be incorrect

I can't really understand the problem. The WPA key is correct, but it still doesn't connect. lsmod shows:
wl 2573568 16892616544235766756 [permanent]

I would try to remove and install the driver again but doing:
pmatos@jupiter:~$ sudo rmmod wl
ERROR: Module wl is in use by [permanent]

Any idea of might be wrong or how I can obtain more information to get to the bottom of this issue?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu bcmwl Edit question
Assignee:
No assignee Edit question
Solved by:
Paulo Matos
Solved:
2012-07-30
Last query:
2012-07-30
Last reply:
2012-07-27
Paulo Matos (pmatos) said : #1

I just found:
$ cat /etc/modprobe.d/blacklist-bcm43.conf
# Warning: This file is autogenerated by bcmwl. All changes to this file will be lost.
blacklist b43
blacklist b43legacy
blacklist ssb
blacklist bcm43xx
blacklist brcm80211
blacklist brcmsmac
blacklist bcma

I wonder if it has something to do with it.

Kernel 3.4 is not suitable for Precise. Does the 3.2 kernel work. I suggest you contact the kernel packager if you used a deb file.

Paulo Matos (pmatos) said : #3

Kernel 3.2 doesn't work well with my Intel Graphics HD 4000 (Ivy Bridge) causing random hangs. I updated to 3.4 which doesn't break the graphics but then it doesn't work well with the wifi driver.

I used the deb file of the driver directly from broadcom website.

Have you tried Quantal in live CD?

Paulo Matos (pmatos) said : #5

Not yet... will give it a try. Unfortunately the driver worked really well with kernel 3.2 but then it's impossible to do anything because of the random crashes.

Hopefully quantal will seal the deal. However, I am also not too keen of starting to use quantal straight away since it's quite beta still. The perfect solution would be to get precise to work with a kernel 3.4 and have wifi driver working.

Paulo Matos (pmatos) said : #6

I have upgraded to Quantal alpha3. It's now working and sort of stable... but I guess that's to be expected.

I'll be released in October and officially stable. Some hardware needs the newer kernels which aren't in the released versions.