On 11/24/2022 1:26 PM, Andy Green wrote:
On 11/24/22 12:22, Arend van Spriel wrote:On 11/24/2022 1:14 PM, Andy Green wrote:On 11/24/22 09:42, Arend van Spriel wrote:On 11/18/2022 6:41 AM, Andy Green wrote:On 11/17/22 21:52, Arend Van Spriel wrote:I see. So could you load bcmdhd and provide log. Preferably with higher debug level. It also has a module parameter for it. I think it is called dhd_msg_level and please set it to 0x817.It's here: https://warmcat.com/ap6275p-dhd-log1.txtHi Andy,Thanks for the log. Together with the dhd driver sources I could make some sense of it. Perhaps you can try the following hack and see if we make it over the first hurdle.OH! I found that the line below should be count, not sizeof(count).Good job! I was testing you obviously. You passed. Nah, I just feel stupid.No it's great, the point is it directly identified the root cause without access to the platform, it's not so easy.... any way, good job!Thanks. Will clean it up and formally submit it. I also had a quick look at the SDIO variant, but not seeing anything obvious there in terms of firmware loading.I only have the pcie module not the SDIO one.For the scan situation, he understands what is being asked via connmanctl "enable wifi", but he feels something wrongconnmanctl> enable wifi connmanctl> Enabled wifi connmanctl> [ 272.174946] ieee80211 phy0: brcmf_run_escan: error (-52) [ 272.174956] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-52) connmanctl> [ 275.133157] ieee80211 phy0: brcmf_run_escan: error (-52) [ 275.133166] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-52) connmanctl> [ 284.138852] ieee80211 phy0: brcmf_run_escan: error (-52) [ 284.138856] ieee80211 phy0: brcmf_cfg80211_scan: scan error (-52)52 is EBADE, I recall you mentioned that the scan api had been changed recently... is this possibly related to that? Grepping around for EBADE near the function it mentions, it tries to take evasive action if it sees one in some places already.
EBADE is a generic error message indicating something went wrong communicating with firmware. Not very informative. Were you using any debug level? Anyway, please load the driver with module parameter debug=0x5416 and try scanning using iw utility.
Regards, Arend
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature