Hifiberry Digi2 Pro is not recognized by Volumio

Rodrigo_Soler · January 20, 2025, 5:41pm

Hello everyone!

After rebooting the system, Volumio no longer recognizes my Hifiberry Digi2 Pro card. I tried to do a factory reset, installed the latest beta version and nothing worked. To clear up any doubts about whether the problem is with the card, I installed Hifiberry OS on another SD card and everything works normally. I did a new installation of Volumio on the SD card and at first it recognizes the card, but after rebooting the system, it is no longer recognized.

I’m new here and I don’t know how to upload the log, but if you can help or suggest something, it would be great.

Regards.

Wheaten · January 20, 2025, 5:47pm

Here are the instructions to post a log

Please make a ssh connection to your device and post the output of:
cat /boot/config.txt
cat /boot/userconfig.txt
aplay -l

Rodrigo_Soler · January 20, 2025, 5:58pm

Hi Wheaten,

Tks for the instructions.

Log: http://logs.volumio.org/volumio/EVHgO96.html

volumio@volumio:~$ cat /boot/config.txt
### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
initramfs volumio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
include volumioconfig.txt
include userconfig.txt
#### Volumio i2s setting below: do not alter ####
dtoverlay=hifiberry-digi-pro


#### Volumio i2s setting below: do not alter ####
dtoverlay=hifiberry-digi-pro

volumio@volumio:~$ cat /boot/userconfig.txt
# Add your custom config.txt options to this file, which will be preserved during updates

volumio@volumio:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3

Regards.

Wheaten · January 20, 2025, 6:01pm

This is a rPi4 or rPi5?

please remove these 2 lines for /boot/config.txt and reboot afterwards.
One entry is more than enough:

#### Volumio i2s setting below: do not alter

dtoverlay=hifiberry-digi-pro

Rodrigo_Soler · January 20, 2025, 6:09pm

Hi,

Host: Raspberry Pi 4 Model B Rev 1.5 (4GB de RAM)

I’ve altered the /boot/config.txt:

volumio@volumio:~$ cat /boot/config.txt
### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
initramfs volumio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
include volumioconfig.txt
include userconfig.txt
#### Volumio i2s setting below: do not alter ####
dtoverlay=hifiberry-digi-pro

I’ve also reboot the system, the card isn’t recognized

volumio@volumio:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3

Wheaten · January 20, 2025, 6:14pm

@nerd

Hi Sheldon we need your magic here.
Summary:

rPi4
Volumio V3.787
Hifiberry-digo-pro
Card not detected
log: http://logs.volumio.org/volumio/EVHgO96.html

nerd · January 20, 2025, 7:41pm

Hey @Rodrigo_Soler,

There is something odd reported by alsa which does not match Pi 4B

Testing on Raspberry Pi 4B without any configuration yet:

aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 2: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Not setting I2S DAC yet:

Disable HDMI in /boot/userconfig.txt

dtoverlay=vc4-kms-v3d-pi4,nohdmi

aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3

Similar response to your setup

Disable HDMI audio routing in /boot/userconfig.txt

dtoverlay=vc4-kms-v3d-pi4,noaudio

aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3

Similar response to your setup

Enable vc4 DRM routing in /boot/userconfig.txt

[all]
display_auto_detect=1
dtoverlay=vc4-kms-v3d-pi4

aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 2: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

DAC

Since I don’t have the HiFiBerry Digi2 Pro, nonetheless steps will be identical:

I2S without reboot

aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 2: sndrpihifiberry [snd_rpi_hifiberry_dacplushd], device 0: HiFiBerry DAC+ HD HiFi pcm179x-hifi-0 [HiFiBerry DAC+ HD HiFi pcm179x-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 4: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

I2S after reboot (multiple reboots)

aplay -l

**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 2: sndrpihifiberry [snd_rpi_hifiberry_dacplushd], device 0: HiFiBerry DAC+ HD HiFi pcm179x-hifi-0 [HiFiBerry DAC+ HD HiFi pcm179x-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 4: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Suggestion

Remove all references to DAC in /boot/config.txt
Configure Playback Options set to “Headphones”
Shutdown and disconnect power sources for 2-3s (power drain)
Start your Raspberry Pi 4B and configure DAC
Configure I2S DAC
Wait for 5-10s before rebooting

Report your findings from your test please.

Kind Regards,

Rodrigo_Soler · January 21, 2025, 4:07pm

Hello again,

I followed the steps and changes suggested by Nerd, and the result is intermittent. After the configuration, the card was recognized on the first reboot, but it did not transmit any signal to the DAC. On the second reboot, the card was no longer recognized. I changed the Volumio configuration to use Headphones and rebooted again. The card was recognized but also did not send any audio signal to the DAC. I rebooted again and the system stopped recognizing the card again.

Current settings:

volumio@volumio:~$ sudo cat /boot/config.txt
[sudo] password for volumio:
### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
initramfs volumio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
include volumioconfig.txt
include userconfig.txt
#### Volumio i2s setting below: do not alter ####

#### Volumio i2s setting below: do not alter ####
dtoverlay=hifiberry-digi-pro

volumio@volumio:~$ sudo cat /boot/userconfig.txt
[sudo] password for volumio:
# Add your custom config.txt options to this file, which will be preserved during updates
[all]
display_auto_detect=1
dtoverlay=vc4-kms-v3d-pi4

Current boot:

volumio@volumio:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 2: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Previus boot:

volumio@volumio:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 0: b1 [bcm2835 HDMI 1], device 1: bcm2835 HDMI 1 [bcm2835 HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones]
  Subdevices: 4/4
  Subdevice #0: subdevice #0
  Subdevice #1: subdevice #1
  Subdevice #2: subdevice #2
  Subdevice #3: subdevice #3
card 2: sndrpihifiberry [snd_rpi_hifiberry_digi], device 0: HiFiBerry Digi+ Pro HiFi wm8804-spdif-0 [HiFiBerry Digi+ Pro HiFi wm8804-spdif-0]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 3: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 4: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Trying to play music on the boot with card recognized:
Captura de tela 2025-01-21 123730

Actual log:
http://logs.volumio.org/volumio/9MuqvsX.html

Regards.

Wheaten · January 21, 2025, 4:08pm

can you try the same and disable the startup sound?

Rodrigo_Soler · January 21, 2025, 4:40pm

I just tried to configure it again without the startup sound and the result was the same.

I redid all the settings I mentioned in the previous post. After about 4 or 5 reboots, the card appeared again. I tried to play music, the Volumio interface shows that it is playing (without errors) but no sound is sent to the DAC (the red light on the optical output is off, it turns on when the card sends a signal to the DAC). I believe that if I reboot again, the card will no longer be recognized.

Very strange

nerd · January 21, 2025, 5:26pm

Hey @Rodrigo_Soler,

Let’s take a look into the overlay, perhaps we will have better view what is yielded during init of the DAC.

Please add to the /boot/userconfig.txt

dtdebug=on

After reboot post output from:

sudo vcdbg log msg

Kind Regards,

Rodrigo_Soler · January 21, 2025, 6:17pm

Hi,

volumio@volumio:~$ sudo vcdbg log msg
[sudo] password for volumio:
004052.882: arasan: arasan_emmc_open
004053.053: arasan: arasan_emmc_set_clock C0: 0x00800000 C1: 0x000e0047 emmc: 200000000 actual: 390625 div: 0x00000100 target: 400000 min: 400000 max: 400000 delay: 5
004157.826: arasan: arasan_emmc_set_clock C0: 0x00800000 C1: 0x000e0047 emmc: 200000000 actual: 390625 div: 0x00000100 target: 400000 min: 400000 max: 400000 delay: 5
004157.914: arasan: arasan_emmc_set_clock C0: 0x00800f00 C1: 0x000e0047 emmc: 200000000 actual: 390625 div: 0x00000100 target: 400000 min: 390000 max: 400000 delay: 5
004176.028: arasan: arasan_emmc_set_clock C0: 0x00800f06 C1: 0x000e0207 emmc: 200000000 actual: 50000000 div: 0x00000002 target: 50000000 min: 0 max: 50000000 delay: 1
004277.507: brfs: File read: /mfs/sd/config.txt
004277.673: brfs: File read: 399 bytes
004279.808: brfs: File read: /mfs/sd/volumioconfig.txt
004280.056: brfs: File read: 366 bytes
004280.830: brfs: File read: /mfs/sd/userconfig.txt
004281.147: brfs: File read: 155 bytes
004364.332: HDMI1:EDID error reading EDID block 0 attempt 0
004365.349: HDMI1:EDID giving up on reading EDID block 0
004369.329: brfs: File read: /mfs/sd/config.txt
004369.486: brfs: File read: 399 bytes
004371.618: brfs: File read: /mfs/sd/volumioconfig.txt
004371.840: brfs: File read: 366 bytes
004372.613: brfs: File read: /mfs/sd/userconfig.txt
004863.350: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not defined
004864.105: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not defined
004866.254: *** Restart logging
004866.273: brfs: File read: 155 bytes
004935.757: hdmi: HDMI1:EDID error reading EDID block 0 attempt 0
004936.776: hdmi: HDMI1:EDID giving up on reading EDID block 0
004941.814: hdmi: HDMI1:EDID error reading EDID block 0 attempt 0
004942.829: hdmi: HDMI1:EDID giving up on reading EDID block 0
004942.848: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_display_state instead
004942.864: HDMI0: hdmi_pixel_encoding: 300000000
004942.875: HDMI1: hdmi_pixel_encoding: 300000000
009332.106: brfs: File read: /mfs/sd/volumio.initrd
009332.132: Loaded 'volumio.initrd' to 0x0 size 0x1b6dba1
009357.798: initramfs loaded to 0x2d492000 (size 0x1b6dba1)
009357.865: dtb_file 'bcm2711-rpi-4-b.dtb'
009357.894: brfs: File read: 28760993 bytes
009369.794: brfs: File read: /mfs/sd/bcm2711-rpi-4-b.dtb
009369.820: Loaded 'bcm2711-rpi-4-b.dtb' to 0x100 size 0xdb5c
009395.440: brfs: File read: 56156 bytes
009411.953: brfs: File read: /mfs/sd/overlays/overlay_map.dtb
009456.156: brfs: File read: 5451 bytes
009457.345: brfs: File read: /mfs/sd/config.txt
009457.536: brfs: File read: 399 bytes
009460.831: brfs: File read: /mfs/sd/volumioconfig.txt
009461.005: dtparam: audio=on
009468.721: dtparam: i2c_arm=on
009485.036: brfs: File read: 366 bytes
009487.083: brfs: File read: /mfs/sd/userconfig.txt
009489.081: brfs: File read: 155 bytes
009508.532: brfs: File read: /mfs/sd/overlays/vc4-kms-v3d-pi4.dtbo
009625.065: Loaded overlay 'vc4-kms-v3d-pi4'
009908.536: brfs: File read: 3913 bytes
009917.967: brfs: File read: /mfs/sd/overlays/hifiberry-digi-pro.dtbo
009947.512: Loaded overlay 'hifiberry-digi-pro'
010028.831: brfs: File read: 1138 bytes
010032.953: brfs: File read: /mfs/sd/cmdline.txt
010033.156: Read command line from file 'cmdline.txt':
010033.197: 'splash plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 quiet console=serial0,115200 console=tty1 imgpart=UUID=8543fa12-4125-4451-a534-cec5480e0606 imgfile=/volumio_current.sqsh
010295.124: brfs: File read: 579 bytes
011516.538: brfs: File read: /mfs/sd/kernel7l.img
011516.567: Loaded 'kernel7l.img' to 0x8000 size 0x7789d0
011516.615: Device tree loaded to 0x2d483b00 (size 0xe447)
011522.734: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER not defined
011628.125: sdram: sdram refresh 1562->3124 (2)
013404.213: vchiq_core: vchiq_init_state: slot_zero = 0xcd580000, is_master = 1
013410.422: TV service:host side not connected, dropping notification 0x00000002, 0x00000001, 0x0000005f

Tks again!

Regards.

nerd · January 21, 2025, 6:40pm

Hey @Rodrigo_Soler,

Looks all clean, EDID error is not a problem here.

Let’s take this further. Please comment out in the /boot/config.txt reference to the HiFiBerry DAC:

# dtoverlay=hifiberry-digi-pro

After reboot and Volumio UI rendered execute dynamic tree loader:

sudo dtoverlay hifiberry-digi-pro
dmesg > dmesg.txt

Please zip created dmsg.txt and attach to this thread.

Kind Regards,

Rodrigo_Soler · January 21, 2025, 6:52pm

Hi @nerd,

The log is attached.

Regards.
dmesg.zip (10.6 KB)

nerd · January 21, 2025, 7:16pm

Hey @Rodrigo_Soler,

[  126.891073] wm8804 1-003b: Failed to read device ID: -121
[  126.891220] wm8804: probe of 1-003b failed with error -121

Failed to read device - This isn’t looking good. Can you share picture/photo of your DAC showing version/revision please?

When was the last time you have updated eeprom on your Pi?

With an utmost care, please inspect connecting pins on 40pin header for hairline cracks on PCB, or something grounding pins below power related. Perhaps remove DAC, check contacts for oxidation or corrosion and reinsert DAC. Inspect power circuitry, disconnect all devices, but essential ones for the DAC to operate.

Kind Regards,

Blackbird · January 22, 2025, 11:42pm

First, check the revision of your Hifiberry Digi2 Pro board. It’s written on the PCB. If it’s v2.1, it won’t be recognized due to hardware compatibility issues with RPi4.

This has been resolved in v2.2. If it’s v2.1, you can use it on Raspberry Pi 3 without any problems, but you can’t use it on Raspberry Pi 4.

Sometimes it’ll be recognized, but you won’t be able to use it.

Rodrigo_Soler · January 27, 2025, 3:17pm

Hello everyone,

I’ve been very busy these past few days, so I apologize for the delay in responding.

I believe the pins and connections on the boards are OK, so I’m sending some images in the post.

The Hifiberry version I’m using is 2.2. I bought the equipment in October last year, so I believe they’re the latest versions (Pi + Digi 2 Pro).

In the past few days, I’ve done the other test I mentioned in the first post again, I installed a Hifiberry OS on another Micro SD Card and it worked normally, local flac, Spotify, etc. I also installed Moode and it also worked normally. Then I did a new installation of Volumio on this other SD Card and it also worked normally. In this last test, I only added the Spotify plugin, I left all the others disabled and without any music on the SD card.

After these tests, I tried to return the SD with the previous Volumio installation and the HAT was not recognized again. I tried to change the output settings to Headphones without I2S DAC, I restarted, I tried to configure the I2S output again with Digi+ Pro and it does not work, it gives an error when playing and does not send a signal to the DAC.

@nerd, I never updated eeprom. How to check if there’s a newer version to do this?

It seems like some witchcraft, but could it be something in the Kernel that is blocking the HAT or some plugin or configuration that is preventing it from working?

nerd · January 27, 2025, 3:39pm

Hey @Rodrigo_Soler ,

Thank you for providing detailed information and confirming that your HiFiBerry Digi2 Pro HAT works with other OSes like HiFiBerry OS and Moode, as well as with a fresh installation of Volumio on a different microSD card. This strongly suggests that the issue lies with the original microSD card or its Volumio installation rather than the hardware or HAT itself.

Observations:

The fact that the HAT is recognised on a different microSD card points to potential corruption or an issue with the original Volumio installation.
The EEPROM update process, as described here, applies to the Raspberry Pi itself, not the HiFiBerry HAT or DAC. Thus, this likely isn’t the source of your issue.

Recommended Steps:

Backup Your Data:
- Before proceeding, back up all your settings, playlists, and configuration data if possible. You can do this via Volumio’s backup plugin or by manually saving important files.
Fresh Installation:
- Use a new, high-quality microSD card for the fresh Volumio installation. Corruption on the current card is a strong possibility, and a fresh installation will often resolve such issues.
Recommended microSD Cards:
- Below is a table of high-quality microSD cards known for their durability and speed. These are ideal for devices like Raspberry Pi that perform frequent read/write operations:

Brand	Model	Key Features
SanDisk	Extreme Pro	High durability, fast write speeds
Samsung	PRO Plus	Designed for heavy use, reliable
Kingston	Canvas Go Plus	Shock and water-resistant
Lexar	Professional 1066x	Optimised for performance

Note: No affiliations to any of these brands – these recommendations are based on general reliability and performance in scenarios like yours.

Restore Configuration:
- After installing Volumio on the new card, configure it to match your original setup. You can restore settings from a backup, if available.
Test Plugins:
- If you use any non-standard plugins, enable them one by one to ensure compatibility with your HAT.

Conclusion:

Starting with a new microSD card is the most reliable way to rule out corruption. While it might feel like a tedious process, this approach is often the quickest path to resolving such issues without lingering problems. If you encounter further issues after the fresh installation, feel free to share your findings for further assistance.

Kind Regards,

Rodrigo_Soler · January 27, 2025, 5:16pm

Hi @nerd,

Thank you very much for your answers!

It is difficult to find original SD or Micro cards here, marketplaces usually sell fake or unreliable ones. I found a Lexar (128GB 633x v30) sold by Amazon. I believe it is a good quality piece.

In this line of thinking about corrupting some files, it may have happened during a power outage. I will format this main SD card again with Volumio and add the music files, settings and plugins again in parts to try to identify if there is something that could be generating this error.

Thank you very much for your support again!

Regards,

Rodrigo Soler.