[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <31a7f0aad8e3de605f95845e77637785@akkea.ca>
Date: Thu, 30 Jan 2020 11:24:30 -0800
From: Angus Ainslie <angus@...ea.ca>
To: Dan Williams <dcbw@...hat.com>
Cc: Amitkumar Karwar <amitkarwar@...il.com>,
Siva Rebbagondla <siva8118@...il.com>,
Kalle Valo <kvalo@...eaurora.org>,
"David S. Miller" <davem@...emloft.net>,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-wireless-owner@...r.kernel.org
Subject: Re: Redpine RS9116 M.2 module with NetworkManager
On 2020-01-30 11:08, Angus Ainslie wrote:
> 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
>>
>
Any chance there's something similar for bluetooth ? hcitool shows the
device and can scan but bluetoothctl can't find the device.
$ hcitool dev
Devices:
hci0 88:DA:1A:9E:XX:XX
[bluetooth]# list
[bluetooth]# devices
No default controller available
Thanks
Angus
>
>> Dan
Powered by blists - more mailing lists