Using ayufan's buster minimal image, I noticed uboot seems to ignore the boot partition and instead looks at the boot folder in the root partition. So if I update extlinux to load additional modules and look at sata for the root partition, it will ignore the changes because the system writes them to the boot partition instead of where uboot actually looks for it.
I have my root moved to an hard drive on sata side and want to use the SD card only for boot, but I seem to be missunderstanding something about how the boot process works.
(11-14-2019, 02:13 AM)Mentaluproar Wrote: Using ayufan's buster minimal image, I noticed uboot seems to ignore the boot partition and instead looks at the boot folder in the root partition. So if I update extlinux to load additional modules and look at sata for the root partition, it will ignore the changes because the system writes them to the boot partition instead of where uboot actually looks for it.
I have my root moved to an hard drive on sata side and want to use the SD card only for boot, but I seem to be missunderstanding something about how the boot process works.
Yup, when you are running rootfs somewhere other than the SDcard, and using the SDcard to boot, all updates are made to /boot/. You need to duplicate them to the SDcard, I have a little script syncsd to do it for me
Code:
sudo mount /dev/mmcblk0p7 /mnt/
sudo rsync -ax --delete /boot/ /mnt/boot/
cat /mnt/boot/extlinux/extlinux.conf
* ROCKPro64 v2.1 2GB, 16Gb eMMC for rootfs, SX8200Pro 512GB NVMe for /home, HDMI video & sound, Bluetooth keyboard & mouse. Started Bionic minimal - now "groovy", Openbox desktop for general purpose daily PC.
* PinePhone BraveHeart now v1.2b 3/32Gb daily driver with Mobian on encrypted SDcard, Arch/f2fs/Phosh on eMMC
* PinePhone v1.2a 2G/16Gb that needs USB board replaced