Complete failure with 2023.04.01

Audio Gear Talk RoPieee
1

dacf037674394b9e

@spockfish I updated my RoPieee to 2023.04.1 on my Pi4. Since updating it is not sending data to my DAC.

I have been experiencing an issue with the 2023.03 release on one of my RoPieee instances so took a flier that perhaps 04 would be better. I am now dead in the water as I stupidly updated my primary endpoint at the same time.

### Roon Core Machine

macOS Monterey Version 12.6.5
Mac Pro (Late 2013)
Processor 2.7 GHz 12-Core Intel Xeon E5
Memory 64 GB 1866 MHz DDR3

### Networking Gear & Setup Details

TrueSpeed Fibre 1GBps. True Speed router (Zyxel) providing DHCP to the network. WiFi is disabled on the TrueSpeed Router
Orbi Mesh wifi network. Hardware RBR40, Firmware 2.7.3.22
plus two satellite units providing full house coverage. Hardware RBS40, firmware 2.7.3.22
(note these use independent 5GHz wifi mesh for interconnect of the network and connected devices).

The Roon Core connects via a wired connection to one of the Orbi satellite units. Speed test on the Roon server gives: Download:362Mbps, Upload:353Mbps, Ping:2ms.
The unit that failed is connected to the same wired ethernet connection as the Core.

There is no VPN involved on the network, no anti virus and no firewall on the Roon server. I have a port forwarding rule on the TrueSpeed router to enable RoonARC connection to my Roon Server.

### Connected Audio Devices

The Roon end point is a Raspberry Pi 4 Model B Rev 1.2 running Ropiee: Software version RoPieee 2023.04.01, Kernel Version:515.92-SPCKFSH-v8+

The Pi has a Pi2AES Hat and connected via Optical to a DAVE DAC
(edit: I just enabled USB Audio and that doesn’t work either. I also used an alternAtive source to the DAVE and that is working)

### Number of Tracks in Library

8326 tracks in the library but use case is with Qobuz

### Description of Issue

RoPieee is running on the Pi4. It shows up in Roon but playing music results in no sound and then the track fails and moves to the next track. That too fails. After a few tracks I get the message “too many failures” from Roon. I have confirmed that my Roon server is working and can happily play the tracks to another end point. I’ve rebooted, Reconfigured, Rebooted, Repowered the whole system, Restarted Roon Core.

Other information.
It was previously running RoPieee 2023.01.1(0719), Kernel Version:5.15.89-SPCKFSH-v8+ without issue

2

There’s a hardware error in the logs showing an Input/Output Error.
That unfortunately doesn’t say that much, but it does explain why you don’t have audio.

Theoretically there could be a regression in the kernel.
This is the link to your working version: https://image.ropieee.io/ropieee_ose_pi4-2023.1.1-stable.20230126.719.bin

You could give that one a try to see if this fixes the issue.

3

Looks like I had a HW failure coincident with the update. The previous version is also not working. 19538d31c7468faf

4

Wow. Have you checked the physical connection from the HAT with the Pi?

5

Yes, that was my first thought when it didn’t work. I checked the power as well (separate power for Pi and Hat) but it does seem to be an ex-Hat. I have swapped in a different Hat and it is working fine. This is actually the second Pi2AES that has failed on me… I’m wondering if the ALLO Shanti dual PSU is too hot for it.

I can only assume it was a failure over a power cycle as I powered down the system as I went away for work for a week and then immediately upgraded when I got back before even playing any music…

Anyway this unit is now up and running. I’ll check the other unit I have in my workshop nect time I’l out there. Thats the one that stops with lost connection after a minute or so.

1 Like