STICKY: PINN - An enhanced version of NOOBS.

[procount]

PINN has been updated to v2.8.2

V2.8.2

• Reinstall - Small bugfix to Reinstall due to partuuid change on USB

[procount]

@wintux - your mapping works fine for me on a Samsung TV.

I added another CEC key mapping which users might find better than the default. See the wiki -> https://github.com/procount/pinn/wiki/C ... bbed-lists . Just copy this to cec_keys.json in PINN's recovery partition and boot it.

[wintux]

@wintux - your mapping works fine for me on a Samsung TV.

I added another CEC key mapping which users might find better than the default. See the wiki -> https://github.com/procount/pinn/wiki/C ... bbed-lists . Just copy this to cec_keys.json in PINN's recovery partition and boot it.

Yes it works fine everywhere, but not in the bootmenue. If i press a random button on the remote or on the keyboard it will start immediately the highlighted OS.

If i want to switch the os, i have go first in the recovery menue, then i must switch to the bootmenue.

BTW. i have a Toshiba TV

[procount]

I see what you mean. Not sure what has gone on there, but I'll look into it.

[mattrix]

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

https://github.com/matthuisman/pinn-os/ ... #L523-L524

Volumio does not support USB boot / or root.
So, it won't show unless you install to SD card.

[procount]

PINN has been updated to v2.8.3

V2.8.3

• Programmable CEC - Fixed bugs
• networktimeout- Added timeout to detect network presence

This version fixes the programmable CEC keys. I also modified the alternative cec_keys2.json on the wiki. I think I might even prefer this to the default myself.

I also added a new `networktimeout` parameter for those networks that take longer to be established.

[wintux]

PINN has been updated to v2.8.3

V2.8.3

• Programmable CEC - Fixed bugs
• networktimeout- Added timeout to detect network presence

This version fixes the programmable CEC keys. I also modified the alternative cec_keys2.json on the wiki. I think I might even prefer this to the default myself.

I also added a new `networktimeout` parameter for those networks that take longer to be established.

Thx for the update.

Now the CEC works like it should.

[Haris1977]

Can i completely remove the:

