STICKY: PINN - An enhanced version of NOOBS.

[DarrenHill]

Is it possible to suppress low voltage warnings under PINN? If so how is it done?

Before people say to change the PSU, this is on a PiTop Ceed, which has a set-up with a powered internal board which powers both its display and the Pi3 inside it via GPIO. According to PiTop it's a known issue for older Ceed's, and needs a cable change.

But as I'm only using it for a Magic Mirror, whilst I organise that (which may take some time apparently) I'd like to just suppress the message in the upper right corner as it's obscuring some of the mirror display. Can that be done under PINN? The MM is running under Raspbian as one of the PINN OS's.

[mattrix]

Is it possible to suppress low voltage warnings under PINN? If so how is it done?

https://www.raspberrypi.org/documentati ... xt/misc.md

You'd edit the config.txt inside Raspbian.
Boot Raspbian, then sudo nano /boot/config.txt
Then add avoid_warnings=1 at the bottom, then reboot.
If using turbo mode, you'll need to use avoid_warnings=2

[procount]

Or from PINN, go to the Maintenance menu, select your Raspbian OS and click the Edit Config Option. From here you can add the avoid_warnings commands to config.txt.

[DarrenHill]

Thanks - I already had that set in the Raspbian config.txt (via ssh into the Ceed) but it didn't seem to be doing anything as the warning still appeared. Hence the original question as I wasn't sure if PINN was bypassing or otherwise changing the config.txt for Raspbian.

I've added it into the config.txt via the maintenance menu for all the different options and will see if it is more effective or not.

[procount]

Each OS (and PINN) is independent with its own config.txt settings. Adding it to PINN's config.txt will prevent it appearing whilst PINN is executing.

[DarrenHill]

It didn't seem to be doing anything when I put it just in the Raspbian one.

Anyway it's in all three now, and so far looks to be working so job done

[WildSioux]

Hello procount,

I have used your program to dual boot my raspberry pi 4 for a few months. Thanks for the great program. I'm looking to redo my sd card with a USB 3 flash drive. The usb drive will have raspberry 64 bit OS with retropie installed with a few other games like supertuxkart (yes it runs great although at lowest graphics settings). The sd card I would like to install LineageOS android TV version 17.1. However, it isn't listed on the available OS's just the regular android version.

I've looked at trying to add it via the /os/ folder with a json. But it is above my skill set. Maybe if I had more time i'd look at it more. Are you able to add it to the list? This is the one I'm looking at installing https://konstakang.com/devices/rpi4/LineageOS17.1-ATV/

Thank you for your consideration!

[jochene]

Hi everyone,
and Big Thanks to ProCount for Pinn,
it's very fun to test multiboot so easyly.
I have a problem with some Os,
like Debian64.Lineage.
They won't boot and return error 00000044
I update my bootloader in RaspiOs 64 bits,
for the latest beta version.
Pinn.Error.Boot1.jpg
Maybe they not boot on usb?
thanks and again,
thanks for PINN

Edit:
I try to edit config.txt in Boot Lineage
add /boot/config.txt under ‘Boot device’ section:
#dtoverlay=android-sdcard
dtoverlay=android-usb
info from https://konstakang.com/devices/rpi4/LineageOS17.1/
with no success.
I test other things in my noob capacity.

Hello,
with the last beta i have the same problem with "libreelec.

My config:
- pi4 8gb
- 240GB ssd on usb
- multiboot with Raspbian64, libreelec, Twister, ubuntu2010

After reinstalling pinn 3.53 beta, I installed 8 projects again and wrote the backups back into the previously used partitions. I can start the other OS except for libreelec.
Then I installed a new installation of libreelec in the project previously occupied with libreelec, with the same error message when starting Error 00000044.

Jochen

[procount]

with the same error message when starting Error 00000044.

I'm afraid I don't know what error 00000044 is. I will add it to my list to see if I can investigate it further. But see my next post about backups in general to see if that helps.

[procount]

Warning - PINN BACKUPS

I am so glad PINN displays that message about "Testing your backups before relying on them" and generally it seems users are doing just that.

