Public Beta Test: Audio Without Compromise - Refining the Future of Volumio on Bookworm

[nerd]

Hey @RedEyeNinja,

Can you please download RC 4.029 and give it a thorough round up?

@volumio - thank you for quick turn around.

Kind Regards,

[RedEyeNinja]

Thank you everyone! I’ll update my Pi5 and report back.

EDIT:

My library and tracklists used for testing seems to be surviving reboots now! Thank you @nerd and @volumio!

Here’s a log:

http://logs.volumio.org/volumio/Fbceo51.html

Observations: reboot and restart process seems to be a bit longer [no big deal!] and I do not see the error messages during bootup.

[Wheaten]

Using an old 10inch Windows tablet with only 2.4GHz WiFi (those who are wondering WHY? Remote for other devices).
On V4.028 every reboot was a surprise, if WiFI would connect, so far V4.029 seems more stable related to WiFi.
OTA from V4.028 to V4.029 failed.

Checking for new Updates
? Update v4.029 is available. Do you want to Update? Yes
Starting Update...
Updating: 1% : Checking system integrity
Updating: 1% : Starting Software Update
Updating: 5% : Preparing update
Updating: 5% : Preparing update
? Update v4.029 is available. Do you want to Update? (Y/n) Update completed successfully, restarting
Restarting

[Edrian_Lois_Villanue]

Hi nerd! mind me to ask if the peppyMeter from gelo is still support in the volumio 4?
another question and problem with the lcd 7.9 inch HMDI, in every boot the volumio logo splash is still broken i also add these line in the cmdline.txt

[JohnR]

I just did an OTA update to 4.029 from 4.028 everything appears to work but I have no sound output other than the start up tones. Log file http://logs.volumio.org/volumio/0S1W4CN.html
Same set up as before Raspberry pi 2 , Pifi usb wifi

[JohnR]

Update , after about 90mins I tried to play some wav files from a USB stick and music appeared! So i went back to Radio Paradise (via the plug-in) and all works too. log http://logs.volumio.org/volumio/x7sGNnl.htmlfile

[JohnR]

Hello Nerd

Thought I would try a clean install of 4.029 on my Pi2b with Wipi USB.
The hotspot now works perfectly as does everything else I have tried.
Log file for info http://logs.volumio.org/volumio/ypRYZXw.html. Well done to all for the hard work.

[Gelo5]

@Edrian_Lois_Villanue
Peppymeter BASIC is compatible with Bookworm (4.xx).
Peppymeter screensaver - Buster (3.xx).

[nerd]

Hey @Edrian_Lois_Villanue,

Regarding your Waveshare 7.9" LCD, let’s keep all display-specific follow-ups in the existing thread dedicated to this model so the information stays consistent for everyone tracking that discussion.

Kind Regards,

[nerd]

Hey @JohnR,

Thank you for taking the time to share your results and logs.

Great to hear that the hotspot is now working correctly on a clean install of 4.029 with your Pi 2B and WiPi USB adapter, and that playback eventually resumed as expected after the OTA.

Your feedback helps confirm improvements to wireless stack stability and plugin compatibility.

Much appreciated!

Kind Regards,

[nerd]

Hey @Wheaten,

Thanks for sharing the feedback. The stability improvement on Wi-Fi reconnects in 4.029 is expected - network service ordering and retry logic were revised in this release.

I am already tracking this notifier for bug assessment.

Kind Regards,

[RedEyeNinja]

@nerd I see you’ve made a post about Touch Display, so if these logs pertain to that more, please relocate. On both my Pi4 & 5, OTA updated to 4.030, and neither display shows up on final reboot after update and the screen is on but blank. I’ve disabled Touch Display on both, rebooted and no difference.Here are the logs:

Pi5: http://logs.volumio.org/volumio/wzcOQdN.html
Pi4: http://logs.volumio.org/volumio/E3u0u6U.html

I’ll do an extended power off cycle and wait and see if either changes.

[nerd]

Hey @RedEyeNinja,

Thanks for the logs. Based on what you’ve shared and previous reports during OTA transitions, especially to 4.030, this does look like a compound plugin interaction issue affecting the Chromium stack used by the Touch Display plugin.

