Hi, I’m the new happy owner of a Pinebook Pro and I’m really impressed with how well and smooth Manjaro KDE runs on it (event though I have fully encrypted my root FS using LUKS).
So thanks to all the Manjaro ARM team for this tremendous work !
However I’m a bit puzzled with the unusual way this ARM machine boots so I have a couple questions.
When I got the machine it initially “booted in the dark” before the Manjaro Plymouth logo appears. I was quite happy with this discretion.
Since, I have installed the uboot-pinebookpro package and dd it to the first sectors of the eMMC.
Unexpected to me, my Pinebook Pro now boots in a more “Traditional PC” way, with the bootloader showing some BIOS-like output, followed by a messed up display for a half-second, and I’d rather disable all this. Is it something that can be easily confiigured ?
Unfortunately I didn’t think of making a backup of the original Pinebook Pro eMMC bootloader space, so I can’t restore it to the original (it there a copy of the original bootloader somewhere ?).
Also, I’m under the impression that the boot process is noticeably longer with the new bootloader compared to the original one. I see that the bootloader is turning on USB and probing the USB ports, which takes some time ; I’d like to disable this as I don’t plan booting my machine from USB.
Again is this feasible, is there some relevant documentation I could read ?
Also, while booting I notice :
Loading Environment from SPIFlash... (blah blah) ***Warning - bad CRC, using default environment
I’m still not sure of the exact role of the SPI flash, I know it may hold a bootloader but I’m not sure if there is even anything on it on an off-the-shelf Pinebook Pro.
Am I supposed to initialize the SPI in some way so u-boot can read-write its environment from/to it ?
Well basically I just would like to feel at ease with the PBPro boot process and u-boot, like I used to be on PCs with BIOS, UEFI, grub or rEFInd…
It looks like u-boot loads an extlinux/extlinux.conf file that resembles much a syslinux configuration file, but well that’s not syslinux, so ? It woud be nice to be able to define a boot menu there with several options, but still is this feasible ?
So any pointers on docs would be much appreciated, everything I coud read was either very specific to one given problem, or necessitated u-boot patches and recompilation, I assumed that there might be a simpler way of doing things…
Thanks in advance for any help.