I have a Raspberry Pi 2B that I have just bought a HiFiBerry DAC2 Pro for (requires dtoverlay=hifiberry-dacplus). I am running the November 2020 Raspberry Pi 2 image on the Pi as I haven’t wanted to upgrade to the version that removed hardware decoding of VC-1 and MPEG2.
I can’t get the Pi to recognise the DAC as the audio output. Should the above approach apply to the image I’m using? The file /boot/config-user.txt doesn’t exist…
Thanks! Hmm googling has revealed that others have experienced a similar issue, but I haven’t found a resolution yet.
This page seems to have some ideas, but the first suggestion to remove the following
dtparam=audio=on
seems somewhat redundant as dtparam=audio=off is already in /boot/config.txt
[ 10.026728] clk-hifiberry-dacpro clocks:dacpro_osc: Fail to register clock driver
[ 10.026771] clk-hifiberry-dacpro: probe of clocks:dacpro_osc failed with error -17
[ 10.281559] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 10.990152] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
It seems as though it’s failing to register the clock driver on the dac??
Well the confusing part of that page is that it refers to Linux 4.x with the new DTB.
But while your OSMC is 4.19 it should still use the old DTB and the dtparam parameter should not be existing.
Maybe try on another SD Card either with Raspbian and/or a newer OSMC version to check if the DAC works.
Also I just read
are you sure that is supported by the old DAC+ overlay?
For what it’s worth I have a second Raspberry Pi 2B, I just chucked the SD card and DAC2 Pro HAT onto that board and got the exact same issue. I did this as I read that Pis can sometimes have issues with GPIO pins… But I think this rules that out…
I’ve posted a question with the dmesg output in the HiFiBerry support community forum.
I’ll post back if they indicate anything or are able to help…