STICKY: PINN - An enhanced version of NOOBS.

[ryan smith]

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

Thanks for the quick response. The install now works for Retropie zero W but it can not see any of the wireless networks. Hopefully it is fixed in the 4.2 version, that update in the Retropie release archives says it works with the pi zero W. I'm just happy to know what the problem is.

[procount]

PINN now includes Retropie v4.2 to support the PiZeroW.

[Theak48]

I used this installer today and installed OSMC and retropie. So it goes to OSMC and I can not find a way to get to retropie. I read where I was supposed to find a repository named Matt something but I cannot find it anywhere could someone help me please

[procount]

So it goes to OSMC and I can not find a way to get to retropie

Hi Theak48. PINN is an OS boot selector, like NOOBS. To switch between installed OSes, you need to reboot your Pi. On reboot, you should get a menu to select which OS you want to boot - in your case, OSMC or Retropie. If you don't choose one, PINN will boot into your last used OS within 10 secs,

[mattrix]

I used this installer today and installed OSMC and retropie. So it goes to OSMC and I can not find a way to get to retropie. I read where I was supposed to find a repository named Matt something but I cannot find it anywhere could someone help me please

If you want to boot to RetroPie directly from OSMC, then you can use my (Matt Huisman) NOOBS Companion Add-on

http://www.matthuisman.nz/2017/02/kodi- ... dd-on.html

[procount]

PINN has been updated to v2.4.2

V2.4.2

• repo_list - Added repo_list cmdline argument
• btrfs - Added support for btrfs file systems
• Update - Rebase onto NOOBS 2.4
• repo - Support "repo=" from NOOBS
• USB support - Supports USB BOOT and USB ROOTFS
• Win10IoT - Fixed annoying warning messages on installation
• RTAndroid - re-included missing cpio to allow installation

Following the complete rebase/rewrite based on NOOBS v2.4, this minor point release fixes a couple of bugs that caused errors when installing Win10IoT and RTAndroid.

In addition, it includes the "repo=" cmdline option from NOOBS to specify an alternative list of os_list_v3.json repository files, so it is easier to switch between NOOBS and PINN using the same recovery.cmdline file. alt_image_source and no_default_source are still retained for backwards compatibility.

Having said that, specifying multiple repositories in recovery.cmdline can get unwieldy. So I also introduced a "repo_list=" option that contains a URL to a JSON file that contains a list of multiple os_list_v3.json files. This is now the default setting for new installs which currently points to the RPF repository, the PINN repository and Matt Huisman's repository of some more gaming distros.

If you use the self-update feature of PINN to get this new version, the recovery.cmdline file is left untouched. So to get the new OSes, you must copy the recovery.cmdline.new file over recovery.cmdline. If you have previously made changes to recovery.cmdline that you don't want to lose, then just copy the appropriate repo_list settings across from the new file.

[procount]

PINN has been updated to v2.4.2a

V2.4.2a

• Translations - Updated Italian and Chinese translations
• New OSes - New OSes and old ones updated for Autoboot

This is a minor update to include some translation updates.

The number of OSes installable by PINN has now increased to the following list:

_23 P Solydx
123 P AIYProjects
123 P C-Stembian
123 P PiTop OS
_23 P Ubunutu 1604LTS
123 P OPenELEC
123 P XBian
123 P Retropie 4.2
_23 P Kali Linux
__3 P RTAndroid 7.1
123 P Lede (OpenWRT)
123 P Arch
123 P Void
123 R LibreELEC
123 R OSMC
123 R Raspbian Lite
123 R Raspbian
123 R Lakka
123 R recalbox
12_ R RiscOS
_23 R Win10 IoT
_23 R TLXOS 60 day trial
123 H recalbox (Unstable)
123 H Batocera

Key

Code: Select all

1 - for Rpi 0/1
2 - for Rpi 2
3 - for Rpi 3
P - hosted by PINN
R - hosted by RPF
H - hosted by Matt Huisman

I have updated the RPI firmware of many of the PINN hosted OSes so that they will work with the Autoboot feature of NOOBS/PINN.

Reminder: If you have self-upgraded to the latest PINN, make sure you edit recovery.cmdline to replace the alt_image_source option with the new repo_list option to access the complete list of OSes. You can do this by copying the recovery.cmdline.new file over recovery.cmdline. If you have previously made changes to recovery.cmdline that you don't want to lose, then just copy the appropriate repo_list settings across from the new file.

