Dear all,
My volumio setup seems to have run into an issue. My setup is Pi 3B+ with Kali and Piano 2.1 (see here for further details: Volumio + 2.42" OLED + PSU in one aluminium case - #22 by Zhapox).
A couple of days ago I turned it on again but it didn’t seem to be accessible over the network. Lights turn on however. To rule out a faulty SD card I took another one, flashed it with the latest built and plugged it in. Volumio comes up with the setup page which I can click through up to the point of selecting the DAC. As soon as I select “Piano 2.1” the web interface no longer responds. Ping still works. Reboot doesn’t help.
I then reflashed again and clicked through the setup guide without selecting a DAC and I successfully landed on the playback page. However, if go to playback options and select the DAC the same symptoms appear. Before going that far I ensured to enable SSH and I can still access it via that way.
I could imagine a hardware defect with either Kali or Piano but I’d like to see if there are any specific hints.
Are there any logs I could look at to see where the issue is coming from?
I just updated to version 3.779 (Raspbery 3b + Allo Piano and Allo Kali). As always I was waiting for some issue to the configuration (usually I have to restore some parameter, it hurts, but it’s a matter of minutes and memory, my memory such as “where did I stored those parameters backup ?”). This time, as happened in the past. The bbot goes on, up to the login (command line) but it’s impossible to connect to volumio local (nor dirtectly to the ip address).A fresh installation on a new sd card starts but it does not work at all. If I connect a monitor I can see the boot and, at some point the screen goes black and energy saving does its job. Any idea ? Can I restore the previous version somehow ? Any config to check ?
Thanks
p.s. As a premium user I wonder why I still accept to update when the popup suggests this harmful operation )
After 3 hours of (… argh …) I decided to create a second sd backup with the most recent but usable version with my configuration (Raspberry PI 3b + Allo Piano 2.1 + Allo Kali). If Volumio’s team would consider me as a tester before releasing a version, I am available.
I do have issues too with V3.779 and Allo Piano 2.1 + Allo Kali, but for me it’s in combination with a Raspberry 5.
It is that after the update I first have to select my DAC because I2S DAC is set to OFF (I cannot remember whether this is always the case with updates). The problem is that if I set I2S DAC to ON during the initial setup and then select ‘Allo Piano 2.1’, the system crashes. And this in a way that I partly cannot boot with the SD card anymore. I say ‘partly’ because I have tried it at least 5 times and sometimes I needed a new SD card. In other words, my repeated attempts were not updates but new installations, which all always crashed exactly when I selected ‘Allo Piano 2.1’.
It would be great if other users who also own Allo’s Piano 2.1 would let me know if they are also having problems or if the update was successful for them.
The update succeeded on my other streamer with Rasberry 4 and Allo Boss. However, only on the 3rd attempt. On the first two attempts, it started normally after the supposed update process, but with the previous version (?).
I’m exactly in your case. Thought that something was faulty in my equipment, but after spending the whole weekend reflashing the latest version of volumio in the SD card and doing multiple tests and troubleshooting, I’m sure it has to do with the new version of volumio.
Something must be wrong with it, 'cause I can ping, I can ssh, but web ui doesn’t work at all. Neither through wifi, nor ethernet.
Please, should someone from volumio reading this, I can offer myself to help you out detecting where is the problem. My equipment is based on Pi 3 model b + Allo piano 2.1 + kali reclocker. But in the meanwhile, I’m installing previous version of volumio.
For me it’s that the web GUI is available, but as soon as I change to I2S DAC and select “Allo Piano 2.1” the system crashes.
I also installed the previous version (V3.757) and now I could select “Allo Piano 2.1” as DAC successfully. But I like to add that when I pressed “Play” I first got the “Alsa” failure message and Volume output only offered “Software” and “None”. After a reboot “Hardware” was available and since that it’s playing fine. I only mention this because I frequently got this “Alsa” failure (see here) since a long time, i.e. it might that in fact linked with a problem of the hardware.
My take on the problem with Raspberry Pi 5 is that the HDMI audio routing from BCM takes priority.
From your description of the problem it is apparent that without access to the hardware it will be a momentous task to troubleshoot. From what I read, debugging is not you are familiar with and you rather expect a solution to be provided. If you are willing forward your hardware for problem research, this would speed up the process.
(Raspbery 4 + Allo Piano 2.1 and Allo Kali, updated to 3.779 and it’s broken. Downloaded image and created new on 3 different SD cards but still no joy, crashes out during setup every time.
Downloaded 3.757 from the link above and all working again.
I recently opened another topic describing issues with Volumio and Kali + Piano 2.1 here:
In short: After updating to version 3.779 Volumio no longer comes up at my setup. I then took a new SD card, flashed 3.779 onto it and that came up with the configuration wizard. As soon as I select Piano 2.1 as DAC Volumio crashes. Whether it be in the configuration wizard or at a later point, it doesn’t matter. The system will immediately stop responding. A forced reboot by removing power will not resolve the issue.
I first suspected a hardware issue with the DAC but that appears to be false. I was able to flash an older version (3.631, the only one I currently have) and got it running with Piano 2.1 without issues.
Hardware: RPI 3B+ DAC: Allo Kali + Piano 2.1
Steps to reproduce:
Scenario 1:
Have a version prior 3.779 installed
Have Piano 2.1 selected as DAC
Update to version 3.779, the update might complete but after triggering a reboot the device will not come up again
Scenario 2:
Have version 3.779 freshly flashed onto an SD card
Boot the device with the freshly flashed SD card
Run through the configuration wizard and select Piano 2.1 as DAC, the system will become unresponsive immediately
Please let me know if there are any tests or other steps I can take to help fixing this bug. I’d gladly contribute to that and would love to enjoy the latest version of Volumio on my system.
I just learned my topic got moved into here. Thanks!
I tried this after freshly flashing 3.779 and selecting Piano 2.1 at the configuration wizard. The command returns no response so I assume that it does no longer work.
I checked to content of that JavaScript file to see which logs it’s collecting. Looking through journalctl I spotted some hints:
Nov 22 15:12:42 volumio sudo[2073]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/dtoverlay allo-piano-dac-plus-pcm512x-audio
Nov 22 15:12:42 volumio sudo[2073]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 22 15:12:42 volumio kernel: OF: overlay: WARNING: memory leak will occur if overlay removed, property: /soc/i2s@7e203000/status
Nov 22 15:12:42 volumio kernel: OF: overlay: WARNING: memory leak will occur if overlay removed, property: /soc/i2c@7e804000/status
Nov 22 15:12:42 volumio kernel: OF: overlay: WARNING: memory leak will occur if overlay removed, property: /soc/sound/compatible
Nov 22 15:12:42 volumio kernel: OF: overlay: WARNING: memory leak will occur if overlay removed, property: /soc/sound/audio-codec
Nov 22 15:12:42 volumio kernel: OF: overlay: WARNING: memory leak will occur if overlay removed, property: /soc/sound/i2s-controller
Nov 22 15:12:42 volumio kernel: OF: overlay: WARNING: memory leak will occur if overlay removed, property: /soc/sound/mute1-gpios
Nov 22 15:12:42 volumio kernel: OF: overlay: WARNING: memory leak will occur if overlay removed, property: /soc/sound/mute2-gpios
Nov 22 15:12:42 volumio kernel: OF: overlay: WARNING: memory leak will occur if overlay removed, property: /soc/sound/status
Nov 22 15:12:42 volumio volumio[968]: warn: Unable to locate the device Allo Piano 2.1 a reboot may be required.
Nov 22 15:12:42 volumio sudo[2073]: pam_unix(sudo:session): session closed for user root
Nov 22 15:12:42 volumio kernel: snd-allo-piano-dac-plus soc:sound: snd_soc_register_card() failed: -517
Nov 22 15:12:42 volumio kernel: snd-allo-piano-dac-plus soc:sound: snd_soc_register_card() failed: -517
Nov 22 15:12:42 volumio volumio[968]: info: CoreCommandRouter::executeOnPlugin: i2s_dacs , getI2sStatus
Nov 22 15:12:42 volumio volumio[968]: info: CoreCommandRouter::executeOnPlugin: i2s_dacs , getI2SMixer
Nov 22 15:12:42 volumio kernel: pcm512x 1-004c: supply AVDD not found, using dummy regulator
Nov 22 15:12:42 volumio kernel: pcm512x 1-004c: supply DVDD not found, using dummy regulator
Nov 22 15:12:42 volumio kernel: pcm512x 1-004c: supply CPVDD not found, using dummy regulator
Nov 22 15:12:42 volumio kernel: pcm512x 1-004d: supply AVDD not found, using dummy regulator
Nov 22 15:12:42 volumio kernel: pcm512x 1-004d: supply DVDD not found, using dummy regulator
Nov 22 15:12:42 volumio kernel: pcm512x 1-004d: supply CPVDD not found, using dummy regulator
Nov 22 15:12:42 volumio kernel: snd-allo-piano-dac-plus soc:sound: snd_soc_register_card() failed: -517
Later messages like this appear:
Nov 22 15:15:41 volumio kernel: INFO: task alsactl:2111 blocked for more than 122 seconds.
Nov 22 15:15:41 volumio kernel: Tainted: G C 6.6.56-v7+ #1803
Nov 22 15:15:41 volumio kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 22 15:15:41 volumio kernel: task:alsactl state:D stack:0 pid:2111 ppid:2088 flags:0x00800000
Nov 22 15:15:41 volumio kernel: __schedule from schedule+0x54/0xe8
Nov 22 15:15:41 volumio kernel: schedule from schedule_preempt_disabled+0x14/0x18
Nov 22 15:15:41 volumio kernel: schedule_preempt_disabled from rwsem_down_read_slowpath+0x220/0x48c
Nov 22 15:15:41 volumio kernel: rwsem_down_read_slowpath from down_read+0x50/0x100
Nov 22 15:15:41 volumio kernel: down_read from snd_soc_card_get_kcontrol+0x24/0x7c [snd_soc_core]
Nov 22 15:15:41 volumio kernel: snd_soc_card_get_kcontrol [snd_soc_core] from snd_soc_limit_volume+0x2c/0x5c [snd_soc_core]
Nov 22 15:15:41 volumio kernel: snd_soc_limit_volume [snd_soc_core] from pcm512x_set_reg_master+0x108/0x124 [snd_soc_allo_piano_dac_plus]
Nov 22 15:15:41 volumio kernel: pcm512x_set_reg_master [snd_soc_allo_piano_dac_plus] from snd_ctl_ioctl+0x200/0x9b4 [snd]
Nov 22 15:15:41 volumio kernel: snd_ctl_ioctl [snd] from sys_ioctl+0x110/0xa20
Nov 22 15:15:41 volumio kernel: sys_ioctl from __sys_trace_return+0x0/0x10
Nov 22 15:15:41 volumio kernel: Exception stack(0xb8dc9fa8 to 0xb8dc9ff0)
Nov 22 15:15:41 volumio kernel: 9fa0: 7e8fcf4c 005e0d68 00000003 c2c85513 005e9d10 005e9668
Nov 22 15:15:41 volumio kernel: 9fc0: 7e8fcf4c 005e0d68 00033aa8 00000036 00000002 00000000 00000000 00000002
Nov 22 15:15:41 volumio kernel: 9fe0: 76f0d818 7e8fc7dc 76e6408c 76cf0e3c
Nov 22 15:15:41 volumio kernel: INFO: task amixer:2124 blocked for more than 122 seconds.
Nov 22 15:15:41 volumio kernel: Tainted: G C 6.6.56-v7+ #1803
Nov 22 15:15:41 volumio kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
This is just an extract. I attached the complete txt dump to this post. The other .log files listed in the JavaScript either didn’t seem to have any meaningful content or didn’t exist.
)