No Sound - vi headphone jack/powered speakers - OS command level works - and Volumio startup sound

Help and Support Help
1

Working with new Raspberry PI model 3 and Volumio for the first time.
Details of new install

  1. Fresh hardware and Volumio install (v3.512)
  2. Internet works, Volumio app update complete
  3. Sound works via headphone jack and OS command line & Volumio startup sound.
  4. Added plugin (FusionDSP) to allow the app to come up on an attach TV to the PI - this works.
  5. Volumio does dispaly all the internet sites serving music
  6. SSH and remote connections work from a Mac
  7. Using hardwired network connection

My problem might be related to the Alsamixer settings, its pointing to the HDMI port.
I make the change and it reverts back to the original HDMI setting.
Can someone confirm this module is used with Volumio for sound support?

Reading tips on how to make the change in Alsamixer, keep it open and in another terminal session save the file.

thanks for your tips.

2

I have now added the HifiBerry DAC PRO and still having the same issues. I still get sound via a command line entry and the start up sound works via the new setup - just no sound in Volumio

3

please post the results of:
how to enable ssh

cat /boot/config.txt
cat /boot/userconfig.txt
aplay -l

please post a log.

4 
Volumio Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Welcome to Volumio for Raspberry Pi (5.10.92-v7+ armv7l)
volumio@musicstreamer:~$ cat /boot/config.txt
initramfs volumio.initrd
gpu_mem=32
max_usb_current=1
dtparam=audio=on
audio_pwm_mode=2
dtparam=i2c_arm=on
disable_splash=1
hdmi_force_hotplug=1
force_eeprom_read=0

include userconfig.txt

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

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


volumio@musicstreamer:~$ 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 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_dacplus], device 0: HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0 [HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
volumio@musicstreamer:~$
5

Can you test what happens if you select the “Hifiberry DAC”
Then reboot and test.

6

Made the change … see screen shot. No sound, notice the song shows .06 sec. Wehn selecting the channel - seemed to be slow.

Volumio screen after DAC change
Volumio screen after DAC change2236×1193 129 KB

Reboot was done

7

Update - I have noticed the screen shows the song being played - but no sound. I’m reading up on how the volume gets changed. The powered speakers are connected to the Hifiberry DAC – This same setup does play the Volumio startup sound. -AlsaMixer shows: Card: HDMI — when I change and view again… still shows HDMI

8

please do a factory reset and try again, without manual changes on the alsamixer configuration, then please provide a system log, if you still have problems.

please post a picture of your DAC too

9

Ok – not sure what this did.
My steps

  1. Perform reset via menu
  2. Changed to add dac puput
  3. Save - reboot
  4. Enable SSH
  5. Strange error - see log
  6. How else do I get the log?
    logfile_afterreset.txt (3.1 KB)

At new log in - enable logging
This is what is on my laptop SSH. – 50.101 is the correct IP and shows on boot screen
192.168.50.101 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBDRm7YGYELgliUOR08oWont7lC3u2LjejFpwFOAab7AXFrLl+p5QKHVYDeZzcsbBdGhzPdKH18Ng+s+ttKZtnzE=

10

Forgot image of DAC card

20230914_130505
20230914_1305052080×4160 316 KB

11

here the procedure for sending a system log

your DAC is a HifiBerry DAC2 HD

To have Volumio loading the correct driver, you must select HiFiBerry DAC2 HD, that will load the dt-overlay hifiberry-dacplushd

from the aplay log I can see you selected the wrong overlay hifiberry-dacplus

12

Made the change and now getting new error when trying to play a song - no startup sound. I did have the network cable disconnected for a little after that last error about using SSH. Log sent

“Failed to open ALSA devcie volumio”

13

Please copy and paste here the link if the log file

14

http://logs.volumio.org/volumio/2r2bcnM.html

16

I had a better look to your picture, sorry I gave you a wrong information yesterday

your PCB is a HifiBerry DAC2 Pro, not a DAC2 HD

Your DAC requires the dt-overlay hifiberry-dacplus to be loaded.

Unfortunately there is no entry for your DAC in the list, but there are other two that will select the required dt-overlay, with slightly different parameters regarding the eeprom name

HiFiBerry DAC Plus
HiFiBerry DAC+ Pro

could you please try with both?

please don’t forget to reboot after changing the entry in the list and saving

17

Ok – will give it a try. I was wondering why you suggested that model. Thanks for your help

18

Ok – I now have sound. I’m guessing it the doing the full reset, plus getting the correct DAC selected. Time to. learn the new app and PI board.

My plans

  1. Changing default passwords
  2. Enable wireless
  3. Learn how to control volume in the app.
  4. Just ordered the original PI display with display case/stand
  5. Start playing music
  6. Link to my Synology NAS for songs.
  7. Set the IP to static - and separate VLAN

LET THE FUN BEGIN – THANKS SO MUCH FOR THE HELP

1 Like
19

Search this forum, and you will see that this can cause you some problems in the future - just so you then are prepared.

20

I did come across this, but need to read deeper! Sure seems a basic thing to do.

thanks for the heads up.

21

please do not change the default password, just disable ssh from the /dev page

wireless should be enabled by default