[RPi5] Problem with HiFiBerry DAC

RadoK · January 23, 2024 at 7:49 AM

Hi
I have a problem with Kodi and HiFiBerry DAC based on the ES9023 chip. I used it on a Raspberry Pi 3B+ and everything worked fine. However, I bought a new Raspberry Pi 5 and installed a new LibreELEC and the DAC stopped working. The sound has wrong/slow timing like a cassette player with bad batteries. In Kodi, the DAC shows up as hHiFiBerryy DAC based on the PCM5102 chip, and in the config text file is set dtoverlay=hifiberry-dac.

Thanks in advance.

**Da Flex** · January 23, 2024 at 2:32 PM

Better ask HiFiBerry. RPi5 is pretty new, so it could be a HiFiBerry driver issue.

**popcornmix** · January 23, 2024 at 3:14 PM

I believe this is a kernel issue that has been fixed upstream, but I'm not sure LibreELEC has picked up the fix.

RadoK · January 23, 2024 at 4:42 PM

Yes, I plugged in the Raspbian Desktop SD card. Everything working fine. The sound is great, but it is not OpenELEC.

RadoK · January 23, 2024 at 5:22 PM

Sorry, L i b r e E L E C.

loglyy · March 11, 2024 at 10:31 AM

Hi, I have the same probleme. Did you find a solution to use this DAC with kodi on rpi5?

Thanks for your help

**popcornmix** · March 11, 2024 at 4:10 PM

Quote from loglyy

Hi, I have the same probleme. Did you find a solution to use this DAC with kodi on rpi5?

Can you try a nightly LE12 build? There may be kernel fixes that aren't in the stable LE11 build.

lotte67890 · April 24, 2024 at 11:14 PM

Well same here, Im using LibreELEC-RPi5.aarch64-11.95.2.img.gz with a RPI5 and a hifiberry dacplushd sndcard, no audio at all.

When playing Audio dmesg continually says:

dma dma2chan0: dma2chan0 is non-idle!
dma dma2chan0: dma2chan0 failed to stop

In the Kodi log it reads:

Code

2024-04-24 23:57:14.030 T:1726 info <general>: CActiveAESink::OpenSink - initialize sink
2024-04-24 23:57:14.030 T:1726 info <general>: CAESinkALSA::Initialize - Attempting to open device "sysdefault:CARD=sndrpihifiberry"
2024-04-24 23:57:14.031 T:1726 info <general>: CAESinkALSA::Initialize - Opened device "sysdefault:CARD=sndrpihifiberry"
2024-04-24 23:57:14.031 T:1726 info <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2024-04-24 23:57:14.031 T:1726 info <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S24NE4
2024-04-24 23:57:14.611 T:1726 error <general>: CAESinkALSA - snd_pcm_writei(-5) Input/output error - trying to recover
2024-04-24 23:57:14.611 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(1)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:14.851 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(2)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:15.091 T:1726 error <general>: CAESinkALSA - snd_pcm_writei(-5) Input/output error - trying to recover
2024-04-24 23:57:15.091 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(1)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:15.331 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(2)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:15.571 T:1726 error <general>: CAESinkALSA - snd_pcm_writei(-5) Input/output error - trying to recover
2024-04-24 23:57:15.571 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(1)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:15.811 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(2)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:16.051 T:1726 error <general>: CAESinkALSA - snd_pcm_writei(-5) Input/output error - trying to recover
2024-04-24 23:57:16.051 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(1)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:16.291 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(2)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:16.531 T:1726 error <general>: CAESinkALSA - snd_pcm_writei(-5) Input/output error - trying to recover
2024-04-24 23:57:16.531 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(1)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:16.771 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(2)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:17.011 T:1726 error <general>: CAESinkALSA - snd_pcm_writei(-5) Input/output error - trying to recover
2024-04-24 23:57:17.011 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(1)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:17.251 T:1726 error <general>: CAESinkALSA::HandleError(snd_pcm_writei(2)) - snd_pcm_writei returned -5 (Input/output error)
2024-04-24 23:57:17.256 T:1726 error <general>: CActiveAESink::OutputSamples - failed

Display More

I also tried with a fresh "2024-03-15-raspios-bookworm-arm64", which behaved the same in the first place but after replacing

dtoverlay=hifiberry-dacplushd

with

dtoverlay=hifiberry-dacplushd,slave

it worked fine.

On Libreelec I also tried with force_eeprom_read=0, disabled dtoverlay=gpio-ir,gpio_pin=17 and hdmi_drive=1 without any difference.

In the end I would prefer going with LIBREELEC, but without Audio it makes no sense...

Any hints?

Thanks in advance

**Da Flex** · April 24, 2024 at 11:38 PM

