Hi, gkkpch.
Just wanna say thanks, for your advice.
In this case, well…i’ll wait a little more, till a beta or a RC goes out.
For me, install volumio it’s very fast, all i have to do it’s take out my NVMe and plug it on my PC and flash it with Balena Etcher…it takes less than 3 min. But, for now i’ll keep 3.8 version.
And again, if you need something to test, just let me know.
Cheers, and keep the good work. 
In Raspberry PI 5 Wireless static IP don’t work, after set and SAVE I can ping my preferred IP or enter also with putty but web interface isn’t work, if I force reboot it seem my IP are set but IP are default
Best regards
hello nerd. I thought I would try 0.69 on my Raspberry Pi model B , this has a dynamode usb wifi and a generic Dac. This has recently been working with Moode , i have used in the past with Volumio2.
I connected the monitor so i could see what was going on. It did not generate the ‘unable to set up hotspot’ message I always see on the Rpi2. The monitor did show the usual GUI message. so i connected the ethernet but I was unable to connect via the GUI so I couldn’t get a log file. I’ll try a cold start with ethernet connected.
Regards
Tried it with a cold start but still no GUI
Just to confirm that while I couldn’t find the plugin Audiophonics Evo Sabre in the official list on 0.069, manual install via the github repo works. Essentially, the plugin is needed to get the secondary screens and remote to work on Audiophonics Evo Sabre boards (volumio-plugins-sources-bookworm/audiophonics_evosabre at master · volumio/volumio-plugins-sources-bookworm · GitHub)
Dear Volumionauts,
FYI: @gkkpch, @Wheaten, @Darmur
As part of the ongoing Alpha testing for Volumio on Bookworm, it’s important to note the current situation with out-of-kernel Wi-Fi driver support. The Alpha build is based on the Raspberry Pi kernel 6.12.x.
Several Realtek USB Wi-Fi chipsets require out-of-tree modules that are not yet fully supported in this kernel, including:
Some of these modules have begun to see partial integration upstream in kernel 6.15.x, but that doesn’t help us yet, as our base kernel remains at 6.12.x for stability and compatibility reasons.
There is no magic bullet here. Supporting these chipsets properly requires manually rebuilding and validating out-of-kernel drivers against our kernel version, and this process is complex and time-consuming.
We understand the importance of reliable Wi-Fi, especially for USB-based devices, and we are working hard to address this. Your patience during this phase is deeply appreciated.
Thanks for testing and helping us improve the platform.
Kind Regards,
Hey @JohnR,
Just to clarify - I’ve reviewed the logs and noticed a subtle but important issue in your /boot/userconfig.txt:
You currently have:
dtoverlay = disable-wifi
dtoverlay = disable-bt
This is not valid syntax. The Raspberry Pi bootloader config parser is whitespace-sensitive, and lines like this will be silently ignored.
dtoverlay=disable-wifi
dtoverlay=disable-bt
The = must be used without any spaces. When written correctly, the bootloader will properly disable onboard Wi-Fi and Bluetooth at boot.
Edit the config:
sudo nano /boot/userconfig.txt
Fix the lines by removing the spaces.
Save and reboot:
Once that’s done, let’s check if the external Wi-Fi adapter initializes as expected.
Kind Regards,
Hey @frog67,
Thanks for reporting this.
To assess what’s happening with your static IP configuration on Raspberry Pi 5 (wireless), please:
Reproduce the issue - set the static IP on Wi-Fi, save, and reboot.
Connect to the device using the IP that responds (if any).
In a browser, go to:
http://<volumio_ip>/dev
Scroll to “Send Log or Bug Report”, submit the log, and post the URL here.
Once we have the system log, we’ll review what’s being applied at runtime and after boot. This will help determine whether the configuration is being overridden, ignored, or misapplied.
Kind Regards,
Hey @JohnR,
Thanks for giving 0.69 a spin on the Raspberry Pi Model B - it’s great to see such thorough cross-hardware testing.
But as much as it seems daunting: nothing starts without logs. Ever.
We love logs. We need logs.
Lack of logs makes us anxious.
We can’t sleep without a good gozillion lines of kernel and journal spaghetti.
Please go to:
http://<your-volumio-ip>/dev
Click “Submit log”, then copy-paste the link here.
No problem - you can still collect logs manually using the terminal. Here’s how:
journalctl > /data/journalctl.log
dmesg > /data/dmesg.log
cat /boot/config.txt > /data/config.log
cat /boot/volumioconfig.txt >> /data/config.log
cat /boot/userconfig.txt >> /data/config.log
lsusb -t > /data/lsusb.log
lsusb -v >> /data/lsusb.log
Important:
> means “overwrite this file or create it if it doesn’t exist”.>> means “append to the end of the file without deleting existing content”.So in the above commands, we’re combining multiple config files into config.log, and full USB info into lsusb.log.
After generating these, power off the Pi and insert the SD card into another computer. Navigate to the data partition - you’ll find the .log files there.
Copy them and share here via upload or paste key sections.
That’s our best bet if the GUI won’t come up.
Kind Regards,
Hey @domi,
Thanks for the detailed test report - great to hear your Raspberry Pi 3B + HiFiBerry DAC Plus setup is running smoothly on v0.069!
Regarding your question about the filesystem change:
Yes, the switch to a new filesystem layout is still planned. This change will require a full reflash of the SD card, as it modifies partitioning and layout in a way that cannot be performed safely via in-place update.
We’re currently targeting this change for the next major release after 0.069, potentially around version 4.005 or later, depending on testing feedback and final implementation. We’ll make a clear announcement in the release notes when that build is out.
Given that disassembling your devices is required to access the SD card, it’s sensible to wait until this version is released before reflashing again.
Thanks again for your kind words and continued support of the project.
Kind Regards,
Yes the plugin is migrated to bookworm. But for a reason I can’t explain,it doesn’t appear in the store. I’ll have a look
I want to test streaming services, so please indicate where to find the plugin on Qobuz? I found the plugin only on Spotify.
since you’re posting in the Alpha release. Qobuz Connect is on V3.812
Thanks for the answer! I’m currently on alpha 0.069, so how can I upgrade to V3.812?
You can’t. You need to flash a new SD or USB drive with the correct version.
Thanks! I get it now!)
@nerd
Maybe we could start a list of wifi dongles that currently work and try to maintain it. Some are not too expensive so I could maybe get a dongle that works while waiting. Any idea what dongles are working on this version of the kernel? txs
Hi, I guess you can’t have everything I have the same problem with the YouTube plugin. I’m using a Raspberry Pi 4 with version 3.812 and also getting the “failed to decode” error. I’ve now installed version 0.069, which I didn’t know before There, YouTube playback works and version 2.3.3 is installed. In version 3.812, the plugin overview still shows 2.33, but actually 1.42 gets installed 
That might be the reason playback doesn’t work. In 0.069, however, the internet radio is very limited. Sure, I can add stations manually, but genres and countries are not available. But that’s a topic for another time I think the last version still worked, but I’m not entirely sure anymore.
@Michael089
Please don’t pollute this topic with issues regarding V3.812.
Youtube is no longer maintained for Buster(V3.xxx), this topic is solely for Bookworm.
sorry is wrong here.