A shell script to automatically create a bootable multi-distribution SD card for the PinePhone Pro.
Ensure the following packages are installed:
wgetrsyncunzip
Change directory to the project root:
cd /path/to/ppp-multi-imageRun the following command to download the images/tarballs for each distro (do not run as root):
./download.shAny time you pull new updates from the repository, or make manual changes to
the distro parameters (i.e. in distros/*/config), you will need to re-run
download.sh to download the updated files.
Finally, run the following command to generate the image:
./mkimage.sh [-p <partition size>] /dev/[DEVICE]Replace /dev/[DEVICE] with the device file of your SD card. Each distribution
will be allocated its own partition; use the -p argument to specify the size
of these partitions. If no -p argument is provided a default size of 10 GiB
per partition will be used.
Note: free space at the end of the device will be formatted as the Ubuntu Touch user data partition.
The -p argument will be passed straight to sfdisk, so refer to man sfdisk
regarding how to specify sizes accurately (e.g. GiB vs GB).
Currently there are six distributions available to install, so if we have a
64 GB (~= 59.6 GiB) SD card on /dev/mmcblk0 and we run the following command:
./mkimage.sh -p 9GiB /dev/mmcblk0Then we will obtain the following partition structure:
/dev/mmcblk0p1: Bootloader (raw partition, 16 MiB)/dev/mmcblk0p2: Distro 1 (9 GiB)/dev/mmcblk0p3: Distro 2 (9 GiB)/dev/mmcblk0p4: Distro 3 (9 GiB)/dev/mmcblk0p5: Distro 4 (9 GiB)/dev/mmcblk0p6: Distro 5 (9 GiB)/dev/mmcblk0p7: Distro 6 (9 GiB)/dev/mmcblk0p8: Ubuntu Touch user data (5.6 GiB)
The mkimage.sh script will automatically install Megi's custom U-Boot image
(source,
config+build) to
the SD card. This image must be executed by the PinePhone Pro during boot in
order to display the graphical distribution selector.
The easiest way to ensure this happens is to install rk2aw to the phone's SPI flash; then it will boot the correct U-Boot image regardless of what is installed on the eMMC.
Alternatively, you can hold the RE button while you power up your phone; this will temporarily disable the eMMC and SPI flash in order force a boot from the U-Boot image on the SD card.
If you have access to the phone's eMMC as a /dev/[DEVICE] node, you can use
the same method (as described above) to install the multi-distribution image
to the eMMC.
You will still need to make sure that the correct bootloader is being executed. You can either do this by installing rk2aw to the SPI flash and not inserting a bootable SD card, or by zeroing out your SPI flash.
This functionality exists mainly for development purposes, e.g. adding support for new distributions. Make sure that:
- You are still in the project's root directory, and
/dev/[DEVICE]has already been imaged viamkimage.sh.
Run the following command, replacing <distro> with the name of one of the
subdirectories in distros/.
util/installdistro.sh distros/<distro> /dev/[DEVICE]If you want to create an SD card image that can be written directly to an SD card (without having to re-run this script), you can do so as follows:
fallocate -l 64000000000 sdcard.img # e.g. for a 64GB SD card
./download.sh # if you haven't downloaded the images already
./mkimage.sh -p 9GiB sdcard.imgIt should be noted that this approach will take up 64GB of space on your hard drive and slow down the final copy to the SD card:
sudo dd if=sdcard.img of=/dev/[DEVICE] bs=1M conv=fsync