An unofficial Debian Installer for Pinebook Pro

[danielt]

My kernel was half the size of Daniel's kernel. That made me realize that mine was compressed while his was not.

I assume that's why uboot refused to boot it and moved on to the next kernel in the extlinux.conf list.

Now that I uncompressed my kernel, a boot ends up in a black screen. I assume Daniel put some magic into his kernel deb.

Sort of. There is an environment variable that controls which kernel image goes into the deb and it needs to be set to point to an uncompressed image (as it happens I *did* have to add some code for get KBUILD_IMAGE to work on the openbuildservice but it is not needed for local builds).

Try something like:

Code:

make  KBUILD_IMAGE=arch/arm64/boot/Image bindeb-pkg

Note that if you have already built a kernel then you don't have to build the kernel again, you can simply uncompress it:

Code:

sudo mv vmlinuz-$ver vmlinuz-$ver.gz
sudo gunzip vmlinuz-$ver.gz

---

@danielt is your kernel config shared anywhere here? I'd like to repro it exactly, with the addition to run armhf binaries when making.
Thanks!

Depends how exact you want to be!

As mentioned in a previous post https://forum.pine64.org/showthread.php?...7#pid56887 I don't want my kernel tree to distract attention from Thomas' since it simply fragments the community (that post also shows how I build the kernel).

However neither do I want to be secretive, especially since the kernel config is included in the kernel itself (try: gunzip -c /proc/kconfig.gz ). Should you ever need it the exact sources can be found on the openbuildservice: https://build.opensuse.org/package/show/...elthompson .

---

Regarding cpus.
Can anyone point me to a working method of bringing big cores back online manually ?

If I do ”echo 1 >” I get input/output error.

Big cores are brought back online (as root) with:

Code:

echo 1 > /sys/devices/system/cpu/cpu4/online
echo 1 > /sys/devices/system/cpu/cpu5/online

If you get input/output errors when running the above as root then check the dmesg log to see if there are any extra details (especially if you are running a self-compiled kernel).