lanefu changed the topic of #armbian-rockchip to: Armbian - Linux for ARM development boards | Rockchip SoC | www.armbian.com | This channel is relayed to the equivalent Discord channel | this channel is logged
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC> [Discord] <dsx724> @lanefu whats the benefit of having edk2?
<DC-IRC> [Discord] <lanefu> In my insane edge case where I've been playing with rpardini's tinkerbell fork for bare metal provisioning--mainline uboot wasn't able to successfully bootstrap from snp.efi to then load iPXE and go from there. tinkerbell doesnt' support pxelinux and needs to do pxeboot via efi.
<DC-IRC> [Discord] <lanefu> edk2 was able to bootstrap and then use vendor kernel for provision stage..... and then afterwards could boot mainline with dtb embedded image lol.
<DC-IRC> [Discord] <lanefu> In my insane edge case where I've been playing with rpardini's tinkerbell fork for bare metal provisioning--mainline uboot wasn't able to successfully bootstrap from snp.efi to then load iPXE and go from there. tinkerbell doesnt' support pxelinux and needs to do pxeboot via efi.
<DC-IRC> [Discord] <lanefu> edk2 was able to tftp snp.efi to bootstrap iPXE and then use vendor kernel for provision stage..... and then afterwards could boot mainline with dtb embedded image lol.
<DC-IRC> [Discord] <dsx724> Ahh gotcha. Thanks!
<DC-IRC> [Discord] <lanefu> meanwhile.. mainline uboot + mainline kernel boots to a pingable rk3588 instance in 22 seconds (and thats with the overhead of dhcp)
<DC-IRC> [Discord] <lanefu> I should try this on the Alta's uboot and see how it handles
chris64 has quit [Ping timeout: 256 seconds]
<DC-IRC> [Discord] <Tonymac32> is this because of the size limitations needing you to trim out some support stuff?
<DC-IRC> [Discord] <lanefu> could be a product of not knowing what I'm doing with my uboot configuration, who knows where the true deficiencies lay
<DC-IRC> [Discord] <Tonymac32> and I don't know the stuff you're trying to do.
<DC-IRC> [Discord] <lanefu> that was this nonsense from a few weeks ago
<DC-IRC> [Discord] <lanefu> Expected behavior is
<DC-IRC> [Discord] <lanefu> ```
<DC-IRC> [Discord] <lanefu> Booting /smp.efi
<DC-IRC> [Discord] <lanefu> MAGIC BEGINS
<DC-IRC> [Discord] <lanefu> ```
<DC-IRC> [Discord] <lanefu> Expected behavior is
<DC-IRC> [Discord] <lanefu> ```
<DC-IRC> [Discord] <lanefu> Booting /snp.efi
<DC-IRC> [Discord] <lanefu> MAGIC BEGINS
<DC-IRC> [Discord] <lanefu> ```
<DC-IRC> [Discord] <lanefu> and I think that `## Application failed, r = 2` is not a uboot message, but either from snp.efi itself, or just some "generic efi error"
<DC-IRC> [Discord] <Tonymac32> so snp.efi --> iPXE --> stuff
<DC-IRC> [Discord] <lanefu> yep
<DC-IRC> [Discord] <Tonymac32> this is so you can keep updated iPXE vailable? I see a lot of "embedding iPXE" stuff
<DC-IRC> [Discord] <lanefu> _if_ i was gonna go back and troubleshoot in earnest. i'd probably do it with the netboot.xyz stack rather than tinkerbell just for simplicity
<DC-IRC> [Discord] <lanefu> yeah in my use case iPXE needs to be external because tinkerbell has its own flavor of it.
<DC-IRC> [Discord] <lanefu> the uboot example of embedding iPXE really is just to take advantage of some of iPXEs features ex: iscsi
<DC-IRC> [Discord] <shivansps> yeah i want to PXE/iPXE boot from an RK3566 OPI3B and failing badly at it
<DC-IRC> [Discord] <shivansps> yeah i want to PXE/iPXE boot from an RK3566 OPI3B and no luck so far
<DC-IRC> [Discord] <lanefu> are you using kwiboo uboot?
<DC-IRC> [Discord] <Tonymac32> kwi-boot
<DC-IRC> [Discord] <Tonymac32> they've never expereinced IBM