This is uncovering a few issues with the backups, particularly regarding ACL which seems to be used more prevalently. Unfortunately, the backup technique PINN uses at the moment does not store ACL information, so some information in the latest OSes is missing when it is restored. The main culprit (in Raspios anyway) relates to the /media/pi folder not having the correct access rights. This manifests itself as the OS no longer being able to auto-mount USB sticks or other external drives when they are attached. At least they appear to mount, but are not accessible.

The solution in this instance is to add the ACL back when the OS is restored with

Code: Select all

sudo setfacl -m user:pi:r-x /media/pi

In some instances, deleting the folder (if it is empty) and rebooting can cause the OS to restore the folder with the correct access rights.
I am looking at different ways to improve the backup process, but in the meantime, please continue to be vigilant in checking your backups are ok and report any problems, preferably as a github issue.

[jochene]

with the same error message when starting Error 00000044.

I'm afraid I don't know what error 00000044 is. I will add it to my list to see if I can investigate it further. But see my next post about backups in general to see if that helps.

Hello,
I continued to experiment.
With pinn-lite 2.5.2, the backup can be restored and works.
Unfortunately, the whole thing doesn't work with pinn-lite 3.5.3. When booting from libreelec, the error 00000044 appears.
For e.g. Twister, the root PartUUID is displayed in cmdline.txt.
Liberelec says in cmdline.txt "boot = LABEL = System disk = LABEL = Storage quit".
The pinn.lite 3.5.3 seems to have a problem with that.
With a new installation in the same partition (with me "ProjektSpace2") the cmdline.txt says "boot = LABEL = System0 disk = LABEL = Storage0 quit", but the boot does not work either.

Maybe this info will help.

Thanks

[procount]

With pinn-lite 2.5.2, the backup can be restored and works.

Did you mean 3.5.2?

3.5.3 is still beta because it uses a new build environment to match NOOBS, so many subtle things may have changed.
Thanks for the report. I shall look into LibreELEC.
Don't forget to check whether the auto-mounting works in your other backups and fix accordingly.

EDIT: When you say 3.5.2 backups work, but 3.5.3 backups don't, were the backups you restored in 3.5.3 backed up with 3.5.2 or 3.5.3? It's helpful to narrow down whether the problem is in the backup or the restore operations.

[aliens72]

Hi there, i've installed PInn Lite last stable version with 4 OS on USB 64Gb flash drive.
When i choose the Raspbian OS give me the error :

thumbnail_IMG_20201218_142152.jpeg (148.38 KiB) Viewed 2892 times

Can u help me please?

[jochene]

Hello,
I work with 3.5.2 and have created working backups with it.
I then installed the 3.5.3 beta and tried to import the backups from 3.5.2.
For this I have created 8 projectspaces under 3.5.3beta and imported my backups in 1-4 (the same order as under 3.5.2).
Only the libreelec backup causes the problems already described.

Then I replayed 3.5.2 and played all backups back, first i have created 8 projectspaces. No more problems with libreelec, the other OS work too.

[procount]

Oh, interesting, so it's the restoration of a 3.5.2 LibreELEC backup on a 3.5.3 version of PINN that's your problem. Restoring it with 3.5.2 is ok. Hmmm. Thanks for the info. I'll do some tests soon.

[procount]

Hi there, i've installed PInn Lite last stable version with 4 OS on USB 64Gb flash drive.
When i choose the Raspbian OS give me the error :

They look like errors with your USB drive. Is it a new one? Have you tested it?
I suggest using something like h2testw to check it for errors, although this will require erasing the drive and reinstalling your OSes to it.
I suggest checking each of your OSes work on the USB drive individually by using Rpi Imaging Utility or similar first. If they all work, then try again with pinn lite.

[jochene]

Oh, interesting, so it's the restoration of a 3.5.2 LibreELEC backup on a 3.5.3 version of PINN that's your problem. Restoring it with 3.5.2 is ok. Hmmm. Thanks for the info. I'll do some tests soon.

Hello,
this info may still be interesting.

I also tried the following:
- Empty 240GB SSD (fat32)
- copy pinn-lite 3.5.3beta on SSD und start the rpi4 8GB
- 8 project spaces created than reboot rpi4
- libreelec installed in the second project space (no backup playing back)
Here, too, the error: 00000044 appears when trying to start libreelec.

