RPi 3B Setup Trouble With HiFiBerry Digi+

[Bautar]

Hi Team - I was running my HiFiBerri Digi+ just fine on a RPi2, but decided to upgrade to a Pi 3B+. After a number of failed setups & going through the forum, I determined I would be better off with a Pi 3B, which I tried but the setup issue is fundamentally the same. Here are the specifics I can share:

Computer: Raspberry Pi 3B
Sound Card: HiFiBerry Digi+
RuneAudio: 0.5 Beta, GitPull to version 10
-NOT using Rern
-RuneAudio and song library (about 90 GB) loaded onto a 400GB micro SD.

Problem: Setup including GitPull go fine, but during one of the reboot attempts, a pop-up appears: "!WARNING The loading layer (spinning arrows) points to a socket error". The system seems to recover from this. Then I will load a few web radios and a very limited section of my music library to the SD card (root/mnt/MPD/LocalStorage). System still appears to behave normally. As soon as I attempt to play a song or a web radio, the problem manifests: The UI shows the song playing, but there is no sound output (I2S and HiFIBerry Digi+ selected correctly). At that point, the UI locks up and will never reappear, even after using SSH sending, reboot or "shutdown -h now" commands through PuTTY. I've tried the various recovery commands with no luck. After research both on HiFiBerry's site and the Rune Forum, I edited the config file to remove "#" from the "dtoverlay=pi3-disable-bt overlay", but this did not solve the problem.

I can still log in to the RPi 3B via PuTTY, but I'm not sure how to address this after numerous setup attempts. Is there more info I can pull using PuTTY to help diagnose?

Thanks much for any help!

Ken

[janui]

Hi Bautar,
This sounds a little familiar. This sort of problem occurs when rune looses an active internet connection, a bad image has been loaded or MPD cant find an output device.
A couple of questions:
Did you check the SHA-256 checksum of your download file?
Have you tried reflashing your SD card?
Are you using a WiFi connection for Rune?
When the UI freezes up can you use SSH to connect to Rune?
Did you switch off the 3,5mm and hdmi output?
Did your HiFiBerry Digi+ appear in the MPD UI? Did you select it?
janui
PS You manually edited the config.txt file to activate your sound card, if you did it correctly this should not be a problem, but there is an option to do this automatically in the Settings UI.

[Bautar]

Thanks for your feedback, Janui. I've replied to your questions below. Based on your comments, I reflashed (again), but this time I first used the RPi3B's analog output, and this worked fine. When I switched on the HiFiBerry Digi+ in Settings and selected it in the MPD, the problem returned immediately: no sound output through card and I can again no longer access the UI (although I can SSH into the Pi). I'm beginning to think my HiFiBerry Digi+ card is damaged. It has a solid green LED light, and it worked in the past with Rune 0.4 in a Pi 2B. I will rebuild that setup to test unless my answers below give you other insight.

Many thanks!
bautar

A couple of questions:
Did you check the SHA-256 checksum of your download file? Downloaded a new file, and ran SHA-256 checksum. Returned this: b27cb298536eb163c20b50fbeed033263d4bcd4d5226f6a239bece26bfd414a7
Have you tried reflashing your SD card? Yes, many times.
Are you using a WiFi connection for Rune? No; using just a LAN cable.
When the UI freezes up can you use SSH to connect to Rune? Yes, I can still get in with SSH.
Did you switch off the 3,5mm and hdmi output? Yes.
Did your HiFiBerry Digi+ appear in the MPD UI? Did you select it? Yes and yes.
janui
PS You manually edited the config.txt file to activate your sound card, if you did it correctly this should not be a problem, but there is an option to do this automatically in the Settings UI. ANSWER: My understanding of the config file mod I made was to disable bluetooth, which at one time was a problem with HiFiBerry Digi+. I have since re-imaged and did not make this mod.

User avatar
janui

