Changing Boot Order on the PineBook Pro
Hello, I searched for an answer but I'm not finding anything.  Apologies if this has been asked and answered already.

My Pinebook Pro boot order was behaving as expected for quite some time.  It was booting from the SD card when a bootable card was inserted, and then from the eMMC otherwise.

After flashing Ayufan's Chromium OS build to the eMMC, now for some reason the PBP always boots from the eMMC card unless I disable the hardware switch for it.  This effectively makes the eMMC worthless since it can't be re-enabled without rebooting, but then the boot happens from the eMMC (which is currently in a totally broken state and needs to be re-installed).  I've now got a real chicken and egg problem going here.

I had read that the boot order was fixed (possibly hardcoded) but given my experience here, I'm wondering how true that actually is.

Is there any way to change the boot order?  How can I restore it to factory settings?
It may be possible to re-enable the eMMC after you have both disabled it, and booted to an alternate source, like MicroSD card.
I've used similar instructions for my x86/x64 Media server's MicroSD card. Here is what I have;

Un-TESTED!!!! Use at your own risk. This is from the default Debian, but may
work on others.

While powered off, switch eMMC to disabled state. Then power on. If the user
is not fast enough with the switch to enabled state, the OS image on the SD card
won't see the eMMC. Thus, it may be needed to un-bind and re-bind the eMMC driver.
Note, it is still REQUIRED to enable the eMMC via the hardware switch. These
instruction below, MAY allow the OS to find it after boot.

The first 2 outputs may show nothing, which could happen if OS thinks the eMMC
does not exist. The 3rd command checks and sees if it's possible to unbind and bind.
Lines 4 & 5 are the real work. Though again, line 4 may not do anything if the device
is already un-bound.

# blockdev --getsize64 /dev/mmcblk1

# readlink /sys/block/mmcblk1

# ls /sys/bus/platform/drivers/sdhci-arasan
bind fe330000.sdhci uevent unbind

# echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/unbind
# echo fe330000.sdhci >/sys/bus/platform/drivers/sdhci-arasan/bind
Arwen Evenstar
Princess of Rivendale

Possibly Related Threads…
Thread Author Replies Views Last Post
  PineBook led got red/green (intermittent), then... Ice-O-Star 1 102 10-14-2021, 05:50 PM
Last Post: belfastraven
  PineBook Pro revision 2.2: Wishlist for the hardware issue fixes dsimic 105 29,934 10-10-2021, 06:25 AM
Last Post: slyecho
  Pinebook pro Hardware failure: how should I diagnose it? alxndr.psclt 5 507 09-08-2021, 09:03 PM
Last Post: KC9UDX
  PineBook Pro dead ottahe 2 464 08-23-2021, 04:47 PM
Last Post: KC9UDX
  pinebook pro trackpad randomly stops working chewie 5 1,613 08-10-2021, 04:33 PM
Last Post: chewie
  Pinebook Pro/Pinetab replacement as400 11 1,901 07-30-2021, 04:40 AM
Last Post: as400
  Touchpad notchy on new 2021 pinebook pro Neilcob 21 5,077 07-28-2021, 09:14 AM
Last Post: dsimic
Question PINEBOOK Pro USB-C Docking Deck issues pawzy 2 788 07-18-2021, 09:15 AM
Last Post: bluekeys
  Fix your Pinebook Pro speaker connection KC9UDX 12 3,678 07-08-2021, 02:10 AM
Last Post: KC9UDX
  Pinebook Pro Critique KABA 0 424 07-06-2021, 12:45 PM
Last Post: KABA

Forum Jump:

Users browsing this thread: 1 Guest(s)