From: Angus Ainslie <angus@akkea.ca>
To: Dan Williams <dcbw@redhat.com>
Cc: Amitkumar Karwar <amitkarwar@gmail.com>,
Siva Rebbagondla <siva8118@gmail.com>,
Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Redpine RS9116 M.2 module with NetworkManager
Date: Thu, 30 Jan 2020 11:08:22 -0800 [thread overview]
Message-ID: <47d5e080faa1edbf17d2bdeccee5ded9@akkea.ca> (raw)
In-Reply-To: <dec7cce5138d4cfeb5596d63048db7ec19a18c3c.camel@redhat.com>
Hi Dan,
On 2020-01-30 10:39, Dan Williams wrote:
> On Thu, 2020-01-30 at 10:18 -0800, Angus Ainslie wrote:
>>
>> I suspect this is a driver bug rather than a NM bug as I saw similar
>> issues with an earlier Redpine proprietary driver that was fixed by
>> updating that driver. What rsi_dbg zone will help debug this ?
>
> NM just uses wpa_supplicant underneath, so if you can get supplicant
> debug logs showing the failure, that would help. But perhaps the driver
> has a problem with scan MAC randomization that NM can be configured to
> do by default; that's been an issue with proprietary and out-of-tree
> drivers in the past. Just a thought.
>
> https://blog.muench-johannes.de/networkmanager-disable-mac-randomization-314
>
Thanks that was the fix.
Angus
> Dan
next prev parent reply other threads:[~2020-01-30 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 18:18 Redpine RS9116 M.2 module with NetworkManager Angus Ainslie
2020-01-30 18:39 ` Dan Williams
2020-01-30 19:08 ` Angus Ainslie [this message]
2020-01-30 19:24 ` Angus Ainslie
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=47d5e080faa1edbf17d2bdeccee5ded9@akkea.ca \
--to=angus@akkea.ca \
--cc=amitkarwar@gmail.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=siva8118@gmail.com \
/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.