From: Daniel Holz <daniel.holz91@gmail.com>
To: ath10k@lists.infradead.org
Subject: Re: QCA6174 Performance
Date: Sun, 18 Sep 2016 20:14:44 +0200 [thread overview]
Message-ID: <1474222484.3948.0@smtp.gmail.com> (raw)
In-Reply-To: <CA+BoTQmxVn_iv4u7KGGDmmeKsJx4cf_qqD=Z2Qv8c_JioNHSjA@mail.gmail.com>
iw wlp2s0 info displays that my bandwidth is 80 MHz. Over the weekend I
tried different configurations like using n instead of ac or 2,4 GHz
and connection speed on a different WLAN, but the performance was
always extremely slow.
Daniel Holz
Am Fr, 16. Sep, 2016 um 2:23 schrieb Michal Kazior
<michal.kazior@tieto.com>:
> On 16 September 2016 at 13:50, Daniel Holz <daniel.holz91@gmx.de>
> wrote:
>> The md5sum matches.
>>
>>
>> I installed Kernel 4.8 from Ubuntu's mainline ppa to get the recent
>> version
>> of ath10k which increased the performance, but it's still pretty
>> low.
>>
>> Here is the output of dmesg with kernel 4.8:
>
> You can check it with a recent enough iw:
> iw wlp2s0 info
>
> It should tell you channel bandwidth you are using.
>
> Maybe ath10k or your AP has a bug that causes wrong capabilities to be
> negotiated during association.
>
> You could try re-configuring your AP (to slower speeds) or force
> wpa_supplicant/ath10k to not use vht or ht modes at all and re-testing
> if it helps.
>
>
> Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-09-18 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 11:50 QCA6174 Performance Daniel Holz
2016-09-16 12:23 ` Michal Kazior
2016-09-18 18:14 ` Daniel Holz [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-15 13:29 Daniel Holz
2016-09-16 4:13 ` Valo, Kalle
[not found] ` <1474018906.3370.0@smtp.gmail.com>
2016-09-16 10:44 ` Valo, Kalle
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=1474222484.3948.0@smtp.gmail.com \
--to=daniel.holz91@gmail.com \
--cc=ath10k@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