STICKY: PINN - An enhanced version of NOOBS.

[321]

Ok, here's an example, I dont see the relevance of mentioning retro.sh in the 1st step as there's no mention of where its called from, once raspbian has been installed and running.
I understand that it can be used as a post installation call, but theres no mention of where its called from which would be useful if retro.sh is going to be called.

Obviously it was written when Wheezy was around as some of the things mentioned like raspi-config running on 1st boot, now does not happen, maybe it might be worth mentioning somewhere at the beginning something like "this was written using raspbian wheezy dd-mm-yy" as these are all available for download AFAIK for anyone else who might visit the page in the future.

[procount]

PINN has been updated to v2.3a

V2.3a

• IT Translation - A minor update to the Italian Translations
• More OSes - Added some more OSes

PINN can now install the following additional Operating Systems:

Retropie (updated to v4.1)
Void Linux
Ubuntu Mate 16.04.2 LTS
Pi-Top OS (Polaris)
Arch
OpenELEC

[procount]

RTAndroid 7.1.1 has been added to the list of OSes installable by PINN.

This is only available for the RPi3.
Configuration for the RPF touchscreen or waveshare touchscreen are not available from within PINN yet, so for now, these need to be configured manually.

[Martin Frezman]

This is only available for the RPi3.

Speaking of things that don't work on all versions of the Pi, are you aware that "Void Linux" doesn't work on the Pi Zero W?

I installed both versions of Void Linux (Why are there 2 of them?) via PINN, but when I try to boot them, it just hangs.

[procount]

That doesn't surprise me as the version of Void I put up was in Feb, before the Zero W was released, but thanks for pointing it out.
I'll see if there is a more recent version that works with the W.

