From: kelly hirai <kgh03@fsu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Dreaded broadcom BCM4312 wireless card causes DMA failures and crashes
Date: Thu, 29 Jul 2010 15:45:39 -0400 [thread overview]
Message-ID: <4C51DA63.2050905@fsu.edu> (raw)
In-Reply-To: <358eca8f1003260657g38a07642h460bc3d45a9defad@mail.gmail.com>
On 03/26/10 09:57, Mick wrote:
> On 26 March 2010 13:53, Mick <michaelkintzios@gmail.com> wrote:
>> Hi,
>>
>> Has anyone managed to get BCM4312, 802.11b/g (pcie) Device: pci
>> 0x4315, going with the b43 module?
>>
>> b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000,
>> 0x00000000, 0x00000000, 0x00000000
>> b43-phy0: Controller RESET (DMA error) ...
>> b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
>> b43-phy0: Controller restarted
>> b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000,
>> 0x00000000, 0x00000000, 0x00000000
>>
>> I've unmasked and am using the latest firmware in portage and the b43
>> module from the gentoo-sources-2.6.32-r7 kernel. The card comes up,
>> then authenticates and tries to get an IP address, but in less than a
>> second after it gets an IP address it crashes with these recurring
>> messages above.
>>
>> Is there a fix, or shall I go for the wl module by Broadcom or even
>> give up and go for the ndiswrapper solution?
> Posted too early perhaps. There seems to be a patch coming for the
> 2.6.33 kernels. Will have to wait I guess.
>
> https://patchwork.kernel.org/patch/66064/
im guessing here. maybe you have old firmware. did you get the "old
firmware" warning in your kernel messages when you loaded the module?
next prev parent reply other threads:[~2010-07-29 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 13:53 [gentoo-user] Dreaded broadcom BCM4312 wireless card causes DMA failures and crashes Mick
2010-03-26 13:57 ` [gentoo-user] " Mick
2010-07-29 19:45 ` kelly hirai [this message]
2010-07-29 21:25 ` Mick
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=4C51DA63.2050905@fsu.edu \
--to=kgh03@fsu.edu \
--cc=gentoo-user@lists.gentoo.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