Hey @SimonE,
Thanks again for the thorough testing and follow-up - and for confirming that the restored userconfig.txt and volumioconfig.txt put things back to a stable state for audio, even though the screen still blanks after a restart.
You’re right: given that the exact same behavior occurs with your older v3.812 SD card, and that a full power cycle reliably restores the screen, this is now pointing very clearly to a hardware-related issue, not a software regression in the Bookworm-based 0.067 build.
Help Me Replicate and Investigate
When you have a moment, could you please collect the following hardware details, using the method from this Volumio community guide?
Guide: Identifying Your Raspberry Pi Board on Volumio – A Comprehensive Guide to Revision Codes
I’m specifically looking for:
-
Exact Raspberry Pi board revision
-
Official touchscreen PCB model and revision (should be printed on the back of the display control board)
-
Whether you’re using:
- Original ribbon cable
- GPIO power for the display
- Or USB power splitter variant
This will help me try to replicate your setup here when I have the time (no promises - things are quite full during ALPHA).
Summary
At this stage, I am treating the issue as hardware-level:
- Most likely due to early DSI init race or voltage holdover on older display hardware.
- The workaround - full power cycle - is valid, safe, and confirms nothing is wrong with Bookworm Volumio itself.
- Your logs show all plugins, audio routing, and network mounts behaving correctly after cold boot.
If you decide to replace the screen later, I’d love to know if the problem resolves entirely.
Thanks again for your help improving stability testing at this level - and glad to hear the system is solid overall.
Kind Regards,