From: Jes Sorensen <jes@wildopensource.com>
To: Thomas Mueller <linux-kernel@tmueller.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 much worse than 2.4 on poor wlan reception
Date: 05 Mar 2004 04:23:00 -0500 [thread overview]
Message-ID: <yq0znavsl57.fsf@wildopensource.com> (raw)
In-Reply-To: <20040304180154.GA1893@tmueller.com>
>>>>> "Thomas" == Thomas Mueller <linux-kernel@tmueller.com> writes:
Thomas> Kernel 2.4 works far better in the poor reception situation I
Thomas> have, anyone any idea what I could do without moving the AP or
Thomas> laptop? When I'm near my AP everything works fine with 2.6
Thomas> too.
Start out by forcing it to a lower link speed, at that signal quality
you really don't want to try and go above 2MBit/sec. If you keep
trying to do 11MBit/sec the card will constantly try the higher rate
and then lose signal, drop down and try again. Fixing the rate should
improve the situation - at least it has always done so for me ;-)
Cheers,
Jes
next prev parent reply other threads:[~2004-03-05 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 18:01 2.6 much worse than 2.4 on poor wlan reception Thomas Mueller
2004-03-04 21:47 ` Denis Vlasenko
2004-03-07 12:01 ` Thomas Mueller
2004-03-05 9:23 ` Jes Sorensen [this message]
2004-03-07 11:32 ` Thomas Mueller
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=yq0znavsl57.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--cc=linux-kernel@tmueller.com \
--cc=linux-kernel@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