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
key2 has quit [*.net *.split]
montjoie has quit [Ping timeout: 258 seconds]
montjoie has joined #armbian-rockchip
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian-rockchip
<DC-IRC> <lanefu> in an offline Discord
<DC-IRC> <mmie4jbcu> Its funny that you brought this up today. Yesterday, I spent the whole day in getting Fedora to boot on my RK3566 tv box. You need the Fedora 39 beta image. Once you have dd'ed it onto the sdcard or usb flash drive, you need to go into the efi>boot directory on the esp partition. Rename or remove the fbaa64.efi file. Then copy grubaa64.efi from efi>fedora to efi>boot directory.
<DC-IRC> <mmie4jbcu> Its funny that you brought this up. Yesterday, I spent the whole day in getting Fedora to boot on my RK3566 tv box. You need any of the Fedora 39 beta image. Once you have dd'ed it onto the sdcard or usb flash drive, you need to go into the efi>boot directory on the esp partition. Rename or remove the fbaa64.efi file. Then copy grubaa64.efi from efi>fedora to efi>boot directory.
<DC-IRC> <mmie4jbcu> Its funny that you brought this up. Yesterday, I spent the whole day in getting Fedora to boot on my RK3566 tv box. You need any of the Fedora 39 beta images. Once you have dd'ed it onto the sdcard or usb flash drive, you need to go into the efi>boot directory on the esp partition. Rename or remove the fbaa64.efi file. Then copy grubaa64.efi from efi>fedora to efi>boot directory. <clipped message>
<DC-IRC> <mmie4jbcu> Now try booting up.
<DC-IRC> <mmie4jbcu> Before that, I flashed the uefi image from here https://github.com/jaredmcneill/quartz64_uefi to make by box be able to boot uefi images
<DC-IRC> <mmie4jbcu> Its funny that you brought this up. Yesterday, I spent the whole day in getting Fedora to boot on my RK3566 tv box. tl;dr - You need any of the Fedora 39 beta images. Once you have dd'ed it onto the sdcard or usb flash drive, you need to go into the efi>boot directory on the esp partition. Rename or remove the fbaa64.efi file. Then copy grubaa64.efi from efi>fedora to efi>boot di <clipped message>
<DC-IRC> <mmie4jbcu> rectory. Now try booting up.
<DC-IRC> <mmie4jbcu> Its funny that you brought this up. Yesterday, I spent the whole day in getting Fedora to boot on my RK3566 tv box. You need any of the Fedora 39 beta images. Once you have dd'ed it onto the sdcard or usb flash drive, you need to go into the efi>boot directory on the esp partition. Rename or remove the fbaa64.efi file. Then copy grubaa64.efi from efi>fedora to efi>boot directory. <clipped message>
<DC-IRC> <mmie4jbcu> Now try booting up.
yang2 has quit [Ping timeout: 245 seconds]
yang2 has joined #armbian-rockchip
<DC-IRC> <kwiboo> You should also be able to boot fedora (and other generic distro images) with u-boot efi boot on rk356x, see https://wiki.pine64.org/wiki/Quartz64_UEFI_with_U-Boot for example and other quirks