Linux wireless drivers development
 help / color / mirror / Atom feed
From: Angus Ainslie <angus@akkea.ca>
To: 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: Redpine RS9116 M.2 module with NetworkManager
Date: Thu, 30 Jan 2020 10:18:56 -0800	[thread overview]
Message-ID: <59789f30ee686338c7bcffe3c6cbc453@akkea.ca> (raw)

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 ?

Thanks
Angus

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30 18:18 Angus Ainslie [this message]
2020-01-30 18:39 ` Redpine RS9116 M.2 module with NetworkManager Dan Williams
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=59789f30ee686338c7bcffe3c6cbc453@akkea.ca \
    --to=angus@akkea.ca \
    --cc=amitkarwar@gmail.com \
    --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