Matt Huisman has provided some additional retro gaming distros as well as a handy online partition sizer so that you can easily change how much space each OS will take up. See viewtopic.php?f=56&t=184603 for the links to his handy utility.

[Tony_Dank]

I may have missed it, but is there a way to output through GPIO for an Adafruit TFT with this program?

[procount]

Do you mean this one -> https://learn.adafruit.com/adafruit-pit ... stallation ?

[procount]

PINN has been updated to v2.4.2b

V2.4.2b

• Translations - Updated Korean translations
• Translations - Added Norwegian and Arabic translations

[paulwratt]

thanks for update

Big Ups on getting PINN listed in June's Sourceforge Update (newsletter)

I hope to see PINN as Project Of The Month (POTM) some time soon

Thanks for your muchley (obvious according to sf downloads) appreciated work on PINN procount

[procount]

PINN has been updated to v2.4.2h

V2.4.2h
Some minor updates:

• Translations - Update to Portuguese, Chinese + other translations
• Password - When resetting an OS password, it is now set so that it will not expire
• Slideshow - During installation, the slides will now be scaled to be a similar size
• Large MSDs - Installing OSes to a USB Mass Storage Device > 1TB is now OK. 2TB is the maximum size supported.

[cjan]

PINN has been updated to v2.4.2h

V2.4.2h
Some minor updates:

• Large MSDs - Installing OSes to a USB Mass Storage Device > 1TB is now OK. 2TB is the maximum size supported.

does this function pi3 only, not for pi2?

[procount]

If you have a Pi3, you can install PINN to a USB Mass Storage Device and install any supported OS to the USB drive such that it will boot from the USB drive without an SD card. (You need to configure the Pi3 to support USB booting).

