This release introduces a new partition layout for both Raspberry Pi and x86 platforms.
As a result:
Fresh flash is required. OTA updates from earlier versions will not proceed.
OTA partition size validation is now active. If your /boot partition is smaller than 380 MB, the update is blocked with an explanatory message shown in the UI.
This ensures future expandability and stable delivery of OTA updates.
Partition Layout Summary
Raspberry Pi
Partition
Start (MiB)
End (MiB)
Size
FS
Purpose
/boot
1
385
384 MiB
FAT32
Boot, kernel, initramfs
/imgpart
385
4673
4288 MiB
squashfs
Read-only OTA root image
x86
Partition
Start (MiB)
End (MiB)
Size
FS
Purpose
/boot
1
385
384 MiB
FAT32
UEFI boot, kernel, initramfs
/imgpart
385
6105
5720 MiB
squashfs
Read-only OTA root image
Additional Changes
Pi:
Enhanced early detection of USB Wi-Fi adapters during boot and update steps.
x86:
Further ACPI input and power event handling improvements.
Known Issues
Devices with earlier layouts must be reflashed to v4.005 or later to remain update-compatible.
Thanks for the continued testing, research, and especially the logs and links - they’re helping us build a clearer picture of where things are failing.
We’ve identified a broader issue affecting generic USB communication devices, particularly Wi-Fi and Bluetooth dongles. The problem isn’t with the drivers themselves, but rather with timing and initialization sequencing - these devices often fail to come up in time during early boot, especially under constrained or legacy hardware.
This affects a range of USB-based network devices, not just the specific models you’re using. So while newer adapters may technically be supported with in-kernel drivers, they’re still subject to these timing-related issues on current builds.
What We’re Doing
Although there are several higher-priority system-level items in progress, USB Wi-Fi and Bluetooth dongle handling is absolutely on our list, and will be addressed before we move to BETA. We’re working on improved detection, delay handling, and possibly persistent retries for slow or late-initializing USB interfaces.
Regarding the Links
Thanks for sharing the excellent reference to in-kernel supported adapters. While we’re not following that list directly, we are treating USB network devices as a dedicated category with specific handling requirements. Your input has helped validate the need to formalize support around this.
So to be clear: No, you wouldn’t be wasting your money - but you may still run into the same early boot timing issue until we roll out the fix. If you do decide to try a new adapter, please keep it around - it’ll likely work flawlessly once the USB handling is patched.
Thank you for testing and for the kind words about the public alpha of Volumio on Bookworm.
Just a quick clarification for others reading along: while Balena Etcher worked in your case, Volumio (unofficially) recommends using the Raspberry Pi Imager for creating bootable images. It ensures the most compatible partition layout and is actively maintained in sync with Raspberry Pi firmware expectations.
Great to hear System Tools and YouTube Music plugins are running flawlessly - credit to @patrickkfkan for the continued excellence on that front.
Thank you again for your consistency and attention to detail - it’s incredibly helpful.
You’ve raised an important point about the channel selector state and the presence of both /data/test-alpha and /data/alpha. Your observation is correct: earlier builds required explicit intervention (e.g., rm -rf /data/test-alpha) to expose or stabilize the channel dropdown. However:
As of v4.005, this logic has been updated and should now work cleanly regardless of leftover state files.
The presence of both /data/test-alpha and /data/alpha will no longer cause ambiguity - the client and backend are aligned under the latest OTA logic. That said, we’ll be confirming this again with v4.005 rollout just to be certain.
Also noted on the dropdown UI - you’re right, the lack of a “Save” button can be confusing, but it is by design: selection applies immediately. Still, your feedback is logged for UI refinement.
Thanks for riding out these infrastructure changes with us.
Thanks for sharing your update and for the kind words. It’s great to hear that 4.005 installed smoothly to NVMe and your system is back up so quickly - 1800 CDs is no small library to bring online! We’re especially glad to know the backup and restore plugin saved you time; feedback like this really helps validate the work we’ve put into it.
Appreciate your continued support and detailed reports throughout the alpha and beta cycles. Keep them coming.
Yes, flashing the NVMe drive directly using dd works regardless of the source system - as long as you have access to the device node (/dev/nvme0n1) and the correct permissions.
Just be absolutely sure you’re targeting the correct device. The command will overwrite the NVMe completely with the Bookworm image.
Dear @Gelo5
Not “wrong”
Your system is missing the unzip executable -
-bash: unzip: command not found
is the corresponding error message.
And if you didn’t unpack the zip-archive the dd cannot work, because the content of the zip (the .img file) is missing.
So you have to install the unzip executable.
As far as I know, you can do this with
sudo apt-get install unzip
Then restart the sequence - without wget, the zip archive is already there.
Re-Flashing 4.005 (this time according your advice with raspi-imager) has worked.
Re-Installing is more time-consuming but has worked as well.
Seen a hint regarding backup/restore few postings ago and just tried -worked like a charm, especially for detailed config for rotary encoders
System is working as expected, no error found.
BUT (mentioned by @nerd some posts ago that you had decided to disable BT support for some reasons): BT Remote is currently NOT pairable (which has worked until 4.004).
Reboot from GUI works, reboot from terminal console works as well but takes a really long time - 3-4 minutes.
(HW) Config:
Pi5,
Raspi 2 Display (DSI),
Two rotary encoders on several GPIOs
NO BT remote
Your the best. When the time comes I have about 5 different adapters that I will be able to test out for you. Regards. Really apprecitae your committment!
What a fool I am. You’re right. I unplugged the cable. Thank you very much!!! @rkorell
You’re right, but I previously unpacked it on my computer and transferred it to Rpi. Thank you
You have to connect another device (PC / Laptop/Tablet ) to a SSID that is “Volumioxxx”.
If this works, a browser window should open and you can configure basic settings for your Volumio.
It’s important, to give your device a name different from “Volumio” !
(this is part of this basic config as well as entering the WLAN credentials for your own home-network)
Now it works without the changes in /boot/cmdline.txt. Display is rotated and touch works though the touch is bit left aligned
I have kept the changes in /boot/userconfig.txt intact.
Hello Nerd A breakthrough with 4.005 !!!
Although the hotspot still doesn’t work , with the ethernet cable attached for initial setup the wifi network is found. I havn’t tried it with the ethernet cable
disconnected but here’s the log file so far http://logs.volumio.org/volumio/QTCd42R.html
Best Regards