Posts: 551
Joined: 20 Dec 2014, 06:55
Location: Ollanda

[janui]

Hi Bautar,

...I've replied to your questions below...

Your answers eliminate a bad SD Card and your experiments using the pi 3.5mm audio output seem to show that Rune is actually working and there is no internet connection problem.
In addition to suspecting your HiFiBerry board, check your power supply. Watch the red led on the Pi board when booting and switching the audio output. It should not blink or go out.
Via ssh you may be able to get some diagnostics after it freezes with this command:

Code: Select all

journalctl | grep -i -E 'error|warning|hifiberry|digi|alsa|mpd'

janui

[Bautar]

Janui -
Thank you for your direction! Unfortunately I cannot rebuild my original functioning setup with the RPi 2, as a colleague has repurposed it & it is no longer in my shop. But I checked my power supply; it is a wall-wart switching supply unit rated at 2 amps; during startup/function/activation of HiFiBerry, it did not dim nor blink at all. Should be good, but I was concerned at the 2 amp rating so I replaced the PS with a physically larger 3 amp switcher to test. This one blinked A LOT after I reflashed my micro SD & restarted, and the system malfunctioned again after choosing the HiFiBerry Digi+. I have the parts for a high-current linear power supply but haven't built it yet, and I'm now questioning the validity of amperage ratings on stickers from low-cost country power supplies.

Based on this, I haven't ruled-out power supply as root cause of my problem but I will do that shortly. The debug command you gave me for SSH yielded a lot of output, pasted below. I reflased my micro SD, put the card into the computer, powered it with the "non-blinking" power supply, then immediately ran your debug command line via SSH. This represents the first grouping of output below.

Then I performed limited setup, just loading one song as library, chose the HiFiBerry Digi+, let the system lock-up, then used your command line through SSH; this represents the second grouping of output below, separated by my line of xxxxxx's. I would appreciate if you could scan this output & see if anything jumps out which easily points to faulty HiFiBerry Digi+, or weak supply.

Thanks!!
Bautar

OUTPUT FROM BRAND NEW SD FLASH OF VERSION 0.5 BETA:

root@runeaudio(rw):~# journalctl | grep -i -E 'error|warning|hifiberry|digi|alsa|mpd'
Apr 12 15:27:05 runeaudio kernel: sdhci: Secure Digital Host Controller Interface driver
Apr 12 15:27:05 runeaudio kernel: Error: Driver 'sdhost-bcm2835' is already registered, aborting...
Apr 12 15:27:07 runeaudio kernel: bcm2835_alsa bcm2835_alsa: card created with 8 channels
Apr 12 15:27:08 runeaudio systemd[1]: Started RuneAudio MPD watchdog.
Apr 12 15:27:08 runeaudio sh[251]: /var/www/command/mpd-watchdog: starting...
Apr 12 15:27:13 runeaudio alsamixer_webui.py[246]: * Running on http://0.0.0.0:8080/ (Press CTRL+C to quit)
Apr 12 15:27:19 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 12 15:27:19 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 12 15:27:19 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 12 15:27:19 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 04 12:10:24 runeaudio logrotate[2926]: error: failed to rename /var/log/rune audio/ui_error.log to /var/log/runeaudio/ui_error.log.1: Operation not permitted
Apr 04 12:11:28 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 04 12:11:28 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 04 12:11:28 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 04 12:11:28 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 04 12:12:58 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 04 12:12:58 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 04 12:13:04 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 04 12:13:04 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 04 12:13:05 runeaudio rune_SY_wrk[287]: Warning: Missing argument 3 for wrk_ sourcecfg(), called in /srv/http/command/rune_SY_wrk on line 129 and defined in /srv/http/app/libs/runeaudio.php on line 3063
Apr 04 12:13:05 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 04 12:13:05 runeaudio rune_SY_wrk[287]: mpd error: Connection refused
Apr 04 12:13:06 runeaudio mpd[3148]: exception: Failed to open /var/lib/mpd/mpd. db: No such file or directory
Apr 04 12:13:07 runeaudio mpd[3148]: output: No 'AudioOutput' defined in config file
Apr 04 12:13:07 runeaudio mpd[3148]: output: Attempt to detect audio output devi ce
Apr 04 12:13:07 runeaudio mpd[3148]: output: Attempting to detect a alsa audio d evice
Apr 04 12:13:07 runeaudio mpd[3148]: output: Successfully detected a alsa audio device
Apr 04 12:13:17 runeaudio dnsmasq[3630]: warning: interface wlan0 does not curre ntly exist

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

