From: "Klaus Müller" <kmueller@justmail.de>
To: Felix Fietkau <nbd@openwrt.org>, linux-wireless@vger.kernel.org
Subject: Re: broken ath9k-driver - problems with creating new TCP-connections. Bad performance
Date: Sun, 27 Mar 2011 16:37:19 +0200 [thread overview]
Message-ID: <4D8F4B9F.9010809@justmail.de> (raw)
In-Reply-To: <4D8F2F3E.9030802@openwrt.org>
Felix Fietkau wrote:
> On 2011-03-27 2:08 PM, Klaus Müller wrote:
>> Hello,
>>
>> I'm running kernel 2.6.38.1 (from the OpenSuSE buildservice on OpenSuSE
>> 11.4) and compat-wireless-2011-03-26 (the performance / functionality of
>> the driver delivered with 2.6.38.1 is unusable).
>> [...]
>> iwconfig wlan0
>>
>> wlan0 IEEE 802.11bgn ESSID:"ssid"
>> Mode:Managed Frequency:2.412 GHz Access Point:
>> 00:25:33:22:11:00
>> Bit Rate=150 Mb/s Tx-Power=17 dBm
>> Retry long limit:7 RTS thr:off Fragment thr:off
>> Encryption key:off
>> Power Management:on
>> Link Quality=14/70 Signal level=-63 dBm
>> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
>> Tx excessive retries:4 Invalid misc:1423 Missed beacon:0
>>
>>
>> I run iwconfig 3 times in 7 seconds. The link quality alternated between
>> 47 and 14.
>>
> Have you tried switching your AP to HT20 instead of HT40 to see if that
> improves stability?
If the AP is set to HT20, this driver doesn't use IEEE 802.11n any more,
or, to say it more specific: the selected bit rate is max. 64 Mb/s and
the performance is even worse.
I'm wondering at all, why the ath9k driver doesn't switch to 300 Mb/s:
the rt3572sta-driver doesn't have any problem with both settings.
Klaus.
next prev parent reply other threads:[~2011-03-27 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 12:08 broken ath9k-driver - problems with creating new TCP-connections. Bad performance Klaus Müller
2011-03-27 12:36 ` Felix Fietkau
2011-03-27 14:37 ` Klaus Müller [this message]
2011-03-27 14:57 ` Felix Fietkau
2011-03-27 15:08 ` Richard Schütz
[not found] ` <4D8F50A6.70508@t-online.de>
2011-03-27 15:39 ` Klaus Müller
2011-03-27 12:45 ` Richard Schütz
2011-03-27 14:45 ` Klaus Müller
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=4D8F4B9F.9010809@justmail.de \
--to=kmueller@justmail.de \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.