From: Jim Haynes <jhhaynes@earthlink.net>
To: b43-dev@lists.infradead.org
Subject: Please help - what is causing these errors and how do I fix them
Date: Fri, 2 Apr 2010 19:57:56 -0500 (CDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1004021943230.1957@localhost> (raw)
In-Reply-To: <4BB66F04.1010700@lwfinger.net>
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.
next prev parent reply other threads:[~2010-04-03 0:57 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 [this message]
2010-04-03 1:05 ` Larry Finger
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=alpine.LFD.2.00.1004021943230.1957@localhost \
--to=jhhaynes@earthlink.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