0

AMP2 not working on a system I'm working on

Gengqin

October 06, 2020 17:54

None

Follow

Hi,

I am trying to use an AMP2 to play music on a rpi I'm working on. After following the configuration instruction, the rpi recognize the AMP2 but the system still shows "No volume control on this device"

I looked through the forum. Most of the discussion seems to suggest my SD card is corrupted. I did get a new sd card, and it works. But transferring all my code is something I'd really like to avoid doing. So I'd like to ask and confirm my issue. Is there something wrong I did to cause this issue? 

 

Here are the information I got:

amm@raspberrypi:~ $ aplay -l

**** List of PLAYBACK Hardware Devices ****

card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ HiFi pcm512x-hifi-0 [HiFiBerry DAC+ HiFi pcm512x-hifi-0]

  Subdevices: 1/1

  Subdevice #0: subdevice #0

 

amm@raspberrypi:~ $ amixer

amixer: Mixer attach default error: Invalid argument

 

Here is the config.txt:

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
# hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835) Disabled for Hifiberry config
# dtparam=audio=on

#this following line is added for hifiberry config to load the correct device tree file
dtoverlay=hifiberry-dacplus
force_eeprom_read=0

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
dtoverlay=vc4-fkms-v3d
enable_uart=1

dtoverlay=disable-bt

# Debug

dtdebug=1

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  David C. Snyder October 06, 2020 18:05

  Your "aplay -l" looks right. What do you have in /etc/asound.conf? Mine looks like this:

  root@psb-pi:~# cat /etc/asound.conf
  pcm.!default {
      type hw
      card 0
      device 0
  }
  ctl.!default {
      type hw
      card 0
  }

  Here's what I'm seeing in alsamixer (under DietPi v6.32.2, but you should see something similar):

  

  Perhaps try re-flashing your microSD card with HiFiBerryOS. It has the nicest looking webUI that I've seen for devices like this and makes configuring HiFiBerry sound cards a snap.

• 0
  
  Gengqin October 06, 2020 18:19

  This is what I have:

  pcm.!default {

          type hw card 0

  }

  ctl.!default {

          type hw card 0

  }

  
  
  This is what I get:

  amm@raspberrypi:~ $ alsamixer

  cannot open mixer: Invalid argument

  
  The thing is, I am developing a module on the rpi based on someone else's setup. Re-flashing my card is a real pain. I'd like to ask if that's what I absolutely need to do.

• 0
  
  David C. Snyder October 06, 2020 18:40

  Well, perhaps order a few more microSD cards that you have some to experiment with: https://www.amazon.com/SanDisk-Ultra-microSDXC-Memory-Adapter/dp/B073K14CVB/

  Looking at what files are opened when I run alsamixer, here are some of the things I see:

  /usr/share/alsa/alsa.conf
  /usr/share/alsa/alsa.conf.d/
  /etc/asound.conf
  /dev/snd/controlC0

  It may be worth making sure that you have all of these and that the contents look valid. For example:

  root@psb-pi:~# ls -ld /usr/share/alsa/alsa.conf /usr/share/alsa/alsa.conf.d/ /etc/asound.conf /dev/snd/controlC0
  crw-rw---- 1 root audio 116, 0 Sep 10 19:45 /dev/snd/controlC0
  -rw-r--r-- 1 root root 93 May 10 2019 /etc/asound.conf
  -rw-r--r-- 1 root root 9663 Mar 25 2019 /usr/share/alsa/alsa.conf
  drwxr-xr-x 2 root root 4096 May 10 2019 /usr/share/alsa/alsa.conf.d/

  I don't have anything interesting under alsa.conf.d. My alsa.conf is 634 lines (unmodified from a default install of DietPi)

  If you just want to enjoy nice music, HiFiBerryOS is a great way to go. If you are doing development on the RPi, you'll have to figure out what's wrong with the setup you were provided or try basing your development on a different (working) distribution, like DietPi.

• 1
  
  Gengqin October 06, 2020 18:56

  Thanks.

  I guess my best bet is to start fresh and figure out which step of the setup (on the development) went wrong.