I will check it for experiment. My Volumio is still powered on and I don’t need to wait for power on.
First I want use Volumio with M.2 hat like a home media server but I built NAS with Samba on Pi4.Now I bought another one Pi5 8M and will use with HatDrive on this server.
The Primoroni does not have a power connector, but that consumption seems excessive to me, a Samsung evo has a maximum consumption of 1A, and taking into account that the Raspberry’s PCI is 1x and on a PC they work at 4x, I highly doubt that it will ever reach the maximum, to which we must add the low volumio consumption. but if you add hats and screen it can be, you can try
This is what it says on the Samsung website for the 2TB, and we must take into account that the maximum will be a 4x PCI, with the 1x of the Raspberry it will be much less
Average: 6.1 WMaximum: 7.2 W (Burst mode)* Actual power consumption may vary depending on system hardware & configuration
Few things to consider:
Your Rpi 5 will need to be prepared to boot from NVME using default Rpi distro:
sudo rpi-eeprom-config --edit
BOOT_ORDER=0xf416
PCIE_PROBE=1
Since Rpi 5 does not have audio jack the default alsa config will complain for as long as you do not route your audio over HDMI or a DAC.
Booting Volumio 3 from NVME can be achieved with custom kernel build using Volumio 3 source with skills beyond an average user:
The build process will create a complete Volumio 3 image without “My Volumio” propriety extension. However, if you require “My Volumio” subscription, you take the originally distributed with the Volumio OS volumio_current.sqsh and modify using instructions from this StackExchange thread:
Copy /lib/modules from your build to the volumio_current.sqsh /lib/modules
Update /etc/fstab in volumio_current.sqsh
It would be cleaverer not to use fixed device and partition names at all, we have better examples with non-Pi devices booting from not just SD cards, using UUID
Very elegant and clean approach. Definitely target for the next iteration. UUID is predictable or can be even made static. Thank you for pointing this out.
The POC image is for RPi5 furnished with a PCIe NVME M.2 HAT only. However, the logic will be the same for RPi4. Based on @gkkpch suggestion, the storage device may be anything, for as long as it is a storage device. As such RPi4 would benefit from the approach with likes of USB storages, etc. In turn, use of MicroSD will become a matter of choice, not necessity. Some development effort will be required.
Second problem, with connected NVMe HAT and boot from SD card I can connect via SSH but my LCD is blank and MyVolumio not start. I have only my second Volumio on PC in app and browser. Some conflict with HAT ??
bad idea, if you wish to try a new version from SD, you want it to have unique identifiers so it boots with the correct partitions. Always have new UUIDs for new versions, Volumio already takes care of replacing them with OTA updates.
There’s more to be done, x86 (and tinkerboard) have an option to install to internal disk (e.g. when booted from an SD card). x86 has an ultra- fast copy, which should be extended to RPi as well to support people who are technically less talented. This is not a trivial job for an RPi, it needs quite a few modifications.