On 07/21/2017 06:22 PM, Carl D. Blake wrote:
This is kernel 3.10.96 on an Nvidia Tegra X1. The driver is the
module for the BCM4354. I don't believe it is out of tree, but I could
be wrong. Of course, this is on ubuntu 14.04 which is a couple years
old, so I suppose the drivers might need to be updated.
According the wifi wiki it is supported via the brcmsmac.
If it is possible I would give a current Linux kernel a try. If the
problems goes away we know where to look at. But if doesn't go away we
are as smart as before.
>> I originally thought it had something to do with miracast and asked this
>> question at that site, but the people there thought it might be an issue
>> with connman.
>> It seems like there might be some issue with DHCP renewal. Does anybody
>> know what's happening here?
> It doesn't look like DHCP, because the wireless driver receives a
> DEAUTH. Why this is happening? I have no clue. Maybe it is possible to
> increase the verbosity of the driver and you might see what is going on.
> Maybe ConnMan is also doing something wrong but I would first check if
> the driver is behaving according the specification. If it is this
> version I found on github I wouldn't be surprised if there are still
> bugs in it. Just one commit and no changes since 2015.
I'll increase the verbosity. The thing is I'm getting this same exact
behavior on an Nvidia Tegra K1 using an AC7260 mini PCIe card, so I
figured it had to be something other than the drivers.
Ah, so different driver and hardware but the same behavior. Indeed, that
sounds like a higher level problem.