STICKY: PINN - An enhanced version of NOOBS.

[gnad]

Thanks for the answer.

Another question: Do you think PINN should implement an "add/remove OS" feature (that are not require to mess with partitioning), since we already have a similar "replace OS" feature and this just expands on that idea:

1/ When you remove an OS, PINN only delete the content of the partitions, but not the partitions themselves (also remove the entry from installed_os.json). This keep the partition scheme intact.

2/ You can add an OS to existing empty partitions.

If it's possible, then its use case could be something like this: On initial PINN setup, I can configure PINN to create a partition scheme that have 5 slots for OS, but I only install 2 OSes. Later, I can always install other OSes into the remaining 3 empty slots (a slot is a set of FAT+ext4 partitions).

[procount]

I have some ideas like that on my roadmap, but it is not an immediate priority.

[procount]

PINN has been updated to v2.6

V2.6

• Firmware - Bump firmware
• Kernel - Update kernel to 4.14

Retropie 4.4 is now available.

[mironto]

You could use the autoboot.txt method and use my KODI add-on to boot from KODI -> Raspbian.
https://www.matthuisman.nz/2017/02/kodi ... dd-on.html

Hi mattrix, unfortunately, this did not work for me. I installed NOOBS companion in Kodi/LibreELEC and was able to boot to Raspbian from addon, but after I added autoboot.txt into PINN recovery partition, the companion addon does not work - when I click on Raspbian, it says "booting to Raspbian", but it always boots back into LibreELEC. Not I have to remove autoboot.txt, which is a problem, since I cannot access PINN partition in LibreELEC and physical access to the SD card is a PITA on my installation.

[procount]

PINN now includes the latest PiTop OS - Polaris 2018-04-03, which has been upgraded to Stretch and supports the Pi 3B+.

[ccunnin71]

Having gone through the resize app url: http://pinn.mjh.nz/

Rasperry Pi 3 B+, 32 GB SD, and selecting; LibreELEC_RPi2, OSMC_Pi2, Raspbian, and Retropie3

I get the latest Pinn-Lite & replace my recovery.cmdline with the generated one and getting an error during the PINN setup

Error downloading distribution list from internet:
http://pinn.mjh.nz/os_list.json:retropi ... c_pi2=7375

It wouldn't be a problem if I just wanted to setup the 32gb SD and use that as my boot device. Ultimately want to move it to a USB HD which I have done on an earlier setup. I have the Pi B+ looking at the HD but without the custom 'recovery.cmdline" is spreads the four systems across the full 1 TB drive.

What's up with the path at http://pinn.mjh.nz/ that is causing the error?

~Thank you for your time.

[procount]

Maybe his website was down, but it seems to be ok now, although the specific link for your OS size choices doesn't seem correct (what is resbain?)

[ccunnin71]

Ha, that would be my typo. I took a picture of the error with my phone and manually typed it. I have the direct download from his site. I was thinking that something in the tool was not setup correctly with the 12 or so choices available for B+. I will try again later...

[mattrix]

@ccunnin71

Should be fixed now.
The issue was that RetroPie3 was renamed RetroPie2 recently-ish.
There was an error in my web app that meant it was using an old version of scraped data.

To fix, either change "retropie3" to "retropie2" in your cmdline.txt

http://pinn.mjh.nz/os_list.json?retropi ... c_pi2=7375

or just run through the web app again to get a new correct cmdline file

[procount]

PINN has been updated to v2.6.2

V2.6.2

• Kernel - Bump to 4.14.37 kernel to work with older firmwares
• pinn_init.sh - Added script to run before PINN (eg. for Hyperpixel)
• Hyperpixel - Added support for Hyperpixel display

The previous bump to the 4.14 kernel branch in v2.6 had created a small inconsistency with older firmware, which has now been fixed with a small update to the kernel to prevent continuous error messages being posted to the console.

If a pinn_init.sh script exists in PINN's partition, it will now be executed before PINN is started. This is useful for initialising displays like the Hyperpixel.

Support for Pimoroni's Hyperpixel display has now been added to PINN.
After installing PINN to the SD card, simply download and unzip hyperpixel-display.zip from the sourceforge website and copy the contents over the top of PINN. The rainbow square will not show up on the Hyperpixel, because the display is not initialised until just before PINN starts. Only the display works at the moment - no touchscreen. I hope to add that in the future.

(Hmm. Nobody told me that the Raspex link was broken. That's probably why it only had 2 downloads It's fixed now)

[procount]

I've added a page to the PINN Wiki to capture the list of distros/OSes that PINN supports.
It now stands at 47 unique OSes, 62 if you include the variants for different Pi models, not counting the Data Partition. More than I thought it was.

[noafterglow]

OS overwrite?

I'm wondering if the add/remove OS discussion is similar to what I'm trying to accomplish. I'd like to be able to automatically OVERWRITE the one installed os (based on raspian for me) with either:

-- a disk image on an additional partition of the SD card from which the OS is currently running, when the Pi reboots... Lets call this "auto upgrade"
-- a disk image on a plugged in USB stick. Lets call this "Recovery"

