Good news,
Audiophonics evo sabre v 2.0.1 is available in bookworm now!
Test and feedback!
Thank you @olivier_audiophonics
1 Like
1 Like
Ok! I’ll let it update.
@RedEyeNinja The advice is not do that until the version is officially communicated/ released as @nerd wrote
I’m wondering how the update path is thought to be coming from the official 3.812. Will all the Volumio users out there be forced to flash their systems from scratch to benefit from releases 4.x?
Best regards,
Robert
Hi Robert,
due to necessary partition size updates, which will ensure OTA updates for the next few major Volumio OS upgrades across platforms, it unfortunately left the team to no other choice than having existing V3.xyz Volumio units reflashed.
1 Like
4.001 OTA updates on both my Pi4 systems (one with USB DAC, the other outputs to HDMI) worked just like 0.069. All good!
Log http://logs.volumio.org/volumio/k8RzTUM.html
Is v4.00x beta?
Volumio Bookworm Alpha – v4.001 / v4.002 (May 23 - 27, 2025)
Changes:
- Internal testing of update delivery infrastructure.
- Introduced and validated release channel selector.
- No functional changes or bug fixes included.
Known Issues:
Unchanged - see previous release.
Kind Regards,
1 Like
oops…reading and comprehension escaped me…
anyway…here’s a log from Pi5 8GB…192/24 FLAC thru i2s/HDMI issues have arisen since v0.068…almost like it was a mistake to allow it to play in earlier alphas? What’s going on? this is certainly not “Audio without compromise”…
Hi @nerd ,
on AMD64 and 0.069 I don’t see the 4.xxx versions in the OTA. System tells me no update available (tried test mode on and off).
Cheers,
Robert
Hey @RedEyeNinja,
Thanks for the log and detailed note. Here’s a precise breakdown of what’s going on with your Pi5 (rev a03111, 8GB) on Volumio v0.069 when attempting 192/24 FLAC playback over I2S/HDMI.
Observed Failures
The log shows multiple critical issues directly during playback:
-
alsa_output: Underrun!- repeated ALSA buffer underruns onhw:2,0 -
bcm2835-i2s: ASoC: error at snd_soc_pcm_trigger: -12- I2S driver fails to allocate DMA buffer (ENOMEM) -
i-sabre-codec-i2c: ASoC: error at snd_soc_component_update_bits: -121- codec register update fails via I2C -
This I2C failure occurs exactly when the
PeppyMeterBasicplugin is stopped:May 28 12:32:13 volumio[2044]: info: PeppyMeterBasic --- status stop May 28 12:32:13 kernel: i-sabre-codec-i2c ... register 0x21 -121
What’s Changed Since v0.068?
- The kernel version has not changed between v0.065 and v0.069:
6.12.27-v8+ #1876 - However, the log shows a new runtime conflict between
PeppyMeterBasicand the I2C codec - This results in communication loss with the DAC during playback, which was not observed in any previous logs under the same plugin state
Installed Plugin State at Failure
At the time of failure, the following plugins were installed and active:
- FusionDsp
- Spotify
- Now Playing
- PeppyMeterBasic
- Touch Display
- System Information
None of these were disabled during the test. This limits the ability to isolate cause and effect.
Alpha Test Expectations
You asked:
“What’s going on? this is certainly not ‘Audio without compromise’…”
This is an Alpha build. It includes new kernel-level audio handling, updated firmware, and plugin subsystem changes. Regressions at this stage are expected, and testers are expected to:
- Disable all plugins and retest
- Reintroduce plugins one by one to isolate regressions
- Report behavior with clear plugin state and control conditions
What You Should Do
-
Disable all user plugins, particularly:
- PeppyMeterBasic
- FusionDsp
-
Reboot and test the same 192/24 FLAC file again
-
If stable, reintroduce plugins one at a time
-
Report which plugin, if any, triggers the regression
If the issue persists in a clean plugin-free state, we’ll review firmware timing or ALSA-layer fixes.
This is exactly the type of layered failure Alpha builds aim to expose. Your report is helpful - but please complete the plugin isolation steps before concluding on system behavior.
Kind Regards,
1 Like
Hey @Robert.Hecht,
Thanks for checking.
The 4.xxx versions are currently only available to Raspberry Pi. On AMD64, the system remains on the 0.xxx OTA track for now, which is why you’re seeing “No update available”.
We’re in the process of testing a new OTA delivery infrastructure, and I’m currently rolling it out to one device family at a time to ensure stability. Once we’ve confirmed it works reliably and safely, it will be extended to other platforms - including AMD64.
We’re still in Alpha, and careful staging is critical at this point to avoid regressions across diverse hardware.
I’ll post updates as this progresses.
Kind Regards,
1 Like
Hey @jocoman,
That’s a good idea - a compatibility list would really help others testing Volumio on the Bookworm base with kernel 6.12.27. We’re already seeing several cases where chipset quirks or USB port behavior affect success.
Known Working WiFi Dongles (with current kernel 6.12.27 on .069)
Based on internal testing and community feedback so far:
Working
-
Edimax EW-7811UN v1
Chipset: RTL8188CUS (driver:rtl8xxxu)
Reliable on USB 2.0 -
Cudy WU600
Chipset: RTL8811CU
Often works with out-of-tree88x2budriver; may function natively depending on patchset -
Generic Realtek RTL8192EU
Driver:rtl8xxxu
Basic 2.4GHz support; 5GHz not available
Partially Working / Under Review
- TP-Link Archer T3U Plus (your current dongle)
Chipset: RTL8822BU
Driver:rtw88_8822buis present in 6.12.27 and we’re tracking binding behavior closely
More stable on USB 2.0, especially when internal WiFi is disabled (dtoverlay=disable-wifi)
Not Yet Working or Requires Manual Driver
-
Mediatek MT7610U-based dongles
Removed from mainline; external DKMS builds required -
Broadcom-based USB WiFi dongles
No open source support; proprietarywldriver not included
We’re also pulling in upstream rtw88 improvements to broaden Realtek USB coverage with fewer quirks and less guesswork. These updates are being folded into the 6.12 series used by the Bookworm-based builds.
Internally, I can either work on the kernel or the updater - unfortunately, I still haven’t found a reliable way to clone myself. If anyone in the community feels like submitting a
fast-clone-and-discard-if-load-is-lowpatch, it would be much appreciated.
Let me know if you’re planning to try more adapters - I’ll help identify the chipset ahead of time to save surprises.
Kind Regards,
Dear @nerd , team,
unsure, if 4.001 is eligible for OTA, but I’ve gave it a try and it worked again without any problem.
Reboot still works.
(HW) Config:
Pi5,
Raspi 2 Display (DSI),
BT remote &
Two rotary encoders on several GPIOs
Testing:
- Spotify plugin, works (my only use case).
- 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!
Regards,
Ralf
Did #1 and #2 as suggested. No go. There’s an audible click and then nothing. The DAC shows 192kHz but no sound comes thru. After taking this log, I tried and played a 96k file with no problem.
Hello ,
V4.001 has anything to do with V0.69 Bookwom or is the OTA updates from 3.812… path
Thanks
thanks
Now I have 3.812 on my RPI. In order to upgrade to 4.001 , I need to Flash or the V4.001 will appear as OTA upgrade ?
You need the alpha release like V0.069. (see post 1) From there you can OTA to V4.00x.
Keep in mind this is still Alpha.
1 Like