General discussion • Re: STICKY: PINN - An enhanced version of NOOBS.

Try enabling the 'showall' option in the Maintenance Menu. (select PINN, Edit Config, Edit Options, Source tab I think?) and reboot PINN.

That did the trick, thanks! After correcting my wrong partition size values and names in partitions.json, and ignoring PINN's warning that none of the OSes were supposedly compatible with Raspberry Pi 5, PINN did install both OSes.

But still no joy. For the first boot I selected the Raspberry OS partition and ended up on an

Code:

(initramfs)

prompt...

*sigh*

Any idea what could be wrong here?

EDIT: please note, I'm targeting the NVMe drive attached to the PCI port. All installed OS files and partitions on the NVMe drive show up and are readable from a Raspberry OS booted from the SD card slot.

EDIT 2: also, between my first initrams woes and this, I had successfully installed and booted a regular (non-PINN) image of Raspberry OS on the NVMe drive.

If the `showall` option displays your OS, then you haven't included the Pi5 model in the list of suitable models this OS is suitable for in the os.json and os_list.json files.

If you end up with an `(initramfs)` prompt, then there's probably something wrong with the cmdline.txt modifications from partition_setup.sh. Maybe you didn't adapt it for bookworm(?) by removing the space after boot?

If you're "targeting the NVME drive", do you still have PINN on an SD card? You should really have PINN on the NVME drive as well. PINN is not just an installer, but a boot selector, and so it needs to be present on the boot drive. Keeping it on the SD card means you must always have the SD card fitted to boot from.

I'm groping in the dark a bit, because I can't see any of your modified files. Converting an OS for use with PINN is a bit of an art since each one is unique and the conversion may even have to change for a new release.
If you're still stuck, try opening an issue on my github and post your meta files there. It's a bit difficult to follow all the posts in this thread over a long period of time, so keeping them together in a github issue would be easier to manage.

Statistics: Posted by procount — Sun May 11, 2025 10:36 pm

---