From: "John W. Linville" <linville@tuxdriver.com>
To: Ferdinand Rau <RauFerd@web.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Bug report: Controller RESET (DMA error) long after connecting
Date: Tue, 13 Apr 2010 09:11:09 -0400 [thread overview]
Message-ID: <20100413131108.GB6331@tuxdriver.com> (raw)
In-Reply-To: <4375153.331710.1271156960878.JavaMail.fmail@mwmweb085>
On Tue, Apr 13, 2010 at 01:09:20PM +0200, Ferdinand Rau wrote:
> 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
Chances are that your device will work in PIO mode -- you can try
building a kernel w/ CONFIG_B43_FORCE_PIO. In 2.6.34, there is code
to switch automatically to PIO mode when such errors are observed.
Hth!
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-04-13 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 11:09 Bug report: Controller RESET (DMA error) long after connecting Ferdinand Rau
2010-04-13 13:11 ` John W. Linville [this message]
2010-04-13 19:19 ` Ferdinand Rau
2010-07-30 14:53 ` [SOLVED] " Ferdinand Rau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100413131108.GB6331@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=RauFerd@web.de \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).