News:

LATEST RELEASE:  FPP 9.5 - Download from here - https://github.com/FalconChristmas/fpp/releases/tag/9.5

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 17231
Latest: email@mattgreen.co.uk
New This Month: 1
New This Week: 1
New Today: 0
Stats
Total Posts: 137033
Total Topics: 17319
Most Online Today: 348
Most Online Ever: 8375
(February 21, 2026, 03:58:04 AM)
Users Online
Members: 1
Guests: 270
Total: 271

FPP 9.3 Released!

Started by dkulp, November 05, 2025, 10:56:07 AM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

dkulp

FPP 9.3 Released!

This release is primarily to address crashes and other bugs found in FPP 9.2. Every crash report from 9.2 was examined to identify crash hot spots and fixes put in place when possible. Users are strongly encouraged to upgrade as this release addresses a bunch of common problems.

NOTE: The OS level has changed slightly from 2025-09. There were some security patches to the base OS that were incorporated. Updating the OS level is optional, but encouraged.

Enhancements
  • Allow plugins to optionally monitor their settings for changes so they can update themselves at runtime instead of requiring fppd restart. (plugins will need updates to use this)
  • Update FSEQFile to not load large variable headers into memory until needed/requested
  • Developers: Use gold/mold linkers if they are installed, faster builds

Bug Fixes (since 9.2)
  • Fix crash if output is recreated while a sub-overlay model is using it
  • Fix ethtool information display for persistent net interface names
  • Fix temperature in header to respect localization settings for F vs C
  • Fix some issues with panelSize setting after upgrade from 8.x
  • Prevent some configuration of GPIO pins that are being used by capes
  • Fix some issues that may prevent eeprom signings
  • Fix for UDP sending Ping announcements for inactive network interfaces
  • Fix to prevent git development branches as showing as new releases
  • Fix BBShiftString starting wrong PRU on BBB, fixes K128 issues
  • Fix more issues with flashing to Beaglebone Black RevD 16GB eMMC
  • Fix some issues with backups to remote FPP instances
  • Fix crash if Start Playlist command is used without an index parameter or without specificing the playlist
  • Fix crash with overly large custom models (limit the size)
  • Fix some crashes with Panels with Pi Panel Hats with invalid configuration
  • Fix crash if custom overlay models have spaces instead of numbers or blanks
  • Fix crash if GPIO input pin cannot be configured as an input
  • Attempt to detect if BBB PRU cannot be started and display a "Please Reboot" warning instead of crashing
  • Fix crash if FPP Command json has a "null" instead of an empty string
  • Fix crash if using "fpp -g" to set GPIO pin without first using -G to set it to output
  • Fix crash if UDP outputs are reloaded while some slow/offline controllers had flipped to "curl" for monitoring
  • Fix crash generating stats if model overlays file is too large
  • Fix crash if Falcon v5 receiver status packet cannot be properly parsed/processed
  • Fix crash if uploading a new fseq file if that sequence is playing (prevent the upload)

Installation Instructions
If you have a system running 9.x, you can go to the FPP about page (about.php) and click on the "Manual Update" button. At that point, a big green "Upgrade" bar should appear on the main status page. Click on that to start the update process. It may take a long time to upgrade. Likely 5-10 minutes. You will need to reboot after the upgrade is complete to finish the upgrade process.
For users of FPP 8.x or older, due to incompatibilities with the underlying libraries, an "OS Level" upgrade is required.
  • Re-image - you can backup your 8.x configuration, create a new image, and restore the configuration.
  • In-place upgrade - This requires you to have the latest FPP 7.5 or newer and all updates already running on the device. On the "About" page in FPP, there is an "Upgrade OS" choice selection where the appropriate 9.3_2025-11 image can be selected. FPP will automatically download the fppos file and install the upgrade. It will take a LONG time. When done, it should reboot into 9.3. At that point, go to the Uploads tab of the FPP File Manager and delete the fppos file.
NOTE: In SOME cases, the reboot will fail due to library replacement. In that case, a power cycle may be required to get it back up and running.

IMAGES CAN BE DOWNLOADED FROM:
https://github.com/FalconChristmas/fpp/releases/tag/9.3
Daniel Kulp - https://kulplights.com

lrhorer

#1
Either I am getting senile or there is a bug in 9.3.

http://siliconventures.net/SiliconVentures/images/Screenshot_20260225_130529.png

lrhorer


Here are some diagnostics:

