I was able to get a orange pi 5 plus with a 256gb emmc for a good price. Not to happy with the various non orange-pi blessed distro's because i am not using images from google drive. So i was wondering if i can get gentoo on it with the following. https://github.com/edk2-porting/edk2-rk ... me-ov-file Is something that seems to provide a less complicated boot system.
Is it possible to use this and the generic arm64/aarch64 efi minimal install cd with openrc? Rather than the method listed in the this wiki https://wiki.gentoo.org/wiki/Orange_Pi_PC/Quick_Start
Because no matter what image i try other than manjaro linux nothing really behaves too much.
I think it is doable. I am currently in progress do EFI+GRUB setup for my Raspberry PI 4B. I got it boot into grub now. I am trying to come up a grub.cfg to my own need.
Currently there is annoying slowness at the time when loading initrd as well at grub loading kernel image. it can take up to 2-3 minutes. it seems to caused by calling EFI service for loading file into memory both grub and efistub is doing the same. I am not sure if this is due to EDK2 setting or device tree default that use a slower SD standard. Once boot into linux the SD I/O work as expected.
The benefit of having EFI boot service is you can use most current day ISO for installation. most distros nowadays livecd use efistub kernel on the CD so it should just work.
I don't know if RK3588's EDK2 suffer same as my RPI4's EDK2 that is you cannot make configuration changes in OS for EFI. you need to use the EDK2's command line to create boot entries so it can be persist. in another work the "efibootmgr' command created boot entries will be lost after reboot.
I would recommend start with serial console setup with second computer, this way you will be able to pickup any minor detail you need to attend in order to load the EFI.fd. Also suggest use SD card first to get configuration setting correct before flash it to firmware device.
pingtoo wrote:I think it is doable. I am currently in progress do EFI+GRUB setup for my Raspberry PI 4B. I got it boot into grub now. I am trying to come up a grub.cfg to my own need.
Currently there is annoying slowness at the time when loading initrd as well at grub loading kernel image. it can take up to 2-3 minutes. it seems to caused by calling EFI service for loading file into memory both grub and efistub is doing the same. I am not sure if this is due to EDK2 setting or device tree default that use a slower SD standard. Once boot into linux the SD I/O work as expected.
The benefit of having EFI boot service is you can use most current day ISO for installation. most distros nowadays livecd use efistub kernel on the CD so it should just work.
I don't know if RK3588's EDK2 suffer same as my RPI4's EDK2 that is you cannot make configuration changes in OS for EFI. you need to use the EDK2's command line to create boot entries so it can be persist. in another work the "efibootmgr' command created boot entries will be lost after reboot.
I would recommend start with serial console setup with second computer, this way you will be able to pickup any minor detail you need to attend in order to load the EFI.fd. Also suggest use SD card first to get configuration setting correct before flash it to firmware device.
Thank you, i'll take that into account when i get time to mess with it again.
Update:
I stuck that on a small sd card, and then stuck the aarch64 minimal iso with openrc on a usb drive. And it boots! Though keep in mind that you will have to use this tip on their site as the kernel is 6.12 not 6.15.
In Mainline mode with generic Linux kernels older than 6.15, the HDMI output will not be usable. To use the UEFI-initialized display instead, go to Device Manager->Rockchip Platform Configuration->ACPI / Device Tree and enable Force UEFI GOP Display. Note that GPU acceleration cannot work in this mode.