Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <dec7cce5138d4cfeb5596d63048db7ec19a18c3c.camel@redhat.com>
Subject: Re: Redpine RS9116 M.2 module with NetworkManager
From:   Dan Williams <dcbw@redhat.com>
To:     Angus Ainslie <angus@akkea.ca>,
        Amitkumar Karwar <amitkarwar@gmail.com>,
        Siva Rebbagondla <siva8118@gmail.com>
Cc:     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
Date:   Thu, 30 Jan 2020 12:39:52 -0600
In-Reply-To: <59789f30ee686338c7bcffe3c6cbc453@akkea.ca>
References: <59789f30ee686338c7bcffe3c6cbc453@akkea.ca>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

On Thu, 2020-01-30 at 10:18 -0800, Angus Ainslie wrote:
> Hi,
> 
> I'm trying the get a Redpine RS9116 module working with
> networkmanager. 
> I've tried this on 5.3, 5.5 and next-20200128. I'm using the Redpine
> 1.5 
> "rs9116_wlan_bt_classic.rps" firmware.
> 
> If I configure the interface using iw, wpa_supplicant and dhclient
> all 
> works as expected.
> 
> If I try to configure the interface using nmtui most of the time no
> APs 
> show up to associate to. "iw dev wlan0 list" shows all of the APs in
> the 
> vicinity.
> 
> If I do manage to get an AP to show when I try to "Activate a 
> connection" I get the error below
> 
> Could not activate connection:
> Activation failed: No reason given
> 
> 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

Dan