[SOLVED] Raspberry Pi 5 and Amp 2

[ribelema]

Hi Guys

My config:

• Raspberry Pi 5
  
• Hifiberry AMP2
  
• Moode release 9.0.0 2024-05-17
  

I have a sound when in the Configure/Audio/Audio Output we set the output device as snd_rpi_hifiberry_dacplus.
When I try to change to I2S and use AMP2/4 I have no sound. Simply, there is no related output device available that I could choose. 
Anyone has similar config and a way to get that working?


Regards
Ribelema

[Tim Curtis]

Reboot and then post the contents of the startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from any of the Config screens. The startup log will be at the end of System info output.

[ribelema]

Reboot and then post the contents of the startup log.

The log can be viewed via the SSH command moodeutl -l or downloaded via the Logs section in System Config, or via Menu, System info from  any of the Config screens. The startup log will be at the end of System info output.

It seems I had to modify dtoverlay. Initially I had there dtoverlay=hifiberry-dacplus but this need to be changed to dtoverlay=hifiberry-dacplus-std

Also had to edit audio output in mpd.conf

audio_output {

        type            "alsa"
        name            "My ALSA Device"
        device          "hw:0,0"       
        mixer_type      "software"
}


All is working now, thanks.

[Tim Curtis]

It looks like DAC+ and Amp2/4 need the hifiberry-dacplus-std overlay. I'll add to the TODO list.

[jezsinglespeed]

Ribelema, I had this with my HifiBerry Dac2 Pro on my Rpi5, got round it by selecting the right DT Overlay, they're all there now the kernel has pulled them through from hifiberry, shown in attached screen snip.

Tim, if its on your TODO would you do all of the new/updated overlays at:-


https://www.hifiberry.com/docs/software/...ux-3-18-x/

Don't be put off by the page title it's the list for 'Kernel >=  6.1.77' overlays, many thanks as always.

[Tim Curtis]

Here is whats currently in the device table along with the proposed change.

Code:

22    HiFiBerry Amp(Amp+)    hifiberry-amp
23    HiFiBerry Amp2/4     hifiberry-dacplus    hifiberry-dacplus-std
24    HiFiBerry Beocreate     hifiberry-dac
25    HiFiBerry DAC         hifiberry-dac
26    HiFiBerry DAC+         hifiberry-dacplus    hifiberry-dacplus-std
27    HiFiBerry DAC+ ADC     hifiberry-dacplusadc
28    HiFiBerry DAC+ DSP     hifiberry-dac
29    HiFiBerry DAC+ Light     hifiberry-dac
30    HiFiBerry DAC+ Pro     hifiberry-dacplus    hifiberry-dacplus-pro
31    HiFiBerry DAC+ Zero     hifiberry-dac
32    HiFiBerry Digi(Digi+)     hifiberry-digi
33    HiFiBerry Digi+ Pro     hifiberry-digi-pro
34    HiFiBerry MiniAmp     hifiberry-dac

For the hifiberry devices not in the table I can't add them without detailed specs and an explanation of how any of the advanced chip/driver or input options function. Here's the table columns.

Code:

name        Device name
dacchip        Chip name/model
chipoptions    ALSA chip options
driver        Overlay name
drvoptions    Driver options (if any)

[jezsinglespeed]

Thanks Tim, now i see that list I'm sorted as the Dac2 Pro is the new Dac+ Pro and uses the same driver, its the successor 2nd revision board if you will.  I'm on their forum so i'll ask if they'll provide info, regards, jez.

[ribelema]

Hi Guys

My modified audio_output in the mpd.conf is not persistent, what I mean that it doesn't survive the reboots.
Is there anyway to address this?
Regards

[Tim Curtis]

Hi Guys

My modified audio_output in the mpd.conf is not persistent, what I mean that it doesn't survive the reboots.
Is there anyway to address this?
Regards

Try the dev tweaks feature
https://moodeaudio.org/forum/showthread....3#pid47753