Hi all,
I have been very happily using Volumio with NVMe on Raspberry Pi5 for some weeks now.
I wanted to get everything finished off, hence putting the assembly into an enclosure with a PSU. Part of that was my thought that my preamp already creates and on/off signal to turn the amplifier on and off, so I could piggy back that so the Volumio system also starts alongside.
To do it, I wanted LED indication once the unit was started, an indication that the unit had shut down (so power can be removed) and a “button” type input to instigate that shutdown process.
Using the Control plugin I got the LEDs working properly.
However, the Button plugin did not work for me. Ok, maybe it is not yet migrated to RPi5, no probs.
I thought though that Audiophonics On/Off actually offered these functions that I needed, so I naively grabbed it and set the pins up how I wanted. That is the last time my system shut down!
It now starts, the RPi5 indicator lights green, then after maybe 30 seconds it turns red. Not enough boot to see the Volumio on the app, so I really have no idea what it is doing.
I thought maybe one of the pins (i.e, shutdown input) was active, causing it to detect a shutdown as soon as it started, but I tried pulling all the GPIO I had assigned both high and low and re-powering to no avail.
Perhaps something else is happening?
Is there anything I can try before doing a flat install and copying all my music back over again, which I’d really rather not do…
Thanks!
A few things that comes to my mind:
- Power issues (Power/current drop during boot)
- Corrupted SD (see you run from NVMe) so prob. not an issue
- Broken rPi5 due to shortening the wrong pins.
The rPi5 has a HW power function, so for that part nothing else is required. Just hookup a momentary switch to the PCB.
To test, just flash a new SD, remove all connections you’ve made to the GPIO and see if it boots.
Hi,
Thanks for your response.
This is still being ran from the same wall power adapter I have used the last few weeks, the new PSU hasn’t been implemented yet, so I am doubtful the power is dipping, unless that plugin causes some additional draw at startup.
This is running from the NVMe, it contains the OS and the media. It’s possible it has corrupted, but odd it coincides exactly with adding this plugin.
The hookup is pretty safe, I checked it carefully with a DMM before ever powering up and it all measures fine still.
It feels like something in the software is kicking back off when this plugin tries to start, maybe it can’t see the Hat it is expecting or it simply behaves badly with RPi5?
I will probably have to load up an SD card with Raspbian and use that OS to inspect the NVMe a bit further, otherwise I just can’t start it up to get any clues.
Thanks.
Hi,
I took a look at this today and have resolved the issue. I’ll explain in case it is useful to someone else!
Most the challenge is just working around a headless OS which isn’t starting up. I created a Raspbian OS on SD card, and fortunately I never changed my boot order so it always tries SD card firstly. That boots, I have to use VNC (once enabled via PuTTy) because I never even bought a mini HDMI lead!
From there, I can quite quickly find the “plugins” directory (I can’t recite the exact path though) on the NVMe drive, and clearly labelled inside are the Control, Button and Audiophonics sub-directories. I simply delete the Audiophonics directory and shut down. Remove SD card and boot again, all starts up correctly!
So, maybe there is a quite severe compatibility issue with the Audiophonics plugin and Raspberry Pi5 2GB? Hard to be sure, but I’d perhaps advise caution to those using that platform.
Anyhow, flat-install avoided, all the music etc. is still there, a decent outcome!