Arch Linux

hkupty

Member

Registered: 2010-01-30

Posts: 7

Problems with Broadcom BCM4312

I'm experiencing problems with my notebook, under Arch x64.

When I use the b43 driver, it has some problems while scanning (sometimes work, sometimes doesn't) and simply does not connect (neither connecting by command-line, GUI or netcfg profile)

When I use the broadcom-wl driver, it scans, but works only under root and shows the board as if it was ethernet (wich I assume is a default behaviour, but some programs would not work with a eth0 device, excpecting a wlan0 or ath0) and does not connect either..

I just want to know which of the drivers I should use and how to configure it correctly. Also, I'd like to know the best tool for managing wifi connections, specially for WPA and WPA with Preshare key.

I'll supply you with whatever info you need, wich I don't have now since I'm on my desktop.

Thanks in advance,
Henry

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,677

Re: Problems with Broadcom BCM4312

Which kernel are you using?  New kernels have vastly improved Broadcom support.

I am having good results with the 2.6.32 kernel with its intrinsic B43 driver.

To manage the connection, I use wicd.  I am currently using the (default) external program backend option in wicd rather than the ioctl option because that has been the only configuration that works.  The latest release of wicd indicated that ioctl support for the b43 driver is now experimental.  I intend to try it soon.  This is because I found the ioctl support of the broadcom-wl driver to be much faster.

The broadcom-wl driver is not compatible with the 2.6.32 kernel.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

hkupty

Member

Registered: 2010-01-30

Posts: 7

Re: Problems with Broadcom BCM4312

Well, it seems that half of the problem is solved then.. I'm using the 2.6.32 kernel.

I tried again the b43 and I had better results this time (it's responding to aircrack-ng, although it's still not scanning with iwlist).

I'll try wicd. Maybe then I'll be able to connect..

Thank you.

ntness

Member

From: The World

Registered: 2009-12-29

Posts: 97

Re: Problems with Broadcom BCM4312

Have you had any luck with this? I've followed the wiki on BCM4312 and countless other suggestions to no avail. I can't seem to get a wireless signal regardless of the driver/utility used.

---

transcend to the fifth abode

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,677

Re: Problems with Broadcom BCM4312

could you post the output of following three programs?

lspci | grep Broadcom
uname -a
sudo grep Broadcom /var/log/everything.log

Thanks.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

ntness

Member

From: The World

Registered: 2009-12-29

Posts: 97

Re: Problems with Broadcom BCM4312

lspci | grep Broadcom

0b:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev01)

uname -a

Linux myhost 2.6.32-ARCH #1 SMP PREEMPT Fri Jan 29 09:10:49 CET 2010 x86_64 Intel(R) Pentium(R) Dual CPU T2390 @ 1.86GHz GenuineIntel GNU/Linux

sudo grep Broadcom /var/log/everything.log

No output.

Everything was working fine as per Archwiki's BCM4312 page a day ago. However, after a format last night I'm getting nowhere (this is after I updated the system through a wired connection).

---

transcend to the fifth abode

lman

Member

From: CZ

Registered: 2007-12-18

Posts: 255

Re: Problems with Broadcom BCM4312

I have the exact same card (rev. 01), but I'm using 32 bit arch. I haven't had a problem since kernel 2.6.31 with the b43 driver. I have used network-manager, wicd and both worked fine (mainly with wpa networks). Networkmanager is a better tool for that if you are using a DE, but I switched to wicd, because it didn't remember my passwords when using compiz-standalone. I didn't try to set it manually/with netcfg. It was way easier with wicd/networkmanager.
Do you have these packages installed? b43-firmware, b43-fwcutter

ntness

Member

From: The World

Registered: 2009-12-29

Posts: 97

Re: Problems with Broadcom BCM4312

I tried using the 'b43-firmware-newest' package from the AUR and followed the instructions on ArchWiki's Wireless Setup page. However, have had no luck using b43/wicd nor bcm43xx. I prefer just using netcfg and creating my own profiles.

As if by the magic of many invisible pixies, I've got a connection after the 400th reboot.

Last edited by ntness (2010-02-07 12:03:16)

---

transcend to the fifth abode

hkupty

Member

Registered: 2010-01-30

Posts: 7

Re: Problems with Broadcom BCM4312

Sorry if I'm late:

lspci | grep Broadcom

0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)

uname -a

Linux Drakkar 2.6.32-ARCH #1 SMP PREEMPT Tue Feb 23 19:43:46 CET 2010 x86_64 Intel(R) Core(TM)2 Duo CPU T6500 @ 2.10GHz GenuineIntel GNU/Linux

sudo grep... everything.log

Mar 14 12:37:16 Drakkar kernel: b43-phy0: Broadcom 4312 WLAN found (core revision 15)
Mar 14 12:37:16 Drakkar kernel: Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ]

I've had some small problems with work and stuff, so I couldn't resolve this wifi problem..

here are my outputs.. Meanwhile, I'll still try to connect with the intrinsec b43 driver..

tks

zenlord

Member

From: Belgium

Registered: 2006-05-24

Posts: 1,229

Website

Re: Problems with Broadcom BCM4312

I had problems with the b43-driver, but broadcom-wl works perfectly for me in combination with netcfg.

When I upgraded from kernel .31 -> .32 I had to reinstall broadcom-wl from AUR, but that should be obvious...

And to the OP: if your devices are named incorrectly (ethX, wlanX, athX etc), you can add a udev-rule to give a specific device the name you want. It's all in the wiki!