Difference between revisions of "Pinebook Pro Installing Void Linux ARM"

From PINE64
Jump to navigation Jump to search
(Split kernel section)
 
(19 intermediate revisions by 3 users not shown)
Line 1: Line 1:
'''DISCLAIMER''': This is Work In Progress, no warranty implied, this is also for experienced linux users.
{{Warning|This guide is a Work In Progress; no warranty is implied. This installation method is not officially recommended (or discouraged) by the Void Linux project. This guide is for experienced Linux users.}}


This will not be a complete guide, as it borrows heavily on [[Installing Arch Linux ARM On The Pinebook Pro]], so read it first then come back here.
This will not be a complete guide, as it borrows heavily on [[Pinebook Pro Installing Arch Linux ARM]], so read it first then come back here.


Only the steps that are different are listed here. Be careful, the numbering of the sections is not the same.
Only the steps that are different are listed here. Be careful, the numbering of the sections is not the same.
==Installing the root filesystem==


=== Downloading and verifying the rootfs tarball ===
=== Downloading and verifying the rootfs tarball ===


You can go to the Void linux [https://voidlinux.org/download/ download page], select the "arm" tab, and choose one of the aarch64 rootfs tarballs, either glibc or musl.
You can go to the Void Linux [https://voidlinux.org/download/ download page], select the "arm" tab, and choose one of the aarch64 rootfs tarballs, either glibc or musl.
How to check integrity of the downloaded file is explained on the same page.
How to check integrity of the downloaded file is explained on the same page.


Or use the following instructions (on debian):
Or use the following instructions (on Debian):
  <nowiki>$ wget https://repo-default.voidlinux.org/live/current/void-aarch64-musl-ROOTFS-20221001.tar.xz</nowiki>
  <nowiki>$ wget https://repo-default.voidlinux.org/live/current/void-aarch64-musl-ROOTFS-20221001.tar.xz</nowiki>
  <nowiki>$ wget https://repo-default.voidlinux.org/live/current/sha256sum.{txt,sig}</nowiki>
  <nowiki>$ wget https://repo-default.voidlinux.org/live/current/sha256sum.{txt,sig}</nowiki>
Line 21: Line 23:
=== Extracting and configuring the root filesystem ===
=== Extracting and configuring the root filesystem ===
==== Extracting the root filesystem ====
==== Extracting the root filesystem ====
  # tar -xpf void-aarch64-musl-ROOTFS-20221001.tar.xz -C /mnt
  tar -xpf void-aarch64-musl-ROOTFS-20221001.tar.xz -C /mnt
 
==== Kernel ====


==== Configuring a login agent on the serial console ====
The Void Linux rootfs tarball does not contain a kernel, however  the '''pinebookpro-kernel''' package can be installed from the Void Linux repositories. Alternatively, one can (cross) build a kernel themselves. Skip this section if you would rather install the package.
# cp -R /mnt/etc/sv/agetty-ttyS0 /mnt/etc/sv/agetty-ttyS2
# ln -sf /etc/sv/agetty-ttyS2 /mnt/etc/runit/runsvdir/default


=== Kernel ===
{{Warning|If you choose the manually built kernel route, you'll have to keep it updated yourself, the same way: manually (cross-)building and installing.}}
The Void linux rootfs tarball does not contain a kernel. We can borrow one from Arch Linux ARM or cross-build one ourselves.


=== Use Arch Linux ARM kernel ===
===== Manually cross-compiling a mainline kernel suitable for the Pinebook Pro =====
TODO


=== Cross-compiling a mainline kernel suitable for the Pinebook Pro ===
We'll use the postmarketOS kernel configuration and boot parameters, because they are working properly, and are sufficiently up-to-date. This is done from an x86_64 computer.
We'll use the PostmarketOS kernel configuration and boot parameters, because they are working properly, and are sufficiently up-to-date. This is done from an x86_64 computer.


This has been tested with PMOS configuration for 6.0.2 and kernel 6.1.0-rc5+. No initramfs was needed to boot the OS.
This has been tested with postmarketOS configuration for 6.0.2 and kernel 6.1.0-rc5+. No additional initramfs was needed to boot the Void Linux OS.


  $ git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
  $ git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
  $ cd linux
  $ cd linux
  $ wget -O .config https://gitlab.com/postmarketOS/pmaports/-/blob/master/device/community/linux-postmarketos-rockchip/config-postmarketos-rockchip.aarch64
  $ wget -O .config 'https://gitlab.com/postmarketOS/pmaports/-/raw/master/device/community/linux-postmarketos-rockchip/config-postmarketos-rockchip.aarch64?inline=false'
$ sed -i \
  -e 's|CONFIG_ROCKCHIP_CDN_DP=.*|CONFIG_ROCKCHIP_CDN_DP=n|' \
  -e 's|CONFIG_BATTERY_CW2015=.*|CONFIG_BATTERY_CW2015=y|' \
  -e 's|CONFIG_TYPEC_FUSB302=.*|CONFIG_TYPEC_FUSB302=y|' \
  -e 's|CONFIG_TYPEC_TCPM=.*|CONFIG_TYPEC_TCPM=y|' \
  .config
  $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j1 oldconfig
  $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j1 oldconfig
  $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j$(grep -c '^processor' /proc/cpuinfo)
  $ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j$(grep -c '^processor' /proc/cpuinfo)


=== Installing the newly built kernel, modules & DTB files ===
===== Manually installing the newly built kernel, modules & DTB files =====


  $ KVER="$(make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j1 kernelrelease)"
  $ KVER="$(make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j1 kernelrelease)"
Line 51: Line 56:
  INSTALL_MOD_PATH=/mnt \
  INSTALL_MOD_PATH=/mnt \
  INSTALL_DTBS_PATH=/mnt/boot/dtbs
  INSTALL_DTBS_PATH=/mnt/boot/dtbs
$ sudo cp arch/arm64/boot/Image "/mnt/boot/Image-${KVER}"
==== Configuring a login agent on the serial console ====
cp -R /mnt/etc/sv/agetty-ttyS0 /mnt/etc/sv/agetty-ttyS2
ln -sf /etc/sv/agetty-ttyS2 /mnt/etc/runit/runsvdir/default
==== Creating extlinux.conf ====
Note: if using the official PBP kernel package, it is also recommended to use the '''u-boot-menu''' package, which automatically regenerates the extlinux.conf file on kernel upgrades. In that case, you will not need to follow the below instructions.
The following borrows from [https://gitlab.com/postmarketOS/pmaports/-/blob/master/device/community/device-pine64-pinebookpro/extlinux.conf postmarketOS u-boot configuration for the kernel command-line parameters].
We force the serial console to 115200 bauds (from the default 1.5M bauds), so that it is the same as tow-boot's.


  $ sudo cp arch/arm64/boot/Image "/mnt/boot/Image-${KVER}"
  # mkdir -p /mnt/boot/extlinux
# cat <<EOF > /mnt/boot/extlinux/extlinux.conf
default l0
menu title Pinebook Pro Boot Menu
prompt 0
timeout 50
label l0
menu label Boot Kernel on SD
linux /Image-${KVER}
fdt /dtbs/rockchip/rk3399-pinebook-pro.dtb
append console=tty0 console=ttyS2,115200n8 coherent_pool=1M pcie_aspm.policy=performance video=HDMI-A-1:1920x1080@60 video=eDP-1:1920x1080@60 rw rootwait root=/dev/mmcblk1p3
EOF
 
=== Finalizing ===
 
Now you can umount the partition(s) and boot the Pinebook Pro with Void Linux. The default root password is "voidlinux".
 
[[Category:Pinebook Pro]]

Latest revision as of 15:34, 20 February 2023

Warning: This guide is a Work In Progress; no warranty is implied. This installation method is not officially recommended (or discouraged) by the Void Linux project. This guide is for experienced Linux users.

This will not be a complete guide, as it borrows heavily on Pinebook Pro Installing Arch Linux ARM, so read it first then come back here.

Only the steps that are different are listed here. Be careful, the numbering of the sections is not the same.

Installing the root filesystem

Downloading and verifying the rootfs tarball

You can go to the Void Linux download page, select the "arm" tab, and choose one of the aarch64 rootfs tarballs, either glibc or musl. How to check integrity of the downloaded file is explained on the same page.

Or use the following instructions (on Debian): 

$ wget https://repo-default.voidlinux.org/live/current/void-aarch64-musl-ROOTFS-20221001.tar.xz
$ wget https://repo-default.voidlinux.org/live/current/sha256sum.{txt,sig}
$ wget https://github.com/void-linux/void-packages/raw/master/srcpkgs/void-release-keys/files/void-release-20221001.pub
$ signify-openbsd -V -p void-release-20221001.pub -x sha256sum.sig -m sha256sum.txt
Signature Verified
$ sha256sum -c --ignore-missing sha256sum.txt
void-aarch64-musl-ROOTFS-20221001.tar.xz: OK

Extracting and configuring the root filesystem

Extracting the root filesystem

tar -xpf void-aarch64-musl-ROOTFS-20221001.tar.xz -C /mnt

Kernel

The Void Linux rootfs tarball does not contain a kernel, however the pinebookpro-kernel package can be installed from the Void Linux repositories. Alternatively, one can (cross) build a kernel themselves. Skip this section if you would rather install the package.

Warning: If you choose the manually built kernel route, you'll have to keep it updated yourself, the same way: manually (cross-)building and installing.
Manually cross-compiling a mainline kernel suitable for the Pinebook Pro

We'll use the postmarketOS kernel configuration and boot parameters, because they are working properly, and are sufficiently up-to-date. This is done from an x86_64 computer.

This has been tested with postmarketOS configuration for 6.0.2 and kernel 6.1.0-rc5+. No additional initramfs was needed to boot the Void Linux OS. 

$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ wget -O .config 'https://gitlab.com/postmarketOS/pmaports/-/raw/master/device/community/linux-postmarketos-rockchip/config-postmarketos-rockchip.aarch64?inline=false'
$ sed -i \
  -e 's|CONFIG_ROCKCHIP_CDN_DP=.*|CONFIG_ROCKCHIP_CDN_DP=n|' \
  -e 's|CONFIG_BATTERY_CW2015=.*|CONFIG_BATTERY_CW2015=y|' \
  -e 's|CONFIG_TYPEC_FUSB302=.*|CONFIG_TYPEC_FUSB302=y|' \
  -e 's|CONFIG_TYPEC_TCPM=.*|CONFIG_TYPEC_TCPM=y|' \
  .config
$ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j1 oldconfig
$ make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j$(grep -c '^processor' /proc/cpuinfo)
Manually installing the newly built kernel, modules & DTB files
$ KVER="$(make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j1 kernelrelease)"
$ sudo make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j1 modules_install dtbs_install \
		INSTALL_MOD_STRIP=1 \
		INSTALL_MOD_PATH=/mnt \
		INSTALL_DTBS_PATH=/mnt/boot/dtbs
$ sudo cp arch/arm64/boot/Image "/mnt/boot/Image-${KVER}"

Configuring a login agent on the serial console

cp -R /mnt/etc/sv/agetty-ttyS0 /mnt/etc/sv/agetty-ttyS2
ln -sf /etc/sv/agetty-ttyS2 /mnt/etc/runit/runsvdir/default

Creating extlinux.conf

Note: if using the official PBP kernel package, it is also recommended to use the u-boot-menu package, which automatically regenerates the extlinux.conf file on kernel upgrades. In that case, you will not need to follow the below instructions.

The following borrows from postmarketOS u-boot configuration for the kernel command-line parameters.

We force the serial console to 115200 bauds (from the default 1.5M bauds), so that it is the same as tow-boot's. 

# mkdir -p /mnt/boot/extlinux
# cat <<EOF > /mnt/boot/extlinux/extlinux.conf
default l0
menu title Pinebook Pro Boot Menu
prompt 0
timeout 50

label l0
menu label Boot Kernel on SD
linux /Image-${KVER}
fdt /dtbs/rockchip/rk3399-pinebook-pro.dtb
append console=tty0 console=ttyS2,115200n8 coherent_pool=1M pcie_aspm.policy=performance video=HDMI-A-1:1920x1080@60 video=eDP-1:1920x1080@60 rw rootwait root=/dev/mmcblk1p3
EOF

Finalizing

Now you can umount the partition(s) and boot the Pinebook Pro with Void Linux. The default root password is "voidlinux".

Retrieved from "https://wiki.pine64.org/index.php?title=Pinebook_Pro_Installing_Void_Linux_ARM&oldid=17551"