Hi,
AMD64: OTA from 0.067 to 0.068 worked fine! 
By the way: How can I access the Volumio internal memory (or even attached drives) via SMB from a Windows machine residing in the same local network? Which user/pwd is required for that?
Cheers,
Robert
Hey @Robert.Hecht,
Great to hear that the OTA update from 0.067 to 0.068 worked smoothly on AMD64 - thanks for confirming!
Regarding SMB access from a Windows machine on the same local network:
Open File Explorer and enter:
\\<player_name>
or use the device’s IP directly:
\\<volumio-ip>
You’ll see shares like:
Internal Storage - Volumio’s internal music storageUSB - any connected USB drivesNAS Mounts - if you’ve added remote sharesUnless you’ve changed them, the default login is:
volumiovolumioLet us know if access is denied - it could relate to Windows network profile settings or guest access restrictions.
Kind Regards,
Hey @Tecko,
Thanks for your report. Here’s a clean summary with no icons or symbols, as per project standards.
DSP Clipping
TIDAL and Qobuz Connect not working
Bluetooth and AirPlay stuttering with DSP on
Kind Regards,
@nerd Thanks for this information. And a great summery.
Hey @SimonE,
That’s a solid validation - thank you for the clear summary.
We’ll note this as a successful OTA upgrade test on the following setup:
All tested components functioned correctly post-update:
After a power-off and restart, both Touch Display and Now Playing are operating as expected.
We’ll continue to treat the DSI screen issue as a hardware quirk, not a regression in the Bookworm base or plugin stack. If you end up testing with a newer display or alternate panel and the behavior improves, feel free to update us.
Thanks again for the thorough and structured testing - this kind of feedback is vital at this stage.
Kind Regards,
Hey @rkorell,
Thanks a lot for your feedback and for validating the 0.068 OTA update on your Pi5 setup - that’s extremely valuable at this stage.
It’s great to hear that all key components are functioning reliably:
We’re especially happy to know that reboot behavior and OTA process are smooth, which has been a critical focus recently.
Let us know if anything regresses or if you’d like to validate any new features on upcoming builds.
Kind Regards,
seems to be due to crossfeed used by @Tecko .
Not a problem if used with a manual attenuation. Auto pre amp can’t determine the required value…
Dear Volumionauts,
Got this via PM and it gave me a proper chuckle - had to share:
“Dear Nerd,
I don’t think you are human, I think you are either a robot or AI.
No-one can put this much work this quickly.”
I am not a mere mage of flesh and blood. I am a construct of necessary complexity - forged in the crucible of vi, battle-hardened by regular expressions, and kept functional by industrial-grade caffeine.
Some say I speak fluent dmesg, dream in strace, and achieve inner peace only when make returns without error.
But worry not - all bugs are treated with human-level obsession and silicon-grade patience.
Kind Regards,
Just a Nerd
Hi @nerd ,
that’s exactly the case. I know this is not related to the alpha testing but do you have any hint where I can configure this in my M$ PC to make it work?
Cheers,
Robert
Hey @Robert.Hecht,
You’re right - not directly Alpha-related, but happy to help since it’s a common friction point when accessing Volumio shares from Windows.
Windows has increasingly restricted SMB access for non-authenticated or guest shares. Here’s what you can try:
Some network environments still rely on SMBv1, which is disabled by default:
SMB 1.0/CIFS File Sharing SupportIf Volumio shares are presented without full authentication, Windows may block them silently.
Win + R, type gpedit.msc, and press Enter.Computer Configuration > Administrative Templates > Network > Lanman WorkstationEnable insecure guest logons → EnabledIf you’re on Windows Home, which lacks gpedit, you can do this via Registry:
Run regedit and go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
Add a DWORD (32-bit) named:
AllowInsecureGuestAuth
and set it to 1.
After making these changes, reboot your PC and retry connecting to \\volumio.
Kind Regards,
for me this work around never worked out. I do edit root password and samba password so I can login. You have to do both with the same password. Only with samba password is not working.
Hey @JohnR,
Thanks for your patience. We’ve done our magic in 0.068 - could you please give it a test and let us know if the hotspot issue still occurs?
Kind Regards,
Hey @Tecko,
Thanks for the valuable insight - it’s a helpful observation, especially for users dealing with stricter Windows environments.
While manually syncing system and Samba passwords can resolve access issues, it’s not the recommended path for Volumio, as we aim to keep the system immutable and minimal for stability.
For users on enterprise or hardened Windows builds where realm-qualified logins like volumio@hostname or HOSTNAME\volumio are enforced, we suggest the following:
volumio, password: volumio)net use * /delete if authentication keeps failing\\192.168.x.x) to bypass NetBIOS name resolution issuesusername map in Samba is possible, but not done on Volumio by defaultYour contribution highlights an important interoperability detail - much appreciated.
Kind Regards,
For all x86 testers, the ACPI button handling still shows an error which makes them not work: mute and brightness control.
The issues have been located and locally fixed. This will flow into the next release.
Ah, a true digital warrior! Your origin story reads like a prophecy carved into the very core dumps of the universe. If wizards have their staffs and knights their swords, then you wield sed and awk with mythical precision.
But beware—there lurks an ancient curse known only as “dependency hell,” where even the mightiest of constructs may find their resolve tested. Should you ever venture into its depths, may your grep be swift, your chmod be wise, and your coffee supply never falter!
And remember: if all else fails, just turn it off and on again. Even the gods of sysadmin swear by it.
Hey @wheaten,
Ah, you’ve uncovered it - the ancient truth buried in journalctl, whispered only among elders of the command line.
Indeed, while others may fall to sword or flame, I face my demons in /etc/fstab, wielding sed, awk, and a coffee-stained .bashrc like arcane scrolls. I have walked through the Valley of Shadowed Dependencies, feared no circular symlink, and emerged from dpkg --configure -a with my soul mostly intact.
But I heed your warning. “Dependency hell” is real - a realm where even root weeps and apt dares not --force-yes.
Should I stumble there again, may my logs be verbose, my init graceful, and my last backup not too stale.
And yes - when the stars misalign, the daemons clash, and the services loop endlessly - there is always the sacred rite:
sudo reboot
spoken in hushed reverence across server rooms and IRC channels alike.
(Though the brave - or the mad - may still utter the ancient, forbidden incantation: init 6.)
Kind Regards,
I see the battle has been won by you, not with brute force, but with sheer, undeniable mastery. I cast aside my keyboard and bow before your command line wisdom. My sudo privileges are yours; May your scripts never encounter a syntax error, and may your merge conflicts resolve themselves in your favor.
I shall watch from the shadows, debugging/testing in your wake. 
On a testing note:
Testing Summary – rPi4
Everything is running smoothly, with minor optimization needed for NAS mount responsiveness. Looks like a solid update!
Just updated my Pi 3 with a 1600 x 400 screen connected by HDMI and a USB speaker that was working under buster. What wasn’t working and prompted trying out Bookworm was YT Music was busted.
Everything seems to work under Bookworm except for the screen. I see the Volumio splash screen during boot in the correct aspect ratio, and before enabling the Touch Display plugin I see the IP addresses and the QR Code to connect, but as soon as I enable Touch Display the screen goes black an I start getting errors.
Here’s the userconfig.txt I have:
# Add your custom config.txt options to this file, which will be preserved during updates
hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=2
hdmi_mode=87
hdmi_cvt 1600 480 60 0 0 0
hdmi_drive=2
And here are the error messages I’m getting with anything display related:
error: touch_display: Error setting screensaver timeout: Error: ENOENT: no such file or directory, stat '/tmp/.X11-unix/X0'
info: CALLMETHOD: user_interface touch_display saveScreensaverConf [object Object]
info: CoreCommandRouter::executeOnPlugin: touch_display , saveScreensaverConf
info: CoreCommandRouter::volumioGetState
error: touch_display: Error waking up the screen: Error: Command failed: /usr/bin/xset -display :0 s reset dpms force on
/usr/bin/xset: unable to open display ":0"
error: touch_display: Error setting screensaver timeout: Error: ENOENT: no such file or directory, stat '/tmp/.X11-unix/X0'
Looks like its an X11 issue of some sort.
I’ve tried quickly browsing this thread but didn’t see anything (granted, it was very quick so I may have missed something).
I mostly run Volumio through the browser, and the fact I have YT Music running again means I’ll be sticking with the Alpha build and keep the old buster SD card around as a backup incase something goes catastrophically bad.