cat /home/fpp/media/config/interface.wlan0
INTERFACE=wlan0
PROTO=dhcp
SSID="SiliconVentures"
PSK="S1l1c0nOR10N123$%^"
HIDDEN=
WPA3=1
BACKUPSSID=""
BACKUPPSK=""
BACKUPHIDDEN=
BACKUPWPA3=

ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.58  netmask 255.255.254.0  broadcast 192.168.1.255
        inet6 fe80::ba27:ebff:fe88:10b7  prefixlen 64  scopeid 0x20<link>
        inet6 fd42:8cd7:437a:1:ba27:ebff:fe88:10b7  prefixlen 64  scopeid 0x0<global>
        ether b8:27:eb:88:10:b7  txqueuelen 1000  (Ethernet)
        RX packets 36559  bytes 4055995 (3.8 MiB)
        RX errors 0  dropped 995  overruns 0  frame 0
        TX packets 45956  bytes 10280151 (9.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 639  bytes 118260 (115.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 639  bytes 118260 (115.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:dd:45:e2  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
signal: -49.00 dBm
last seen: 0 ms ago
SSID: Hunter-Guest
Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0
DS Parameter set: channel 44

iw dev wlan0 scan | egrep -A2 'SSID:|RSN:|WPA:|signal:' | head -n 80
--
signal: -49.00 dBm
last seen: 0 ms ago
SSID: SiliconVentures
Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0
DS Parameter set: channel 44
--
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
--
signal: -49.00 dBm
last seen: 0 ms ago
SSID: culebra
Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0
DS Parameter set: channel 44
--
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
--
signal: -76.00 dBm
last seen: 0 ms ago
SSID: wifi-socket4b56
Supported rates: 1.0* 2.0* 5.5* 11.0*
DS Parameter set: channel 1
--
signal: -49.00 dBm
last seen: 0 ms ago
SSID: SiliconVentures
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 3
--
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
--
signal: -47.00 dBm
last seen: 0 ms ago
SSID: Hunter-Guest
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 2
--
signal: -48.00 dBm
last seen: 0 ms ago
SSID: culebra
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 2
--
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
--
signal: -49.00 dBm
last seen: 0 ms ago
SSID: Hunter-Guest
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 3
--
signal: -49.00 dBm
last seen: 0 ms ago
SSID: Silicon2.4G
Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
DS Parameter set: channel 3
--
RSN: * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
--
signal: -52.00 dBm
last seen: 0 ms ago
SSID: DIRECT-45-HP Officejet 5740
Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0
DS Parameter set: channel 4
--

iw dev wlan0 link
Not connected.

wpa_cli -i wlan0 status
wpa_state=SCANNING
p2p_device_address=ba:27:eb:dd:45:e2
address=b8:27:eb:dd:45:e2
uuid=b342fed3-e613-555e-8fd5-74cdd51b2a09

wpa_cli -i wlan0 logon  2>/dev/null || true
OK

journalctl -b | egrep -i 'wpa_supplicant|wlan0|dhcpcd|dhclient|authentication|assoc|reject|rfkill' | tail -n 200
Sep 11 19:11:39 Lighting1 systemd[1]: Created slice system-wpa_supplicant.slice - Slice /system/wpa_supplicant.
Sep 11 19:11:39 Lighting1 systemd[1]: Expecting device sys-subsystem-net-devices-wlan0.device - /sys/subsystem/net/devices/wlan0...
Sep 11 19:11:40 Lighting1 systemd[1]: Listening on systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch.
Sep 11 19:11:40 Lighting1 systemd[1]: Starting systemd-rfkill.service - Load/Save RF Kill Switch Status...
Sep 11 19:11:42 Lighting1 systemd[1]: Found device sys-subsystem-net-devices-wlan0.device - /sys/subsystem/net/devices/wlan0.
Sep 11 19:11:42 Lighting1 systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status.
Sep 11 19:11:44 Lighting1 rfkill[561]: unblock set for type wifi
Sep 11 19:11:44 Lighting1 rfkill[563]: unblock set for all
Sep 11 19:11:46 Lighting1 systemd[1]: Started wpa_supplicant@wlan0.service - WPA supplicant daemon (interface-specific version).
Sep 11 19:11:46 Lighting1 systemd-networkd[607]: wlan0: Configuring with /etc/systemd/network/10-wlan0.network.
Sep 11 19:11:46 Lighting1 systemd-networkd[607]: wlan0: Link UP
Sep 11 19:11:46 Lighting1 systemd[1]: Starting wpa_supplicant.service - WPA supplicant...
Sep 11 19:11:46 Lighting1 wpa_supplicant[639]: Successfully initialized wpa_supplicant
Sep 11 19:11:46 Lighting1 wpa_supplicant[687]: Successfully initialized wpa_supplicant
Sep 11 19:11:46 Lighting1 systemd[1]: Started wpa_supplicant.service - WPA supplicant.
Sep 11 19:11:47 Lighting1 wpa_supplicant[639]: nl80211: kernel reports: Registration to specific type not supported
Sep 11 19:11:47 Lighting1 systemd[1]: systemd-rfkill.service: Deactivated successfully.
Feb 25 13:40:04 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:40:12 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:40:20 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:40:27 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:40:35 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:40:43 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:40:45 Lighting1 sudo[1781]:      fpp : PWD=/opt/fpp/www/api ; USER=root ; COMMAND=/sbin/ifconfig wlan0 up
Feb 25 13:40:45 Lighting1 sudo[1786]:      fpp : PWD=/opt/fpp/www/api ; USER=root ; COMMAND=/sbin/iw dev wlan0 scan
Feb 25 13:40:50 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:40:58 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:41:06 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:41:14 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:41:21 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:41:29 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:41:37 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:41:45 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:41:52 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:42:00 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:42:08 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:42:16 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:42:23 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:42:31 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:42:39 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:42:46 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:42:54 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:43:02 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:43:10 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:43:17 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:43:25 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:43:33 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:43:41 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:43:48 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:43:56 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:44:04 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:44:11 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:44:19 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:44:27 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:44:35 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:44:42 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:44:50 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:44:58 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:45:06 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:45:13 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:45:21 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:45:29 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:45:37 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:45:44 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:45:52 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:46:00 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:46:07 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:46:15 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:46:23 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:46:31 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:46:38 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:46:46 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:46:54 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:47:02 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:47:09 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:47:17 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:47:25 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:47:32 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:47:40 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:47:48 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:47:56 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:48:03 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:48:11 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:48:19 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:48:27 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:48:34 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:48:42 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:48:50 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:48:58 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:49:05 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:49:13 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:49:21 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:49:28 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:49:36 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:49:44 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:49:52 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:49:59 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:50:07 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:50:15 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:50:23 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:50:30 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:50:38 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:50:46 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:50:53 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:51:01 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:51:09 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:51:17 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:51:24 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:51:32 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:51:40 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:51:48 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:51:55 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:52:03 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:52:11 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:52:18 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:52:26 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:52:34 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:52:42 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:52:49 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:52:57 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:53:05 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:53:13 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:53:20 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:53:28 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:53:36 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:53:44 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:53:51 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:53:59 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:54:07 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:54:14 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:54:22 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:54:30 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:54:38 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:54:45 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:54:53 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:55:01 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:55:09 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:55:16 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:55:24 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:55:32 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:55:39 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:55:47 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:55:55 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:56:03 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:56:10 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:56:18 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:56:26 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:56:33 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:56:41 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:56:49 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:56:57 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:57:04 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:57:12 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:57:20 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:57:28 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:57:35 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:57:43 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:57:51 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:57:58 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan
Feb 25 13:58:06 Lighting1 wpa_supplicant[639]: wlan0: Failed to initiate sched scan

Poporacer

I would suggest upgrading to 9.5 and any supplemental upgrades, there was a bug about that.
If to err is human, I am more human than most people.

lrhorer

In situ?  I had to fix a great many things to get 9.3 working


Support FPP

+- Recent Topics

FPP 9.3 Released! by lrhorer
February 25, 2026, 09:28:30 PM

P2.4 128X64 32S (ICND2153/TC7262) by darylc
February 24, 2026, 09:29:31 PM

Projector Controler by djmc2002
February 24, 2026, 05:30:55 PM

Trying to get lights working on one port, no luck by gthoman
February 23, 2026, 07:59:22 PM

FPP 9.5 by alman4511
February 16, 2026, 09:53:32 AM

F16V5 FW 37 Fan settings by jnealand
February 14, 2026, 07:48:45 AM

Issues with firmware update by 2Couyon
February 11, 2026, 04:45:33 PM

FPP won't connect with F16v3 by patdepri
February 11, 2026, 05:25:33 AM

LoRa plugin. Is it worth pursuing in 2026 by csmith
February 10, 2026, 09:57:30 AM

Explanation of ED (Extended Data) by dkulp
February 09, 2026, 05:58:08 PM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod