That's what I'm using. Aside from the orange led, it offers much more power savings under mem sleep, but sound doesn't work after wake.
Be aware of the one partition vs two issue, since that bsp package is from before manjaro switched to two partitions and will come with an incorrect setting for an up-to-date system. It's a simple edit.
I got really confused because of the missing orange led. I thought this uboot has messed up my pbp, because it didn't come on. I had my finger on the power switch for minutes. I only realized, it's something to do with the led, because I went for a screwdriver to open the case in order to disable the emmc. When I returned, I saw the login screen
I prepared a sd card with mrfixit2001's latest debian image. When I booted from sd, immedately after the green led came on, the "open sesame" splash appeared. The green led started flickering (expanding the root file system) and after a short while ---- I got the manjaro splash and login screen. So after reboot it booted from emmc. Shutting down and starting again, however, booted into Debian from the sd card. From now on, the boot process is reliable. With a sd card inserted, it boots from the sd card. Otherwise it boots from emmc.
The behavior of the LED and bootorder also confused me while setting up a new clean KDE install. By the way the manjaro-arm-flasher is a realy nice tool. Differently than mentioned it does not ask for sudo password.
Boot from SD card before eMMC works, but if a different ROOT partition is defined in extlinux (on SD) and ROOT_MNJRO partition is present on eMMC, extlinux.conf is ignored and ROOT_MNJRO is taken as ROOT. By renaming ROOT_MNJRO on eMMC the ROOT from extlinux.conf is used.
One thing I noticed is, that the boot process takes a very long time when you don't have network access. The spinning circle in the boot splash freezes for a pretty long time. When I then log in to the kde de, the connection widget in the system tray is missing. I have to start NetworkManager manually to bring it up.
So, the thread above perhaps already answers this for me but: is ARM Testing meant to be stable enough that you can test updates with a machine in real use? Or should we stay clear if we somewhat depend on the machine normally working for us? I'd like to help, but the PBP is currently my only personal laptop and I would like to have it normally mostly working.
It’s meant to be less stable than the stable branch, but more stable than the unstable branch. I would say you should expect at least some things to break from time to time, so if you need your system to be the most reliable, you should stick to the stable branch.
I tested booting 7 SD cards with distros installed. All cards successfully boot from power on with uboot-pinebookpro-bsp 1.5-7 installed and written to emmc.
With uboot-pinebookpro 2020.07rc4-4 installed and written to emmc the results are varied.
I came to the conclusion that SD card model effects the boot order. Four cards are the same model (ADATA 64GB A1) but with different distros. None of these four cards will boot from power on, the manjaro installation on emmc boots instead. All four cards will attempt to boot when restarting from manjaro on emmc, whether the boot is successful depends on the distro.
The three other SD cards I tested booted from power on but did not boot from restart, whether it was restarted from emmc or SD card distro.
Distros that booted successfully:
Manjaro pinebook pro factory image
Manjaro image from earlier this year without separate boot partition
Danielt unofficial Debian installer
Debian Desktop Community Build Image by mrfixit2001 (but fails to poweroff)
Distros that did not successfully boot:
Ubuntu Bionic Mate Community Build Image by ayufan
Alright, back in business.
After some questionable decisions to wipe certain bits and fixing broken partitions, I've backed up my settings and re-installed through Etcher. There is a high chance that my original install used different dd settings for the block sizes messing up things which wouldn't be otherwise visible.
So, it's a bit early to provide full results yet can already see a few things with rc4-4:
So far, no odd grey line display initialization
Boots fine targeting default uboot with 20.06 on SD card