From: sHittmeyer <hittmeyer@corscience.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Poor performance on AR5418
Date: Wed, 27 Aug 2008 08:11:43 +0200 [thread overview]
Message-ID: <48B4F01F.4000609@corscience.de> (raw)
In-Reply-To: <14d615330808261602t775294d0q51c954071950fdfd@mail.gmail.com>
Jeremy Apthorp schrieb:
> 2008/8/27 Luis R. Rodriguez <lrodriguez@atheros.com>:
>
>> On Tue, Aug 26, 2008 at 03:47:05PM -0700, Jeremy Apthorp wrote:
>>
>>> 2008/8/27 Luis R. Rodriguez <mcgrof@gmail.com>:
>>>
>>>> Link quality is not 100% correct, its actually better. We need to add
>>>> noise floor calibration to get it to report more accurate values. So
>>>> for now just use it as a guide. Also the rate reported by iwconfig is
>>>> not correct, please rely on iperf for proper performance tests.
>>>>
>>> I was more concerned about the packet loss than the link quality or
>>> the reported rate. Also, I tried loading google.com in a browser, and
>>> it took several minutes.
>>>
>> How soon after associating and getting an IP and pinging do you get
>> packet loss? Whatever it is we definitely will need to fix it.
>>
>
> Directly. I didn't at any point get a good link.
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>
>
>
I'm using an ordinary Desktop-PC with Kubuntu and an selfbuilded
Kernel-2.6.26.2 / Kernel-2.6.26.rc3. with both Kernels I tried the Ath9k
using a D-Link DWA-547 (AR5416 inside). I simply have the same lossrate
of up to over 50% while connecting to a 11g network.
So unfortunately it doesn't seam to be just a problem of AR5418.
-stefan-
next prev parent reply other threads:[~2008-08-27 6:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 22:09 [ath9k-devel] Poor performance on AR5418 Jeremy Apthorp
2008-08-26 22:23 ` Luis R. Rodriguez
2008-08-26 22:47 ` Jeremy Apthorp
2008-08-26 23:01 ` Luis R. Rodriguez
2008-08-26 23:02 ` Jeremy Apthorp
2008-08-27 6:11 ` sHittmeyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-26 22:49 Amit Sood
2008-08-26 23:53 Amit Sood
2008-08-27 1:33 ` John Dong
2008-08-27 8:44 Amit Sood
2008-08-27 11:08 ` F
2008-08-27 14:59 Amit Sood
2008-08-27 17:22 ` Luis R. Rodriguez
2008-08-27 23:10 ` John Dong
2008-08-28 0:48 ` F
2008-08-28 6:26 Amit Sood
2008-08-29 10:03 Amit Sood
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=48B4F01F.4000609@corscience.de \
--to=hittmeyer@corscience.de \
--cc=ath9k-devel@lists.ath9k.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.