b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Dylan Cristiani <d.cristiani@idem-tech.it>
To: b43-dev@lists.infradead.org
Subject: Trouble using bcm4318 compact flash with b43 driver
Date: Fri, 21 Jan 2011 22:54:08 +0100	[thread overview]
Message-ID: <20110121225408.00003e2c@unknown> (raw)
In-Reply-To: <4D39C0B9.8050708@lwfinger.net>

On Fri, 21 Jan 2011 11:22:01 -0600
Larry Finger <Larry.Finger@lwfinger.net> wrote:

> On 01/21/2011 09:51 AM, Dylan Cristiani wrote:
> > probably i found a clue (maybe the point): when the b43 wlan
> > interface comes up its rate is, at the beginning, setted to the
> > lowest possible: 1Mbit, as i can see with iwconfig, and it seems
> > that, at this low rates, some access points doesn't work, becuase
> > of some handshake timeout failure happening or other different
> > timeouts issue, like they can't 'deal' with such communication
> > being too slow; if i set higher rates (i.e. 'iw set rate 24M') it
> > associates to access point (WPA2 encryption), it gets dhcp address
> > and it is possible to ping other net's nodes, also if there are
> > still some issue, like high percentage of packet lost and so on;
> > furthermore, trying to force setting of the rate to highest
> > possible 'iw set rate 54M', doesn't improve the performances but,
> > at the opposite, it leads again to association failures; is this a
> > normal behaviour? do you think that i'm doing something wrong? why
> > is the starting rate setted to 1M (it's a wlan module policy or a
> > driver choice?); which is the best way to solve this issue if any?
> > 
> > as usual thanks for you support and patience!!
> 
> Your finding may be a good clue, but I'm not sure how to interpret
> it. Any AP must be able to handle traffic at 1 Mbps. Consider a
> station at an extreme distance where rates no higher that 1M can be
> supported. In addition, all management frames are sent at 1M to
> minimize the chances of packet loss.
ok so that's normal and sensible policy and for sure very reasonable in
fact maybe my question was little blind (near to stupid!)
> 
> You may have found a bug in the firmware of the AP, although that is
> not too likely. What make and model is the AP and what firmware
> version is it using?
problems came up with motorola wireless switch RFS6000 and access
port650; but same problems with motorola ap7131 and less with ap5131 
> 
> Fixing the transmission rate at too high a value will reduce
> throughput, just as you see because of transmission errors. Any new
> connection always starts at 1M. The rate-control algorithm will then
> increase the rate until the error rate increases.
same as first point i was blind and hasty but you know when something
is not working, you change something and it works, then you revert it
but it still works it's not a good feeling, because you cannot target
the problem...
> 
> I think you must do the git bisection to find the kernel change that
> caused the problem. I know that it is a lot of work, but at least you
> already know how to compile a kernel.
yes at least, other than bother community ;-), i know how to compile the
kernel i think i'm over thousand, only with 2.6.36 i reached more than
200 :-(; btw tks for you time, i'll bisect kernel but i'm not really
sure that it's a question of driver's problem, because as i told you
same kernel version sometimes works sometimes not.

dyl

  reply	other threads:[~2011-01-21 21:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 17:21 Trouble using bcm4318 compact flash with b43 driver dylan cristiani
2011-01-14 18:52 ` Larry Finger
2011-01-15  7:05   ` Dylan Cristiani
2011-01-15 16:38     ` Larry Finger
2011-01-17 10:06       ` dylan cristiani
2011-01-17 13:51         ` dylan cristiani
2011-01-18 10:58           ` dylan cristiani
2011-01-18 14:34             ` Larry Finger
2011-01-19 13:03               ` dylan cristiani
2011-01-21 15:51                 ` Dylan Cristiani
2011-01-21 17:22                   ` Larry Finger
2011-01-21 21:54                     ` Dylan Cristiani [this message]
2011-01-21 22:13                       ` Larry Finger
2011-01-22 10:48                         ` Dylan Cristiani
2011-02-01 14:41                           ` dylan cristiani
2011-02-01 20:40                             ` Larry Finger
2011-02-02  9:11                               ` dylan cristiani
2011-02-02 11:55                                 ` dylan cristiani
2011-02-02 15:30                                   ` dylan cristiani
2011-02-02 21:58                                     ` Larry Finger
2011-02-03  8:28                                       ` dylan cristiani
2011-02-02 22:40                                     ` Michael Büsch
2011-02-03  8:45                                       ` dylan cristiani
2011-02-03 10:29                                         ` Michael Büsch

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=20110121225408.00003e2c@unknown \
    --to=d.cristiani@idem-tech.it \
    --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).