I know little about Void, but I believe one uses libc and the other uses musl (https://wiki.voidlinux.eu/Musl)

[Martin Frezman]

OK, that all makes sense.

[321a]

So still using the PiKitchen and trying to get the data section working
https://pihw.wordpress.com/guides/pi-ki ... allations/


Noobs is throwing an error

Code: Select all

Raspbian: Error Executing partition setup scripts.

Then I get lots of commands echo'ed with their variables that goes off the bottom of the screen so how can I get at this information in full to even find out which part of the script its failed on?

The line immediately below it says

Code: Select all

+ [-z /dev/mmcblk0p6 ]

Lets just say this worked once tonight and then stopped working thereafter.

Personally I've spent over a week on this now way way more time than anyone would persevere with normally and everything seems so temperamental, but when you have 7 desktops and laptops & one server hacked so the bios doesnt even boot up, you are left with little options.

[321a]

As my BT business line seems temperamental, I'll post from my TalkTalk line, and wait for the messages to be approved.

In addition to my previous message, how do you get to scroll down the error messages that go off the screen or get a copy of the error message to step through?

[procount]

Ctrl-alt-F2 to get to shell.
Login with root/raspberry.
Cat /tmp/debug.

[procount]

@martinFrezman - I checked and there is a later void image but it is still from before the Pi0W. But if you update the firmware it seems to run though. I'll look at updating it.
For now, if you copy bootcode.bin and recovery.elf form the pinn partition to the void boot partition it should then boot. (Rename recovery.elf to start.elf and overwrite the existing file.)

[321a]

Ctrl-alt-F2 to get to shell.
Login with root/raspberry.
Cat /tmp/debug.

Where can I find a summary of all the noobs/pinn key functions and settings like an overview if one exists?

PiKitchen is too wordy for me.

[gtechn]

Looking good!

At this point, why doesn't PINN replace NOOBS officially? Why doesn't the RPF just merge PINN into NOOBS, or just discontinue NOOBS and support PINN instead?

[procount]

Different markets / support.
NOOBS is for beginners and has full RPF/T support.
PINN will have more advanced features but more limited support (mostly just me).
Since PINN is a fork of NOOBS they are compatible and NOOBS can incorporate any of PINN features if they match with RPF aims.
There is a place for both - take your pick! But thanks for your comments.

[procount]

@321 - its all documented in https://github.com/procount/pinn/blob/m ... ME_PINN.md

The ctrl-alt-f2 is a standard linux feature to switch terminals.

PiKitchen is quite comprehensive but therefore also quite complex.
Why not start with noobsconfig to understand the basics. You can build up from there.

Just create a flavour and a text file with a list of additional files to copy (plus some extra info like owner and permissions)

[jamesh]

So still using the PiKitchen and trying to get the data section working
https://pihw.wordpress.com/guides/pi-ki ... allations/


Noobs is throwing an error

Code: Select all

Raspbian: Error Executing partition setup scripts.

Then I get lots of commands echo'ed with their variables that goes off the bottom of the screen so how can I get at this information in full to even find out which part of the script its failed on?

The line immediately below it says

Code: Select all

+ [-z /dev/mmcblk0p6 ]

Lets just say this worked once tonight and then stopped working thereafter.

Personally I've spent over a week on this now way way more time than anyone would persevere with normally and everything seems so temperamental, but when you have 7 desktops and laptops & one server hacked so the bios doesnt even boot up, you are left with little options.

You appear to be using Noobs, this is not a Noobs thread. Please start a new thread and describe your problem fully there.

[321a]

@321 - its all documented in https://github.com/procount/pinn/blob/m ... ME_PINN.md

The ctrl-alt-f2 is a standard linux feature to switch terminals.

PiKitchen is quite comprehensive but therefore also quite complex.
Why not start with noobsconfig to understand the basics. You can build up from there.

Just create a flavour and a text file with a list of additional files to copy (plus some extra info like owner and permissions)

I'm flick switching, taking noobs & pinn to pieces to understand it, which is why I asked about the different settings options.

Where it says

PINN now includes direct support for noobsconfig so it is no longer necessary to add the noobsconfig files to your PINN installation. Just add your configuration and customisations files and install your "flavoured" OS. Please see (https://github.com/procount/noobsconfig) for full documentation on how to use this feature.

What exactly do this mean? Is it refering to the json files like partition and the partitions script file to go with it and/or something else?
Are the noobsconfig files different to a normal raspbian img file in the fat32 partition? I havent looked perhaps I should?

[procount]

Are the noobsconfig files different to a normal raspbian img file in the fat32 partition? I havent looked perhaps I should?

Yes, I suggest you look at https://github.com/procount/noobsconfig IFF you want to customise an OS installed by PINN after it has been installed but before it is booted for the first time. Have a look at the examples provided, although they are a bit old now. If you have any further questions on NOOBSCONFIG, I'll be happy to answer you, but maybe best to start a separate thread for those discussions.

[ryan smith]

Thanks,

I was looking for an easy way to install and dual boot Raspbian Pixel and Retropie. I was ready to install Retropie on a SD and try to manually add those files to Noobs when I stumbled upon this. My Raspberry Pi 3 model B is triple booting into Pixel, OSMC, and Retropie. When my Pi Zero W comes in I want to install Pixel and Retropie on it.

This is a great program.

[DBoy88]

Thank you for developing this... Was able to install RetroPie and LibreElec with Windows/My samsung TV (CEC control for installation was crucial!). This program also made the dual install super easy!

Is there a way I can select my OS using just my CEC remote control? I currently have LibreElec as my default OS, can I get into RetroPie with just my TV remote?

Also, I am unable to connect with Putty software due to incorrect User/Password combos...

I have tried root/raspberry, pi/rasberry, root/toor etc.... any idea why these passwords aren't working for Putty. I am actually just looking for an easy way to edit my config.txt without a keyboard....

Thanks!

[procount]

Is there a way I can select my OS using just my CEC remote control? I currently have LibreElec as my default OS, can I get into RetroPie with just my TV remote?

From boot up of PINN, use your remote to click on the screen, which should take you to the noobs menu. Click exit, select your OS and click on BOOT button

Also, I am unable to connect with Putty software due to incorrect User/Password combos...

The putty/ssh password for PINN is root/raspberry. The caveat is that there is no keyboard mapping to your locale, so it assumes a UK keyboard. So I think for a german keyboard for example, the A/Z keys are swapped so you might have to type rzspberry or something similar.

I am actually just looking for an easy way to edit my config.txt without a keyboard....

If you add 'vncshare' to recovery.cmdline, you can access the NOOBS screen remotely with a VNC client. Then you can use the built-in config editor.

Full documentation can be found at https://github.com/procount/pinn/blob/m ... ME_PINN.md

[DBoy88]

Thanks for your help! You are awesome!

I was able to switch to other OS.

I am still having issue with the user name/password though. I am using a UK/US keyboard... I checked all of the letters in the username field and they all correspond to the correct letters... Maybe I unwittingly changed the password myself somehow...

Anyways. Thank you for your help. This is an excellent program.

[procount]

PINN has been updated to v2.3.1a

V2.3.1a (beta)

• Rebased on NOOBS 2.4
• USB MSD support
• Show Wifi password

For a while now, the PINN source code has diverged from NOOBS, but I felt it was time to converge them to make them better align.
So I have rebased all of my enhancements on top of the latest NOOBS v2.4 that has just been released.
This means you get all of the latest NOOBS features, plus all the previous additional PINN features.

The latest major NOOBS change that has been incorporated is the ability to install the OS to a USB storage device.
If you have an RPi3 (or RPI2B+?) and have enabled the USB boot feature, PINN should also boot from there.
If you have any other RPi, you still need PINN and the OS boot partitions on the SD card, but the rootfs should be executable from USB.

BETA TESTERS WANTED!

This is a major organisational change to the PINN source code base and I have tested quite a bit, but maybe not all combinations or features.
So I am releasing this as a test version only at the moment and asking for feedback on any issues found or features missed or broken etc.
Please raise any issues on git hub here-> https://github.com/procount/pinn/issues or as a sourceforge ticket here-> https://sourceforge.net/p/pinn/tickets/

Once it is considered stable, I will release it as PINN v2.4 and it will be available via the PINN self-update mechanism to all users.
The previous documentation should still be valid. I will add the additional features to it when I release v2.4

PLEASE BE AWARE THAT THIS IS TEST SOFTWARE, so be prepared to lose all of your data and backup everything first before using it. Make sure any USB storage devices are blank before using - they may get wiped!

Download v2.3.1a from here ->pinn-231a.zip on sourceforge

[ryan smith]

I'm installing Raspbian Pixel and Retropie on pi zero w. Raspbian works perfectly and Retropie loads to a blank screen. I tried using different power supplies and reinstalling the OS from the boot menu and get the same result every time. Does the two OS conflict with each other on the pi zero W?

[procount]

The version of Retropie installed came out before the PiZeroW, so the firmware is just a bit too old to recognise your Pi.
If you copy the firmware from your Raspbian installation, it should then work.
I'll try and find some time to update the firmware in Retropie to prevent this happening.
Thanks for letting me know.

[procount]

I updated the firmware in Retropie1 v4.1 to be suitable for the PiZeroW.
I'll look to updating it to v4.2 soon.