Gentoo on Pinebook Pro RELEASE
I have a rockpro64, ive built a gentoo Iinux on debian-arm64 , usb emmc, as chroot.
64 was max , however i have to replace laptop m.2... (i bought i mini adapter and ribbon adapter to stuff an m.2 into a playbox case.
Touchscreen drivers are a rarity but doable pia, screen mirroring to hdmi/dsp0-ts)
For a demo feild pentester contraption..

Sdcard to emmc adapter so.. as sdcards stresses out faster.. or need endurance models.
Emmc are more akin to m.2 and far more re

My emmc is outa space so opportune time to move the build mess to 550 m.2.

Now 128 emmc are on menu so 2 might be good.
Multi instace binhost, will keep packages, with different build flags but also eats space.
And can prepare, the manjaro root fs , cleave out / /boot /boot/efi symbolic link some files on /boot to /efi ..
I have grub with uefi, uboot zfs etc etc etc.,
Newer uboot can load uefi. Ie grub-efi as intermediate boot, pick a kernel, or even refind..
Pick kernel/os on m.2 emmc, sd.. usb etc.

So preparing a chroot is quite doable.

Sakaki's Rpi4 binhost is helping, but be warned, many are opengl+gles2 or majority -gles2..
However many packages wont build , but her/his crossdev build pkgs can the be rebuilt..
+/- features.. xfce is in tree.
Upstream has a few older packages but more on server targets.

Ive added a few pine64 rockpro64, rock64, and the pine book pro files as binaries.

And PENTOO LINUX, my original purpose.
Ports of metasploit, gcc crossdev's etc.

Scaleway hosting, 35 usd/32 E's a mo 8-16 gigs , and dep on virtual cores, debian host 256 gigs of mounted chroot.
Speed of compiles is greatly improved.
Make linux j8 etc. Useful if fakeroot = ./my-kernel
-C to chroot on tar xz > kernel.txz

Most kernels, gentoo, panfrost sorces , Sabayon, pentoo, make all modules, then allyess
Fix config, sysfs v2 depreciated in general setup, N as in hell No.
Next i need to grepout debugging items in config.

Aufs5 sources. Or stand alone async-emerge needs it. , cloveros a gentoo live has a reliable aufs5 patching bit in gitgud , buildroot scripts.
Uses chroot in tmpfs/ramdrive to remake world.
Drops bins in /packages, ie kde qt5-x.y.z x.y.35 out deps hell no letgo...
Upgrade qt stack revdep-rebuild wala.

Since i care to run possible 3x arm64 devices, id rather go failsafe on kernel.

Scaleway, ill need to renew soon i suppose, and docker is good for building and reliable.

Sent from my SM-N960U using Tapatalk
Great resource for Gentoo users.

Does it take a long time to compile OS + kernel + DE? Meaning from usability point, if regular 2-4-weekly update takes more than 1 day to compile (of course excluding browsers)?

Unrelated, is there a way to make this set-up more/fully FLOSS?:

Gentoo is great by giving option ACCEPT_LICENSE="-* @FREE" in make.conf

But those binaries are needed:


First three are for wifi/BT - could be skipped while using USB wifi, right?

While is dptx.bin critical for machine operation, or only for usb-c video out?

Are there any other binary blobs that I'm not aware of?

Finally, manjaro kernel is used. Is this kernel baked with proprietary firmware binaries, or firmware is installed separately as a package (as in Gentoo sources) - making ideal case so no need to install linux-libre or deblob kernel by yourself

Thanks a lot
I doubt anyone will read this, but here we go.
I followed all the install instructions, except for when it comes time to install the boot-loader. The pinebook pro doesn't use grub2 or lilo or anything like that (i think), it instead uses u-boot, right? Well, I wasn't able to boot and when I checked the boot partition I noticed that there wasn't an Image or Image.gz file. I know I missed something, so can someone tell me please? I would appreciate it so much, because it's my dream to turn this into a gentoo machine with i3-gaps, rice it up, and post on r/unixporn. I would love nothing better than to neofetch that gentoo logo right in the middle of the screenshot.
For those of you that have successfully managed a working Gentoo install, can you provide a little more detail around the bootloader process?

