Arch Linux

Dheart

Member

From: Sofia, Bulgaria

Registered: 2006-10-26

Posts: 956

Something breaks b43 for BCM 4312 after update

I have the aforementioned card and ever since kernel 2.6.33 it's worked excellent with the b43 driver, however as of this morning, upgrading to kernel 3.5 the driver loads just fine, no errors on dmesg but I get the

wlan0 deauthenticating from by local choice (reason=3)

every time I try to connect to a network...

EDIT: The kernel is not at fault. I tried broadcom-wl which doesn't work, nor does downgrading the kernel... Here's my pacman.log with the latest update

[2012-08-29 08:29] upgraded calibre (0.8.65-1 -> 0.8.66-1)
[2012-08-29 08:29] upgraded espeak (1.46.02-1 -> 1.46.02-2)
[2012-08-29 08:29] upgraded ethtool (1:3.4-1 -> 1:3.5-1)
[2012-08-29 08:29] upgraded hspell (1.1-2 -> 1.2-1)
[2012-08-29 08:29] upgraded hwids (20120730-1 -> 20120815-1)
[2012-08-29 08:29] upgraded initscripts (2012.08.2-1 -> 2012.08.3-1)
[2012-08-29 08:29] upgraded iotop (0.4.4-2 -> 0.4.4-3)
[2012-08-29 08:29] upgraded libatasmart (0.18-2 -> 0.19-1)
[2012-08-29 08:29] upgraded libgssglue (0.3-1 -> 0.4-1)
[2012-08-29 08:29] upgraded libwbclient (3.6.7-1 -> 3.6.7-2)
KERNEL UPDATE INFORMATION HERE
2012-08-29 08:30] upgraded linux (3.4.9-1 -> 3.5.3-1)
[2012-08-29 08:30] upgraded linux-docs (3.4.9-1 -> 3.5.3-1)
[2012-08-29 08:30] upgraded linux-headers (3.4.9-1 -> 3.5.3-1)
[2012-08-29 08:30] upgraded lirc-utils (1:0.9.0-22 -> 1:0.9.0-26)
[2012-08-29 08:30] upgraded openvpn (2.2.2-1 -> 2.2.2-2)
[2012-08-29 08:30] upgraded sane (1.0.22-9 -> 1.0.23-1)
[2012-08-29 08:30] upgraded smbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 08:30] upgraded udisks (1.0.4-4 -> 1.0.4-5)
[2012-08-29 08:30] upgraded xf86-video-intel (2.20.4-1 -> 2.20.5-1)
[2012-08-29 08:30] upgraded xorg-server-common (1.12.3.901-1 -> 1.12.4-1)
[2012-08-29 08:30] upgraded xorg-server (1.12.3.901-1 -> 1.12.4-1)
[2012-08-29 08:30] upgraded xorg-server-devel (1.12.3.901-1 -> 1.12.4-1)

Connecting by hand with dhcpcd gives

 open_control: Connection refused

EDIT2:
Killing dhcpcd several times and trying another network got my networkmanager magically connected...

EDIT3:
Now back 3.5.3 I found out how to connect: Killall dhcpcd, try to assosiate from console to some open network nearby and while dhcpcd is waiting for a carrier order networkmanager to assossiate and it works....

Last edited by Dheart (2012-08-29 08:45:25)

---

My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...