I upgraded my Amplipi to 0.3.0 today. The input process seemed to go fine. Afterward, the RCA input still worked, but no other input is working.
I have a number of web streams I use regularly, and now they appear to play but I get no audio. If I turn the volume way up I get some crackling at the top end of the range.
Airplay does not work either. I can see it on the phone once enabled and the Amplipi interface shows the tune that is playing, but again, no audio.
And I had a working doorbell via the /api/announce call, but that is no longer working either.
I’ve tried a HW Reset and a HW Reboot. Any other troubleshooting that can be done? And do I need to re-image it to get back to 0.2.1 or can I just downgrade.
Can you send us the system logs (go to settings->about->logs), as well as you current configuration file (settings->config->save configuration).
In the meantime while you are waiting you may want to try a factory reset (after saving your config) which resets the configuration file to stock just in case anything got messed up during the upgrade.
Thanks. Now that I look at the logs and see this looping, it is pretty clear there is an issue.
I sent full logs and config to support@ email.
Thanks.
-jim
Dec 14 19:34:13 amplipi authbind[828]: Subprocess exited with non-zero code: 1. Restarting…
Dec 14 19:34:13 amplipi authbind[828]: ALSA lib pcm_direct.c:1824:(_snd_pcm_direct_get_slave_ipc_offset) Invalid value for card
Dec 14 19:34:13 amplipi authbind[828]: playback ch3 open error: No such device
Dec 14 19:34:13 amplipi authbind[828]: Loopback initialization failure.
Dec 14 19:34:13 amplipi authbind[828]: Subprocess exited with non-zero code: 1. Restarting…
Dec 14 19:34:13 amplipi authbind[828]: ALSA lib pcm_direct.c:1824:(_snd_pcm_direct_get_slave_ipc_offset) Invalid value for card
Dec 14 19:34:13 amplipi authbind[828]: playback ch3 open error: No such device
Dec 14 19:34:13 amplipi authbind[828]: Loopback initialization failure.
Do you happen to have a user configured ALSA configuration (in /home/pi/.asoundrc), that was used to do some software equalization? I know a couple of our customers experimented with that…
This would override AmpliPi’s global ALSA configuration (set in /etc/asound.conf) and has the potential to cause lots of weird issues such as this.
Either way my instincts are this is an ALSA configuration/hardware issue. To check could you send us the output of the following commands (over an ssh session):
aplay -L
aplay -l
These will tell us what the sound hardware looks like and how it is configured.
It looks like our updates to the ALSA configuration hid the USB audio devices on your AmpliPi due to an old boot configuration file.
There is an extra HDMI audio device that should have been disabled, but wasn’t in older units. I think we either need to have you re-flash your unit to a recent image or just update the file /boot/config.txt on your AmpliPi.
Here’s the current /boot/config.txt file we are shipping with units:
# 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,i2c_arm_baudrate=100000
dtparam=i2s=on
dtparam=spi=on
# Additional overlays and parameters are documented /boot/overlays/README
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
enable_uart=1
gpio=4=op,dh # Preamp RESET pin
gpio=5=op,dl # Preamp BOOT0 pin
# enable i2s DAC
dtoverlay=hifiberry-dac
dtoverlay=i2s-gpio28-31
# Enable SPI1 and SPI2 with two chip selects each
dtoverlay=spi1-2cs
dtoverlay=spi2-2cs
# Default core_freq for Pi3 is 400 MHz
# Lock it so it doesn't scale down and lower SPI speed
core_freq=400
core_freq_min=400
You can edit it over ssh and restart your AmpliPi. This should make all of the sound devices show up again!
Otherwise you can follow the steps here to re-image your unit. NOTE: we are in the process of creating an image with 0.3.0 but it has not been finished yet, so you will have to image to 0.2.1 then update to 0.3.0 at this moment.