Difference between revisions of "Pinebook Pro Software Releases"

Jump to navigation Jump to search
(Added instructions for custom kernel configuration)
(Wrapped up installation instructions)
Line 408: Line 408:


Don't follow any of Janikk's other instructions. They appear to be out of date (no offense bro). Let me be clear: DO NOT INSTALL U-BOOT. I don't know what will happen, but it won't be an improvement over the existing boot-loader so don't worry about it.
Don't follow any of Janikk's other instructions. They appear to be out of date (no offense bro). Let me be clear: DO NOT INSTALL U-BOOT. I don't know what will happen, but it won't be an improvement over the existing boot-loader so don't worry about it.
Finish installing your system until you come to the kernel.


'''Custom Kernel'''
'''Custom Kernel'''
Line 425: Line 427:
<code>make menuconfig</code>
<code>make menuconfig</code>


At this point, you're almost on your own. I don't know a strict cause-and-effect relationship between my kernel config and the behavior of my system. For starters, just go into platform selection and deselect everything except rockchip platforms. Once you're done save your configuration and exit. Make sure boot is mounted, and your fstab is set up with your swap mounted.
At this point, you're almost on your own. I don't know a strict cause-and-effect relationship between my kernel config and the behavior of my system. For starters, just go into platform selection and deselect everything except rockchip platforms. Once you're done save your configuration and exit. Make sure boot is mounted, and your fstab is set up with your swap mounted. Make sure dracut is installed.


<code>make
<code>make
Line 438: Line 440:


make dtbs_install  
make dtbs_install  
ls /lib/modules
dracut -f --kver <name of directory in /lib/modules matching your kernel, *not* the kernel name from eselect>
</code>
emerge the package extlinux and run <code>u-boot-update</code>. Open the extlinux configuration file.
<code>nano /boot/extlinux/extlinux.conf</code>
And configure it as follows:
LABEL <label of your choice, for example GENTOO ARM>
KERNEL /<name of your vmlinuz kernel image. Include the slash, but be relative to boot, not root.>
FDT /dtbs/<kernel-version>/rockchip/rk3399-pinebook-pro.dtb
APPEND initrd=/<name of initramfs image> root=PARTUUID-<nboot partition's PARTUUID, no quotes> rw rootwait
</code>
</code>
You can use the blkid command to find the PARTUUID of every partition on the machine. None of this configuration is guaranteed to work, but it worked for me, and given enough fiddling you can get it to work as well.
Now you should reboot the machine and see if it boots into gentoo. If it does: congratulations! If not, too bad. Try again.


== Kali Linux ==
== Kali Linux ==