Quote from lotte67890

Well same here, Im using LibreELEC-RPi5.aarch64-11.95.2.img.gz with a RPI5...

Use the latest nightly build instead: Download

lotte67890 · April 25, 2024 at 9:10 AM

Sadly the same behaviour. Is anybody using a RPI5 with an attached Hifiberry?

**HiassofT** · April 25, 2024 at 10:07 AM

Please test with RPiOS and the latest rpi-update kernel. If it doesn't work either create an issue on the RPi kernel github https://github.com/raspberrypi/linux/issues

BTW: the hifiberry-dacplushd overlay doesn't seem to have a "slave" option and the "slave" option of the hifiberry-dacplus overlay won't work on RPi5 so there are now two separate overlays for the (non-HD) DAC+, hifiberry-dacplus-std and hifiberry-dacplus-pro

so long,

Hias

HarryH · April 25, 2024 at 1:18 PM

Because of this:
Configuring Linux 4.x or higher | HiFiBerry
HiFiBerry sound cards on the Pi5 | HiFiBerry
Changes in HiFiBerry drivers | HiFiBerry

you should ensure that this line is commented out:
dtparam=audio=on
to
dtparam=audio=off or #dtparam=audio=on

I had read that this command
force_eeprom_read=0
is deprecated, you should instead move this 2 lines to the very beginning of the config.txt

Code

dtoverlay=
dtoverlay=hifiberry-dacplushd

The first line prevents it from loading the overlay out of the HAT EEPROM (hifiberry).

I know that some users with RPi5 and a Argon ONE case use successful the hifiberry driver set with their new BLSTR DAC modules. But the driver for dacplushd could have his own bugs.

lotte67890 · April 25, 2024 at 1:52 PM

Hi Hias, thanks a lot for your reply. I got it working! All I needed to do, is to not have the dtoverlay=hifiberry-dacplushd in the config file. So if I would have not edited the config in the first place I would have not ran into trouble.

This works for both, the nightly fro 2024 04 24 and for the LibreELEC-RPi5.aarch64-11.95.2

Maybe it is worth a note before others run in the same error.

Regards

Lotte

HarryH · April 25, 2024 at 2:20 PM

Hi Lotte,

nice, that you found a solution.

If you currently doesn‘t have a dtoverlay=hifiberry … line in your config it seems that the overlay was instead loaded from the HAT EEPROM. Please keep in mind, that in future kernel versions it could be possible that this overlay in the HAT EEPROM will be outdated. Then you will need a matching dtoverlay line for your hifiberry.

Regards,

Harry

**HiassofT** · April 25, 2024 at 2:30 PM

Quote from HarryH

If you currently doesn‘t have a dtoverlay=hifiberry … line in your config it seems that the overlay was instead loaded from the HAT EEPROM. Please keep in mind, that in future kernel versions it could be possible that this overlay in the HAT EEPROM will be outdated. Then you will need a matching dtoverlay line for your hifiberry.

RPi folks recommend to store the name of the overlay in the eeprom, not the actual overlay itself, to avoid kernel version issues.

Unfortunately Hifiberry did the latter (and OFC the overlays became incompatible with RPi5) but fortunately this could be fixed up with hat_map entries (see commit https://github.com/raspberrypi/li…fdda902104650b3) so the hifiberry cards should work fine now without any config.txt trickery.

so long,

Hias

HarryH · April 25, 2024 at 2:55 PM

HiassofT ,

thank you for the additional explanation to make the current state more clear.

Regards,

Harry

lotte67890 · April 25, 2024 at 7:58 PM

Well, sorry and sad to say, the hifiberry stopped working. On both of the releases, the nightly and the LibreELEC-RPi5.aarch64-11.95.2. Yes I was playing around, but only with the keymapping of the lirc remote. And this only on LibreELEC-RPi5.aarch64-11.95.2 release, the nightly was untouched since it worked this morning.

Same errors as before in dmesg and kodi.log. I first was thinking that the hifiberry might be broken, so I attached it again to my RPI4 which still has the configuration I used over the last years, and voila, works as usual.

I have no clue what is going... Maybe I give it another try on the weekend...

**HiassofT** · April 25, 2024 at 8:34 PM

Post a full log when it happens again, using the latest LE12 nightly build (ssh in, run "pastekodi" and post the URL). It could be anything from a connection problem to power supply issue or something else - hopefully the log will give more info.

so long,

Hias

[RPi5] Problem with HiFiBerry DAC

Similar Threads

McuZone PCIE M.2 NVME 2230 2242 Gen3 SSD HAT for Raspberry Pi 5 with LibreElec

Is there a way to adjust delay between tracks on RPi 5?

How do I disable onboard audio on a Raspberry pi 5