If you have a Pi 0/1 or old Pi2, (I'm not sure about the latest Pi2 based on the BCM2837 - maybe it behaves like a Pi3?) then they do not support USB booting. In this case, you can install PINN to an SD card and install a supported OS boot partition on the SD card, and the OS root partition on the USB drive. So the OSes will boot from the SD card, but then run from the USB drive.

Edit: See https://github.com/procount/pinn/blob/m ... boot-modes for more info

[matheussavi]

Hi!
I'm having some trouble to instal Recalbox by PINN.
The system, when i choose recalbox says that cant download some files, from png to jar.
Openlec instals fine...

What i can do?

Regards!

[procount]

It seems to be a problem with the recalbox website.
This is one of the "official" OSes that can also be downloaded with NOOBS, so you could try NOOBS to confirm the problem, but I suspect it will fail with that too.
Maybe contact the recalbox maintainers, or post an issue on NOOBS github if you can't find the maintainers.
Edit: it could be their file servers are overloaded, so maybe jsut wait a while and try again....?

[Kenjutsu]

If you have a Pi3, you can install PINN to a USB Mass Storage Device and install any supported OS to the USB drive such that it will boot from the USB drive without an SD card. (You need to configure the Pi3 to support USB booting)

I can't seem to get this to work. My RPi 3 is already configured to boot from USB.

When I copy all the PINN files to a USB flash drive and boot the Pi, I am informed: "Cannot find the drive with PINN files". Clicking on close gives: "Recovery application crashed. Starting shell sh: can't access tty; job control turned off"

When I copy all the PINN files to an SD card and boot the Pi, I get the option to install to the USB flash drive, which I then proceed to do (Ubuntu Mate 16.04.2 LTS for this example). I am informed: "OS(es) Installed Successfully". I click on OK, and the Pi reboots. Ubuntu loads and I complete the System Configuration. The Pi reboots again, I get the Ubuntu MATE welcome screen. From here, I shut down, and power-off, and remove the SD card. I power on the Pi, but nothing happens

[procount]

This feature is inherited from NOOBS, so it should work exactly the same.

When I copy all the PINN files to a USB flash drive and boot the Pi, I am informed: "Cannot find the drive with PINN files". Clicking on close gives: "Recovery application crashed. Starting shell sh: can't access tty; job control turned off"

Your USB drive should be formatted as FAT32 and all the PINN files should be stored in partition 1 (SDA1 normally). It seems PINN is booting ok, but not finding the correct drive. Maybe there is some issue there. It should not crash so I will try to investigate.

When I copy all the PINN files to an SD card and boot the Pi, I get the option to install to the USB flash drive, which I then proceed to do (Ubuntu Mate 16.04.2 LTS for this example). I am informed: "OS(es) Installed Successfully". I click on OK, and the Pi reboots. Ubuntu loads and I complete the System Configuration. The Pi reboots again, I get the Ubuntu MATE welcome screen. From here, I shut down, and power-off, and remove the SD card. I power on the Pi, but nothing happens

Using this method, you must keep the SD card inserted. The BOOT partition is stored on the SD card, so Ubuntu will not boot without it. Once booted from the SD card, Ubuntu will run the rootfs from the USB drive. This method will work with all RPi models.

If you need to run without the SD card, you must copy PINN to the USB drive, boot into it without any SD card inserted and install the OS from there.

[SeNS]

Can't find the Windows 10 IoT Core in the OS'es list. Your app was my last hope to get damn MS thing work on my RPi Model B

I tried everything with MS "bugware" (different and fast sd-cards, powerful power supplies: 2A, 2.5A) with the same result, a "rainbow screen" (GPU test procedure results).

NOOB and PINN are booting fine, and able to install other OS'es (available from menu).

Could you please provide me a working ffu file for W10 IoT Core with instructions, to install it manually, or provide previous version of PINN or whatever to get damn MS thing working on my RPi?

Thanks a lot!

[Martin Frezman]

Can't find the Windows 10 IoT Core in the OS'es list. Your app was my last hope to get damn MS thing work on my RPi Model B

WIn 10 IOT on the Raspberry Pi won't run your x86 Windows apps.

So, there's really not much point in it.

[SeNS]

WIn 10 IOT on the Raspberry Pi won't run your x86 Windows apps.
So, there's really not much point in it.

Why do you think I'm going to run x86 Windows apps on RPi???

I'm developer, and looking for new experience with IoT. RPi is a cheapest option I have now; I already have IoT SDK and Visual Studio installed. All I need is to run W10 IoT on RPi but MS bugware don't allow me do this

[fruitoftheloom]

WIn 10 IOT on the Raspberry Pi won't run your x86 Windows apps.
So, there's really not much point in it.

Why do you think I'm going to run x86 Windows apps on RPi???

I'm developer, and looking for new experience with IoT. RPi is a cheapest option I have now; I already have IoT SDK and Visual Studio installed. All I need is to run W10 IoT on RPi but MS bugware don't allow me do this

You should really be asking Microsoft for support as it is their own Operating System, the only involvement from RPF /RPT is to provide the require "boot" files. They have a MSDN Forum here (though you are not the first to have issues recently):

https://social.msdn.microsoft.com/forum ... WindowsIoT

The WIN10IOTC section of the Forum here: viewforum.php?f=105 is largely unloved.

IMO Microsoft seem more interested in supporting SnapDragon SoC's

[Martin Frezman]

Why do you think I'm going to run x86 Windows apps on RPi???

Its the usual case when people learn that there is a Windows variant for the Pi.

If this is not your use case, then never mind. But it is the usual case.

[SeNS]

You should really be asking Microsoft for support as it is their own Operating System, the only involvement from RPF /RPT is to provide the require "boot" files.

I'm asking developer of PINN 'cause his program had this option not long time ago. I'm not looking for useless advises about useless MSDN forums (however if you bothered to open forum you've refereed for, you should see my post).

[fruitoftheloom]

You should really be asking Microsoft for support as it is their own Operating System, the only involvement from RPF /RPT is to provide the require "boot" files.

I'm asking developer of PINN 'cause his program had this option not long time ago. I'm not looking for useless advises about useless MSDN forums (however if you bothered to open forum you've refereed for, you should see my post).

Only trying to help, this is after all a Community Forum totally run by volunteers, no one here gets ££££££££s

Now to your original question, have you tried NoobS ?? I have not personally used recently, but if an active internet connection is present W10IOTC was offered for RPi 2B & 3B:

https://www.raspberrypi.org/downloads/noobs/

https://github.com/raspberrypi/noobs/bl ... /README.md