Initial suggestions: Process of Elimination

You’re already on the right track. Here’s what we recommend:

1. From a cold boot (power off):

   • Disable all UI-affecting plugins: PeppyMeterBasic, FusionDSP, Now Playing, Touch Display.
   • Reboot cleanly.
   • Then enable Touch Display only, and check for screen recovery.

2. If display returns:

   • Re-enable the other plugins one at a time, rebooting between each to see which one breaks Chromium or framebuffer output.

There have been prior community notes (though not formalized yet) warning that PeppyMeterBasic, Now Playing, and FusionDSP can conflict with the display layer if left enabled during an OTA update. The result is often a blank screen with an active backlight - is it not what you’re seeing?

Additional notes

• The Pi logs show Touch Display plugin is enabled but Chromium is not running properly after boot.
• This isn’t unique to 4.030 but may have been made worse by Chromium version bump, new kernel timing, or plugin state not resetting correctly after OTA.

Let us know what you find after isolating the plugin order - if a specific one is confirmed to break the display stack post-update, we can flag that in the known issues list and plugin threads.

Kind Regards,

[RedEyeNinja]

@nerd Seems the Pi4 has recovered. I’ll see about the Pi5 now. On another note, trying your “best practice” OTA update method with all plugins disabled on the PC and I saw this, so before updating, I want to make sure it’s ok and that it won’t affect versioning for next update:

[Panos70]

Guys, I don’t know what is happening but 4.30 cannot detect my XMOS DAC. 4.29 works OK. It does not show at all.

[tweed77]

@nerd
Problem with correct USB DAC detection in Volumio 4.030

Raspberry Pi 5 - 2 GB - Volumio 4.030 - USB DAC Khadas Tone 2 Marker Kit not working.
Volumio - 4.029 Khadas Tone 2 Marker Kit working ok.
Volumio - 3.832 Khadas Tone 2 Marker Kit working ok

[nerd]

Hey @Panos70,

Thank you for your report. I wonder what is that you are expecting here. Please read opening posts, where problem reporting format is explained. To summarize:

No logs = no help

No technical hardware details = no help

Kind Regards,

[Panos70]

Sure I will send the logs. I need to change to another drive first unfortunatelly.

• Board info

• Manufacturer:

• Model: Raspberry Pi Compute Module 5 Lite Rev 1.0

• Version: d041a0

• Firmware Version: 2025/05/08 15:13:17 Copyright (c) 2012 Broadcom

• • Brand: BCM2712

• Speed: 1.5 GHz

• Family: Cortex-A76

• Model: 1

• Number of cores: 4

• Physical cores: 4

• Average load: 25%

• Temperature: 46°C

[nerd]

Dear Volumionauts,

We got caught in the middle of a Raspberry Pi kernel and firmware re-base. This is not the first time it happened, and it caused version mismatches between kernel modules and core symbols. You may see errors like these in your logs:

[Sat Oct  4 12:50:01 2025] snd_usb_audio: disagrees about version of symbol _printk
[Sat Oct  4 12:50:01 2025] snd_usb_audio: Unknown symbol _printk (err -22)
[Sat Oct  4 12:50:01 2025] snd_usb_audio: disagrees about version of symbol _dev_info
[Sat Oct  4 12:50:01 2025] snd_usb_audio: Unknown symbol _dev_info (err -22)
[Sat Oct  4 12:50:01 2025] snd_usb_audio: disagrees about version of symbol _dev_err
[Sat Oct  4 12:50:01 2025] snd_usb_audio: Unknown symbol _dev_err (err -22)
[Sat Oct  4 12:50:01 2025] snd_usb_audio: disagrees about version of symbol _dev_warn
[Sat Oct  4 12:50:01 2025] snd_usb_audio: Unknown symbol _dev_warn (err -22)

This indicates that the kernel and the modules were built against different base revisions of the Raspberry Pi source tree.

I will issue a kernel downgrade build to the last known stable version, 6.12.47, to restore full module compatibility. The re-base will be reintroduced later when upstream stabilizes the matching firmware set.

Kind Regards,