From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: bcm43xx-dev@lists.berlios.de, "John H." <mistamaila@gmail.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org, Michael Buesch <mb@bu3sch.de>
Subject: Re: timeout problems with certain APs and b43
Date: Fri, 23 Nov 2007 23:21:56 +0100 [thread overview]
Message-ID: <200711232321.58516.rjw@sisk.pl> (raw)
In-Reply-To: <1195855050.4149.179.camel@johannes.berg>
On Friday, 23 of November 2007, Johannes Berg wrote:
>
> > > > on certain APs, the internet works for a long time then stops, and I
> > > > get authentication time outs, why? It usually works again if I reset
> > > > the AP itself, which i should not have to do and don't have to if in
> > > > XP....
> > >
> > > > wlan0: Initial auth_alg=0
> > > > wlan0: authenticate with AP 00:0f:66:53:3e:24
> > > > wlan0: authenticate with AP 00:0f:66:53:3e:24
> > > > wlan0: authenticate with AP 00:0f:66:53:3e:24
> > > > wlan0: authentication with AP 00:0f:66:53:3e:24 timed out
> > >
> > > Does it help to reload the b43 module? I think I have seen this problem
> > > before but always associated it with suspend/resume rather than a long
> > > time elapsing, I also thought it was due to bad power recalibration.
> >
> > It seems that I can reproduce something similar on demand with an SMC wireless
> > router by moving my box sufficiently far away from it. :-)
>
> Well, yeah, that's expected though, you lose signal at some point. Not
> expected is that it happens without moving anything. Unless the
> calibration code is wrong which wouldn't really surprise me either.
In my case, everything works just fine when the box is 6 meters away from the
AP (including a thick wall in between), but when I move it another 5-6 meters
away from the AP, things break down ...
I'd expect it to work at longer distances, but well. :-)
Greetings,
Rafael
next prev parent reply other threads:[~2007-11-23 22:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 19:35 timeout problems with certain APs and b43 John H.
2007-11-21 22:18 ` Larry Finger
2007-11-23 4:31 ` John H.
2007-11-23 5:41 ` Larry Finger
2007-11-23 10:05 ` Johannes Berg
2007-11-23 21:58 ` Rafael J. Wysocki
2007-11-23 21:57 ` Johannes Berg
2007-11-23 22:21 ` Rafael J. Wysocki [this message]
2007-11-24 1:56 ` John H.
2007-11-24 8:35 ` Johannes Berg
2007-11-24 11:17 ` Rafael J. Wysocki
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=200711232321.58516.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=mistamaila@gmail.com \
/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).