Subject: Fixed Raspberry OS Audio Issue with HiFiBerry Amp2 (Headless Setup) - Lessons Learned!

homeplayer

May 05, 2024 19:13

None

Hi everyone,

I wasted a bunch of time getting audio working on my headless Raspberry Pi with a HiFiBerry Amp2. Here's my experience to hopefully save you some trouble!

boss@pi:~ $ uname -a #latest Raspberry OS 64b lite
Linux pi 6.6.28+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) aarch64 GNU/Linux
cat ~/.bash_history

 1 echo 'export LC_ALL="en_GB.UTF-8"' >> ~/.bashrc 
 2 sudo reboot 
 3 sudo apt -y update && sudo apt -y full-upgrade 
 4 sudo reboot 
 5 sudo nano /boot/firmware/config.txt 
 6 sudo apt install mc mpd mpc -y 
 7 sudo nano /etc/mpd.conf 
 8 mkdir ~/mpd 
 9 mkdir ~/mpd/music 
10 mkdir ~/mpd/playlists 
13 sudo systemctl enable mpd.service 
14 sudo reboot 
15 mpc volume 35; mpc play
16 mpc add http://86.94.213.59:8000 
17 mpc play # we have SOUND and a volume set to 35

1, dont bother whit it, i have a locale issue need to sort that still out

5 {- sudo nano /boot/firmware/config.txt -} see below; it is for a headless setup (server mode)

gpu_mem=32 
arm_64bit=1 
dtoverlay=hifiberry-dac 
dtoverlay=vc4-kms-v3d,noaudio 

#more testing needs to be done, there is more in this file then is here

7, {- sudo nano /etc/mpd.conf -} see below

music_directory         "~/mpd/music" 
playlist_directory      "~/mpd/playlists" 
db_file                 "~/mpd/database" 
state_file              "~/mpd/state" 
user                    "boss" 
bind_to_address         "localhost"  
audio_output { 
       type            "alsa" 
       name            "My ALSA Device" 
       device          "hw:0,0" 
       mixer_type      "software" } 
auto_update "yes" 
filesystem_charset      "UTF-8"

and thats all, we have sound and volume controle, I was folowing this guide https://www.hifiberry.com/docs/software/configuring-linux-3-18-x/ so i did do the asound.conf asound.conf <--- thats where it all went down hill
Also; dont trust what you see; As you can see no Hihiberry card listed at all Dont Use dacplus or dacplus-std they will not work ( atleast for me)

boss@pi:~ $ lsmod | grep snd 
snd_soc_hdmi_codec     20480  0 
snd_soc_rpi_simple_soundcard    20480  1 
snd_soc_pcm5102a       12288  1 
snd_soc_bcm2835_i2s    16384  2 
snd_soc_core          307200  5 snd_soc_bcm2835_i2s,vc4,snd_soc_pcm5102a,snd_soc_hdmi_codec,snd_soc_rpi_simple_soundcard 
snd_compress           20480  1 snd_soc_core 
snd_bcm2835            24576  0 
snd_pcm_dmaengine      16384  1 snd_soc_core 
snd_pcm               151552  8 snd_soc_bcm2835_i2s,snd_bcm2835,snd_soc_hdmi_codec,snd_compress,snd_soc_core,snd_soc_rpi_simple_soundcard,s
nd_pcm_dmaengine 
snd_timer              36864  1 snd_pcm 
snd                   122880  7 snd_bcm2835,snd_soc_hdmi_codec,snd_timer,snd_compress,snd_soc_core,snd_pcm

yeah aplay -l and aplay -L give some good output
But i was using AI to to solve it, and a AI wants to see a driver/firmware loaded, ohboy
 
boss@pi:~ $ aplay -l 
**** List of PLAYBACK Hardware Devices **** 
card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pcm5102a-hifi-0 [HifiBerry DAC HiFi pcm5102a-hifi-0] 
 Subdevices: 0/1 
 Subdevice #0: subdevice #0 
boss@pi:~ $ aplay -L 
null 
   Discard all samples (playback) or generate zero samples (capture) 
hw:CARD=sndrpihifiberry,DEV=0 
   snd_rpi_hifiberry_dac, HifiBerry DAC HiFi pcm5102a-hifi-0 
   Direct hardware device without any conversions 
plughw:CARD=sndrpihifiberry,DEV=0 
   snd_rpi_hifiberry_dac, HifiBerry DAC HiFi pcm5102a-hifi-0 
   Hardware device with all software conversions 
default:CARD=sndrpihifiberry 
   snd_rpi_hifiberry_dac, HifiBerry DAC HiFi pcm5102a-hifi-0 
   Default Audio Device 
sysdefault:CARD=sndrpihifiberry 
   snd_rpi_hifiberry_dac, HifiBerry DAC HiFi pcm5102a-hifi-0 
   Default Audio Device 
