STICKY: PINN - An enhanced version of NOOBS.

[procount]

Those are the wrong files.
You need to download the raspios_full_armhf/ folder
From the https://downloads.raspberrypi.org/ website.

It is easiest to use the download feature in PINN which will do it for you.

[desmo2v]

@procount

I have been trying to get windows on raspberry pi (WOR) working but can't work out the partition setup, I either get windows needs a boot partition or it boots to a windows recovery screen.. Do you have any tips in regards to this?

Thanks...

[procount]

I have been trying to get windows on raspberry pi (WOR) working

As you are posting here, are you trying to get it working under PINN in a multi-boot scenario?
If so, I'm afraid you are on your own. I haven't looked at it at all apart from googling WOR after reading your post.
I stumbled across https://www.worproject.ml/ which suggests it needs a GPT partitioned drive. PINN uses MBR.
IIRC someone got PINN working with GPT, but I'm not supporting it at present.

WinIOT was supported by Microsoft and they used partition_setup for handling the partitions themselves. Maybe you have to do a similar thing with WOR as well.

[Solid Rhino]

@procount

How can I create my own repo? And package my own OS images? For an updated Ubuntu Mate, Manjaro and Diet pi for Raspberry Pi 4 8 GB.

[procount]

@Solid Rhino - apologies if the PINN versions of the mentioned OSes are not quite the latest ones. It takes quite a while to convert and test each one and I'm rather swamped at the moment. Normally an installed OS can be easily updated once a version has been installed.
Details of how to convert an OS for installation by PINN are detailed in the README_PINN.md file on github, and in my wiki.
If you have the time to convert any newer versions, I am always ready to update my images with new tested versions so feel free to send them to me so that everyone can benefit. Otherwise you can host them your self by creating your own os_list_v3.json file, or simply install them from a local USB stick.

[miketvguides]

Did anyone manage to get Ubuntu boot on PINN?

[Paisano87]

Good morning

I want to replace batocera with recalbox, but it gives me an error that the number of partitions is not compatible.
I have seen that recalbox uses 3 partitions and batocera 2.
I have tried to convert batocera in projectspace to recalbox but it has not worked. I have created a new partition with gparted and assigned it to os_config.json prjboot partition and it has not worked. Any solution?

Thank you

[procount]

Replacing an OS is limited to one that can fit into the existing partition space, since in this case, PINN is merely re-using the existing partitions.
If you can manually repartition your drive correctly, and convince PINN that batocera actually uses 3 partitions, you might be able to replace it with recalbox.
Otherwise, you could backup all your existing OSes to a USB drive, then restore the backups that you want plus recalbox, but it may take a little while to do.

[Rpi4man]

How can you connect to PINN via VNC through ssh tunnel for security? There is nothing in the forums or online that explains how to do this? I already tried, but tight vnc or real vnc viewers just does not connect. Tried with windows 10 powershell ssh and putty.

[procount]

Can you confirm that you can access PINN via VNC normally and can also access it via SSH normally? - it's just that you want to access VNC through an SSH tunnel?

EDIT: I just found your other post and clearly you have some more fundamental issues going on. Let us continue the discussion over there.

[THX1182]

Dear procount

First of all i want to thank you, for all of your hard work on PINN...

Is there any chance that the latest lineage os 17.1 builds by Konstakang will be added to PINN? Or is it simply to time consuming, and hard to add these images?

These work great on the raspberry pi unlike the more sluggish 16.0 versions.

Thanks again

[procount]

I have a number of OSes outstanding to either update or add.
Many can be upgraded post-install, but some can't.
I shall try to find some time to focus on these.

[THX1182]

I have a number of OSes outstanding to either update or add.
Many can be upgraded post-install, but some can't.
I shall try to find some time to focus on these.

Thanks for reacting to my post...

[BRX7]

Hi,
can the new Ubuntu 20.10 builds be added to PINN? or is the booting method still hassle.
Thanks

[procount]

