Arch Linux

tavianator

Member

From: Waterloo, ON, Canada

Registered: 2007-08-21

Posts: 858

Website

[SOLVED] b43 connection troubles

I'm trying to get my friend set up with arch, but getting the BCM4312 in his dell laptop working is being a pain.  The broadcom-wl driver completely fails (creates a device, but all iwconfig/iwlist commands fail).  b43 shows promise, and I have the firmware installed and everything, and have successfully connected at least once.  However, almost every time I try to get an IP with dhcp, the carrier drops.

I've started wpa_supplicant, checked that the card is associated, then run dhcpcd wlan0.  It prints this:

dhcpcd[5111]: version 5.2.7 starting
dhcpcd[5111]: wlan0: rebinding lease of 192.168.1.104
dhcpcd[5111]: wlan0: carrier lost

and times out.  iwconfig afterwards shows that the card isn't associated, and an ifconfig down/up cycle is needed to get it to associate again.

For the record, this is on kernel 2.6.34.3-1, which patched that recent b43 bug.  Any ideas?

Last edited by tavianator (2010-08-24 15:33:19)

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: [SOLVED] b43 connection troubles

Check the kernel log for driver-related errors during/after the connection attempt.

tavianator

Member

From: Waterloo, ON, Canada

Registered: 2007-08-21

Posts: 858

Website

Re: [SOLVED] b43 connection troubles

I did do a dmesg | tail after trying, and there were some messages from b43, but no errors.  The messages were just along the lines of "associated with 00:..." as far as I remember; I didn't save them and I don't have access to the machine right now.  I'll paste them here next time I try, but they didn't stand out to me as being relevant.

tavianator

Member

From: Waterloo, ON, Canada

Registered: 2007-08-21

Posts: 858

Website

Re: [SOLVED] b43 connection troubles

Looks like the upgrade to .35.2 fixed it for him.

tavianator

Member

From: Waterloo, ON, Canada

Registered: 2007-08-21

Posts: 858

Website

Re: [SOLVED] b43 connection troubles

Actually the upgrade didn't fix it, but the advice in this thread did.  Basically, you need to pass "pio=1 qos=0" to the b43 module.