Hi,
I got an HiFiBerry amp+ a few months ago. It's been working well via Volumio but stopped working yesterday. I haven't done any system updates, it just stopped giving any audio output when I booted it up in the morning.
I've read a lot of the forums and followed all the install guides (I'm pretty familiar with Linux). I've re-written the Volumio image which I used originally which worked out the box once set up ... but still no sound.
I've tried a different Raspberry Pi (B+) too.
Any suggestions or has the amplifier died?
Thanks,
Dan.
Date
Votes
8 comments
-
HiFiBerry team Hi Dan,
most likely this is a configuration issue. What is the output of
uname
aplay -l
lsmod
Best regards
Daniel -
Dan Barratt Thanks for the quick reply.
Original Volumio install (installed and worked ... then stopped working). Output below is from after it stopped working.
root@ChapelFM:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_amp], device 0: HifiBerry AMP HiFi tas5713-hifi-0 []
Subdevices: 0/1
Subdevice #0: subdevice #0
root@ChapelFM:~# uname -r
3.12.36+
I don't have lsmod in the history.
Fresh install via a dd from the same Volumio img. Then set up via the Volumio interface I believe the same as before. There is no HiFiBerry amp listed in the audio output menu this time, even after selecting it as an i2S driver via Volumio and rebooting. I'm pretty sure that's all I had to do last time. Nothing via the command line with the previous install was required.
root@volumio:~# aplay -l
aplay: device_list:268: no soundcards found...
root@volumio:~# uname -r
3.12.26+
root@volumio:~# lsmod
Module Size Used by
nfsd 247413 2
ipv6 315765 34
snd_soc_hifiberry_dacplus 2327 0
bcm2708_dmaengine 5344 0
virt_dma 2329 1 bcm2708_dmaengine
snd_soc_wm8804 7932 0
snd_soc_pcm512x 9034 0
snd_soc_bcm2708_i2s 6194 0
regmap_mmio 2818 1 snd_soc_bcm2708_i2s
snd_soc_core 127841 4 snd_soc_pcm512x,snd_soc_wm8804,snd_soc_hifiberry_dacplus,snd_soc_bcm2708_i2s
snd_compress 8259 1 snd_soc_core
regmap_i2c 1661 3 snd_soc_pcm512x,snd_soc_wm8804,snd_soc_core
snd_pcm_dmaengine 5505 1 snd_soc_core
regmap_spi 1913 3 snd_soc_pcm512x,snd_soc_wm8804,snd_soc_core
snd_pcm 83845 2 snd_soc_core,snd_pcm_dmaengine
snd_page_alloc 5132 1 snd_pcm
snd_seq 55484 0
snd_seq_device 6469 1 snd_seq
snd_timer 20998 2 snd_pcm,snd_seq
leds_gpio 2079 0
led_class 4118 1 leds_gpio
snd 62252 6 snd_soc_core,snd_timer,snd_pcm,snd_seq,snd_seq_device,snd_compress
spi_bcm2708 4960 0
i2c_bcm2708 4943 0
Thanks,
Dan. -
HiFiBerry team Hi,
as far as I remember, the 3.12.26 kernel did not have Amp support. You were using 3.12.36 before.
You can update to 3.12.36 firmware with
sudo rpi-update 216c2f79ca0633bebe3916184bf3550e1b8f2f80
State of 3.18.x: The bug of the Amp in 3.18.5 has been fixed now. That means if the firmware is updated again, you can just run rpi-update and configure the Amp as documented. However this might still take some time (RPI developers don't update it every day).
You can check here: https://github.com/raspberrypi/firmware
Best regards
Daniel -
Dan Barratt Hi Daniel,
Well spotted, I may well have installed Volumio and then updated the Pi prior to the 3.18 release.
I tried updating to 3.18 and following the instructions but didn't have any luck, so going back to 3.12.36 would be the best option as I know I have it working with 3.12.36 - however I get the following error when trying sudo rpi-update 216c2f79ca0633bebe3916184bf3550e1b8f2f80 as suggested:
root@volumio:~# rpi-update 216c2f79ca0633bebe3916184bf3550e1b8f2f80
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Performing self-update
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 7938 100 7938 0 0 11777 0 --:--:-- --:--:-- --:--:-- 17369
*** Relaunching after update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
*** Downloading specific firmware revision (this will take a few minutes)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 168 0 168 0 0 206 0 --:--:-- --:--:-- --:--:-- 299
100 9 100 9 0 0 5 0 0:00:01 0:00:01 --:--:-- 16
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Thanks,
Dan. -
HiFiBerry team Hmm, can you try another one:
216c2f79ca0633bebe3916184bf3550e1b8f2f80
The list of commits can be found here:
https://github.com/raspberrypi/firmware/commits/master
Otherwise try the first 3.18 release and add the
device_tree=
line to config.txt
However I hope the new kernel will be available soon.
Best regards
Daniel -
Dan Barratt Hi Daniel,
Success!
I installed standard Rasbian (rather than Volumio) and 3.12.36 (using a commit from https://github.com/Hexxeh/rpi-firmware/commits/master#), and followed the 3.12 set-up guide from your web site and I've got sound again.
Maybe I ran an update on on Volumio between it working and not working and didn't remember, that's why it stopped working initially.
Now I know the card is still good I'll go back to Volumio and get it working there again.
Thanks for your help and patience.
Dan. -
HiFiBerry team You're welcome. We will inform the users when the fixed 3.18 Kernel is available through rpi-update.
Best regards
Daniel -
HiFiBerry team A new kernel has been released last night. You can update using rpi-upgrade and configure the Amp with
dtoverlay=hifiberry-amp
in config.txt
Best regards
Daniel
Please sign in to leave a comment.