I have now got Ubuntu 20.04 converted, so I shall release that soon (although it's somewhat lacking in slideshow installation)
Hoping to have lineage 17.1 next, then I'll look at 20.10 along with some others I need to add/update.

[thatchunkylad198966]

I have now got Ubuntu 20.04 converted, so I shall release that soon (although it's somewhat lacking in slideshow installation)
Hoping to have lineage 17.1 next, then I'll look at 20.10 along with some others I need to add/update.

Sounds good! Keep up the great work.

[procount]

PINN has been updated to v3.5

V3.5

• KERNEL - Bump firmware & kernel as NOOBS 3.5 for CM4
• Certificates - Fix arora certificate errors
• Translations - Update it and zh_TW translations
• Prompt - Update shell prompt
• Clarify - Clarify text between replace & reinstall
• Logs - Add Show Log in Fix up menu

This latest version brings PINN up to date with NOOBS 3.5 latest kernel, firmware and userland which enables support for the CM4.

I've clarified the text in the warning dialogs relating to replacing and reinstalling OSes to indicate exactly how much of the card will be wiped.

The debug log is now available in the UI as well as the usual access though the command shell (/tmp/debug) which should make debugging a little more accessible. It's available from the Fix option in the maintenance menu so it is first necessary to select an OS in this window to make the Fix menu available first. As it only captures a snapshot of the log, a refresh button is provided to update the display with any recent additions.

Since the kernel has changed, I've had to temporarily drop support for the RTL8188eu wifi driver until I can get a new version compiled. I hope to include it again in the next version.
Support for the Pimoroni Hyperpixel 4 is partially working on the Pi4. It needs the pimhyp44-overay.dtbo file instead of pimhyp4-overlay.dtbo. At the moment, if you are using screenswitch.zip, you'll need to manually replace all occurrences in the config files. I hope to get it better integrated for the next version.

EDIT: Please be aware that self-updating to this version will install a new config.txt file, overwriting any existing one you may have. Normally this would not be a problem because previous PINN versions did not have a config.txt file. However, if you created one for some specific reasons, e.g. to force a specific monitor resolution, you will have to re-apply these settings to the new config.txt file.

[thatchunkylad198966]

PINN has been updated to v3.5

V3.5

• KERNEL - Bump firmware & kernel as NOOBS 3.5 for CM4
• Certificates - Fix arora certificate errors
• Translations - Update it and zh_TW translations
• Prompt - Update shell prompt
• Clarify - Clarify text between replace & reinstall
• Logs - Add Show Log in Fix up menu

This latest version brings PINN up to date with NOOBS 3.5 latest kernel, firmware and userland which enables support for the CM4.

I've clarified the text in the warning dialogs relating to replacing and reinstalling OSes to indicate exactly how much of the card will be wiped.

The debug log is now available in the UI as well as the usual access though the command shell (/tmp/debug) which should make debugging a little more accessible. It's available from the Fix option in the maintenance menu so it is first necessary to select an OS in this window to make the Fix menu available first. As it only captures a snapshot of the log, a refresh button is provided to update the display with any recent additions.

Since the kernel has changed, I've had to temporarily drop support for the RTL8188eu wifi driver until I can get a new version compiled. I hope to include it again in the next version.
Support for the Pimoroni Hyperpixel 4 is partially working on the Pi4. It needs the pimhyp44-overay.dtbo file instead of pimhyp4-overlay.dtbo. At the moment, if you are using screenswitch.zip, you'll need to manually replace all occurrences in the config files. I hope to get it better integrated for the next version.

Any update on Ubuntu 20.04/20.10?

[procount]

Sorry, it's taken me a lot longer than I expected to get this new version out, but I can now turn my attention to Ubuntu.
LineageOS 17.1 has also been giving me some grief, so that might have to wait a bit.

[procount]

Just to announce that PINN v3.5 is already compatible with the new Pi400.

Also, I have just added Ubuntu 20.10 Desktop and Twister OS to the list of installable OSes.

[fayni]

Great news!
As RetroPie has released its 4.7 version just yesterday: when will this be available with PINN lite or how could I alter the config for 4.6 so it loads 4.7?

[xaeiou]

Thanks @procount for the great tool. I like to constantly toy with different distro so this looks perfect.

Rather than lock down my rpi for a long time downloading distros, I'd like to do this on another machine and then just copy them to my SD as needed.

If I understand correctly, I can just clone any directory from:

https://sourceforge.net/projects/pinn/files/os/

Into the os/ directory on my PINN SD.

In the documentation here: https://github.com/procount/pinn/blob/m ... on-sd-card

It talks about setting the "reserve=" config option. I plan on using a fairly large (say 256GB) "A1" SD card. Are there any drawbacks (boot time or speed) to setting the reserve option fairly large, eg 64GB or so?

[procount]

Yes, you have that correct.
The sourceforge repository you quoted is only 1 of several, so depending on which OSes you want to download, you may need to look at the others too.

Apart from using up valuable space on your SD card, the only caveat to having a large /os folder is that it will prevent RiscOS from being installed. This is probably not an issue since the NOOBS version included is quite old and won't run on a PI4 anyway.

[procount]

An issue has arisen with PINN v3.5 which only seems to effect the 8GB versions of the Pi4.
If you have one of these 8GB models, please stick with PINN v3.3.4.4 for now.
When prompted that a new version is available and asks you to update, please select ignore. Normal update notifications will resume when the next version becomes available.

If you mistakenly upgrade from v3.3.4.4 to v3.5 on the 8GB model and end up with just a white cursor in a green box, do not panic.
Please download v3.3.4.4 from the archive folder on sourceforge and copy it manually to PINN's SD card with the exception of recovery.cmdline.
Please double-check that recovery,cmdline DOES NOT contain the `runinstaller` option, otherwise it will wipe all your OSes.
Once confirmed that it is absent you can reboot PINN, not forgetting to select 'ignore' when asked to upgrade to 3.5.

I am looking into this problem and will produce a fix as soon as possible.

[procount]

version 3.5.1 is now available for download that fixes the issue on 8GB PI4 models.
Sorry for the inconvenience.