mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Subject: Re: Redpine RS9116 M.2 module with NetworkManager
Date: Thu, 30 Jan 2020 12:39:52 -0600	[thread overview]
Message-ID: <dec7cce5138d4cfeb5596d63048db7ec19a18c3c.camel@redhat.com> (raw)
In-Reply-To: <59789f30ee686338c7bcffe3c6cbc453@akkea.ca>

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


  reply	other threads:[~2020-01-30 18:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30 18:18 Angus Ainslie
2020-01-30 18:39 ` Dan Williams [this message]
2020-01-30 19:08   ` Angus Ainslie
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=dec7cce5138d4cfeb5596d63048db7ec19a18c3c.camel@redhat.com \
    --to=dcbw@redhat.com \
    --cc=amitkarwar@gmail.com \
    --cc=angus@akkea.ca \
    --cc=davem@davemloft.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®