From: Larry Finger <larry.finger@lwfinger.net>
To: david@identd.dyndns.org
Cc: bcm43xx-dev <bcm43xx-dev@lists.berlios.de>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: b43legacy woes
Date: Fri, 31 Aug 2007 17:26:05 -0500 [thread overview]
Message-ID: <46D8957D.2010705@lwfinger.net> (raw)
In-Reply-To: <BAY128-W312E506592CDC1EF65AF0C86CE0@phx.gbl>
David Ellingsworth wrote:
> I've been using the b43legacy driver since it was first posted to this list.
> The driver has been relatively stable, but my wireless connection has not.
> In an environment with approximately 26 wireless access points, I experience
> frequent disconnects and reconnects with the rate stuck at 1Mb/s. The ranges
> for signal and noise reported under these conditions were (-53db, -59db) and
> (-93db, -89db) respectively, with an average difference between the two around 20db.
> The Windows driver under these conditions quickly scaled to 54Mb/s and maintained a
> connection. In an environment with a single AP, the b43legacy driver performs very
> similar to the results above where the rate is limited at 1Mb/s and the Windows driver
> scales significantly higher.
>
The poor performance of the BCM4306/2 (your chip/card) is known. There has been a report that this
is a regression since 2.6.20, or so, has not been confirmed. With a 2.6.21 kernel, I got an iperf
transmit rate of 4 Mbs, but that quickly dropped to 0.3 Mbs without me changing anything - I just
repeated the iperf command. I will be doing a bisection on bcm43xx to see if I can indeed find a
regression.
As for the loss of connection in an environment with lots of AP's, I cannot duplicate that
environment. Has anyone else seen this with b43, or with some other mac80211 driver. Perhaps we can
localize the problem component. Is there a possibility of buffer overflow in the scan results with
that many AP's?
Larry
next parent reply other threads:[~2007-08-31 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY128-W312E506592CDC1EF65AF0C86CE0@phx.gbl>
2007-08-31 22:26 ` Larry Finger [this message]
2007-08-31 23:55 ` b43legacy woes David Woodhouse
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=46D8957D.2010705@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=david@identd.dyndns.org \
--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;
as well as URLs for NNTP newsgroup(s).