I was able to run through the entire chroot process successfully (as far as I can tell), but got tripped up at the last stage of installing a bootloader. Is installing u-boot and the "u-boot-update" step all that's required? And more specifically, is u-boot being installed to the bootloader partition or the /boot partition? (I'm guessing bootloader partition is correct which is probably where I've gone wrong.)

I've used Gentoo for years and years, but never with a u-boot setup. Thanks.
Went through the install process for a third time with no luck booting. Reading some of the previous posts, it sounds like maybe uboot should be installed on one of the mmcblk1 partitions rather than mmcblk2?

Feels like the uboot piece is the hangup. Curious if anyone has any further details on which partition to target during uboot install. Thanks.

Edit: I guess mmcblk1 is the SD card. I've been looking at this too long and need to step away.
If you've created partitions as per post #27 you should dd to the corresponding partition
otherwise you have to dd to mmcblk2 (no partition number as you're writing to disk sectors) using seek command to place the files on the right disk sectors

dd if=idbloader of=/dev/mmcblk2 seek=64
dd if=uboot of=/dev/mmcblk2 seek=16384

double check mmcblk number using lsblk

You'll also need trusted firmware file if using debian uboot
Thanks @nightranger73 . That helps knowing to write to mmcblk rather than a partition and that got me further. No successful boot, but I no longer have to flip the emmc hardware switch to boot an SD.

What’s the trusted firmware situation? Is there documentation around that? I honestly have no idea whether I’m using the Debian uboot. I need to do some basic uboot research to better understand the entire process. Done dozens of gentoo installs but never worked with uboot. Thanks again for assistance.
@midnightcheese The trusted firmware is built separately and then bundled into the two uboot binaries during its compilation. It is easy to build both yourself, if you don't want to use precompiled images from various places. See step 5 in my Debian/Devuan guide for sample instructions:

Also, I recommend making a partition for storing both idbloader.img as well as u-boot.itb, so you don't accidentally overwrite either your regular filesystem with them or vice versa. Simply leave some space before your first partition or (my personal recommendation) create a "fake" partition which you never format to "mark" the respective u-boot area.
And some more info here, I think he uses gentoo also

Possibly Related Threads…
Thread Author Replies Views Last Post
  An unofficial Debian Installer for Pinebook Pro danielt 430 151,507 6 hours ago
Last Post: ab1jx
  OpenMandriva to release ARM builds for PineBook Pro and Pi ludix 8 760 Yesterday, 04:38 PM
Last Post: wdt
  postmarketOS/Alpine edge image for the Pinebook Pro MartijnBraam 62 31,319 02-14-2021, 12:25 PM
Last Post: pmjohann
  Pinebook Pro wifi not working seyo-iv 1 188 02-01-2021, 11:00 AM
Last Post: seyo-iv
  slarm64 (unofficial slackware) Pinebook Pro RK3399 (aarch64) mara 25 3,538 01-30-2021, 11:03 AM
Last Post: mara
  FLOSS pinebook pro linux set-up misha64 3 1,097 01-14-2021, 04:05 PM
Last Post: kuleszdl
  My Debian journey on the Pinebook Pro schwarzwieweiss 32 3,821 01-07-2021, 09:35 AM
Last Post: schwarzwieweiss
  Armbian for the Pinebook Pro [WIP] Luke 41 14,083 01-06-2021, 06:14 PM
Last Post: Idaho
Question Help: Pinebook Pro will not enter sleep [Manjaro 20.04] EverythingIsInput 48 17,464 12-30-2020, 09:08 AM
Last Post: wdt
Question New to Pinebook Pro and lots of questions! Anarethos 2 495 12-29-2020, 03:39 PM
Last Post: Anarethos

Forum Jump:

Users browsing this thread: 1 Guest(s)