Arch Linux

Dheart

Member

From: Sofia, Bulgaria

Registered: 2006-10-26

Posts: 956

bcm 4312 fail...

My bcm4312 was doing just fine... Until I upgraded to the newest kernel (2.6.32.10)
Then the b43 driver started spilling this errors.
I said "oh well" and tried to get downgrade the kernel... DIDN'T work.
Tried the ndiswrapper driver and the broadcom-wl drivers... They load fine but it says "no scanning results" when my wireless network is working just fine. I'm really puzzled, any suggestions? I gave up on my notebook for tonight, will try downgrades and driver reinstalling tomorrow.

---

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...

Dheart

Member

From: Sofia, Bulgaria

Registered: 2006-10-26

Posts: 956

Re: bcm 4312 fail...

It could, or could not have been overheating (i had uptime of 30 days and my laptop doesn't have good cooling)
Either way it's fixed after cold reboot.

---

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...

Kintaro

Member

Registered: 2010-03-20

Posts: 3

Re: bcm 4312 fail...

I was about to start a new thread about it right now!... I have a Dell Mini 9 with a Broadcom 4312 on it... and the same problem. The difference is that I have never been able to use wireless on it, just because I installed Arch a week ago, so the kernel updated to 2.6.32.10 before configuring wireless. I configure it following this, this, and this articles, but when I install the firmware I get this error. This is my daemons part in /etc/rc.conf:

DAEMONS=(!network @syslog-ng dbus hal networkmanager !lib80211 !lib80211_crypt_tkip wl !b43 !ssb netfs @crond @alsa kdm)

And this is what is shown when I execute "dmesg | grep b43":

b43-pci-bridge 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
b43-pci-bridge 0000:03:00.0: setting latency timer to 64
b43-phy0: Broadcom 4312 WLAN found (core revision 15)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
b43 ssb0:0: firmware: requesting b43/ucode15.fw
b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
b43-phy0: Controller RESET (DMA error) ...
b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
b43-phy0: Controller restarted
b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
b43-phy0: Controller RESET (DMA error) ...
b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
b43-phy0: 
b43-phy0: Controller RESET (DMA error) ...
b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
b43-phy0: Controller restarted
... (and repeat many times)

I think I'ts a problem with firmware. I tried to install b43-firmware-legacy from AUR but it's very old and doesn't work (some files are missing), and when I install b43-firmware or b43-firmware-newest I get the error above. I've also tried to use both b43-fwcutter and b43-fwcutter-patched with the same results... this is the only trouble I have on my netbook, but I'm trying to get it work for a week, and I'm pretty tired an desperate

wonder

Developer

From: Bucharest, Romania

Registered: 2006-07-05

Posts: 5,941

Website

Re: bcm 4312 fail...

@Kintaro you are doing wrong!

you mix modules with daemons.

!lib80211 !lib80211_crypt_tkip wl !b43 !ssb

should be copied to MODULES array.

---

Give what you have. To someone, it may be better than you dare to think.

Kintaro

Member

Registered: 2010-03-20

Posts: 3

Re: bcm 4312 fail...

Ouch >.<... well, this is embarrasing... almost five years using Linux and now I do this... It had been all the time behind my face when I was reading the articles! Get used to me, this happens to me a lot!

By the way... It works perfect now!, thank you very much!