"mouse_left/right/up/down/lclick" portion in the "any": { window name?

I do not really want them. Or do i need to have them in order for the script to work?

[procount]

Yes, you can remove them if you do not want the mouse simulation.

EDIT: The examples I have given attempt to show most of the functionality that work with most of the UI for most TV remotes. All CEC remotes are different, so just map whatever you have available for whatever you want to do. You could just get away with 2 buttons to move up and down the bootSelection dialog and another button to boot the OS, if you wanted.

[Haris1977]

Thanks. Let's say that i only want the up/down/left/right cec keys plus the select (enter) option for the boot option and nothing else. Should the cec_keys.json file look like this? (I just copy-pasted it from my notepad ++ here)

Code: Select all

{
    "bootSelection": {
        "any": {
            "Key_Enter":    "CEC_User_Control_Select"
        }
    },

    "any": {
        "any": {
            "Key_Left":     "CEC_User_Control_Left",
            "Key_Right":    "CEC_User_Control_Right",
            "Key_Up":       "CEC_User_Control_Up",
            "Key_Down":     "CEC_User_Control_Down",
        }
    }
}

[procount]

Nearly, you need to delete the last comma after "CEC_User_Control_Down" then it should be ok (I've not tested it)

But why do you even need left and right on the boot selection dialog? I don't think they will do anything. So you could just have a really minimal setup:

Code: Select all

{
    "bootSelection": {
        "any": {
            "Key_Enter":    "CEC_User_Control_Select",
            "Key_Up":       "CEC_User_Control_Up",
            "Key_Down":     "CEC_User_Control_Down"
        }
    }
}

But of course, this would ONLY work on the bootSelection dialog and not on the main menu.

[Haris1977]

Yes you are right and thanks again. I just need a minimal 3 button setup like yours cause most of the times (99%) i just want to use my remote to only boot into an os. If i want to correct smth i will just plug my wireless touchpad and get the job done.

I will test it if i get the time.

[FJaeger]

Hi, I'm trying to install Raspbian, OSMC, and Lakka onto a Pi 3B+ using PINN. The problem I'm having is that Lakka isn't supported on PINN for the 3B+, so I'm trying to install it from a USB drive using the latest nightly build here (http://nightly.builds.lakka.tv/2018-05-17/RPi2.arm/) which is currently working on the 3B+.

I've followed this advice here (http://disq.us/p/1spmtnq) and it still does not show anything in PINN. I can see the USB drive and I can see the OSes offered when I connect to the internet, but I cannot see the Lakka OS from my USB.

I got all of my downloads from here (https://downloads.raspberrypi.org/os_list_v3.json) except for the System file, which I got from the nightly build on Lakka's website.

Do I need to do anything else so PINN will see the Lakka OS on my USB drive?

Thanks

[procount]

In your new /os/Lakka_RPi2 folder on your USB stick, you would need to edit os.json.

1. Change the "release_date" to be the same as the date of your nightly build so that it is later than the version on the internet and will therefore take precedence over it.

2. In the "Supported_models" section, the "Pi 3 Model B Rev" entry means that it is suitable for the Pi3 but not for the 3B+, so it will not show up. To make it show up, you need to change it to "Pi 3", which means your new version is suitable for all 3B models.

[mattrix]

@FJaeger
I just noticed they provide a NOOBS package already.
Download the *-noobs.tar file.
Extract that (use 7zip on windows)
Copy that Lakka_RPi2 to your OS folder inside PINN.

That's all you should need to do as NOOBS packages are compatible with PINN

@procount
Do you think I should add a Lakka_Dev OS to PINN in the meantime so people with 3B+ can get going?
Pretty easy as they provide the files. Just need to upload them to github and tarballs to Sourceforge

[procount]

Yes, why not, if it is made clear it is a nightly dev version.

[mattrix]

All done.

Its called Lakka_RPi2_Dev
Description "The DIY retro emulation console (Developer build)"

Made a few tweaks to OS.json to make it PINN friendly (download size, url etc)

@FJaeger
You should be able to see & install it in the PINN menu now via the internet.
No need to install via USB.

[procount]

PINN has been updated to v2.8.4

V2.8.4

• Replace OSes - Allows the replacement of one OS with another
• Project Spaces - Added Project Spaces
• Reserve disk space - Reserve some space on PINN's partition before formatting
• mkimage - Added mkimage from uboot
• xz - Allow XZ Compression
• Update Dialog - This now cancels any timeout setting

The combination of the new `Project Spaces` and `Replace OS` functions makes PINN a lot more flexible, because now it is possible to delay installing OSes, or change one OS for another, all without having to completely wipe all the partitions each time, thus preserving all your hard customisation work!

See the full documentation for more details.

[wintux]

I have a question:
Is it possible to export an OS without exporting the whole SD card?

I have two OSs on tue SD Card, retropi and libreelec. I want to put libreelc on a other SD card, for testing reasons

[procount]

No. PINN can only clone a whole sd card.
If you want to do that you'll have to do it manually atm.

By "export" do you mean to create a new sd card with just pinn and libreelec on it, or a card with only libreelec on it?

[KilliK]

Hello.
I an a new owner of RPI3 and I used today your program to install 3 OSes (raspbian,retropie,libreelec) on a 64GB microsd. The operation was a success and all the OS work fine.

But I noticed that each OS has a partition of 20GB. I need the Libreelec partition to be the bigger one, since it will store movie files with big sizes. The other two partitions with a size of 10GB each will suffice for my needs.

My question is: can I manually set the partition size from PINN before I instal the OS? I can repeat the process and reinstall the OS if it's possible for each OS partition to have a custom size.

I tried to resize the partitions with a Windows software but it takes too long, estimated time of completion was 3 days for all partitions!

I ll give a shot with Gparted too, but it will be easier for me if I can tell PINN to give a manual size to each partition before it install the OSes.

here is the mapping of my sd card:

[procount]

Matt Huisman has done an excellent WebApp to do exactly this for you.

Please see his write up at https://www.matthuisman.nz/2017/05/noob ... sizes.html

His webapp is at http://pinn.mjh.nz/

[KilliK]

Thank you very much, I am trying it now.

One last question:
Is there a way I can reorder the position of the OSes in the select OS boot screen of PINN after I install them?
for example, I want from top to bottom to appear first Raspbian, then Retropie and last Libreelec.

[procount]

No I don't think so.

[chrisino]

Hi,

I've got 2 operating systems installed and want to install a third without wiping the 2 already installed.

Is this possible?

Everything I've seen re multiboot on Pinn seems really complicated using terminals and can copying files over or changing files.

I've wiped my files several times as Pinn only offers to overwrite and not add to existing. Luckily I've backed the SD and restored.

Help would be greatly appreciated.