Hi @rkorell
I am running rPi4’s and rPi5’s, mainly for supporting Volumio. (only 1 rPi5 is used on a remote location as main player)
The rPi5’s run stable , on both IR- as BT-Remote.
I have 1 rpi5 running with a 4.3 Inch DSI, 1 with a 7Inch DSI, both function without a glitch.
Only thing to consider with the rPi5, is a 5A PSU and cooling.
8 posts were split to a new topic: Raspberry Pi 5 8GB - Out-of-Memory (OOM) Killer Activations
I got this screen on pi 5 how do I get off it
thanks
Sorry, I just saw your post and I don’t understand your question.
Andy
My frustrating but ultimately successful experience setting up Volumio to boot via NVMe. Maybe I’m the only person to make this small mistake that led to me pulling my hair out for a whole morning, but maybe it’ll help someone.
I was trying to use SD Copy on Raspberry Pi OS to copy Volumio Beta from a USB SSD to a new M.2 NVMe mounted on a Pimoroni PCIe hat.
I had up-to-date Raspbian on an SD card and on the NVMe drive (clue!) and Volumio 4.062 on the USB drive.
What I tried:
Updated my Pi5 to the latest EEPROM firmware using the new updater plugin.
Set boot order to SD-USB-NVMe using the EEPROM config plugin.
Boot to Raspbian using the SD card so I could use the SD Copy program.
Each time it would show options to copy from USB-SD, SD-USB, NVMe-SD and NVMe-USB, but not SD or USB to NVMe. I tried different combinations of boot order using the EEPROM Config plugin, even excluding NVMe, so USB-SD (another USB drive with Raspbian) and SD-USB. Nothing worked.
Then it dawned on me that the Raspberry Pi OS on the NVMe was a clone of the SD. Even if it booted Raspberry Pi OS via SD, the NVMe was taking over! The solution was to change the system name on the SD’s OS and then it saw the SD as a separate system. Finally SD Copy offered the option to copy from SD /USBto NVMe. It works, it’s great!
Thanks to the devs for the excellent new EEPROM plugins.
Hello everyone,
I’m still having some difficulties. I found several pieces of information in community threads. I’ve tried multiple things, but I still can’t solve my issue: I am able to boot using SSD with USB enclosure but I am never able to reboot.
I’ve tested this with 3 different SSD drives/enclosures.
I tried rebooting with the same hardware using different distributions : (Raspberry Pi OS Debian Trixie, Moode Audio 9.4.1, and LibreELEC and I have no issue rebooting via USB-SSD.
I tried plugging the drives into USB 2.0 ports, and that didn’t work either.
I attempted various EEPROM configurations as suggested in the post https://community.volumio.com/t/plugin-raspberry-pi-eeprom-configuration-manager/74038, but nothing was usefull in my case.
I updated the firmware on one of the SSD enclosures as described in the post: community.volumio.com/t/guide-prepare-raspberry-pi-for-boot-from-usb-nvme/65700/46. I also disabled UAS with usb-storage.quirks=0bda:9210:u using the relevant material ID.
Hardware:
Why does it works with all other distributions but not with Volumio 3 or 4? I don’t think the issue lies with the EEPROMs since everything works fine with other distributions.
Does anyone has such configuration working, can you please share any relevant information or workaround that can help. Of course maybe I am wrong but I am now totally lost…
It’s hard for myself to imagine that the issue could be related to the Pi’s EEPROM configuration or the hardware itself, since everything works fine with the other distributions I tested and with all three SSD enclosures.
Many thanks in advance.
Best Regards
Ben
cmdline.txt :
volumio@volumio3-orico:~$ cat /boot/cmdline.txt
splash plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 quiet console=serial0,115200 console=tty1 imgpart=UUID=7f0c0e47-027d-47ad-bd0c-5159b014252e imgfile=/volumio_current.sqsh bootpart=UUID=10D8-1DF5 datapart=UUID=307f8728-204c-4df1-9dcc-f9fb9dec6fbe uuidconfig=cmdline.txt pcie_aspm=off pci=pcie_bus_safe rootwait bootdelay=7 logo.nologo vt.global_cursor_default=0 net.ifnames=0 snd-bcm2835.enable_compat_alsa= snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 loglevel=0 nodebug use_kmsg=no usb-storage.quirks=0bda:9201:u
From my recent experience…and elaborated by @nerd re: NVME boot…
For my Pi4, I had no issues when booting NVME via USB3 when I was using POE to power the Pi. While testing with USB power alone, I also faced instabilities while booting off NVME via USB3/2. It is very likely you’re running the same issue. Look for a post or thread by nerd re: NVME boot for more info.
This post, but looking at the cmdline, he already did.
Yes, but maybe I miss something… But what… I can not know … And my question is why it can works with other distros and not Volumio…
Maybe @nerd has some additional idea’s. I never got it able to work on a rPi4, with different brands of USB Thumbs and disks.