From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Please help - what is causing these errors and how do I fix them
Date: Fri, 02 Apr 2010 20:05:21 -0500 [thread overview]
Message-ID: <4BB69451.5040409@lwfinger.net> (raw)
In-Reply-To: <alpine.LFD.2.00.1004021943230.1957@localhost>
On 04/02/2010 07:57 PM, Jim Haynes wrote:
> On Fri, 2 Apr 2010, Larry Finger wrote:
>
>>
>> Use the Broadcom wl driver or configure b43 for PIO. Did you do any
>> searching on this problem?
>>
>
>
> Thanks. I did searching a few months ago, and had everything working at
> that time, but I guess I need to do a fresh search. I'm not sure what
> it means to do either of the two things you suggest. There is a b43
> module that came with the kernel I am running - are you saying I need
> to get the source and recompile it with something different done?
> Should that have been done by the Fedora people when they made the
> kernel? Or is there a way to tell whether it is or is not compiled
> with PIO?
>
> I wish things would Just Work sometimes.
We do to. Unfortunately, some boxes with Intel CPU and Phoenix BIOS get
this kind of error. We do not know why and have put a lot of effort into
the search since this problem was first reported.
If you can find a late enough Fedora kernel, it will automatically
switch to PIO when the DMA error happens. Otherwise, you might get that
functionality with compat-wireless packages. I'm an openSUSE user and do
not know the inner details of the Fedora system.
Larry
prev parent reply other threads:[~2010-04-03 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 22:14 Please help - what is causing these errors and how do I fix them Jim Haynes
2010-04-02 22:26 ` Larry Finger
2010-04-03 0:57 ` Jim Haynes
2010-04-03 1:05 ` Larry Finger [this message]
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=4BB69451.5040409@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.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