Hifiberry Dac+ Pro and RPI4 combo not working

[rgro]

I would try the hifiberryOS as a test, If you have bad hardware, they are going to ask you to do this step anyway.

Also, can you test your pi4 with another DAC hat?

I don't have another DAC hat, sorry.

A couple days ago, I did test with hifiberryOS and everything worked perfectly. Just tested again a few minutes ago and, w/the hifiberryOS, all is still working just fine. So, most definitely not a hardware problem.

[paul-]

Well then record what overlay is being used and all loaded modules when running HifiberryOS. But I know others are using this card just fine, so I'm not sure what the problem is with these new batch cards.

[rgro]

Well then record what overlay is being used and all loaded modules when running HifiberryOS. But I know others are using this card just fine, so I'm not sure what the problem is with these new batch cards.

Paul,

I have no idea how to do that. The HifiberryOS system webpage doesn't have anywhere near the various options that piCoreplayer does. There is no place to see diagnostics, configurations, etc. It's quite opaque but I guess that's fine for most users.

If you can tell me what commands to type in using SSH to get the overlay info, I may be able to get you some information that way.

That said, I did SSH into HifiberryOS and typed in DMESG...pure luck that I got anything. Nonetheless, here's part of what I got--don't know if it's helpful or not.

[ 4.543563] snd-rpi-hifiberry-dacplus soc:sound: ASoC: failed to init link Hi FiBerry DAC+: -517
[ 4.764310] cfg80211: Loading compiled-in X.509 certificates for regulatory d atabase
[ 4.803988] bcm2835_mmal_vchiq: module is from the staging directory, the qua lity is unknown, you have been warned.
[ 4.803994] bcm2835_mmal_vchiq: module is from the staging directory, the qua lity is unknown, you have been warned.
[ 4.857332] bcm2835_v4l2: module is from the staging directory, the quality i s unknown, you have been warned.
[ 4.860268] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0
[ 4.862987] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
[ 4.873256] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[ 4.875049] snd-rpi-hifiberry-dacplus soc:sound: ASoC: failed to init link Hi FiBerry DAC+: -517
[ 4.876841] snd-rpi-hifiberry-dacplus soc:sound: ASoC: failed to init link Hi FiBerry DAC+: -517
[ 4.879050] snd-rpi-hifiberry-dacplus soc:sound: ASoC: failed to init link Hi FiBerry DAC+: -517
[ 4.880188] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev /video13
[ 4.881559] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /de v/video14
[ 4.882036] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /de v/video15
[ 4.882453] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/ video16
[ 4.882481] bcm2835-isp bcm2835-isp: Register output node 0 with media contro ller
[ 4.882504] bcm2835-isp bcm2835-isp: Register capture node 1 with media contr oller
[ 4.882537] bcm2835-isp bcm2835-isp: Register capture node 2 with media contr oller
[ 4.882559] bcm2835-isp bcm2835-isp: Register capture node 3 with media contr oller
[ 4.882794] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
[ 4.884136] snd-rpi-hifiberry-dacplus soc:sound: ASoC: failed to init link Hi FiBerry DAC+: -517
[ 4.896461] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[ 4.896503] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[ 4.902773] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[ 4.902813] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[ 4.914431] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 4.919565] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[ 4.919614] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[ 4.927021] snd-rpi-hifiberry-dacplus soc:sound: ASoC: failed to init link Hi FiBerry DAC+: -517

[paul-]

to list modules, type lsmod

Otherwise it looks like alot of info is written to /var/log/hifiberry.log

[rgro]

to list modules, type lsmod

Otherwise it looks like alot of info is written to /var/log/hifiberry.log

O.K...first, aplay says this:

card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0 [HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0]

Then lsmod says this:

