Public Alpha Test: Audio Without Compromise - Volumio on Bookworm Begins

Volumio Development Volumio Beta Testing
, , , ,
606

Yup, confirmed as working

607

Hi again @nerd !

I can.t do an OTA update from 4.003 to 4.004. Is it possible or am I missing something?
I tried all update channels in dev. Do I need to do a fresh install?

kind regards /C

1 Like
608

A post was merged into an existing topic: About the Introduce Yourself category

609

What is the best way to go from Buster to Bookworm if booting is from an nvme drive (not an SD card)?

610

Important Notice: Alpha Channel Update Fix (v4.004)

Weā€™ve identified an issue affecting updates to v4.004 via the Alpha channel:

  • The updater client checks for the file /data/test-alpha
  • The backend, however, creates /data/alpha

This mismatch will be resolved in the next build.

How to update to v4.004 (Alpha channel):

If youā€™re on a previous version and not receiving the update:

  1. SSH into your Volumio device

  2. Run the following command:

    touch /data/test-alpha
reboot

  3. After reboot, the device will correctly detect and apply the v4.004 Alpha update

Thank you for testing and for your patience while we finalize the new release infrastructure.

Kind Regards,

1 Like
611

Hey @Gelo5,

The best and currently supported way to migrate from Buster to Bookworm when booting from an NVMe drive is through a fresh install, following these steps:

  1. Download and flash a 4.xxx Bookworm-based image to a microSD card.
  2. Boot from the microSD card and perform initial configuration.
  3. Use the ā€œInstall to Diskā€ feature from the System UI to install Volumio onto the NVMe drive.

Important: This method performs a full wipe of the NVMe target.
Make sure to back up any important data beforehand - music files, playlists, configuration, etc.

Let us know if you hit any issues during the process.

Kind Regards,

612

Hey @JohnR,

Thanks again for providing the logs - and for the extra effort it took to get them off the Pi 1B. That gave us what we needed.

Regarding your config question: youā€™re correct - you didnā€™t add anything manually. The entries in config.txt are applied automatically by Volumio OS as part of its standard setup. We review them to detect if anything was enforced or altered that could affect Wi-Fi behavior, especially in edge cases like yours.

Current Development Priorities

To give you clarity on where your issue stands in the broader context, hereā€™s how weā€™re prioritizing work internally:

1. System-Level Regressions - Highest Priority

Issues affecting core functionality (like broken functionality or boot failure) across multiple devices or versions. These are tackled immediately.

2. Global OS Changes - High Priority

This includes changes to kernel, firmware handling, and core services in the Bookworm base. These are critical for stability and compatibility across platforms.

3. Device-Specific Recipes - Medium Priority

Support for individual devices (like Pi 1B) and their quirks, including things like USB initialization order or missing firmware paths. Your case nearly fits here.

4. Plugins - Low Priority

Plugin-related bugs and enhancements take a backseat until the core system is solid.

5. Edge Cases - Lowest Priority

Rare hardware configurations, unusual adapters, or legacy devices (like early Pi boards) fall into this category. Fixes are still pursued, but may take more time due to complexity and lower impact.

Your Case

Your setup is an edge case, but it has helped surface issues related to early board handling and USB Wi-Fi firmware behavior. A fix is possible, but itā€™s going to take some careful integration work to avoid breaking things for everyone else.

Iā€™ll update you once weā€™ve got something ready to test.

Kind Regards,

613

The problem is that it does not want to boot from the SD card (Bookworm) if there is Buster on the NVMe disk

614

Hey @Gelo5,

The bootloader may prioritize the NVMe drive, depending on the configured boot order you have set. In that case, an existing Buster-based install on NVMe can prevent the system from booting the Bookworm image from the SD card.

This approach using dd should work:

wget https://updates2.volumio.org/pi/volumio/4.004/Volumio-4.004-2025-05-29-pi.zip
unzip Volumio-4.004-2025-05-29-pi.zip
sudo dd if=Volumio-4.004-2025-05-29-pi.img of=/dev/nvme0n1 bs=4M status=progress conv=fsync

That will perform a direct flash of the 4.004 Bookworm image to the NVMe disk.

That said, we recommend waiting if youā€™re not in a rush - a new partition layout is currently being finalized and will impact how storage expansion and future upgrades are handled, especially on USB and NVMe devices.

Kind Regards,

1 Like
615

Hi @nerd !
I did an update from 4.003 to 4.004 wit SD card and then installed 4.004 to nvme disc.
Tried to intall touch display plugin but got some error. What to do?

log: toch display install error

Maybe other plugin installs may shox same behavior?

