From: Clemens Helfmeier <clemens@helfmeier.de>
To: b43-dev@lists.infradead.org
Subject: bcm4322 success (WPA2)!
Date: Mon, 21 Feb 2011 08:56:01 +0100 [thread overview]
Message-ID: <20110221075600.GQ6696@helfmeier.de> (raw)
In-Reply-To: <4D616BDC.6080504@lwfinger.net>
Hello Larry,
On Sun, Feb 20, 2011 at 01:30:36PM -0600, Larry Finger wrote:
> On 02/20/2011 12:25 PM, Clemens Helfmeier wrote:
>> Hello Developers,
>>
>> I have just tried the current wireless-testing git tree with my bcm4322
>> device:
>>
>> # lshw
>> 0c:00.0 Network controller [0280]: Broadcom Corporation BCM4322
>> 802.11a/b/g/n
>> Wireless LAN Controller [14e4:432b] (rev 01)
>>
>> # dmesg shows:
>> [ 11.358762] b43-phy0: Broadcom 4322 WLAN found (core revision 16) [
>> 11.400231] b43-phy0 debug: Found PHY: Analog 8, Type 4, Revision 4 [
>> 11.400257] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2056,
>> Revision 3
>>
>> I had to apply this patch to b43-fwcutter in order to extract the firmware:
>> http://lists.infradead.org/pipermail/b43-dev/2010-July/000225.html
>>
>> Using WPA2, the connection is very stable, no connection break downs so far.
>>
>> My dmesg log shows quite a lot of error messages (approx every 7 seconds in
>> idle and more often when traffic is high):
>> [ 4015.044435] b43-phy0 ERROR: PHY transmission error
>> [ 4021.910720] b43-phy0 ERROR: PHY transmission error
>> [ 4028.866892] b43-phy0 ERROR: PHY transmission error
>>
>> Thanks for your efforts to get my hardware working!
>
> The attached patch should fix the PHY transmission errors, which happens
> whenever the rate control code tries to set an OFDM rate. With the patch,
> those rates will not work, but no errors will be printed.
>
> You can also lock the rate at 11M (iwconfig wlan0 rate 11M) to get rid of
> those errors.
Locking the rate at 11M makes the driver not output any more error messages
here ,too.
Thanks for your work!
Best regards,
Clemens
next prev parent reply other threads:[~2011-02-21 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201101032121.10454.christoph.thielecke@gmx.de>
[not found] ` <AANLkTikto8PkO8aD3x3i_E6b_GXKsx9XYJ0X+WjkrBaN@mail.gmail.com>
[not found] ` <201102201340.52880.christoph.thielecke@gmx.de>
2011-02-20 13:05 ` bcm4322 success! Rafał Miłecki
[not found] ` <201102201431.45988.christoph.thielecke@gmx.de>
2011-02-20 13:41 ` bcm4322 success (WPA2)! Rafał Miłecki
2011-02-20 18:25 ` Clemens Helfmeier
2011-02-20 19:27 ` Rafał Miłecki
2011-02-21 0:05 ` Tom Gundersen
2011-02-20 19:30 ` Larry Finger
2011-02-21 7:56 ` Clemens Helfmeier [this message]
[not found] ` <201102201930.43815.christoph.thielecke@gmx.de>
2011-02-21 18:55 ` Rafał Miłecki
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=20110221075600.GQ6696@helfmeier.de \
--to=clemens@helfmeier.de \
--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;
as well as URLs for NNTP newsgroup(s).