Trouble connecting to broadcom AC APs?

[Adrian Chadd]

Did the per-rate transmit statistics ever make it into the firmware / driver?

I'd start by looking at what rate(s) it's trying and what the transmit
completion statistics say. It could be doing something exceedingly
dumb like transmitting on an invalid rate or stream setup.

Same deal with STBC/LDPC. Try disabling those; see what happens.



-a


On 20 March 2014 08:59, Ben Greear <greearb at candelatech.com> wrote:
> On 03/19/2014 11:36 PM, Kalle Valo wrote:
>> Ben Greear <greearb at candelatech.com> writes:
>>
>>> We are seeing various funny things when trying to connect
>>> ath10k stations to commercial APs with broadcom AC NICs.
>>>
>>> It sort of works sometimes, but we often see failure to
>>> acquire DHCP lease in a timely manner, etc.
>>
>> So it's a problem with broadcast frames? With or without encryption? Did
>> you try disabling power save?
>
> With and without encryption we see issues.  I am disabling power-save,
> but from poking around in firmware, I'm not sure how much affect that
> has.
>
> I'm using commands like this to disable it:
> ./local/sbin/iw dev sta219 set power_save off
>
>>> Similar testing on APs using QCA AC NICs appears to work
>>> much better.
>>>
>>> Our problems could be most anything, including the fact that this
>>> testing is done on our modified firmware, but I am curious if anyone
>>> else seems any similar issues?
>>
>> Occasionally I test connecting to D-Link DIR-865L in STA mode. But I
>> just do just simple ping tests and with manual IPs.
>
> We'll keep poking at things and see if we can find any
> pattern or work around.
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc  http://www.candelatech.com
>
>
> _______________________________________________
> ath10k mailing list
> ath10k at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k