dmix:CARD=sndrpihifiberry,DEV=0 
   snd_rpi_hifiberry_dac, HifiBerry DAC HiFi pcm5102a-hifi-0 
   Direct sample mixing device

so what happend i was not testing if mpc play would produse sound, i was looking for volume controls in alsamixer, Me the NOOB...

Below is the old OP;

-----------------------------------------------------------------------------------------------------

Need some help;



cat /boot/firmware/config.txt  
# Enable DRM VC4 V3D driver 
dtoverlay=vc4-kms-v3d,noaudio 
# Run in 64-bit mode 
arm_64bit=1 
disable_overscan=1 
arm_boost=1 
dtdebug=1 
dtoverlay=hifiberry-dac 
dtoverlay=i2s-mmap 
dtoverlay=i2c-mmap 
dtparam=i2c1=on 
dtparam=i2c_arm=on

cat /etc/asound.conf 
pcm.!default  { 
type hw card 0 } 
ctl.!default { 
type hw card 0 }

alsamixer tell me no sound controls,

only dtoverlay=hifiberry-dac

will give me;
aplay -l 
**** List of PLAYBACK Hardware Devices **** 
card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pcm5102a-hifi-0 [HifiBerry DAC HiFi pcm5102a-hifi-0] 
 Subdevices: 1/1 
 Subdevice #0: subdevice #0

dacplus dacplus-std

aplay -l 
aplay: device_list:274: no soundcards found...

aplay -L 
null 
   Discard all samples (playback) or generate zero samples (capture) 
default 
hw:CARD=sndrpihifiberry,DEV=0 
   snd_rpi_hifiberry_dac, HifiBerry DAC HiFi pcm5102a-hifi-0 
   Direct hardware device without any conversions 
plughw:CARD=sndrpihifiberry,DEV=0 
   snd_rpi_hifiberry_dac, HifiBerry DAC HiFi pcm5102a-hifi-0 
   Hardware device with all software conversions 
sysdefault:CARD=sndrpihifiberry 
   snd_rpi_hifiberry_dac, HifiBerry DAC HiFi pcm5102a-hifi-0 
   Default Audio Device 
dmix:CARD=sndrpihifiberry,DEV=0 
   snd_rpi_hifiberry_dac, HifiBerry DAC HiFi pcm5102a-hifi-0 
   Direct sample mixing device

Linux pi 6.6.28+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-04-22) aarch64 GNU/Linux

Date Votes

9 comments

0

HiFiBerry team May 05, 2024 19:44

hifiberry-dac is the wrong driver. This won't work. hifiberry-dacplus is the correct overlay. Check if it exists on your system.

Comment actions Permalink

homeplayer May 05, 2024 20:02

I do have hifiberry-dacplus.dtbo
but if i put this in config and reboot
boss@pi:~ $ aplay -l
aplay: device_list:274: no soundcards found...

boss@pi:~ $ cat /boot/firmware/config.txt  
# Enable DRM VC4 V3D driver 
dtoverlay=vc4-kms-v3d,noaudio 
# Run in 64-bit mode 
arm_64bit=1 

# Disable compensation for displays with overscan 
disable_overscan=1 

# Run as fast as firmware / board allows 
arm_boost=1 
dtdebug=1 
dtoverlay=hifiberry-dacplus 
dtoverlay=i2s-mmap 
dtoverlay=i2c-mmap 
dtparam=i2c1=on 
dtparam=i2c_arm=on 
force_eeprom_read=0

0

HiFiBerry team May 06, 2024 06:39

