Closed jamstec0 closed 1 month ago
Sorry, I'm late updating this because I didn't have enough information. I then rebuilt the driver so that it can be debugged and the debug logs can be displayed. debug.log As a result, I found this as a possible cause of the logs.
Aug 27 17:52:16 arch kernel: brcmfmac: brcmf_fil_cmd_data Firmware error: BCME_UNSUPPORTED (-23)
Aug 27 17:52:16 arch kernel: brcmfmac: brcmf_fil_cmd_data Firmware error: BCME_BADADDR (-21)
However, the installed firmware was identical to the ubuntu one. What is this error from? Is it a bad driver? What is different from ubuntu, which uses the same kernel? Thank you very much.
I'm opening this issue because I haven't verified the behavior of the brcmfmac driver on the vendor kernel.
It seems that this kernel displays logs up to level 7 by default, so even after adding ignore_loglevel, there was no change.
I've also attached the log after adding ignore_loglevel. ignore.log
When I enabled cfg80211 with dynamic_debug, the following was displayed:
I have no idea what the cause is... It looks like there are no particular problems with systemd or udev, even though it uses the same firmware and driver source as ubuntu-rockchip. But the log shows a
ieee80211 phy0: brcmf_c_set_cur_etheraddr: Setting cur_etheraddr failed, -52
error. This -52 says it means BCME_IE_NOTFOUND. The device itself seems to be recognized, as the surrounding wifi scan is successful and shows up inip link
. it could be a connection error due to cur_etheraddr, mac address, etc.I am trying to figure out how to see the debug logs for brcmfmac.