There is a very revealing detail - and potentially linked to the behavior you observed which lines up with what I found in your system log:
May 20 17:09:43 sibermusicalpha rpi-eeprom-update[766]: BOOTLOADER: up to date
May 20 17:09:43 sibermusicalpha rpi-eeprom-update[766]: CURRENT: Wed Jan 11 17:40:52 UTC 2023 (1673458852)
May 20 17:09:43 sibermusicalpha rpi-eeprom-update[766]: LATEST: Thu May 8 15:21:35 UTC 2025 (1746717695)
So although the bootloader reports “up to date”, the actual installed version is from January 2023, and there’s a newer one available from May 2025.
Why This Matters
The Raspberry Pi bootloader is responsible for initializing the DSI display before the Linux kernel takes over. In older versions:
The DSI screen often fails to reinitialize properly on warm boots.
Rotation state and framebuffer persistence can also behave unpredictably (as you saw with the upside-down splash).
Full power loss (removing the cable) resets all hardware correctly, which is why it temporarily fixes the issue.
This worryingly matches your symptoms: screen OK after cold boot, blank after reboot.
“Worth a shot” Action
Please run the following to upgrade your Pi’s EEPROM bootloader to the latest stable version:
sudo rpi-eeprom-update -a
sudo reboot
After rebooting, test whether the screen reliably initializes on restarts (no power cycling).
Also Make Sure
Your current /boot/userconfig.txt should remain as:
Hi @nerd,
After restoring userconfig and volumioconfig, the system is as it was. Screen stays off with a restart, but all music sources/plugins I use are working. After a power off/on, screen and music are working properly.
I also tried my v3.812 SD card in the same set-up and I have exactly the same results. Must be the screen right?
In any case, until I get a new screen, the system works reliably with the power off/on workaround.
Thanks so much for all your help. I’m really impressed that Bookworm Volumio is so stable (other than restarts on my system).
I’ve been out of the loop while moving and I see others are now looking at DSD output above. I’ve updated to v0.067 via OTA last night, after I installed a new HAT on a Pi4 8gb [I’m using a SMSL DO400 as DAC]:
The link above is the one with the most English for the description. I’ve tried both “Audiophonics ES9028/9038 DAC” and “HifiBerry DAC” options for output. The pics in the link with regards to the jumpers and the config of i2s modes/output appears to be wrong, but having played around with it, I’ve gotten it to output the correct channel by just leaving it as is [no jumpers]. Meanwhile, I also played with the jumpers for MCLK_modes…this is where it gets interesting as I can not rely on the pics in the link to correspond to what actual mode it’s in…however, previously with another HAT, the i2s/HDMI output will max out at 96/24, but in MCLK_mode4, I was able to get it to play 192/24 thru i2s but no DSD output. The log I have attached is supposedly in MCLK_mode2 and it was able to output DSD thru i2s as PCM. In the Playback options, it was left as DSD native. HOWEVER!1!!! It played like 3 songs and then audio completely dropped out when I tried to load another DSD file, with only a slight click and then white noise. In this mode, it also maxes out at 96/24 otherwise.
For some reason, this seems hopeful for me if Volumio will eventually support these audio HATs so that I can reliably use 1 output for everything but I’ll be happy if I have to use coax/optical for 192/24 FLAC and below and switch to i2s just for DSD or DOP. From the description in the link, it appears that moode already has full support for these hats for DSD via i2s.
player: Decoder is too slow; playing silence to avoid xrun
I²S interface issues are suspected:
i2s: warning: unexpected frame size, possible clock mismatch
These are consistent with an unstable master clock or format transitions the DAC and Volumio stack cannot recover from cleanly.
Why This Is Happening
The Ustars Audio R19 board is not supported by any existing Volumio device-tree overlay. Its HDMI-style I²S output is non-standard, and there is no known kernel-level support or documentation available to configure it properly.
Jumper-controlled MCLK modes cannot signal the kernel to adapt clocks dynamically, which leads to issues when switching between PCM and DSD or between DSD sample rates.
This Is Outside Alpha Scope
The Volumio Bookworm Alpha is focused on ensuring base functionality and hardware compatibility that aligns with the upstream Linux kernel.
Boards like the Ustars Audio R19:
Are not part of the officially tested hardware
Lack upstream kernel support
Do not ship with a dtoverlay or standard identification
Requests for support of such boards should begin with the upstream kernel or manufacturer.
Volumio Can Still Assist
If you’re willing to proceed:
Please start a dedicated thread on the Volumio forums for the Ustars Audio R19.
Once that thread exists, we can help with:
Reviewing high-res photos or board scans
Pin-mapping the HDMI-style I²S connector
Drafting a minimal dtoverlay for testing
Guiding through manual clock and driver configuration
This avoids diluting the scope of the Alpha testing thread and provides a clear path for reproducible testing and community feedback.
Suggestions
Use coaxial or optical for PCM up to 192 kHz
Use I²S with fixed jumper settings only for DSD playback in DoP mode
Avoid switching formats mid-playback
Increase buffer sizes in Playback Options to reduce underrun risk
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?
Important to mention that after several attempts, a usercofig.txt of …
dtoverlay=vc4-kms-dsi-7inch
lcd_rotate=2
Ends up with a grey lit screen even after power on/off. All music and plugins work.
With
lcd_rotate=2
display_hdmi_rotate=2
Display (and everything else) works properly after power on/off.
Contents of /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 270.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 1
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 270.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 2
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 270.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
processor : 3
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 270.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3
Hardware : BCM2711
Revision : c03112
Serial : 10000000a65e7bfe
Model : Raspberry Pi 4 Model B Rev 1.2
Contents of /proc/device-tree/compatible
raspberrypi,4-model-b brcm,bcm2711
Touchscreen info:
Raspberry Pi Display V1.1 2015
E305654 94V-0 5015
I am testing alpha 0.068 now om my new RPI5.
Should qobuz connect be working? No USBdisk problems now. Installation runs smooth go now checking plugins.
DSP is working only lot of clipping messages I have to add -4.5 to the gain speakers. And preamp is on. Now playing is working Touch display is working for kiosk mode in now playing plugin.And displaying on my 4k oled screen. Tidal and Qobuz connect not working
Bluetooth and Airplay working not with dsp on then stuttering
Update (OTA) to 0.068 has worked without any problem - reboot has worked directly, again.
Pi5, Raspi 2 Display (DSI), BT remote & two rotary encoders on several GPIOs
Mainly using spotify, works.
Touch display (and corresponding plugin) works
Rotary encoders are working
BT remote is working
WiFi is working (can access from laptop / phone).
“Now Playing” plugin works
Great work!
