Re: brcmfmac disconnects when iwd scans
Arend Van Spriel <[email protected]> Thu, 12 Jun 2025 19:27:43 +0200
| Newsgroups | dev.linux.lists.iwd |
|---|---|
| Message-ID | <[email protected]> |
On June 12, 2025 6:51:29 PM KeithG <[email protected]> wrote: > ... > > On Thu, Jun 12, 2025 at 9:37 AM Arend Van Spriel > <[email protected]> wrote: >> >> On June 12, 2025 3:51:34 PM KeithG <[email protected]> wrote: >> >>> Arend, >>> >>> I am still seeing this: >>> wpa_supplicant[431]: wlan0: Failed to initiate sched scan >>> >>> I tried the brcmfmac options listed above and got no change? Still >>> getting this every 6 seconds in the log. >>> Did I get the command in the modprobe conf wrong? >> >> Maybe. You could try to merge the two value so one line with 0x200002. >> Could be that wpa_supplicant determines support for scheduled scan in an >> unexpected way. Have not looked at the wpa_supplicant code for that. >> >> Regards, >> Arend >> >>> >>> On Fri, May 9, 2025 at 1:01 PM KeithG <[email protected]> wrote: >>>> >>>>>> >>>>>> With this setup, things work really well and the only strange thing I >>>>>> am getting is a 'failed scheduled scan' message in the log every ~6 >>>>>> sec. >>>>>> >>>>>> May 09 08:53:50 pi4 wpa_supplicant[2254218]: wlan0: Failed to initiate >>>>>> sched scan >>>>>> May 09 08:53:57 pi4 wpa_supplicant[2254218]: wlan0: Failed to initiate >>>>>> sched scan >>>>>> May 09 08:54:03 pi4 wpa_supplicant[2254218]: wlan0: Failed to initiate >>>>>> sched scan >>>>>> May 09 08:54:09 pi4 wpa_supplicant[2254218]: wlan0: Failed to initiate >>>>>> sched scan >>>>>> May 09 08:54:16 pi4 wpa_supplicant[2254218]: wlan0: Failed to initiate >>>>>> sched scan >>>>>> May 09 08:54:22 pi4 wpa_supplicant[2254218]: wlan0: Failed to initiate >>>>>> sched scan >>>>> >>>>> I thought wpa_supplicant had a config option to disable scheduled scan, but >>>>> can not find it. You can disable it in brcmfmac using feature_disable=2 >>>>> modparam. >>>>> >>>>> Regards, >>>>> Arend >>>> Arend, >>>> >>>> Thanks. I must be doing something wrong as I still get the 'Failed to >>>> initiate scan' spammed in the log with this config: >>>> >>>> # cat /etc/modprobe.d/brcmfmac.conf >>>> options brcmfmac feature_disable=0x200000 >>>> options brcmfmac feature_disable=2 >>>> >>>> Do I have it formatted wrong? >>>> >>>> Keith >>>> >>>> I think you suggested the the first line due to a different log >>>> spamming message. > Arend, > > Thanks for the help, but that does not seem to change anything. My > modprobe.conf: > > # cat /etc/modprobe.d/brcmfmac.conf > options brcmfmac feature_disable=0x200002 > > Still lost of the same "wpa_supplicant[423]: wlan0: Failed to initiate > sched scan" every 6 seconds. > > When I reboot, I get these mesages wrt wpa_supplicant (journalctl | grep wpa): > Jun 12 11:05:48 pi4 systemd[1]: Created slice > system-wpa_supplicant.slice - Slice /system/wpa_supplicant. > Jun 12 11:05:51 pi4 systemd[1]: Started [email protected] - > WPA supplicant daemon (interface-specific version). > Jun 12 11:05:53 pi4 wpa_supplicant[423]: Successfully initialized > wpa_supplicant > Jun 12 11:05:54 pi4 wpa_supplicant[423]: nl80211: kernel reports: > Registration to specific type not supported > Jun 12 11:06:07 pi4 wpa_supplicant[423]: wlan0: Failed to initiate sched scan > lots more... > Jun 12 11:07:51 pi4 wpa_supplicant[423]: wlan0: > CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US > Jun 12 11:06:07 pi4 wpa_supplicant[423]: wlan0: Failed to initiate sched scan > lots more... > > yet when I look, it seems it has scanned and are there SSIDs: Right. Scheduled scan is a different API compared to the normal scan. It allows userspace to say "scan periodically and let me know when you see any of the ssids I am interested in" to the driver/firmware and go take a nap. If I remember correctly wpa_supplicant does a couple of normal scans and when it doesn't see the ssids in its config file, it switches to using the scheduled scan api. Regards, Arend > # wpa_cli scan_results > Selected interface 'wlan0' > bssid / frequency / signal level / flags / ssid > c0:94:35:54:bb:10 5220 -59 [WPA2-PSK-CCMP][WPS][ESS] > AlignedHedronNetwork > d2:94:35:54:bb:10 5220 -69 [WPA2-EAP-CCMP][ESS][HS20] > Xfinity Mobile > c6:4f:d5:4b:36:c0 5785 -68 [WPA2-PSK-CCMP][ESS] > c6:4f:d5:4b:36:c2 5785 -68 [WPA2-PSK+SAE-CCMP][ESS] > ameliafanclub