Could be a hardware or software problem. The easiest way to test is to download HiFiBerryOS (https://hifiberry.com/os) and check if the Amp2 is detected correctly.

Comment actions Permalink

homeplayer May 06, 2024 10:55

On Hifiberry Os it works (well almost*) I do have sound

# cat /boot/config.txt 
# Please note that this is only a sample, we recommend you to change it to fit 
# your needs. 
# You should override this file using a post-build script. 
# See http://buildroot.org/manual.html#rootfs-custom 
# and http://elinux.org/RPiconfig for a description of config.txt syntax 

# We always use the same names, the real used variant is selected by 
# BR2_PACKAGE_RPI_FIRMWARE_{DEFAULT,X,CD} choice 
start_file=start.elf 
fixup_file=fixup.dat 

kernel=zImage 

# To use an external initramfs file 
#initramfs rootfs.cpio.gz 

# Disable overscan assuming the display supports displaying the full resolution 
# If the text shown on the screen disappears off the edge, comment this out 
disable_overscan=1 

# How much memory in MB to assign to the GPU on Pi models having 
# 256, 512 or 1024 MB total memory 
gpu_mem_256=100 
gpu_mem_512=100 
gpu_mem_1024=100 
# Enable I2C and SPI 
dtparam=i2c=on 
dtparam=spi=on 
dtoverlay=i2c-gpio,i2c_gpio_sda=0,i2c_gpio_scl=1 
dtoverlay=vc4-fkms-v3d,audio=off 
dtoverlay=hifiberry-dac 
# cat /etc/asound.conf 
#  
# asound.conf for exclusive audio mode 
# 
defaults.pcm.rate_converter "samplerate" 

defaults.pcm.card 0 
defaults.ctl.card 0 

pcm.hifiberry { 
 type hw 
 card 0 
 device 0 
} 
pcm.ttable { 
type route 
#ttable_config:stereo 0 
ttable.0.0 1.00000000000000000000 
ttable.1.1 1.00000000000000000000 
ttable.0.1 0 
ttable.1.0 0 
slave.pcm "hifiberry" 
} 
pcm.softvol { 
 type softvol 
 slave.pcm "ttable" 
 control { 
   name "Softvol" 
   card 0 
 } 
 min_dB -90.2 
 max_dB 0.0 
} 
ctl.equal { 
 type equal; 
} 
pcm.equal { 
 type equal; 
 slave.pcm "plug:softvol"; 
} 
pcm.!default { type plug; slave.pcm "softvol" } # SOFTVOL 
# cat /etc/mpd.conf 
# 
# Sample configuration file for mpd 
# This is a minimal configuration, see the manpage for more options 
# 

# Directory where the music is stored 
music_directory         "/library/music"     

# Directory where user-made playlists are stored (RW) 
playlist_directory      "/library/playlists"     

# Database file (RW) 
db_file                 "/library/mpd"          

# Log file (RW) 
log_file                "syslog" 

# Process ID file (RW) 
pid_file                "/var/run/mpd.pid" 

# State file (RW) 
#state_file              "/var/lib/mpd/state" 

# TCP socket binding             
bind_to_address         "any" 
bind_to_address         "/var/run/mpd/socket"  


audio_output { 
       type            "alsa" 
       name            "HiFiBerry" 
       device          "default" 
       mixer_control   "Softvol" 
       enabled         "yes" 
} 

auto_update "yes"

dmesg | grep hifi 
[    2.327539] systemd[1]: Hostname set to <hifiberry>. 
[    5.625686] systemd[243]: hifiberry-detect.service: Failed to connect stdout to the journal socket, ignoring: Connection refused 
[    5.880024] systemd[285]: hifiberry-detect.service: Failed to connect stdout to the journal socket, ignoring: Connection refused

cat /etc/os-release
NAME=Buildroot
VERSION=2021.11-dirty
ID=buildroot
VERSION_ID=2021.11
PRETTY_NAME="Buildroot 2021.11"

I think i did blowup something, second from the write, can't use that -pole

0

homeplayer May 06, 2024 12:56

Oke all i want is to run a headless server, that can deal whit the amp2
for now i am running around in circles, trying all kinds of config options and rebooting, but no luck in loading drivers for the amp2

Comment actions Permalink
0

HiFiBerry team May 06, 2024 16:43

This cabling is definitely wrong and you may damage the Amp with this. Do NOT connect one speaker to the other speaker output!

If HiFiBerryOS detected the card fine, there is probably a problem with your Raspberry Pi OS installation. Try a fresh installation on a new SD card. SD card corruption can result in all kinds of strange behavior.

Comment actions Permalink
0

homeplayer May 06, 2024 17:46

Cabling will be taken care of, possibly with the addition of a new amp.

Currently, I'm running Raspberry OS from a USB stick. I've gone through about four new installations in an attempt to make it work smoothly.

After testing Hifiberry OS and MusicLounge, I finally got sound. So, the Raspberry Pi is functioning, the Amp2 is mostly operational, and the USB stick is working fine.

Oh man, I just discovered that Hifiberry OS runs DOCKER. I've been scouring the forums and never came across that information before.

BUT can HifiBerry OS be booted from a USB ---> https://www.hifiberry.com/blog/booting-the-raspberry-pi-from-an-usb-stick/ <--- August 5, 2016

Edited by homeplayer May 06, 2024 18:45

Comment actions Permalink
0

HiFiBerry team May 07, 2024 05:06

> BUT can HifiBerry OS be booted from a USB

Not today. This will be coming at some point in the future, but it's not our highest priority.

Comment actions Permalink
0

homeplayer May 08, 2024 11:02

updated OP (first post), Its working

One last thing is; if i poke the big black box thing above the not working connector, it wil work, there for i think there is a lose wire/contact or something, what is it, i know how to replace it, i need to know what it is

Edited by homeplayer May 08, 2024 11:53

Comment actions Permalink

Please sign in to leave a comment.

Subject: Fixed Raspberry OS Audio Issue with HiFiBerry Amp2 (Headless Setup) - Lessons Learned!

Hi everyone,

9 comments

BUT can HifiBerry OS be booted from a USB ---> https://www.hifiberry.com/blog/booting-the-raspberry-pi-from-an-usb-stick/ <--- August 5, 2016