After over a month, I’ve updated Manjaro (with yay) on my PineBook Pro. In the log, I saw a message concerning updating u-boot. I followed the instructions (I did that a few times in the past without problems). Reboot. The result is that u-boot detects Manjaro, but then the screen stays blank. Now, I cannot even boot from SD or USB (as I was able to do in the past).
It’s boot firmware. There’s a reason why we don’t flash it for you.
As I just pushed an update that has been tested to work, you need to reflash the new one when your mirrors syncs in the new one for your updates. If that’s not possible for you to access, you need to disable the eMMC by the eMMC switch on the main board, then you can boot from the SD card and reflash a working u-boot to eMMC.
I foolishly followed the instructions that came with the u-boot update, and now S3 suspend is b0rked (it just shuts down when I close the lid or issue a systemctl suspend).
(I had to reinstall, too, as I had no video on boot, but that’s not a biggie).
I found this thread which mentions using the uboot-pinebookpro-bsp package to restore the functionality, but I can’t find that anywhere in the repos or in AUR. I found it on github, but the build instructions were as long as my arm (pun not intended).
Does anyone have a copy of this I can flash to restore the bootloader to a fully-functioning state?
Yeah, it’s not the lack of options which makes me afraid, it is rather the numerous options, without clear understanding of the pros and cons of each approach, and how they relate to each other, and also to the age of my hardware resp. my OS (Manjaro), i.e. which ones are living corpses.
Currently I boot kali on my pbp - but triggered by this I decided to build the u-boot package as I clearly remember there was no flickering of screen when I received my pbp back in early september last year, it only came after flashing tow-boot.
Techically you should be able to flash the images from the repo. I don’t think the pbp changes with respect to hardware - it is what it is - also because a lot of developers is intended to work with the same hardware.
So I am creating a sd-card using manjaro-arm-installer - to be loaded - I can alwys reflash to tow-boot
There is also the uboot-pinebookpro which is newer than pinebookpro-bsp.
From one of the commit messages it appears that the bsp sets the boot order specifically.
This could be the difference between the two - I mean - it makes sense to create a loader which doesn’t require you to disassemble to be able to disable eMMC if you have borked the loader.
That is why I like Tow-Boot better than U-boot - for the option to hit ESC then choose where to load from - and when you say you have the same flicker when switching from loader to system - then I have absolute no desire to verify :).
And for the S3 thingy - I believe I read something about S3 being deprecated - that may have been in another context though - I cannot remember but fairly recent I believe.
I actually installed my uboot from the uboot-pinebookpro package, but, as said, it is rather worse than the default bootloader coming originally with the PBP. And it didn’t improve the sleep battery time.