Raspberry Pi 5 Support
Will you be adding RPI5 Support?
thanks
Yes please.... I am also eager to know if pinn will be updated to support RPi5
Please,,,
Sorry, github has stopped sending me notifications so I missed many messages - I will have to fix that. Anyway, I have been working on PI5 for several months. Finally I am seeing light at the end of the tunnel. It will still be a little while yet, but it's coming....
Just chasing for an update on Pi5 compatibility. Version 3.8.9 seems to get as far as letting us install OS-es, but when booting into one of them the Pi5 appears to reboot. Any work-around?
Using a micro SD from Samsung (512 Pro Ultimate).
It is essenrial to upgrade your firmware, as detailed in the release post https://forums.raspberrypi.com/viewtopic.php?p=2173713#p2173713
Many thanks for the quick reply. I've shared this info with the discussion thread under this YouTube video: https://www.youtube.com/watch?v=WVCNPCHN4xU
The video is all about trying to get PINN working on a Pi 5.
The readme file in the rpi-eeprom-recovery.zip indicates it's intended for Raspberry Pi 4 specifically. Is it safe to run it on Pi 5?
Yes. they (RPL) probably forgot to update the readme. It is essential to get multi-boot working. A small regression when they were getting Power Delivery sorted.
Thanks for adding the comment to Leepsvideo. I tried to add my own comment with a link, but It wasn't very satisfactory.
Got it. I'll give it a try. Thanks for the quick reply.
Yep, that one works. Successful boot into Ubuntu 23.10. Hope RPL get around to releasing a fixed firmware.
I don't know their timescale, but it will eventually make it into a future apt-update; apt full-upgrade
It looks like it was fixed in the pieeprom-2023-12-14 release https://github.com/raspberrypi/rpi-eeprom/commit/3f325bd482649e697ddf46c1484a1a7c7e25d6e5
But the most recent "full release" was rpi-boot-eeprom-recovery-2023-12-06-2712 https://github.com/raspberrypi/rpi-eeprom/releases (and the latest tag was also v2023.12.06-2712 https://github.com/raspberrypi/rpi-eeprom/tags ).
So as you say, hopefully it won't be too long for things to get updated in apt too.
EDIT: rpi-boot-eeprom-recovery-2024-01-05-2712 now includes the relevant fix https://github.com/raspberrypi/rpi-eeprom/releases (and is also in apt).
Has anyone managed to get PINN working on a pi 5 booting from NVMe? I'd like a dual boot 64 and 32 bit Rasp os...
Thanks!
It should be OK if it is connected over USB, but I assume as you mention the PI5 you are referring to an NVME connected to the PCIE connection? It should work, but I would also be interested to hear some feedback to make sure I have the right drivers loaded in the kernel for it. 😉
I have a pineberry hat top that should be coming this weekend, so ill give it a try... am sure you already know if this hat, but here is the link just in case :) https://pineberrypi.com/products/hat-top-2230-2240-for-rpi5 Will give PINN a go ... and report back! Thanks again!
I use NVM connected to Rpi5 via PiHat. I've installed Ubuntu and Pi OS. Pi boots to busybox but it is not finding the root partition. Ubuntu cannot even unpack rootfs. See attached screenshots. Without PINN I can boot NVM with either Ubuntu or PiOS without any issues. Any suggestions for further analysis?
I've been testing the PIMORONI NVME base with PINN.
So far:
- raspiOS works perfectly
- lineage20 ATV works perfectly (even the TWRP recovery)
- ubuntu 23, as poopi reported, stops at boots.
I'm happy to do more testing whenever needed, and I'll continue to play around myself and report here if I find something that's not working properly
Hmmm. It should not be that different from what I'm doing. So let me start messing around with configs ...
Regarding Ubuntu, please download the attached partition_setup.sh script (You will need to unzip it) partition_setup.zip Copy it to the SETTINGS partition ( maybe /dev/nvme0n1p5 ? ) into the /os/ubuntu2310 folder, overwriting the existing file.
Then in PINN, go to the maintenance menu, select (tick the checkbox next to) ubuntu, Click the Fix-up button and choose to "re-run partition_setup script." If that succeeds, then try booting into Ubuntu.
Hello procount
Can you please provide a bit more detail on your last comment? I have connected my PINN SSD to a NVME reader so I have access to all partitions.
I do not see a SETTING partition and the RECOVERY partition has an empty /os/ folder
I have a lot images installed (and all the Project Spaces for future plans and tests), so it's possible I'm getting confused between folders.
I have attached a screenshot of my partitions.
@ardoviniandrea - Are you viewing this on an Apple device? I am not familiar with those. As you have all the other partitions visible, and you can boot PINN, then the settings partition must be there. Perhaps Apple devices don't show partitions named "SETTINGS" ? I know that many OSes (e.g. Ubuntu) don't show partitions named "RECOVERY".
From the RPi forums, I have discovered that Ubuntu 23.10 seems to have problems with some USB hubs on the Pi5. May be the same issues are happening with NVME, so this partition_setup script may not make any difference.
Anyway, as a workaround, I suggest you copy the partition_setup.sh script to the RECOVERY partition and boot PINN on that device on your RPi. Press Shift when prompted so that you go into the recovery menu.
From the recovery menu press [CTRL]-[ALT]-F2 to open a terminal and login with root/raspberry.
From here, the settings partition should already be mounted as /settings. so type:
cd /settings/os/ubuntu2310
mv partition_setup.sh partition_setup.bak
cp /mnt/partition_setup.sh .
(Don't miss the dot/period in the last command! Please check the above for spelling/accuracy etc. as I am recounting this from memory!)
Return to PINN by pressing [CTRL]-[ALT]-F1 Go to the maintenance menu. Tick the box next to Ubuntu to enable the Fixup button. Select the Fix button tick the box to re-run the partition_setup.sh and press OK. Hopefully it will complete successfully, and then you can try and boot Ubuntu. (Probably won't make any difference but worth a try)
An empty /os folder on RECOVERY is to be expected.
@Poopi
Any suggestions for further analysis?
Could you post copies of /settings/installed_os.json along with copies of cmdline.txt from your Ubuntu boot partition and /etc/fstab/ from your Ubuntu root partition?
files.tgz Please find attached. Interestingly when I connect the NVMe via USB dongle then Ubuntu boots like a charm... I also checked the configs for Ubuntu when I installed it to NVMe directly and they are identical.
So i got my pineberry hat top, and after MANY attempts, finally managed to get booting from the nvme to stick! I had to re-image the sd card quite a few times... as well as the nvme drive... setting the boot config etc... as the nvme would install raspios just fine... but if i did a system update from the prompt for first login... when rebooting, it would just drop me right into the busybox cmd screen (which i have no clue what to do with btw!!! n00b) ... re-image PINN... bootup from sd card... redo boot config etc.... last night tho, and this morning... i managed to get it working as expected, multiple reboots later... and still good! So, long story short, at least in my case, do not run the updater when prompted on first boot! reboot a few times first... then do the update via ssh/terminal! Looking forward to the next version of Pinn!!!
PS: Would be awesome if it could support wubuntu or zorin (i know they arent pi compatible... just wish they were :D )
That's good news! So what is your setup? Have you got PINN on the sd card that you've used to install Raspios on your nvme?
Thanks man! So, essentially, i have managed to get PINN installed on the nvme (no sd card, or usb anymore :) ) ... then installed raspios onto the nvme as well! much neater. I have always had bad luck with sd cards!!!! Am still blown away at the speed of this pi5... especially now... bootup takes just a few seconds!
As i am in experimental mode with this setup... if there is anything you want me to test... feel free to use me as a guineapig!!
Thanks. I don't have any nvme drives, so I appreciate any help in testing them and documenting any special instructions to get an OS working on them. It would be really good to test all the Pi5 OSes that I have provided to see if any of them don't work or if I need to do some extra work for them.
Sure thing, i will install them all... document each one as i go through them... and report back! Gimme a few days to play as and when i can, i mess about with the pi5 in between work!
Some updates here.
I've tested what procount shared in the previous comment.
The Fix run successfully but as anticipated, didn't solve the issue for Ubuntu that still stops here immediately after the boot.
I did test most of the other OSes and I can report that all of these works correctly when booting from PINN on NVME:
- RaspOS arm64
- kde2lee64
- AOSP14-rpi5 (although I managed to brick it somehow and required to reinstall it)
- lineage20-rpi5 (with TWRP and successfully installing Gapps)
- lineage20-rpi5-ATV (with TWRP and successfully installing Gapps)
- mxlinux
- LibreELEC_RPi5
- recalbox5 (boots fine, but I haven't try any games for so far, so I cannot report the full funcionality)
- ProjectSpace --> I've initially installed all 8 possible, and already used/swapped a few without any issues.
2 notes I want to report, other than Ubuntu not working:
- HDR, HDR+ and HVEC content in KODI in LineageOS (even ATV) plays with washed out / grey colors, but plays normally in LineageOS. I looked around a bit and looks like it could be related to codec issue, but haven't been able to identify more than this
- PINN boot related, very minor but I am not able to re-order the OSes in the boot menu using the UP and DOWN buttons. Every time I do it and either boot or turn off the RPI, the order comes back to the initial one the next boot.
Happy to keep testing new thing procount, if you have anything in mind