Hi,

I'm on a Dell Vostro 1310 (running Debian testing) using a BCM4312 wireless chip and the firmware retrieved by the b43-fwcutter from git (the debian version didn't work with my card - the upgrade to kernel 2.6.31 only happend recently).
I basically followed the instructions on this site:
http://www.linuxwireless.org/en/users/Drivers/b43#fw-b43-lp

The wireless connection works in principle (can connect to different networks, can ping, can browse), but at some point the following error happens and the connection is reset every few seconds afterwards rendering it unusable:
> ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
> Controller RESET (DMA error) ...

Similar to this thread (?): https://lists.berlios.de/pipermail/bcm43xx-dev/2009-November/006273.html

About my system:
> $ uname -a
> Linux vostro1310 2.6.32-3-686 #1 SMP Thu Feb 25 06:14:20 UTC 2010 i686
> GNU/Linux

> #b43-fwcutter --version
> b43-fwcutter version 012

> $ lspci -vvn|grep 43 -A7
> 06:00.0 0280: 14e4:4315 (rev 01)
>	Subsystem: 1028:000b
>	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx-
>	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>	Latency: 0, Cache Line Size: 64 bytes
>	Interrupt: pin A routed to IRQ 19
>	Region 0: Memory at f4000000 (64-bit, non-prefetchable) [size=16K]
>	Capabilities: <access denied>
>	Kernel driver in use: b43-pci-bridge
>
>07:00.0 0200: 10ec:8168 (rev 02)
>	Subsystem: 1028:026f
>	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx+
>	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR+ <PERR- INTx-
>	Latency: 0, Cache Line Size: 64 bytes
>	Interrupt: pin A routed to IRQ 28

The full output of dmesg is attached, as is my kernel configuration (stock debian) and the list of installed packages (note that the "debian" b43-fwcutter is removed since I used the version from git instead).

I am using network manager (networkmanager) by the way, do you think I should try it without first? Since the connection is established and working for some time before the error shows up I thought it can't be NMs fault this time.

If there's anything else you need to know, just contact me.

Regards,
___________________________________________________________
NEU: WEB.DE DSL für 19,99 EUR/mtl. und ohne Mindest-Laufzeit!
http://produkte.web.de/go/02/