UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant)

[megous]

You're giving too little detail. This is just an image that's meant to be flashed to SD card and has everything setup already. No need to run p-boot-conf.

Yes, I should have been more clear: I was following the p-boot install instructions on the website before you posted this ready-made image. Nevermind, it's a bit off-topic for this thread and probably beyond my skill level.

You can check the scripts in the git repo. It's an example of how to install p-boot.

---

Thank you, very much for this. I'll try it as soon as i get my pinephone.

One question, could glodroid work with p-boot?
Apparently it is in a very rough state right now but it would like to try it out once it gets more polished.

I don't see why not. p-boot just loads the kernel and starts it.

[ikidd]

I've dd or etchered this a few times now, and I can't get gparted or kde partition manager to resize the btrfs partition. There's always bad tree blocks during the partition check prior to resizing that error it. I've done a scrub on the mounted partition and it says it fixes errors, but still fails.

Any ideas how to expand this so the operating systems on the image don't die within a few minutes from disk space issues?

[megous]

I've dd or etchered this a few times now, and I can't get gparted or kde partition manager to resize the btrfs partition.  There's always bad tree blocks during the partition check prior to resizing that error it.  I've done a scrub on the mounted partition and it says it fixes errors, but still fails.

Any ideas how to expand this so the operating systems on the image don't die within a few minutes from disk space issues?

Let me try (you can of course do this from a PC using a SD card reader, just change the device from /dev/mmcblk0 to something else):

# resize partition, dry run

echo ", +" | sfdisk -n -N 2 /dev/mmcblk0

Disk /dev/mmcblk0: 29.74 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x12345678

Old situation:

Device        Boot  Start      End  Sectors  Size Id Type
/dev/mmcblk0p1 *      8192  262143  253952  124M 83 Linux
/dev/mmcblk0p2      262144 15359999 15097856  7.2G 83 Linux

/dev/mmcblk0p2:
New situation:
Disklabel type: dos
Disk identifier: 0x12345678

Device        Boot  Start      End  Sectors  Size Id Type
/dev/mmcblk0p1 *      8192  262143  253952  124M 83 Linux
/dev/mmcblk0p2      262144 62333951 62071808 29.6G 83 Linux
The partition table is unchanged (--no-act).

# verify changes look sane, and do a real resize

echo ", +" | sfdisk -N 2 /dev/mmcblk0

# resize filesystem

mount /dev/mmcblk0p2 /mnt
btrfs filesystem resize max /mnt
df -h

# /dev/mmcblk0p2  30G  6.6G  24G  23% /mnt

umount /mnt

# and that's all

# btrfs check seems to succeeed without issues on the resized filesystem

btrfs check /dev/mmcblk0p2

Opening filesystem to check...
Checking filesystem on /dev/mmcblk0p2
UUID: 0cb50b0b-77a3-45bd-a605-857472b88281
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space cache
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups skipped (not enabled on this FS)
found 6970880000 bytes used, no error found
total csum bytes: 6340868
total tree bytes: 471728128
total fs tree bytes: 443301888
total extent tree bytes: 20905984
btree space waste bytes: 63863678
file data blocks allocated: 6499180544
referenced 14152331264

Here's a better formatted guide: https://xnux.eu/log/#010

[SpoofyKid]

I was able to get all OSs running on my Braveheart without any issues. Why was it that this wasn't recommended for the Braveheart?

I haven't tried expanding the partition yet; something I'll try later.

Thanks for the image - it was fantastic being able to try all OSs on one SD card without having to go through the hassle of flashing them all individually.
p-boot really works a treat!

[megous]

I was able to get all OSs running on my Braveheart without any issues. Why was it that this wasn't recommended for the Braveheart?

I haven't tried expanding the partition yet; something I'll try later.

Thanks for the image - it was fantastic being able to try all OSs on one SD card without having to go through the hassle of flashing them all individually.
p-boot really works a treat!

This uses only 1.2 DTB, so the kernel will drive some HW incorrectly, notably type-c stuff, and modem powerup/powerdown will be probably broken.

I have to add support to p-boot to automatically load the correct DTB based on auto-detection of Pinephone variant, before this will properly support Braveheart.

[BillButter]

Is it possible to flash this multi-image to the eMMC? I have version 1.1, so I can't really test it yet.

[megous]

Is it possible to flash this multi-image to the eMMC? I have version 1.1, so I can't really test it yet.

Yes. It should work as is when flashed to eMMC.

[megous]

And now it's a 13 distro image.

https://megous.com/dl/tmp/multi4.mp4

https://megous.com/dl/tmp/multi5.mp4

The image size is the same, despite the addition on 4 new postmarket OS variants.

[zer0sig]

Very cool, megous. I'll have to try this one when I get a pinephone. Maybe the kernel support will look a little better then. If not, maybe I can help.

[murak]

P-boot is impressive! I´m looking forward to trying this on my braveheart!