Hardware & Version:
-
Device: Raspberry Pi 5 (8GB)
-
Screen: Waveshare 5.5-inch AMOLED Touch Screen (1080x1920 resolution)
-
Volumio Versions:
-
Working: v4.119 (Clean install)
-
Broken: v4.231 (Clean install / Update)
-
Issue Description: After updating or doing a clean installation of Volumio v4.231, the display becomes completely corrupted/garbled upon booting. It appears the system is failing to correctly recognize the screen driver and resolution.
For comparison:
-
On a clean install of v4.119, the boot sequence correctly displays the Volumio QR code and startup text.
- v4.119 Boot Log: http://logs.volumio.org/volumio/HmdnVa6.html
-
On a clean install of v4.231, the screen is completely garbled after booting.
- v4.231 Boot Log: http://logs.volumio.org/volumio/Paylnjz.html
Workaround Found: If I add the following line to /boot/userconfig.txt:
Plaintext
dtoverlay=vc4-kms-v3d,cma-256
Then v4.231 boots correctly, and the screen properly displays the QR code and interface.
However, hardware acceleration does not seem to be properly invoked with this workaround. Running the Glass plugin results in a noticeable performance drop and sluggish rendering, suggesting that the system is falling back to CPU software rendering (e.g., llvmpipe) rather than utilizing GPU acceleration (e.g. opengl ).
Question: Could adding this overlay manually like this have any negative impact on system performance or stability? And is this something that needs a fix in the official build?
Thanks for your help!