I don't use an SD card in the rpi4, I boot and start libreelec from the SSD.

In the cmdline.txt from libreelec is:
boot = LABEL = System0 disk = LABEL = Storage0 quit
I believe that pinn-lite 3.5.3beta does not understand this entry or interprets it incorrectly.

For example, if I Twister or Raspbian installing in a project space, the PartUUID of the root drive is displayed in the cmdline.txt. These can be started without any problems.

[jochene]

Hello,
I came across the following problem with pinn-lite 2.5.2 and pinn-lite 2.5.2.1.
If I install the OS Raspian64, libreelec, Twister, Ubuntu and RecallBox on an empty SSD (RPI4, pinn-lite is also on the SSD), everything works.

If I install 8 ProjectSpaces on an empty SSD (pinn-lite is also on the SSD) and then want to install the OS Raspian64, libreelec, Twister, Ubuntu and RecallBox in these ProjectSpaces, there is a problem with RecallBox.

The following error message is displayed.
"Recallbox - Pi4 has an incompatible number of partitions with ProjektSpace - 5".

The OS Lakka, Retropie and batocera also do not work if you install them on the SSD with multiboot.
It would be really great if you could install and run as much OS as possible with a large SSD.

Is there a way to fix this problem?


I have only had a PI4 with a large SSD for a short time and am slowly starting to deal with pinn-lite. I think the possibility of not having to change SD any more is great.
When new pinn-lite versions are available, I like to try them out.

Thanks

[procount]

ProjectSpaces are only applicable to the majority of OSes that have the standard 2 partitions: one FAT32 for BOOT, and another usually ext4 partition for the rootfs. Others with 3 partitions or more just won't work. You can use an existing ProjectSpace to create your own template for another OS, like recalbox. Or just install recalbox with 7 ProjectSpaces at the beginning.

Not all OSes are suitable for installing to USB. I have generally blocked the ones that don't work, but maybe I forgot to block these ones from installing. This is normally a problem with the OS itself, either the firmware needs updating, or it can't cope with PARTUUID references to the partitions.

[jochene]

Hello,
thanks for the hints. I'll try to see if I can do something.

Thanks

[jochene]

Hello,

I replaced the files start4.elf and fixup4.dat in the boot.tar.xz from retropie with the files from raspbian64 and retropie starts in multiboot from the SSD. I installed the retropie from the USB stick in the "ProjektSpace 5"

It can't be that simple ?????
Couldn't test retropie yet, but it starts.

Will definitely not work on every OS.

I'll keep trying.

Thanks

[procount]

PINN has been updated to v3.5.4

The following additional features are included in this version:

V3.5.4

• buildroot - improve some build scripts
• dualhdmi - fix license
• Installation - Refactor close dialogs for better error handling
• Memory - Display amount of Pi memory fitted
• partuuid - Allow installation to USB without partuuid
• Filesystems - Added support for ext3 and exfat
• wifi - Wifi firmware updated

This version contains all the features of the previous v3.5.3 beta with the addition of support for some additional filesystems and updated wifi firmware. I've also reverted to my previous build environment until I can investigate the one issue that was reported with the previous beta.

[busywait]

PINN has been updated to v3.5.4

Thank you! I currently have a slightly customised set of partitions in PINN 3.3.4.2: I resized my shared data partition, and converted it to F2FS.

Is there a built-in way to back up the PINN setup before I update, and an easy way to restore that?

[procount]

If you connect your Pi to the internet and boot it, it should inform you of the update and then you can tell it to upgrade.
This does not affect any of your existing partitions.

[WildSioux]

Maybe my post above was missed. Does anyone know how to add Android TV version of Lineage to PINN? https://konstakang.com/devices/rpi4/LineageOS17.1-ATV/

I tried to follow a few guides but couldn't make it show up.

Also, I installed Android Lineage on SD card and raspberry pi os on a USB drive. Why does it seem to install raspberry pi twice? I actually had to go through the install process twice for raspberry pi os.

Looking at gparted there are a lot of unnecessary partitions on my sd card. I think the actual OS is installed on the sd card with storage on the usb drive but I'm not sure. I have a root64 and some other folders. I wish it was all on usb as I thought. Is that possible?

Thanks