12-18-2024, 05:13 AM
(12-17-2024, 04:59 PM)ethical_haquer Wrote: I tried using it with U-Boot, but U-Boot couldn't find the pmOS installation I have on the eMMC.
...
rk2aw includes its own flavour of uboot (as does Tow-Boot): I had problems with pmOS and rk2aw as pmOS wasn't happy to have its boot directory in the same partition as /. So if I did a "default" pmOS where /boot had its own partition, and didn't bother with extlinux stuff, rk2aw happily picked up the EFI hooks and it loaded fine. However it kept randomly rebooting so I went with arch.
(12-17-2024, 04:59 PM)ethical_haquer Wrote: ...I am perplexed as to why you would want to? Both Tow-Boot & rk2aw are "facilitators" between the board startup firmware and (their own flavour of) uboot. As such they flash LEDs, make disks available over USB and give some options which is your OS of choice for the day. I prefer rk2aw as it (better) supports multiple OSs on each disk.
I'm just surprised that no one has tried using Tow-Boot with rk2aw before. It should be possible, seeing as Tow-Boot is based off U-Boot.
- ROCKPro64 v2.1 2GB, 16Gb eMMC for rootfs, SX8200Pro 512GB NVMe for /home, HDMI video & sound, Bluetooth keyboard & mouse. Arch (6.12 kernel, Openbox desktop) for general purpose daily PC.
- PinePhone Pro Explorer Edition, daily driver, rk2aw & U-boot on SPI, Arch/SXMO on eMMC
- PinePhone BraveHeart now v1.2b 3/32Gb, Tow-boot with pmOS/SXMO on eMMC
