Dietpi for Allo Boss2 with Roon gives a failure

Creating a bug report/issue

I have searched the existing open and closed issues

Required Information

  • DietPi version | cat /boot/dietpi/.version
    G_DIETPI_VERSION_CORE=8
    G_DIETPI_VERSION_SUB=24
    G_DIETPI_VERSION_RC=1
    G_GITBRANCH=‘master’
    G_GITOWNER=‘MichaIng’

  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
    bookworm 0

  • Kernel version | uname -a
    Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux

  • Architecture | dpkg --print-architecture
    arm64

  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
    RPI3

Additional Information (if applicable)

  • Software title | (Roon)
  • Was the software title installed freshly or updated/migrated?
    I tried both
  • Can this issue be replicated on a fresh installation of DietPi?
    Yes

Steps to reproduce

  1. Start Roon “This may indicate a hardware og network problem”

Expected behaviour

That Roon just started. This happened before update to bookworm

Probably the boss2 audio driver is not ready for Bookworm?

Do you use wifi? Maybe bad connection?
And the message is

Roon audio file is loading slowly. This may indicate a performance or hardware problem.

and not “This may indicate a hardware or network problem”? (couldn’t find any threads posts etc with this message anywhere)

and is this the only “problem” or are you not able now to use roon?

no, it is wired. Before the update it worked fine. To test that it wasn’t a failure, I installed Dietpi from scratch and the same fault came again. It links fine, gets IP address, I don’t think it is a network problem. I read it as a problem with the driver. I don’t know enough of Linux to recognise whether this is the problem

but GitHub issue has been closed/fixed. Can you share the whole log from roon?

yes, here are two logs. One trying to play from Tidal, and one playing from my local library. Interestingly, it played from my local library, but far too fast, and after some seconds it replied with a fault message.
log 2.txt (2.1 KB)
log.txt (20.7 KB)

Here are the two logs - apparently there is something with the flow, but without being able to read it exactly, it is still my hunch that it is about the DAC-2 software. As an info: Ropiee works fine with it, but without the fine screen addition, that this version of Allo software on top of Dietpi offers. As mentioned,it worked before upgrading the dietpi software,

can you watch system resources while playing a file? You could use htop. Does memory or CPU consumption reached any limit?

Thank you for engaging :slight_smile: No unusual activity, one core now and then up to 20% otherwise 3-8%, Nothing to see on memory. What strikes me is that when playing music from my own library ig is distorted, as if it plays far too fast. If I try to play an external source it gives me the message; Unable to play, the address may have changed or it might be temporable unavailable.

can you have a look to global system log and kernel error messages while playing music?

journalctl
dmesg

Anything specific for that period of time?

Sorry, I don’t know enough to know what to look for. Here are the two files, that should contain the insights. I am not expecting you to take the time, but if you do, I will appreciate it .
dsmeg.txt (50.4 KB)
journalctl.txt (103.7 KB)

looks like system has been rebooted at Dec 06 13:42 and the log has been taken right after? At least it’s fresh clean log without anything special in.

yes, and no. It was a fresh boot, but I started Roon after the fresh reboot and before did the commands, and saw it doing the failures. So if the failure in anyway can be seen in these files, it should be there.
I find it strange that it apparently seems to work fine until I start Roon. It shows the display in the Boss2 as expected, as an example

Maybe @MichaIng has an idea what the issue could be.

I guess the fix was done after the last (classic) kernel upgrade. Hence the migration to the new firmware packages + /boot/firmware mount needs to be done first.

Makes sense to me with the behaviour I see. Is this something I easily can do - not being more than a noob?

Actually we are working on a migration to the new firmware package/layout. Be patient.

OK - thank you for the effort. I will wait patiently :slight_smile:

Any update on this? If not what is the recommended method to recover from a failed SD card? Can an older DietPi image with a kernel version that works with Boss2 hardware be downloaded anywhere?

What do you mean by this? Is the system not booting anymore? What has been done before? Any update you did? And which image you are looking for?

Yes system not booting from the old SD card - SD card hardware failure confirmed on my linux desktop PC, the SD card has no partitions and new partitions can’t be created.
Nothing done before, the RPi / DietPi failed to boot up after a power failure.

I’ve tried the latest image version 9.0.2 on a new SD card but the Boss2 DAC doesn’t work correctly - roon bridge just skips through tracks, speaker-test -t wav -c 2: gives no audio output.

I’ve since however found the original DietPi image version 8.5.1 that I downloaded back in 2022, so back up and working correctly again - NB. I had to stop it from auto updating on first boot by disconnecting the ethernet/internet temporarily.

I’m hoping to be able to run the latest version of DietPi again at some stage.