From: Tom Cada <thomas.cada@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Intermittent wlan operation ( b43-phy0 ERROR: PHY transmission error).
Date: Sat, 7 Mar 2009 16:54:41 -0500 [thread overview]
Message-ID: <960a51b60903071354ked42068w829e233cf3cc7d94@mail.gmail.com> (raw)
In-Reply-To: <49B2B9E4.9090006@lwfinger.net>
On Sat, Mar 7, 2009 at 1:16 PM, Larry Finger <Larry.Finger@lwfinger.net=
> wrote:
> Tom Cada wrote:
>> I went so far as to download the broadcom-wl-4.150.10.5.3 drivers
>> thinking that a more recent version would have addressed the problem=
=2E
>> However, I found out I couldn't install them with the error:
>>
>> =C2=A0$ ../../b43-fwcutter-011/b43-fwcutter -w /lib/firmware wl_apst=
a_mimo.o
>> Sorry, the input file is either wrong or not supported by b43-fwcutt=
er.
>> This file has an unknown MD5sum b84bc801b9b8f39069c252f533655af8.
>
> The driver is b43. What fwcutter gets is firmware. AFAIK, the firmwar=
e for your
> device that you are using is the same as that of driver 4.150.10.5.3.=
There is a
> difference in the firmware for LP and N PHY devices, but as they are =
not yet
> supported, it doesn't matter.
>
> We are aware of those errors, but don't know why they occur, or how t=
o fix them.
> Sorry.
>
> Larry
>
>
Oh poo!
I guess I will have to fire up ndiswrapper.
Thanks for the reply. Place me on the list if you would like me to
test any changes.
Tom.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-03-07 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 17:42 Intermittent wlan operation ( b43-phy0 ERROR: PHY transmission error) Tom Cada
2009-03-07 18:16 ` Larry Finger
2009-03-07 21:54 ` Tom Cada [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=960a51b60903071354ked42068w829e233cf3cc7d94@mail.gmail.com \
--to=thomas.cada@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--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