8c4qebzy0 Posted March 6, 2023 Share Posted March 6, 2023 I have been using the ALLO BOSS 2 DAC for some time now with the excellent raspberry image raudio, a fork of rune audio; but as these things happen with sd cards, they sometimes get corrupted. So after creating a fresh installation, there seems to be no audio coming from the DAC. I have an old SD card based on an older image, and when I use that, the DAC works fine, so it does not seem to be a DAC issue. aplay -l shows the dac to be present and available, but I hear nothing. Hardware: Raspberry Pi 3B Rev 1.2 BCM2837 • 951 MiB 4 x Cortex-A53 @ 1.20 GHz Working: rAudio 20221210 5.15.78-1 aarch64 Failing: rAudio 20230303 6.1.14-1 aarch64 The difference between the working setup and the failing setup seems to be be the Linux kernel version. How can I find out if the kernel and drivers properly support the ALLO BOSS 2 DAC? Are there perhaps know issues with the new kernel? (i could not find this to be honest, but maybe the other images are still on 5.x? - I know Moode is as I tried that yesterday and it worked out-of-the-box with proper audio) some other info on the failing setup: # cat /boot/cmdline.txt root=PARTUUID=09d2dcf4-02 rw rootwait selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 ipv6.disable=1 fsck.repair=yes isolcpus=3 console=tty1 # cat /boot/config.txt gpu_mem=32 initramfs initramfs-linux.img followkernel max_usb_current=1 disable_splash=1 disable_overscan=1 dtparam=i2s=on dtoverlay=allo-boss2-dac-audio # pacman -Qs 'firmware|bootloader' | grep ^local | cut -d/ -f2 firmware-raspberrypi 20230125-1 linux-firmware 20230210.bf4115c-1 linux-firmware-whence 20230210.bf4115c-1 raspberrypi-bootloader 20230302-1 raspberrypi-firmware 20230124-2 # /etc/modules-load.d/raspberrypi.conf i2c-dev # i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: UU -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Link to comment
argumentd Posted March 14, 2023 Share Posted March 14, 2023 I'm running into the same issue with my Raspberry Pi 4 and Arch Linux. I recently upgraded to Linux 6.1 and BOSS2 is recognized but can't actually play audio. Link to comment
FdeAlexa Posted April 19, 2023 Share Posted April 19, 2023 Hello everyone, unfortunately the problem also exists with other software: in fact I'm having the same problem with moOde 8.3.1 which is based on Linux 6.1.2. Is there any possibility to have the driver for BOSS2 aligned to release 6.1.X? Thanks to anyone who can help us and best regards, Francesco Link to comment
BH_Solly Posted April 20, 2023 Share Posted April 20, 2023 Just upgraded to Moode 8.3.1 and have the same problem as others above. My Boss 2 player is barely a year old. I'm hoping that there will be a fix available soon. It's a great DAC and I don't want to have to scrap it. Link to comment
8c4qebzy0 Posted June 24, 2023 Author Share Posted June 24, 2023 Until the fix is merged in the mainstream kernel releases, raudio can be made to play audio again on the Boss2 by running the commands at : https://github.com/raspberrypi/linux/issues/5505#issuecomment-1598650135 as raudio does not have rpi-update by default, it needs to be downloaded before you can run it: curl -L --output /usr/bin/rpi-update https://raw.githubusercontent.com/raspberrypi/rpi-update/master/rpi-update && sudo chmod +x /usr/bin/rpi-update then run the patch: rpi-update pulls/5510 hit y a few times and reboot Enjoy (like me) Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now