Is it expected/known for the Trixie image to fail to boot when using the imagers customisation option? It looks like it boots, does the fs resize, shows the systemd error "Failed to populate /etc with preset unit settings, ignoring: Read-only file system", many services starting/stopping then "Failed to start kernel-command-line.service - Command from Kernel Command Line." then stops a load of services and powers off (solid red LED on Pi5).
After pressing the power button to turn it back on it boots up, restarts, then goes into the desktop with the user added but no wifi (using "sudo raspi-config" to try and set the wifi SSID/passphrase errores with "Error: Device '' is not a Wi-Fi device").
I was using the Trixie image dated 2025-08-25 (similar with 2025-08-21) with Raspberry Pi Imager 1.9.6 - customising the hostname/username+password/wireless/locale.
After pressing the power button to turn it back on it boots up, restarts, then goes into the desktop with the user added but no wifi (using "sudo raspi-config" to try and set the wifi SSID/passphrase errores with "Error: Device '' is not a Wi-Fi device").
I was using the Trixie image dated 2025-08-25 (similar with 2025-08-21) with Raspberry Pi Imager 1.9.6 - customising the hostname/username+password/wireless/locale.
Statistics: Posted by burtyb — Mon Aug 25, 2025 8:19 pm — Replies 0 — Views 9