best regards / C

616

I di did this on an earlier alpha release. If plugin testmode is not enabled, itā€™ll try to install the old plugin. You need to reflash, enable plugin testmode and try again.

617

Hi @nerd
This worked for my Pi4.
Thanks.

618

ok. I will try that.
I think itĀ“ā€™s little odd since I flashed from sd card to nvme and also enabled plugin test mode.

Anyway, Thanks for your advice

best regards / C

Edit: That didnā€™t work.

619

Hey @ClaesM,

Thanks for posting the log.

The entries are timestamped:

May 29 16:54:17

Since today is May 30, 2025, could you please confirm - was this log generated today, or are you reviewing a log saved from yesterday?

This matters because of the error message:

E: Release file ... is not valid yet (invalid for another 16h ...)

This typically means the system clock was set incorrectly at the time the log was generated, causing APT to reject repository metadata as not yet valid.

If the Log Was Generated Today

Then the system clock is still out of sync and should be corrected. You can do this by:

sudo date -s "2025-05-30 14:00:00"

(adjust to current date and time)

Then run:

sudo apt-get update

This should resolve the release file validity errors and restore package installation.

Let us know once you confirm the timing of the log.

Kind Regards,

1 Like
620

Hey @Lintbf,

Thanks again for your interest in Qobuz Connect support.

To clarify the current development status:

Qobuz Connect on Bookworm - Not Yet, But Planned

There is a plan to bring Qobuz Connect to the Bookworm-based Volumio builds, but not until work on the current production builds is complete. The development team is currently focused on fixing remaining issues in the stable channel and ironing out regressions reported by the community.

So while itā€™s not cancelled or forgotten, thereā€™s no immediate ETA. Once production stabilizes, focus will shift back to bringing features like Qobuz Connect into the Bookworm line.

Weā€™ll make sure to update the thread when that happens so youā€™re not left guessing.

Kind Regards,

2 Likes
621

Hi!

My log was from today, just about 2 hours ago. Anyway, system clock was not set correct.

I used the commands you showed me and everything works now! This have never happen for me earlier.

Thanks a lot!
/C

622

@nerd
I know a wifi dongle is not a priority, but I am anxious to get on this new release. I did some research on adapters that work with this kernel and I found this link.
Would it narrow down a decent adapter that would work? The ones that you have indicated that work, are very old almost obsolete adapters, unless Iā€™m reading it wrong. Thanks and no worries until you get to it.
J.

623

Congratulations to @nerd and all others responsible for the public alpha of Volumio on Bookworm. Installed it just now with only one hiccup, wouldnā€™t boot with image created with Rufus but worked fine after imaging with Balena Etcher. Installed just two plugins, System Tools and Youtube Music (thanks @patrickkfkan for all your work on a great plugin) and both work flawlessly.

System Information
OS info
Version of Volumio: 4.004
Hostname: musicbox2
Kernel: 6.12.27-v7l+
Governor: performance
Uptime: 0 days, 0 Hrs, 40 Minutes, 26 Seconds
Audio info
Hw audio configured: IQaudIO DAC Plus
Mixer type: Hardware
Number of channels: 2
Supported sample rate: 22050 44100 48000 88200 96000 176400 192000 384000
Board info
Manufacturer: Raspberry Pi Foundation
Model: Raspberry Pi 4 Model B Rev 1.5 Raspberry Pi
Version: b03115
Firmware Version: Apr 29 2021 17:11:25 version c2f8c388c4ee37ad709ace403467d163e8dd91ce (release)

Regards,

624

Dear @nerd , team,

Today OTA to V4.004 worked again without any problem.
Reboot still works.

To my big surprise it was NOT necessary to explicitely enable the channel selector
(connect via SSH and run: rm -rf /data/test-alpha) as described in this post .

Checking file system my volumio have both files:

  • The updater client checked ā€œ/data/test-alphaā€
  • The backend created ā€œ/data/alphaā€

both described in this post.
Should I remove/touch these files? As mentioned, update to 4.004 has successfully worked and channel selection works, too ā€¦
(The drop down for channel selection worked immedately without intervention.

  • It is a little bit confusing that there is no ā€žsaveā€œ button at this drop-down - but it works without, so itā€˜s good to meā€¦)

(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

625

Hello Nerd hereā€™s the log file for an OTA update on the 2B from 0.69 to 4.04
still using ethernet.
http://logs.volumio.org/volumio/FvU0H1V.html

I might try a new usb wifi adapter, Pi Hut are selling a dual band one which doesnā€™t need drivers. Let me know if Iā€™ll be wasting my money

Thanks