So what would happen is that when the system boots, PINN does the following:
1) check for the presence of an inserted USB stick, and if present, and has image file(s) overwrite the partitions with the new images.
2) if not check for the presence of a new os on the spare partition, and if available overwrite the main partition with those images.

Of course the point of this is to NOT have to answer any questions along the way.

Anyone done this?

[sat0shii]

I need help

I have 2 64GB microsd and 1 32GB microsd card
(all are already formatted to fat32)

when I tried to use Pinn lastest ver. on my 64GB. My pi is doesn't boot (sd card won't loading )
but if I put same files to 32GB and plug it, my pi is working well.

after that I have also tried offical NOOBs on my 64GB cards. both are working well

could any one help me how can I use Pinn with 64GB card ?

thanks

[procount]

There should be no difference between running NOOBS or PINN on a 64GB card - they work almost identically.
However, there could be a difference between 32 and 64GB cards.
If you format a 64GB or larger card as FAT, it will normally be formatted as exFAT and therefore will not boot. To format it as FAT32 you need to use some specific formatting tools to ensure it really does use FAT32.

Please see this link -> https://github.com/raspberrypi/document ... matting.md

I also provide an image of PINN that you can flash to an SD card with Etcher, thus avoiding having to format it in the first place. See https://github.com/procount/pinn/blob/m ... ing-etcher . PINN may need to self-update on first boot if installed in this manner, so just let it do so to get the latest version.

[sat0shii]

@procount


Thanks for your quickly reply

Actually, I tried PINN first, but boot fail
Then tried NOOBS (just copy files without re-formatting) that boot success.

I have checked and use Guiformat fat32 to formatted
Windows 10 shown 64GB cards are already Fat32 format

I don’t know why larger card on my pi is boot failed with PINN

Maybe try an image as you advised later, I hope that will be working well for me

Thanks

[procount]

PINN has been updated to v2.8

V2.8

• Fix menu - Replaced Fsck with Fix menu option to include a wider range of tools
• Store meta - Additional meta files stored on installation for fix up tools
• Partuuid - Store partuuid references for better USB support
• Tab fix - Fixed synchronisation of OS tab display

I've corrected a lot of things in this version, so I think it finally warrants being given the same version as NOOBS on which it is based.

Following discussions in other threads, I have released a FULL PINN version that aligns with NOOBS FULL, as it includes Raspbian and LibreELEC, but it is a 1.6GB download. (This may not be updated as often as PINN-Lite, depending on demand).

I have also updated the Etcher image version for those who prefer that.

As far as changes go, I have moved the Fsck option into a more general Fix option. This is in preparation for possibly more Fix options in the future. For now, the only addition is the ability to re-run the partion_setup.sh script. This will be useful when OSes get upgraded that are not aware of the multi-boot modifications that are necessary to run under PINN. Re-running this script should repair their ability to run again. (So far I think this only applies to Volumio and Gentoo64). If you previously installed such an OS from a USB stick, then you may need to insert the original installation USB stick in order for the partition_setup.sh script to be available. (This limitation will not apply to OSes installed with v2.8, or those installed directly from the internet).

For OSes installed to a USB drive, some references to their partitions were not converted to partuuids, so they became inaccessible if the USB drive device name changed. This is now fixed.

And finally, some improvements to the OS Tab display were made, and the recommended OSes are now indicating again.

[procount]

PINN has been updated to v2.8.1

V2.8.1

• Programmable CEC - Allow TV remote buttons using CEC to be programmed

Users have been asking for this for some time, and now I've finally delivered: You can now program CEC keys on your TV remote to control PINN.
I've added some separate instructions on how to program the keys and the default key mappings are also in the Wiki.

If you create some useful key mappings, it would be good to share them on the wiki for other users, especially if they are for different TV manufacturers.

[fyrulayz]

PINN Is Not NOOBS
Announcing PINN - a fork of NOOBS.
EDIT: Now updated to v2.8.1 (11/05/2018)

Like NOOBS, PINN is an Operating System installer for the Raspberry Pi that allows multiple OSes to be installed on your SD card. At boot time, ..............

..........iles directly to the SD card, then carry on.
But if you like NOOBS and like the idea of the above new features, then maybe give PINN a try.

Hi there!
Short question for a quick answer.

System Debian on RPi 3b already installed and working
Is PINN a solution to add a new OS or it is a "replacement" to NOOBS and install more than one OS from start, beginning by one and along time install a second one from PINN ?

Thanks.

[procount]

As my signature indicates, PINN is more like a replacement for NOOBS with many additional features.

You cannot use it to simply add another OS to an SD card that already has an OS on it.
You need to install PINN to a fresh SD card and use it to install the OSes onto the card, just like NOOBS.

If you have an existing OS installation, you could back it up in a particular way and then re-install it as a multi-boot with other OSes using PINN.
There are instructions in the documentation regarding to such "custom os versions" and details in the wiki on how to do it for 2 typical OSes.