COMMAND OUTPUT AFTER SETUP FAILURE; LOSS OF UI ACCESS:

root@runeaudio(rw):~# journalctl | grep -i -E 'error|warning|hifiberry|digi|alsa|mpd'
Apr 12 15:27:05 runeaudio kernel: sdhci: Secure Digital Host Controller Interface driver
Apr 12 15:27:05 runeaudio kernel: Error: Driver 'sdhost-bcm2835' is already registered, aborting...
Apr 12 15:27:07 runeaudio kernel: bcm2835_alsa bcm2835_alsa: card created with 8 channels
Apr 12 15:27:07 runeaudio kernel: snd-hifiberry-digi soc:sound: ASoC: CPU DAI (null) not registered - will retry
Apr 12 15:27:07 runeaudio kernel: snd-hifiberry-digi soc:sound: ASoC: CODEC DAI wm8804-spdif not registered - will retry
Apr 12 15:27:07 runeaudio kernel: snd-hifiberry-digi soc:sound: ASoC: CODEC DAI wm8804-spdif not registered - will retry
Apr 12 15:27:07 runeaudio kernel: snd-hifiberry-digi soc:sound: wm8804-spdif <-> 3f203000.i2s mapping ok
Apr 12 15:27:08 runeaudio systemd[1]: Started RuneAudio MPD watchdog.
Apr 12 15:27:09 runeaudio sh[248]: /var/www/command/mpd-watchdog: starting...
Apr 12 15:27:09 runeaudio alsactl[282]: Found hardware: "HifiberryDigi" "" "" "" ""
Apr 12 15:27:09 runeaudio alsactl[282]: Hardware is initialized using a generic method
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #1 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #2 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #3 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #4 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #5 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #6 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #7 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #8 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #9 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #10 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #11 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #12 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #13 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #14 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #15 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #16 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #17 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #18 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #19 (No such file or directory)
Apr 12 15:27:09 runeaudio alsactl[282]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #20 (No such file or directory)
Apr 12 15:27:10 runeaudio systemd-udevd[217]: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
Apr 12 15:27:13 runeaudio alsamixer_webui.py[249]: * Running on http://0.0.0.0:8080/ (Press CTRL+C to quit)
Apr 04 12:28:26 runeaudio rune_SY_wrk[317]: mpd error: Connection refused
Apr 04 12:28:26 runeaudio rune_SY_wrk[317]: mpd error: Connection refused
Apr 04 12:28:38 runeaudio dnsmasq[905]: warning: interface wlan0 does not currently exist
Apr 04 12:36:06 runeaudio kernel: bcm2835-i2s 3f203000.i2s: I2S SYNC error!
Apr 04 12:36:23 runeaudio sh[248]: /var/www/command/mpd-watchdog: restarting mp
Apr 04 12:36:53 runeaudio sh[248]: mpd error: Timeout
Apr 04 12:36:53 runeaudio sh[248]: /var/www/command/mpd-watchdog: error restarting mpd

[Bautar]

OK. Problem solved fundamentally by your earlier reply. The case I used has the RPi on the bottom half and the HiFiBerry on the top half and assembling them together does not guarantee connection between all pins. So the HiFiBerry had power but not full communication. Grrrrrrr.

Thanks for your help!