Module Size Used by
uinput 20480 1
cmac 16384 3
algif_hash 16384 1
aes_arm_bs 24576 2
crypto_simd 16384 1 aes_arm_bs
cryptd 24576 2 crypto_simd
algif_skcipher 16384 1
af_alg 28672 6 algif_hash,algif_skcipher
bnep 20480 2
hci_uart 40960 1
btbcm 16384 1 hci_uart
bluetooth 360448 28 hci_uart,bnep,btbcm
ecdh_generic 16384 2 bluetooth
ecc 36864 1 ecdh_generic
brcmfmac 319488 0
snd_soc_tpa6130a2 16384 1
brcmutil 20480 1 brcmfmac
snd_soc_pcm512x_i2c 16384 1
snd_soc_pcm512x 32768 1 snd_soc_pcm512x_i2c
vc4 237568 0
regmap_i2c 16384 2 snd_soc_tpa6130a2,snd_soc_pcm512x_i2c
bcm2835_codec 36864 0
bcm2835_isp 32768 0
spidev 20480 2
bcm2835_v4l2 45056 0
sha256_generic 16384 0
v4l2_mem2mem 32768 1 bcm2835_codec
cec 49152 1 vc4
v3d 69632 0
libsha256 20480 1 sha256_generic
bcm2835_mmal_vchiq 28672 3 bcm2835_isp,bcm2835_codec,bcm2835_v4l2
drm_kms_helper 184320 2 vc4
videobuf2_dma_contig 20480 2 bcm2835_isp,bcm2835_codec
videobuf2_vmalloc 16384 1 bcm2835_v4l2
gpu_sched 36864 1 v3d
videobuf2_memops 16384 2 videobuf2_dma_contig,videobuf2_vmalloc
cfg80211 675840 1 brcmfmac
videobuf2_v4l2 28672 4 bcm2835_isp,bcm2835_codec,bcm2835_v4l2,v4l2_mem2me m
drm 458752 5 v3d,vc4,gpu_sched,drm_kms_helper
rfkill 28672 5 bluetooth,cfg80211
videobuf2_common 57344 5 bcm2835_isp,bcm2835_codec,bcm2835_v4l2,v4l2_mem2me m,videobuf2_v4l2
snd_soc_hifiberry_dacplus 16384 3
snd_soc_bcm2835_i2s 16384 2
videodev 237568 6 bcm2835_isp,bcm2835_codec,videobuf2_common,bcm2835 _v4l2,v4l2_mem2mem,videobuf2_v4l2
drm_panel_orientation_quirks 16384 1 drm
mc 40960 6 bcm2835_isp,bcm2835_codec,videobuf2_common,videode v,v4l2_mem2mem,videobuf2_v4l2
snd_soc_core 188416 5 snd_soc_pcm512x,vc4,snd_soc_hifiberry_dacplus,snd_ soc_bcm2835_i2s,snd_soc_tpa6130a2
spi_bcm2835 24576 0
raspberrypi_hwmon 16384 0
i2c_bcm2835 16384 0
snd_pcm_dmaengine 16384 1 snd_soc_core
vc_sm_cma 32768 2 bcm2835_isp,bcm2835_mmal_vchiq
snd_pcm 94208 6 snd_soc_pcm512x,vc4,snd_pcm_dmaengine,snd_soc_hifi berry_dacplus,snd_soc_bcm2835_i2s,snd_soc_core
snd_timer 32768 1 snd_pcm
snd 73728 10 snd_soc_pcm512x,snd_timer,snd_soc_core,snd_pcm
rpivid_mem 16384 0
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops 16384 1 drm_kms_helper
uio_pdrv_genirq 16384 0
i2c_gpio 16384 0
uio 20480 1 uio_pdrv_genirq
i2c_algo_bit 16384 1 i2c_gpio
clk_hifiberry_dacpro 16384 1
sch_fq_codel 24576 7
ipv6 458752 45

[paul-]

Well that's definitely the older DAC+ (and Pro) driver.

Would you mind trying pCP7.0.0b6?

[rgro]

Well that's definitely the older DAC+ (and Pro) driver.

Would you mind trying pCP7.0.0b6?

Wouldn't mind at all. Since I have the RPI4, would you suggest I use the 32bit or the 64 bit version?

[paul-]

If you have an 8GB board, stay with 64bit, otherwise its your choice for a player only system. LMS seems to run a bit snappier on the 64bit OS.

[rgro]

If you have an 8GB board, stay with 64bit, otherwise its your choice for a player only system. LMS seems to run a bit snappier on the 64bit OS.

I just have the 2GB board as both of my pi's are player only. I have LMS running on a separate server. I'll try the 32 bit to start with and let you know..

[rgro]

Hey Paul...

Success!!!!!! Burned the 32 bit beta version, chose HifiBerry DAC+ (and Pro, Amp), Squeezelite came up running for the first time, left the output setting (field was already populated) at hw:CARD=sndrpihifiberry, saved that, and was able to play music via LMS/Squeezelite.

Just FYI, as you would have expected, these are now the available options under the output settings:

null
default
plugequal
equal
hw:CARD=Headphones,DEV=0
plughw:CARD=Headphones,DEV=0
sysdefault:CARD=Headphones
hw:CARD=sndrpihifiberry,DEV=0
plughw:CARD=sndrpihifiberry,DEV=0
sysdefault:CARD=sndrpihifiberry

Thanks so much for your help and patience. Can I safely assume that the official release version of 7.0 will work just as well??