(Currently) the SD card space will be distributed among all the installed OSes, so you must install all the OSes at the start otherwise there will be no space left on the SD card to install more in the future. However, you can now "reinstall" any one of the OSes without affecting the others in the event that you trash an OS.

[Haris1977]

PINN has been updated to v2.8.1

V2.8.1

• Programmable CEC - Allow TV remote buttons using CEC to be programmed

Users have been asking for this for some time, and now I've finally delivered: You can now program CEC keys on your TV remote to control PINN.
I've added some separate instructions on how to program the keys and the default key mappings are also in the Wiki.

If you create some useful key mappings, it would be good to share them on the wiki for other users, especially if they are for different TV manufacturers.

I am a little confused here . Let's say i want to program my own cec buttons. Let's say i want to use up/down/enter instead of ChannelUp/ChannelDown/Play tv remote buttons for my boot selection. From what i understood i must create a cec_keys.json file with the corresponding cec codes in "bootSelection": { tab (inside cec_keys.json) and just put that file inside pinn folder?

[procount]

Yes. If you get stuck, raise a github issue and I'll try to help you.

[Haris1977]

Yes. If you get stuck, raise a github issue and I'll try to help you.

Thanks i ll try that when i get the time

But, wouldn't it be much easier if you implement that function in PINN's user's interface toolbar e.g in main menu? Let's say in a tab between Info (n) and Exit (Esc) tab? And then just following the on screen prompts to program CEC keys on our TV remote to control PINN..Just an idea..

[dschamal]

Hello,
I have an Raspberry 3B + with 230GB SSD to boot
Pinn version is 2.8
Now in the Pinn Install menu some OS version but the Volumio 2 not
I have change in the ...recovery.cmdline showall and add: repo://...matthuisman...staging.json
no error!
Please how can i enable Volume 2 throw the select menu???
If i change to RPI3 B without Plus there is Volume but after install the SSD not boot and i must new Format the SSD

Thanks
Uwe

[procount]

I don't know about volumio because it is one of Matt's and I'm not able to test it on a 3B+ at the moment. But the version in his staging.json looks the same as the one in his os_list_v3.json.
On your 3B, have you tried changing PINN's firmware in the maintenance menu before booting Volumio? depending on what its firmware is, you may need to do this to get it to boot.

[wintux]

PINN has been updated to v2.8.1

V2.8.1

• Programmable CEC - Allow TV remote buttons using CEC to be programmed

Users have been asking for this for some time, and now I've finally delivered: You can now program CEC keys on your TV remote to control PINN.
I've added some separate instructions on how to program the keys and the default key mappings are also in the Wiki.

If you create some useful key mappings, it would be good to share them on the wiki for other users, especially if they are for different TV manufacturers.

Thx for this.
I have change the mappings for the bootmenu:

Code: Select all

{
    "mainwindow": {
        "Main Menu": {
            "Key_I":        "CEC_User_Control_Number1",
            "Key_W":        "CEC_User_Control_Number2",
            "Key_H":        "CEC_User_Control_Number3",
            "Key_N":        "CEC_User_Control_Number4",
            "Key_Escape":   "CEC_User_Control_Number5"
        },
        "Archival": {
            "Key_D":        "CEC_User_Control_Number1",
            "Key_C":        "CEC_User_Control_Number2",
            "Key_N":        "CEC_User_Control_Number3",
            "Key_F":        "CEC_User_Control_Number4"
        },
        "Maintenance": {
            "Key_E":        "CEC_User_Control_Number1",
            "Key_P":        "CEC_User_Control_Number2",
            "Key_F":        "CEC_User_Control_Number3",
            "Key_R":        "CEC_User_Control_Number4",
            "Key_N":        "CEC_User_Control_Number5"
        },
        "any": {
            "Key_Space":    "CEC_User_Control_Play",
            "Key_Escape":   "CEC_User_Control_Exit",
            "Key_M":        "CEC_User_Control_F2Red",
            "Key_Enter":    "CEC_User_Control_Play",
            "Key_PageDown": "CEC_User_Control_Number9",
           [b] "Key_Down":     "CEC_User_Control_FastForward",
            "Key_Up":       "CEC_User_Control_Rewind" [/b]
        }
    },

    "bootSelection": {
        "any": {
            "Key_Enter":    "CEC_User_Control_Play",
            "Key_Escape":   "CEC_User_Control_Exit",
[b]            "Key_Up":       "CEC_User_Control_Rewind",
            "Key_Down":     "CEC_User_Control_FastForward"[/b]
        }
    },

    "any": {
        "any": {
            "mouse_left":   "CEC_User_Control_Left",
            "mouse_right":  "CEC_User_Control_Right",
            "mouse_up":     "CEC_User_Control_Up",
            "mouse_down":   "CEC_User_Control_Down",
            "mouse_lclick": "CEC_User_Control_Select"
        }
    }
}

Works so long. But i got a little problem. If i push a button, it starts the partition. It happends by pushing any button.

(Sorry about my english, i will hope someone understands what i mean)