Unstable Raspberry Pi Networked Connection with Roon Bridge

I’ve run into a very strange problem with my Schiit Yggdrasil (Yggy) connected via USB to a Raspberry Pi 3 (RPi3) running Roon Bridge.

Initially, everything was working properly. However, once I disconnect the Yggy from the RPi3, I was unable to reestablish a stable USB connection to the RPi3. When using Roon Remote running on a Windows 10 PC, I can see the RPi3 (DietPi) connected in the Networked section of the Audio Setup window (see below). However, when I try to reconnect the Yggy to the RPi3, the entire Roon DietPi group in the Networked section disappears then momentarily reappears then disappears again. This cycle repeats until I physically disconnect the Yggy’s USB connection at which point the Roon DietPi group reappears in the Networked section.

I also have an iFi micro iDSD connected to the RPi3 which is working properly (also shown in the screenshot). I’m able to disconnect/reconnect the iDSD without any issues.

Lastly, if I re-install a new Roon instance on the PC, I’m then able to successfully connect the Yggy to the RPi3, and the networked connection is stable in the Audio Setup window. But, again, once I disconnect the Yggy, I must re-install Roon before reconnecting the Yggy to the RPi3.

Any suggestions on how I might address this issue?

Seems to me the USB interface on the Yggy drains USB power? Have you tried setting USB Power to Max on yer Pi?
What distro are you running?

Edit:
Reinstalling Roon on your control point could hardly affect the endpoints USB connection it seems? Could you elaborate?

@Mikael_Ollars, Thanks for the suggestions. This is what I can tell you so far…

It appears USB Max current is enabled.

I’m running Linux version 4.9.27-v7+ (root@DietPi) (gcc version 4.9.2 (Raspbian 4.9.2-10) )

I just re-installed Roon again on my PC , but unfortunately this time the problem was not corrected.

I have a bit more information. I was able to capture a screenshot while the Roon Network section flashed and it appears that Roon was attempting to enable the Schiit DAC and it also appears to be enabling two USB ports (Audio and Audio #1) even though only one port was physically connected.

The highlighted device below is the Schiit DAC connected to the RPi3:

root@DietPi:~# lsusb
Bus 001 Device 007: ID 0d8c:0316 C-Media Electronics, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@DietPi:~#

Hi Larry

This seems very odd… I suggest we send a smoke signal sos @support

You dont have anything else connected to the USB ports? Just one (good) cable between the Pi and the Yggy?

I have some further suggestions to, like disabling the internal soundcards on the Pi. I’ll have to look the procedure upp though!

Okey, i’m back!

Disconnect everything on the Pi except power and network
Do dietpi-update first (v151 as we speak)
After reboot, do dietpi-config, Select “2 Audio Options” and select soundcard = None (Disables internal/HDMI audio)
Exit and Reboot
Display your soundcards using:

aplay -l

Your response should be:

aplay: device_list:268: no soundcards found…

Now, back into dietpi-config, select “Audio Options” and select USB Audio from the bottom of the list.
After exit and reboot, your ALSA list of soundcards should still be empty (aplay -l)
At this time Roon should not display your Pi as an endpoint. (A soundcard/output is necessary)

Now, connect your Yggy with a simple, good USB cable and allow a few seconds.
List your soundcards again, this time it should display something?
For me it looks like this:

root@DietPi:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 1: x20 [xCORE USB Audio 2.0], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

Let’s see where this takes us!

Edit: This is what it looks like in Roon after clearing all other soundcards:

1 Like

I disabled the internal soundcard and HDMI audio. Then attached the Yggy via USB and received the following results:

aplay -l output
root@DietPi:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 1: USB [Schiit Audio Gen 3 USB], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: USB [Schiit Audio Gen 3 USB], device 1: USB Audio [USB Audio #1]
Subdevices: 1/1
Subdevice #0: subdevice #0
root@DietPi:~#

lsusb output
root@DietPi:~# lsusb
Bus 001 Device 039: ID 0d8c:0316 C-Media Electronics, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@DietPi:~#

However, Roon is still flashing Enabling status every 9 seconds or so.

Once I disconnect the Yggy, the DietPi goes away as expected.

Larry, this seems most peculiar? Can you attach the Yggy to a PC or preferably a Mac and make sure it connects properly? (The Mac is also a driverless USB host, like the Pi)
I’m beginning to think something is weird with the Yggys USB… :frowning:

Yes, very strange indeed. The Yggy has been and continues to work fine on Windows, and has done so for well over two years. I just tried the Yggy via USB from a MacBook Pro and it worked as well, but when I then connected the Yggy to the RPi, I saw the same DietPi config flashing in the Network section of Roon on the MPB.

This suggests there’s an issue with the RPi, which was working previously. But I’m at a lost to explain what is causing the current failure to connect.

Just please detail the power supply you are using with the RPi as I’m wondering if its around <=1A if you having a power supply issue.

1 Like

It’s an Anker 24W Dual Port 5V / 4.8A USB Wall Charger.

One other note… not sure if this is important, but the lights on the Yggy indicate it’s trying to sync to the RPi at 192kHz.

You may well be correct, but i agree with @wizardofoz that the power supply may be delivering nasties or not enough voltage. I was also considering whether some incompatible settings from a previous USB DAC on the Pi could be still present in Roon Settings. I dont know how to clear those, though…
A different Pi and/or power supply would answer these questions i believe.

I may have missed this, but can you attach the Yggy to another Roon Bridge in your setup, and access it normally?

I would steer clear of any USB charging devices as they typically have current limiting built in… get a proper 2.5A RPi power supply and ifs thats not working then look at a different pi perhaps

Just ordered an official PS and a spare PI to test. Both should arrive tomorrow.

As a last resort I decided to re-image my RPi which corrected the issue. The RPi network connection is stable now, but Roon now shows two Yggy USB connections even though there is only one Yggy physically connected via USB. This is odd, but not a show stopper.

Thank you everyone for your time and assistance with this issue.

1 Like