You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
WIFI -seems to default to hotspot mode; valid SSID and password flagged w/ invalid password #258
Title: WiFi connectivity issues after "Update All" on Pi-stomp v3
Description:
I am experiencing persistent WiFi connectivity issues following the latest "Update All" procedure on my Pi-stomp v3 device. Since performing the update, the device consistently defaults to hotspot mode and fails to connect to my local WiFi network.
Troubleshooting Steps Taken:
Credential Verification: I attempted to manually disable hotspot mode and configure the WiFi network settings. The device returns an "invalid" error for the SSID/password combination. I have confirmed these credentials are correct and working on multiple other devices. I have also seeded the correct credentials with the config file; this had no impact.
Network Testing: I connected the Pi-stomp via Ethernet; the connection functions perfectly while plugged in, indicating the issue is isolated to the WiFi interface or its configuration post-update.
Installation Context: This issue is occurring on a fresh install of the latest Pi-stomp software version on a v3 unit; factory reset was done on the config files as well.
Expected Behavior:
The device should be able to connect to a standard WPA2/WPA3 WiFi network after the update, rather than being forced into hotspot mode.
System Details:
Device: Pi-stomp v3
Software Version: Latest (fresh install)
Status: Ethernet working, but wireless stack is failing to authenticate or join known networks.
Yeah, it's unfortunate if that's the case -- it means that some APs will break no matter what we choose there. But I do agree this is the most likely candidate. This update came with a pistomp-wifi package.
It would also be helpful if you posted some diagnostics from when it's refusing to connect to your wifi, and if the ROAMOFF=1 fix works for you, getting the same logs in that configuration would maybe help pin down how we can get a working configuration for everyone on the same settings.
after connecting it by ethernet to do the updates to patches...it intermittently loses connection and I can't effectively add some pedals now. This is kind of getting wild
Does the roamoff=1 fix work?
• Partially, but not completely.
• With roamoff=0: The kernel driver (brcmfmac) throws repeated external authentication and driver event worker errors (brcmf_cyw_external_auth: External authentication failed: status=1, brcmf_cyw_mgmt_tx: TX Auth frame operation is failed, brcmf_fweh_event_worker: event handler failed (187)).
• With roamoff=1: All kernel-level brcmf_cyw_external_auth and driver crashes disappear completely. However, connection still fails because the access point or client times out during the 802.11 association phase (CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16).
Contributing Root Causes Discovered:
• Modprobe Configuration Conflict: /etc/modprobe.d/brcmfmac.conf sets roamoff=1, but pistomp-wifi (installed via deb) ships /etc/modprobe.d/rpi-brcmfmac.conf with roamoff=0 feature_disable=0x282000. Because rpi-* sorts alphabetically after b*, roamoff=0 overrides roamoff=1 at runtime.
• WPA2/WPA3 Mixed-Mode Bug in modalapi/wifi/types.py:
if "SAE" in s or "WPA3" in s:
return cls.SAE
When an access point advertises WPA2 WPA3 (transition mode), from_scan_security classifies it as pure KeyMgmt.SAE rather than KeyMgmt.WPA_PSK. Because Raspberry Pi's Broadcom driver has feature_disable=0x282000 (which disables hardware/firmware SAE), pure SAE negotiation immediately fails.
• Association Rejection (status_code=16):
During association on both 5 GHz (channel 112) and 2.4 GHz (channel 11), wpa_supplicant receives bssid=00:00:00:00:00:00 status_code=16 (internal driver timeout waiting for the AP's association response frame), causing NetworkManager to assume bad secrets and drop the connection.
──────
Sanitized Diagnostics to Post to the Team
All credentials, network SSIDs, BSSIDs, hardware MAC addresses, IP addresses, and hostnames have been scrubbed.
@jpremill that helps narrow it down -- and it looks like it's not ROAMOFF as (1) the results are the same with it on/off and (2) the wifi is failing in auth / association handshake, before roaming would be triggered.
I think you're right that this has to do with WPA3-specific security ("SAE"). I think what caused this to start failing is that the WPA3 support branch chooses SAE for APs that support both that and WPA2-PSK; our new software is forcing the failing path whereas before it was defaulting to the working one.
While we get a proper bug fix out, it would be helpful to get the following from you:
Can you confirm that "Update All" means the updates from Updates and Recovery, and not a more-general debian apt upgrade?
Can you confirm that powering off both the AP and the pi-Stomp, waiting 60 seconds, and then powering the AP then the pi-Stomp on does not fix it?
Can you try connecting via WPA2 over e.g. wired SSH:
@sastraxi It was updated via the updates and recovery menu not the apt updates. I did a 60 second reboot on both devices. I will try the script and wired ssh commands later and report on it when I get a moment.
Collection output:
`===== MODEL =====
Raspberry Pi 5 Model B Rev 1.1
===== OS =====
Raspberry Pi reference 2026-08-14
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, a2f0d8ae8c4c5f577d0c4139876d2c96ba965014, stage3
Linux pistomp 6.18.36-rpi-v8-rt #1 SMP PREEMPT_RT Tue Jun 23 05:54:35 UTC 2026 aarch64 GNU/Linux
===== PISTOMP-PKGS =====
ii browsepy 0.5.6-2 arm64 File browser for pi-Stomp user files
ii cabsim-lv2 1.1.1-5 arm64 VeJa Cabinet Simulator LV2 plugin (pistomp fork)
ii ffmpeg-pistomp 7.1.1-2 arm64 Minimal ffmpeg build for pi-Stomp
ii jack2-pistomp 1.9.22-8 arm64 JACK Audio Connection Kit v2 (pi-Stomp build)
ii jackbridge 1.0-5 arm64 netJACK2 client for DAW recording over Ethernet
ii lcd-splash 1.0-20 arm64 Fast ILI9341 LCD boot splash for pi-Stomp
ii lg-pistomp 0.2.2-5 arm64 Linux C library and Python bindings for GPIO (lgpio/rgpio)
ii mod-host-pistomp 0.10.6-7 arm64 MOD Host — LV2 plugin host for JACK (pi-Stomp fork)
ii mod-ui 3.0-15 arm64 MOD Web UI — web-based pedalboard interface for pi-Stomp
ii pi-stomp 3.3.2-0 arm64 pi-Stomp application — guitar effects pedalboard software
ii pistomp-audio 1.0.0-2 arm64 Realtime audio IRQ tuning and PCM bind repair for pi-Stomp
ii pistomp-recovery 0.1.0-32 arm64 Package update and recovery service for pi-Stomp
ii pistomp-usb-automount 1.0.0-2 arm64 Lightweight udev-based USB automount for pi-Stomp
ii pistomp-wifi 1.0.0-1 arm64 WiFi driver configuration for pi-Stomp
ii rpi-preseed 0.1.0-pistomp3 all first-boot OS customisation for Raspberry Pi OS
ii sfizz-pistomp 1.2.3-9 arm64 SFZ library and LV2 plugin (minimal, headless)
ii veja-1960-cab-lv2 1.0-2 arm64 VeJa Marshall 1960 Cabinet LV2 plugin (pistomp fork)
ii veja-bass-cab-lv2 1.0-2 arm64 VeJa Bass Cabinets LV2 plugin (pistomp fork)
===== SYS-PKGS =====
||/ Name Version Architecture Description
+++-==================-=========================-============-==========================================================
ii firmware-brcm80211 1:20260519-1~bpo13+1+rpt1 all Binary firmware for Broadcom/Cypress 802.11 wireless cards
ii network-manager 1.52.1-1+rpt4 arm64 network management framework (daemon and userspace tools)
ii wpasupplicant 2:2.10-24 arm64 client support for WPA and WPA2 (IEEE 802.11i)
===== MODPROBE =====
/etc/modprobe.d/brcmfmac.conf:options brcmfmac roamoff=1
/etc/modprobe.d/rpi-brcmfmac.conf:# Shadow the distro file of the same name (/usr/lib/modprobe.d/rpi-brcmfmac.conf,
/etc/modprobe.d/rpi-brcmfmac.conf:# shipped by firmware-nonfree in both Bookworm and Trixie) which sets roamoff=1.
/etc/modprobe.d/rpi-brcmfmac.conf:# We need roaming on for the Pi to work properly with some access points,
/etc/modprobe.d/rpi-brcmfmac.conf:# so we override it here.
/etc/modprobe.d/rpi-brcmfmac.conf:options brcmfmac roamoff=1 feature_disable=0x282000
/usr/lib/modprobe.d/rpi-brcmfmac.conf:options brcmfmac roamoff=1 feature_disable=0x282000
@jpremill interesting -- so in the end you were able to connect with SAE! I'm curious, now that the temporary wpa2-test profile has been removed, does a cold boot successfully connect to wifi? And are you using the #260 branch or the pristine pi-stomp from OTA?
Activity
rreichenbach commentedon Sep 9, 2026
This change was made:
TreeFallSound/pi-gen-pistomp#48
I wonder if changing roamoff back to 1 in rpi-brcmfmac.conf would fix your issue.
sastraxi commentedon Sep 10, 2026
Yeah, it's unfortunate if that's the case -- it means that some APs will break no matter what we choose there. But I do agree this is the most likely candidate. This update came with a
pistomp-wifipackage.It would also be helpful if you posted some diagnostics from when it's refusing to connect to your wifi, and if the ROAMOFF=1 fix works for you, getting the same logs in that configuration would maybe help pin down how we can get a working configuration for everyone on the same settings.
jpremill commentedon Sep 10, 2026
after connecting it by ethernet to do the updates to patches...it intermittently loses connection and I can't effectively add some pedals now. This is kind of getting wild
jpremill commentedon Sep 11, 2026
Hope this is sufficient:
Executive Summary
• Partially, but not completely.
• With roamoff=0: The kernel driver (brcmfmac) throws repeated external authentication and driver event worker errors (brcmf_cyw_external_auth: External authentication failed: status=1, brcmf_cyw_mgmt_tx: TX Auth frame operation is failed, brcmf_fweh_event_worker: event handler failed (187)).
• With roamoff=1: All kernel-level brcmf_cyw_external_auth and driver crashes disappear completely. However, connection still fails because the access point or client times out during the 802.11 association phase (CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16).
• Modprobe Configuration Conflict: /etc/modprobe.d/brcmfmac.conf sets roamoff=1, but pistomp-wifi (installed via deb) ships /etc/modprobe.d/rpi-brcmfmac.conf with roamoff=0 feature_disable=0x282000. Because rpi-* sorts alphabetically after b*, roamoff=0 overrides roamoff=1 at runtime.
• WPA2/WPA3 Mixed-Mode Bug in modalapi/wifi/types.py:
if "SAE" in s or "WPA3" in s:
return cls.SAE
When an access point advertises WPA2 WPA3 (transition mode), from_scan_security classifies it as pure KeyMgmt.SAE rather than KeyMgmt.WPA_PSK. Because Raspberry Pi's Broadcom driver has feature_disable=0x282000 (which disables hardware/firmware SAE), pure SAE negotiation immediately fails.
• Association Rejection (status_code=16):
During association on both 5 GHz (channel 112) and 2.4 GHz (channel 11), wpa_supplicant receives bssid=00:00:00:00:00:00 status_code=16 (internal driver timeout waiting for the AP's association response frame), causing NetworkManager to assume bad secrets and drop the connection.
──────
Sanitized Diagnostics to Post to the Team
All credentials, network SSIDs, BSSIDs, hardware MAC addresses, IP addresses, and hostnames have been scrubbed.
[ 1281.712145] ieee80211 phy0: brcmf_cyw_external_auth: External authentication failed: status=1
[ 1281.713263] ieee80211 phy0: brcmf_cyw_external_auth: External authentication failed: status=1
[ 1284.978967] ieee80211 phy0: brcmf_cyw_external_auth: External authentication failed: status=1
[ 1284.979199] ieee80211 phy0: brcmf_cyw_external_auth: External authentication failed: status=1
[ 1292.831654] ieee80211 phy0: brcmf_cyw_mgmt_tx: TX Auth frame operation is failed: status=10)
[ 1358.090945] ieee80211 phy0: brcmf_cyw_notify_ext_auth_req: Ext Auth request to supplicant failed (-22)
[ 1358.090960] ieee80211 phy0: brcmf_fweh_event_worker: event handler failed (187)
wlan0: Trying to associate with SSID ''
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
wlan0: CTRL-EVENT-AUTH-REJECT <AP_BSSID_2.4G> auth_type=3 auth_transaction=2 status_code=1
wlan0: Trying to associate with SSID ''
wlan0: CTRL-EVENT-AUTH-REJECT <AP_BSSID_2.4G> auth_type=3 auth_transaction=2 status_code=1
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
wlan0: Authentication with <AP_BSSID_5G> timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=<AP_BSSID_5G> reason=3 locally_generated=1
wlan0: BSSID <AP_BSSID_5G> ignore list count incremented to 2, ignoring for 10 seconds
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="" auth_failures=1 duration=10 reason=CONN_FAILED
wlan0: Trying to associate with <AP_BSSID_5G> (SSID='' freq=5560 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
wlan0: BSSID <AP_BSSID_5G> ignore list count incremented to 2, ignoring for 10 seconds
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="" auth_failures=1 duration=10 reason=CONN_FAILED
wlan0: Trying to associate with <AP_BSSID_2.4G> (SSID='' freq=2462 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=00:00:00:00:00:00 status_code=16
wlan0: CTRL-EVENT-DISCONNECTED bssid=<AP_BSSID_2.4G> reason=3 locally_generated=1
sastraxi commentedon Sep 12, 2026
@jpremill that helps narrow it down -- and it looks like it's not
ROAMOFFas (1) the results are the same with it on/off and (2) the wifi is failing in auth / association handshake, before roaming would be triggered.I think you're right that this has to do with WPA3-specific security ("SAE"). I think what caused this to start failing is that the WPA3 support branch chooses SAE for APs that support both that and WPA2-PSK; our new software is forcing the failing path whereas before it was defaulting to the working one.
While we get a proper bug fix out, it would be helpful to get the following from you:
You can run the same
connection deletecommand afterwards to get rid of this new profile.This file will contain your SSID, your BSSIDs and your MAC address so please feel free to redact as necessary.
sastraxi commentedon Sep 12, 2026
@jpremill i added deployment instructions in the fix PR linked above. In addition to the above let us know if that works!
jpremill commentedon Sep 13, 2026
@sastraxi It was updated via the updates and recovery menu not the apt updates. I did a 60 second reboot on both devices. I will try the script and wired ssh commands later and report on it when I get a moment.
jpremill commentedon Sep 14, 2026
Collection output:
`===== MODEL =====
Raspberry Pi 5 Model B Rev 1.1
===== OS =====
Raspberry Pi reference 2026-08-14
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, a2f0d8ae8c4c5f577d0c4139876d2c96ba965014, stage3
Linux pistomp 6.18.36-rpi-v8-rt #1 SMP PREEMPT_RT Tue Jun 23 05:54:35 UTC 2026 aarch64 GNU/Linux
===== PISTOMP-PKGS =====
ii browsepy 0.5.6-2 arm64 File browser for pi-Stomp user files
ii cabsim-lv2 1.1.1-5 arm64 VeJa Cabinet Simulator LV2 plugin (pistomp fork)
ii ffmpeg-pistomp 7.1.1-2 arm64 Minimal ffmpeg build for pi-Stomp
ii jack2-pistomp 1.9.22-8 arm64 JACK Audio Connection Kit v2 (pi-Stomp build)
ii jackbridge 1.0-5 arm64 netJACK2 client for DAW recording over Ethernet
ii lcd-splash 1.0-20 arm64 Fast ILI9341 LCD boot splash for pi-Stomp
ii lg-pistomp 0.2.2-5 arm64 Linux C library and Python bindings for GPIO (lgpio/rgpio)
ii mod-host-pistomp 0.10.6-7 arm64 MOD Host — LV2 plugin host for JACK (pi-Stomp fork)
ii mod-ui 3.0-15 arm64 MOD Web UI — web-based pedalboard interface for pi-Stomp
ii pi-stomp 3.3.2-0 arm64 pi-Stomp application — guitar effects pedalboard software
ii pistomp-audio 1.0.0-2 arm64 Realtime audio IRQ tuning and PCM bind repair for pi-Stomp
ii pistomp-recovery 0.1.0-32 arm64 Package update and recovery service for pi-Stomp
ii pistomp-usb-automount 1.0.0-2 arm64 Lightweight udev-based USB automount for pi-Stomp
ii pistomp-wifi 1.0.0-1 arm64 WiFi driver configuration for pi-Stomp
ii rpi-preseed 0.1.0-pistomp3 all first-boot OS customisation for Raspberry Pi OS
ii sfizz-pistomp 1.2.3-9 arm64 SFZ library and LV2 plugin (minimal, headless)
ii veja-1960-cab-lv2 1.0-2 arm64 VeJa Marshall 1960 Cabinet LV2 plugin (pistomp fork)
ii veja-bass-cab-lv2 1.0-2 arm64 VeJa Bass Cabinets LV2 plugin (pistomp fork)
===== SYS-PKGS =====
||/ Name Version Architecture Description
+++-==================-=========================-============-==========================================================
ii firmware-brcm80211 1:20260519-1~bpo13+1+rpt1 all Binary firmware for Broadcom/Cypress 802.11 wireless cards
ii network-manager 1.52.1-1+rpt4 arm64 network management framework (daemon and userspace tools)
ii wpasupplicant 2:2.10-24 arm64 client support for WPA and WPA2 (IEEE 802.11i)
===== MODPROBE =====
/etc/modprobe.d/brcmfmac.conf:options brcmfmac roamoff=1
/etc/modprobe.d/rpi-brcmfmac.conf:# Shadow the distro file of the same name (/usr/lib/modprobe.d/rpi-brcmfmac.conf,
/etc/modprobe.d/rpi-brcmfmac.conf:# shipped by firmware-nonfree in both Bookworm and Trixie) which sets roamoff=1.
/etc/modprobe.d/rpi-brcmfmac.conf:# We need roaming on for the Pi to work properly with some access points,
/etc/modprobe.d/rpi-brcmfmac.conf:# so we override it here.
/etc/modprobe.d/rpi-brcmfmac.conf:options brcmfmac roamoff=1 feature_disable=0x282000
/usr/lib/modprobe.d/rpi-brcmfmac.conf:options brcmfmac roamoff=1 feature_disable=0x282000
===== PARAMS =====
/sys/module/brcmfmac/parameters/alternative_fw_path =
/sys/module/brcmfmac/parameters/debug = 0
/sys/module/brcmfmac/parameters/roamoff = 1
===== FIRMWARE =====
[ 3.081468] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 3.083031] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 3.084338] usbcore: registered new interface driver brcmfmac
[ 3.258985] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2)
[ 3.259227] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Aug 29 2023 01:47:08 version 7.45.265 (28bca26 CY) FWID 01-b677b91b
[ 5.399357] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[ 8.337870] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
===== REGDOM =====
global
country US: DFS-FCC
(902 - 904 @ 2), (N/A, 30), (N/A)
(904 - 920 @ 16), (N/A, 30), (N/A)
(920 - 928 @ 8), (N/A, 30), (N/A)
(2400 - 2472 @ 40), (N/A, 30), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5350 @ 80), (N/A, 24), (0 ms), DFS, AUTO-BW
(5470 - 5730 @ 160), (N/A, 24), (0 ms), DFS
(5730 - 5850 @ 80), (N/A, 30), (N/A), AUTO-BW
(5850 - 5895 @ 40), (N/A, 27), (N/A), NO-OUTDOOR, AUTO-BW, PASSIVE-SCAN
(5925 - 7125 @ 320), (N/A, 12), (N/A), NO-OUTDOOR, PASSIVE-SCAN
(57240 - 71000 @ 2160), (N/A, 40), (N/A)
phy#0
country 99: DFS-UNSET
(2402 - 2482 @ 40), (6, 20), (N/A)
(2474 - 2494 @ 20), (6, 20), (N/A)
(5140 - 5360 @ 160), (6, 20), (N/A)
(5460 - 5860 @ 160), (6, 20), (N/A)
===== RFKILL =====
/tmp/collect.sh: line 11: rfkill: command not found
===== NM-DEV =====
DEVICE TYPE STATE CONNECTION
eth0 ethernet connected wired-eth0
wlan0 wifi connected
lo loopback connected (externally) lo
p2p-dev-wlan0 wifi-p2p disconnected --
WIFI-HW WIFI WWAN-HW WWAN
enabled enabled missing enabled
===== SCAN =====
SSID BSSID CHAN FREQ SIGNAL SECURITY WPA-FLAGS RSN-FLAGS
28:74:F5:D0:5B:EA 11 2462 MHz 99 WPA2 WPA3 (none) pair_ccmp group_ccmp psk sae
-- 2A:74:F5:C0:5B:EE 112 5560 MHz 65 WPA2 (none) pair_ccmp group_ccmp psk
28:74:F5:D0:5B:EE 112 5560 MHz 62 WPA2 WPA3 (none) pair_ccmp group_ccmp psk sae
FC:B2:D6:BF:31:88 112 5560 MHz 19 WPA2 WPA3 (none) pair_ccmp group_ccmp psk sae
===== PROFILES =====
NAME TYPE AUTOCONNECT DEVICE
wired-eth0 ethernet yes eth0
wifi yes wlan0
lo loopback no lo
pistomp-hotspot wifi no --
===== JOURNAL =====
Sep 12 18:53:05 pistomp systemd[1]: Starting NetworkManager.service - Network Manager...
Sep 12 18:53:05 pistomp systemd[1]: Starting wpa_supplicant.service - WPA supplicant...
Sep 12 18:53:05 pistomp systemd[1]: Started wpa_supplicant.service - WPA supplicant.
Sep 12 18:53:05 pistomp wpa_supplicant[730]: Successfully initialized wpa_supplicant
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.2416] NetworkManager (version 1.52.1) is starting... (boot:8926c8be-a57f-4b61-9e35-f1c4b21658ab)
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.2417] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/{no-mac-addr-change.conf,rpi-no-scan-rand-mac-address.conf}, /etc/NetworkManager/conf.d/{wifi-mac.conf,wifi-powersave.conf}
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.2615] manager[0x559651cd90]: monitoring kernel firmware directory '/lib/firmware'.
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.2615] monitoring ifupdown state file '/run/network/ifstate'.
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.3697] hostname: hostname: using hostnamed
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.3698] hostname: static hostname changed from (none) to "pistomp"
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.3712] dns-mgr: init: dns=dnsmasq,systemd-resolved rc-manager=symlink (auto), plugin=dnsmasq
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.3722] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/platform/axi/1001100000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/rfkill0) (driver brcmfmac)
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.3723] manager[0x559651cd90]: rfkill: Wi-Fi hardware radio set enabled
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.3724] manager[0x559651cd90]: rfkill: WWAN hardware radio set enabled
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.3852] Loaded device plugin: NMAtmManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.52.1/libnm-device-plugin-adsl.so)
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.4050] Loaded device plugin: NMWwanFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.52.1/libnm-device-plugin-wwan.so)
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.4108] Loaded device plugin: NMWifiFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.52.1/libnm-device-plugin-wifi.so)
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.4174] Loaded device plugin: NMTeamFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.52.1/libnm-device-plugin-team.so)
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.4249] Loaded device plugin: NMBluezManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.52.1/libnm-device-plugin-bluetooth.so)
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.4252] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.4253] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.4253] manager: Networking is enabled by state file
Sep 12 18:53:06 pistomp NetworkManager[729]: [1789253586.4267] settings: Loaded settings plugin: keyfile (internal)
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.1686] dhcp: init: Using DHCP client 'internal'
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.1688] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.1697] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.1700] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.1714] device (lo): Activation: starting connection 'lo' (6c20527d-9ba5-40e4-aa09-a8b9e6a96b99)
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.1721] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.1723] device (eth0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.1962] device (wlan0): driver supports Access Point (AP) mode
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.1968] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.1969] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Sep 12 18:53:07 pistomp systemd[1]: Started NetworkManager.service - Network Manager.
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.2251] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.2397] modem-manager: oFono is not available
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.2399] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.2401] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.2403] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.2428] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.2511] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.2513] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.2521] device (lo): Activation: successful, device activated.
Sep 12 18:53:07 pistomp wpa_supplicant[730]: nl80211: kernel reports: Registration to specific type not supported
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.3480] device (wlan0): supplicant interface state: internal-starting -> disconnected
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.3481] Wi-Fi P2P device controlled by interface wlan0 created
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.3483] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.3485] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.3489] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Sep 12 18:53:07 pistomp NetworkManager[729]: [1789253587.3494] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1560] policy: auto-activating connection '' (170cd55c-ff3d-4c66-bcfb-3e2b1c0c444b)
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1564] device (wlan0): Activation: starting connection '' (170cd55c-ff3d-4c66-bcfb-3e2b1c0c444b)
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1564] device (wlan0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1566] manager: NetworkManager state is now CONNECTING
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1568] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1570] device (wlan0): Activation: (wifi) access point '' has security, but secrets are required.
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1570] device (wlan0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1571] sup-iface[a80ee1e4bd166633,0,wlan0]: wps: type pbc start...
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1579] device (wlan0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1581] device (wlan0): state change: prepare -> config (reason 'none', managed-type: 'full')
Sep 12 18:53:10 pistomp wpa_supplicant[730]: wlan0: WPS-PBC-ACTIVE
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1583] device (wlan0): Activation: (wifi) connection '' has security, and secrets exist. No new secrets needed.
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1591] Config: added 'ssid' value ''
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1592] Config: added 'scan_ssid' value '1'
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1592] Config: added 'bgscan' value 'simple:30:-70:86400'
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1592] Config: added 'key_mgmt' value 'SAE FT-SAE'
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1592] Config: added 'psk' value ''
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1592] Config: added 'ieee80211w' value '2'
Sep 12 18:53:10 pistomp wpa_supplicant[730]: wlan0: WPS-CANCEL
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1613] device (wlan0): supplicant interface state: disconnected -> scanning
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.1613] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Sep 12 18:53:10 pistomp wpa_supplicant[730]: wlan0: Trying to associate with 28:74:f5:d0:5b:ee (SSID='' freq=5560 MHz)
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.2910] device (wlan0): supplicant interface state: scanning -> associating
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.2910] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Sep 12 18:53:10 pistomp wpa_supplicant[730]: wlan0: PMKSA-CACHE-ADDED 28:74:f5:d0:5b:ee 0
Sep 12 18:53:10 pistomp wpa_supplicant[730]: wlan0: Associated with 28:74:f5:d0:5b:ee
Sep 12 18:53:10 pistomp wpa_supplicant[730]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 12 18:53:10 pistomp wpa_supplicant[730]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.7848] device (wlan0): supplicant interface state: associating -> associated
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.7848] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Sep 12 18:53:10 pistomp wpa_supplicant[730]: wlan0: WPA: Key negotiation completed with 28:74:f5:d0:5b:ee [PTK=CCMP GTK=CCMP]
Sep 12 18:53:10 pistomp wpa_supplicant[730]: wlan0: CTRL-EVENT-CONNECTED - Connection to 28:74:f5:d0:5b:ee completed [id=0 id_str=]
Sep 12 18:53:10 pistomp wpa_supplicant[730]: bgscan simple: Failed to enable signal strength monitoring
Sep 12 18:53:10 pistomp wpa_supplicant[730]: wlan0: TRANSITION-DISABLE 01
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.8573] device (wlan0): supplicant interface state: associated -> completed
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.8574] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network ""
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.8574] device (p2p-dev-wlan0): supplicant management interface state: associated -> completed
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.8576] device (wlan0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Sep 12 18:53:10 pistomp NetworkManager[729]: [1789253590.8580] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Sep 12 18:53:13 pistomp NetworkManager[729]: [1789253593.1511] dhcp4 (wlan0): state changed new lease, address=192.168.1.65, acd pending
Sep 12 18:53:13 pistomp NetworkManager[729]: [1789253593.2965] dhcp4 (wlan0): state changed new lease, address=192.168.1.65
Sep 12 18:53:13 pistomp NetworkManager[729]: [1789253593.3018] policy: set '' (wlan0) as default for IPv4 routing and DNS
Sep 12 18:53:13 pistomp NetworkManager[729]: [1789253593.3021] dnsmasq: starting /usr/sbin/dnsmasq
Sep 12 18:53:13 pistomp dnsmasq[1011]: started, version 2.91 cachesize 400
Sep 12 18:53:13 pistomp dnsmasq[1011]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset nftset auth DNSSEC loop-detect inotify dumpfile
Sep 12 18:53:13 pistomp dnsmasq[1011]: chown of PID file /run/NetworkManager/dnsmasq.pid failed: please add capability CAP_CHOWN
Sep 12 18:53:13 pistomp dnsmasq[1011]: DBus support enabled: connected to system bus
Sep 12 18:53:13 pistomp dnsmasq[1011]: no upstream servers configured - please set them from DBus
Sep 12 18:53:13 pistomp dnsmasq[1011]: cleared cache
Sep 12 18:53:13 pistomp dnsmasq[1011]: setting upstream servers from DBus
Sep 12 18:53:13 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53(via wlan0)
Sep 12 18:53:13 pistomp NetworkManager[729]: [1789253593.3664] device (wlan0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Sep 12 18:53:13 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 1.168.192.in-addr.arpa
Sep 12 18:53:13 pistomp dnsmasq[1011]: cleared cache
Sep 12 18:53:13 pistomp NetworkManager[729]: [1789253593.3697] device (wlan0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Sep 12 18:53:13 pistomp NetworkManager[729]: [1789253593.3700] device (wlan0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Sep 12 18:53:13 pistomp NetworkManager[729]: [1789253593.3706] manager: NetworkManager state is now CONNECTED_SITE
Sep 12 18:53:13 pistomp NetworkManager[729]: [1789253593.3734] device (wlan0): Activation: successful, device activated.
Sep 12 18:53:13 pistomp NetworkManager[729]: [1789253593.3752] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 12 18:53:13 pistomp NetworkManager[729]: [1789253593.3758] manager: startup complete
Sep 12 18:53:28 pistomp NetworkManager[729]: [1789253608.7357] device (eth0): carrier: link connected
Sep 12 18:53:28 pistomp NetworkManager[729]: [1789253608.7361] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Sep 12 18:53:28 pistomp NetworkManager[729]: [1789253608.7366] policy: auto-activating connection 'wired-eth0' (1eea9955-7683-3705-b576-e205494e3454)
Sep 12 18:53:28 pistomp NetworkManager[729]: [1789253608.7370] device (eth0): Activation: starting connection 'wired-eth0' (1eea9955-7683-3705-b576-e205494e3454)
Sep 12 18:53:28 pistomp NetworkManager[729]: [1789253608.7370] device (eth0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Sep 12 18:53:28 pistomp NetworkManager[729]: [1789253608.7372] device (eth0): state change: prepare -> config (reason 'none', managed-type: 'full')
Sep 12 18:53:28 pistomp NetworkManager[729]: [1789253608.7377] device (eth0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Sep 12 18:53:28 pistomp NetworkManager[729]: [1789253608.7382] dhcp4 (eth0): activation: beginning transaction (timeout in 15 seconds)
Sep 12 18:53:30 pistomp NetworkManager[729]: [1789253610.6539] device (eth0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Sep 12 18:53:30 pistomp NetworkManager[729]: [1789253610.6806] device (eth0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Sep 12 18:53:30 pistomp NetworkManager[729]: [1789253610.6808] device (eth0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Sep 12 18:53:30 pistomp NetworkManager[729]: [1789253610.6812] device (eth0): Activation: successful, device activated.
Sep 12 18:53:30 pistomp NetworkManager[729]: [1789253610.9174] dhcp4 (eth0): state changed new lease, address=192.168.1.74, acd pending
Sep 12 18:53:31 pistomp NetworkManager[729]: [1789253611.0390] dhcp4 (eth0): state changed new lease, address=192.168.1.74
Sep 12 18:53:31 pistomp NetworkManager[729]: [1789253611.0406] policy: set 'wired-eth0' (eth0) as default for IPv4 routing and DNS
Sep 12 18:53:31 pistomp dnsmasq[1011]: setting upstream servers from DBus
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53(via eth0)
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 1.168.192.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 254.169.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 224.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 225.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 226.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 227.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 228.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 229.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 230.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 231.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 232.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 233.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 234.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 235.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 236.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 237.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 238.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 239.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53(via wlan0)
Sep 12 18:53:31 pistomp dnsmasq[1011]: using nameserver 192.168.1.254#53 for domain 1.168.192.in-addr.arpa
Sep 12 18:53:31 pistomp dnsmasq[1011]: cleared cache`
jpremill commentedon Sep 14, 2026
@sastraxi running #3 fixed the issue for me. (did that last)
sastraxi commentedon Sep 14, 2026
@jpremill interesting -- so in the end you were able to connect with SAE! I'm curious, now that the temporary
wpa2-testprofile has been removed, does a cold boot successfully connect to wifi? And are you using the #260 branch or the pristine pi-stomp from OTA?jpremill commentedon Sep 15, 2026
@sastraxi just the OTA version afaik.
sastraxi commentedon Sep 18, 2026
I'm re-opening this for visibility. The linked PR (#260) I think works around it, but I'm not 100% confident in the solution yet.