DAC+ADC PRO not recognized with Raspbian Stretch Kernel 4.19.127

Suondlab

September 08, 2021 13:30

None

I'm trying to get a DAC+ADC Pro up and running with a Raspberry 3 Board with a Raspbian dist with Kernel 4.19. The board is recognized and supported when booting the current Hifiberry OS on the same hardware, so the hardware setup should be fine.

When i boot the Raspbian dist with Kernel 4.19 though the soundcard is not recognized when checking this with aplay.

I've run the Hifiberry check-system script and get the following output:

Kernel: 4.19.127-16-gb1425b1
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"


snd_soc_bcm2708 missing in /etc/modules
snd_soc_bcm2708 module not loaded
snd_soc_bcm2708_i2s missing in /etc/modules
snd_soc_bcm2708_i2s module not loaded
bcm2708_dmaengine missing in /etc/modules
bcm2708_dmaengine module not loaded
snd_soc_pcm5102a missing in /etc/modules
snd_soc_pcm5102a module not loaded
snd_soc_hifiberry_dac missing in /etc/modules
snd_soc_hifiberry_dac module not loaded
module file /lib/modules/4.19.127-16-gb1425b1/kernel/drivers/dma/bcm2708-dmaengine.ko not found
module file /lib/modules/4.19.127-16-gb1425b1/kernel/sound/soc/bcm/snd-soc-bcm2708-i2s.ko not found
module file /lib/modules/4.19.127-16-gb1425b1/kernel/sound/soc/bcm/snd-soc-hifiberry-dac.ko not found
module file /lib/modules/4.19.127-16-gb1425b1/kernel/sound/soc/codecs/snd-soc-pcm5102a.ko not found
Sound cards
aplay: device_list:270: no soundcards found...
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default
aplay: main:788: audio open error: No such file or directory

From previous postings it looks like the error messages about snd_soc_bcm2708 can be ignored?

Could you give me some help what to check out next to find out why my setup is not recognizing the DAC+ADC Pro?

My understanding is that the Hifiberry modules are part of the kernel drivers since 4.18, how can i verify this?

Date Votes

12 comments

0

HiFiBerry team September 08, 2021 14:35

Linux 4.19 is very old and I'm not even sure if the DAC+ ADC Pro was supported on 4.x. You should upgrade your system, current Raspberrey Pi OS kernel is 5.10.x

Comment actions Permalink
0

Suondlab September 08, 2021 16:46

Thanks for your reply! Due to the setup i am stuck with this kernel version for now, but would still be interested what i could do next to find out about the issue. I saw this page and was hoping that it is possible to get it up and running on 4.19:

"The use the input functionality of the DAC+ ADC, you will need to update the Linux kernel to at least version 4.18.12. As the official Raspbian kernel now already includes the the necessary drivers, you might not need to upgrade your system. "

https://www.hifiberry.com/docs/archive/deploying-a-new-linux-kernel-onto-a-raspbian-based-system/

Comment actions Permalink
0

HiFiBerry team September 09, 2021 05:13

This i about the DAC+ ADC, not the DAC+ ADC Pro. You might try to disable the EEPROM:
https://www.hifiberry.com/blog/configuration-changes-in-linux-5-4/

Comment actions Permalink
0

Suondlab September 09, 2021 06:13

Thanks! I just tried this but no change unfortunately. Took a peek at the device tree output and the HifiBerry is listed as this entry:

hat {
    product = "DAC+ ADC Pro";
    product_id = "0x0000";
    product_ver = "0x0000";
    uuid = "36e3d3da-1ed9-468b-aea3-cd165f6820f0";
   vendor = "HiFiBerry";
};

Does this look correct? How can i find out if the correct HiFiBerry drivers are part of the kernel modules/system?

Edited by Suondlab September 09, 2021 06:15

Comment actions Permalink
0

Suondlab September 11, 2021 14:45

It looks like the driver is missing in the kernel i have, so will build a new 4.19 kernel to include hifiberry support. Have downloaded the 4.19.206 kernel sources but don't see a CONFIG_SND definition pointing out to a hifiberry device.

What do i need to enable in the defconfig file for 4.19.206 to include Hifiberry support in the kernel i am building?

Comment actions Permalink
0

HiFiBerry team September 11, 2021 19:34

All HiFiBerry sound cards are enabled in the default config.

Comment actions Permalink
0

Suondlab September 12, 2021 15:16

Yes, but that answer does not help me get the card up and running unfortunately, as i need to build a kernel to support this. So what do i need to enable in the defconfig file for a kernel 4 build to enable Hifiberry support?

Comment actions Permalink
0

HiFiBerry team September 12, 2021 17:31

If in the Raspberry pi 4 default config these are missing, there's some problem with your kernel source. The default config has all HiFiBerry drivers enabled.
Otherwise run make menuconfig and enable these.

Comment actions Permalink
0

Suondlab September 13, 2021 06:13

That is what i plan to do, but i still need an answer what to enable in the defconfig file/make menuconfig. Can you please answer my question what to enable in the devconfig file. A grep on the kernel sources did not yield any reference to hifiberry.

Comment actions Permalink
0

HiFiBerry team September 13, 2021 06:19

No, I can't. I don't even have a 4.19 kernel here somewhere and we can't give support to compile individual kernels.

If you can't find any HiFiBerry references, there's something very wrong in your kernel sources:
https://github.com/raspberrypi/linux/search?q=hifiberry

Comment actions Permalink
0

Suondlab September 14, 2021 10:05

Thanks for the link, i've added CONFIG_SND_BCM2708_SOC_HIFIBERRY_DACPLUSADCPRO=y to my defconfig and have been able to build and boot a new kernel.

There are two red leds on the DAC+ADC Pro Board which are turned on when booting, what do they indicate?

Question, i do get the following error messages when booting up, is this to be expected or do you have an idea what might have went wrong?

[ 2.008241] systemd[1]: alsa-state.service: Cannot add dependency job, ignoring: Unit alsa-state.service is masked.
[ 2.008301] systemd[1]: alsa-restore.service: Cannot add dependency job, ignoring: Unit alsa-restore.service is masked.

...

[ 2.600087] snd-rpi-hifiberry-dacplusadcpro soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 2.605280] snd-rpi-hifiberry-dacplusadcpro soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 2.606375] snd-rpi-hifiberry-dacplusadcpro soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 2.655195] snd-rpi-hifiberry-dacplusadcpro soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
[ 2.775937] snd-rpi-hifiberry-dacplusadcpro soc:sound: multicodec <-> 3f203000.i2s mapping ok

aplay returns this:

% aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplusadcpro], device 0: HiFiBerry DAC+ADC Pro HiFi multicodec-0 [HiFiBerry DAC+ADC Pro HiFi multicodec-0]
Subdevices: 0/1
Subdevice #0: subdevice #0

Thanks!

Comment actions Permalink
0

HiFiBerry team September 14, 2021 10:38

Nothing went wrong. The driver is loaded correctly.

Comment actions Permalink

Please sign in to leave a comment.