Error with HiFiBerry DAC2 Pro

Hi! :slight_smile:

After having my eye on this thing for a while, and testing it out on an RPi 3 I had lying around I finally decided to build a RPi 4 Zynthian myself.

However I’m having some issues getting the HiFiBerry DAC2 Pro working.

Some observations:
A) If I select the dummy audio interface everything boots OK (UI included) and the sound card is showing up with aplay -L and in alsamixer
B) If I configure the DAC2 Pro as dtoverlay=hifiberry-dacplus the UI won’t start and I get the generic error screen - which keeps shutting down, showing the terminal for a bit, and then coming back.

Maybe worth noting:

  • I’m running with a screen on the DSI connector - works great in itself.
  • I’ve updated the software from the webconfig.
  • In case A I can do normal reboots from the webconfig. In B it seems to shut down, but doesn’t reboot.
  • I’ve tried getting qjackctl up and running with the X11 option in Putty - but can’t get that to work.

Any suggestions would be hugely appreciated :slight_smile:

/Thomas

Im getting this in the log:

  Nov 26 08:44:35 zynthian startx[844]: jackdmp 1.9.14
Nov 26 08:44:35 zynthian startx[844]: Copyright 2001-2005 Paul Davis and others.
Nov 26 08:44:35 zynthian startx[844]: Copyright 2004-2016 Grame.
Nov 26 08:44:35 zynthian startx[844]: Copyright 2016-2019 Filipe Coelho.
Nov 26 08:44:35 zynthian startx[844]: jackdmp comes with ABSOLUTELY NO WARRANTY
Nov 26 08:44:35 zynthian startx[844]: This is free software, and you are welcome to redistribute it
Nov 26 08:44:35 zynthian startx[844]: under certain conditions; see the file COPYING for details
Nov 26 08:44:35 zynthian startx[844]: JACK server starting in realtime mode with priority 10
Nov 26 08:44:35 zynthian startx[844]: self-connect-mode is "Don't restrict self connect requests"
Nov 26 08:44:36 zynthian startx[844]: creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
Nov 26 08:44:36 zynthian startx[844]: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
Nov 26 08:44:36 zynthian startx[844]: JackTemporaryException : now quits...
Nov 26 08:44:36 zynthian startx[844]: Cannot initialize driver
Nov 26 08:44:36 zynthian startx[844]: JackServer::Open failed with -1
Nov 26 08:44:36 zynthian startx[844]: Failed to open server
Nov 26 08:44:36 zynthian startx[844]: Cannot connect to server socket err = No such file or directory
Nov 26 08:44:36 zynthian startx[844]: Cannot connect to server request channel
Nov 26 08:44:37 zynthian startx[844]: Cannot connect to server socket err = No such file or directory
Nov 26 08:44:37 zynthian startx[844]: Cannot connect to server request channel
Nov 26 08:44:38 zynthian startx[844]: Cannot connect to server socket err = No such file or directory
Nov 26 08:44:38 zynthian startx[844]: Cannot connect to server request channel
Nov 26 08:44:39 zynthian startx[844]: Cannot connect to server socket err = No such file or directory
Nov 26 08:44:39 zynthian startx[844]: Cannot connect to server request channel
Nov 26 08:44:40 zynthian startx[844]: Cannot connect to server socket err = No such file or directory
Nov 26 08:44:40 zynthian startx[844]: Cannot connect to server request channel
Nov 26 08:44:41 zynthian startx[844]: jack server is not running or cannot be started
Nov 26 08:44:41 zynthian startx[844]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Nov 26 08:44:41 zynthian startx[844]: ZynMidiRouter: Error connecting with jack server.

qjackctl just flat out doesn’t work over XForwarding. if you apt install patchage that works fab.

Can you paste the output of aplay -l on the cli and the jack config line from the webconfig as it’s an issue with jack starting.

1 Like

Here’s what aplay -l is saying:

null
    Discard all samples (playback) or generate zero samples (capture)
default:CARD=Dummy
    Dummy, Dummy PCM
    Default Audio Device
sysdefault:CARD=Dummy
    Dummy, Dummy PCM
    Default Audio Device
dmix:CARD=Dummy,DEV=0
    Dummy, Dummy PCM
    Direct sample mixing device
dsnoop:CARD=Dummy,DEV=0
    Dummy, Dummy PCM
    Direct sample snooping device
hw:CARD=Dummy,DEV=0
    Dummy, Dummy PCM
    Direct hardware device without any conversions
plughw:CARD=Dummy,DEV=0
    Dummy, Dummy PCM
    Hardware device with all software conversions
default:CARD=Headphones
    bcm2835 Headphones, bcm2835 Headphones
    Default Audio Device
sysdefault:CARD=Headphones
    bcm2835 Headphones, bcm2835 Headphones
    Default Audio Device
dmix:CARD=Headphones,DEV=0
    bcm2835 Headphones, bcm2835 Headphones
    Direct sample mixing device
dsnoop:CARD=Headphones,DEV=0
    bcm2835 Headphones, bcm2835 Headphones
    Direct sample snooping device
hw:CARD=Headphones,DEV=0
    bcm2835 Headphones, bcm2835 Headphones
    Direct hardware device without any conversions
plughw:CARD=Headphones,DEV=0
    bcm2835 Headphones, bcm2835 Headphones
    Hardware device with all software conversions
default:CARD=sndrpihifiberry
    snd_rpi_hifiberry_dacplus, HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0
    Default Audio Device
sysdefault:CARD=sndrpihifiberry
    snd_rpi_hifiberry_dacplus, HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0
    Default Audio Device
dmix:CARD=sndrpihifiberry,DEV=0
    snd_rpi_hifiberry_dacplus, HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0
    Direct sample mixing device
dsnoop:CARD=sndrpihifiberry,DEV=0
    snd_rpi_hifiberry_dacplus, HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0
    Direct sample snooping device
hw:CARD=sndrpihifiberry,DEV=0
    snd_rpi_hifiberry_dacplus, HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0
    Direct hardware device without any conversions
plughw:CARD=sndrpihifiberry,DEV=0
    snd_rpi_hifiberry_dacplus, HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0
    Hardware device with all software conversions

I’ll try out patchage.

Patchage did indeed work fab :slight_smile:

Ok, after having tried a whole lot of things I finally did a rpi-update - and now everything works.

1 Like