Just my two cent.
Iâve been using the Innomaker DAC PRO for all my Bookworm testing, which also features the ES9038Q2M. Iâve successfully tested a wide range of audio files, including WAV, FLAC, MPx, and DSD, without any issues.
The problem might be related to the dt overlay being used. Please try the same tests with the Innomaker DAC PRO or Allo Katana overlay and let me know your results.
Sorry, must ask the time-honoured question, resented by all development teams - Is there an anticipated or target date to have âTidal Connectâ (and not to discriminate, âQobuz Connectâ) functioning?
Yes, the current source from https://github.com/volumio/volumio-oscan be used to build a Bookworm-based Volumio image for the Banana Pi M1, but with some important caveats:
Kernel Compatibility
Armbian-based targets generally work best. If youâre using a custom Armbian rootfs, ensure it matches the Volumio Bookworm expectations (Debian 12, systemd init, nodejs 20 support, etc.).
Audio Output
HDMI or onboard I2S audio support may require tweaks in /boot/userconfig.txt and ALSA configuration. USB DACs are typically the safest path to success on first build.
Known Issues
As of Volumio v4.x (Bookworm), some Allwinner devices may experience issues with:
Broken MPD hardware volume if no proper mixer is exposed
Inconsistent Wi-Fi or Ethernet unless u-boot and kernel are up-to-date
HDMI audio being disabled or non-functional due to kernel flags
Fair question - and yes, a dreaded one for any dev team.
Right now, there is no official ETA for TIDAL Connect and Qobuz Connect to function under the Volumio v4 Bookworm BETA. The root blocker is still the OpenSSL 1.1 vs 3.x incompatibility between:
Backend plugins (rebuilt for Bookworm with OpenSSL 3.x), and
Remote service APIs (MyVolumio cloud infrastructure, still on OpenSSL 1.1.x).
This isnât a simple patch fix. It requires either:
Rebuilding and redeploying backend cloud services with OpenSSL 3.x compatibility, or
Introducing compatibility layers that wonât break Volumio v3 (Buster-based) systems that rely on OpenSSL 1.1.x.
Both approaches need careful regression testing across the ecosystem. Until this architectural bridge is cleanly resolved, the âConnectâ features remain non-functional in the Bookworm branch.
The community will be notified once a compatible implementation is confirmed. Until then, regular streaming (within the Volumio interface) remains the functional alternative.
Hi @nerd , Thank you for your info. I will try to build it and test on my board.
Also about my old RPi1B, i found the issue is that the dhcpd is crashed with segmentation fault. I set static IP for my network interface and it seems working. I can ping internet. But i lead to another issue.
/usr/local/bin/volumio: line 113: 947 Illegal instruction node /volumio/ut ils/tests/checkRemoteEndpoints.js
volumio@volumio:~$ node
Illegal instruction
I think the nodejs is not working at all.
Im on 4.010 on my RPI4.
I want to go to the next version with ota, but system says Iâm on the latest release.
I know that 4.012 is available. is this a bug?
Regarding your RPi1B issue - the Illegal instruction error from node is expected. The current Volumio v4.x builds use Node.js 20 binaries which are compiled for ARMv7+ (armhf), and not compatible with the ARMv6 CPU in the Raspberry Pi 1 Model B.
To clarify: Volumio v4.x (Bookworm) has officially dropped support for ARMv6 devices such as the RPi1 and Pi Zero. This was not due to any single technical issue like Node.js, but rather a broader strategic decision based on:
Severely limited CPU and RAM on ARMv6 hardware, which can no longer meet the performance needs of modern Volumio features
Lack of ongoing testing and maintainership for ARMv6 targets
Increasing complexity in maintaining compatibility across the ecosystem (plugins, UI, streaming, Bluetooth, etc.)
Streamlining build infrastructure to focus on actively used platforms (ARMv7+, ARM64, x86_64)
That said, nothing prevents community members from working on unofficial community ports. If you are motivated to build a Volumio Bookworm image for ARMv6, youâre absolutely welcome to do so. Just note it will require:
A compatible Node.js 20 binary for ARMv6 (which is not provided upstream and may need to be cross-compiled)
This has been addressed several times already during both the ALPHA and BETA cycles.
Starting from v4.003, Volumio includes a Release Channel Selector. If you are on 4.010 and not seeing 4.012 via OTA, itâs because your system is still set to the Stable channel - and 4.012 is currently in the Test channel only.
To change this:
Go to http://<your-volumio-ip>/dev
Look for Release Channel Selector
Switch to Test
Reboot, then check for updates again
This infrastructure was one of the key deliverables during the ALPHA testing phase, specifically outlined here:
I am now running 4.013 and am happy to report that my tp-link archer T3U plus AC1300 is working!
Way to go !!!
I tried searching for a web radio and that causes a restart. where do i find the prototype plugin?
cheers
Hi @Wheaten, I tested web radio, both playing an existing stream and then adding and playing a new station (m3u format). These worked fine without crashing. Is there a specific webradio test case I can try?
I donât have Tidal or Qobuz.
