dgilmore changed the topic of #fedora-riscv to: Fedora on RISC-V https://fedoraproject.org/wiki/Architectures/RISC-V || Logs: https://libera.irclog.whitequark.org/fedora-riscv || Alt Arch discussions are welcome in #fedora-alt-arches
jednorozec has quit [Read error: Connection reset by peer]
jednorozec has joined #fedora-riscv
somlo_ has joined #fedora-riscv
kalev has quit [Ping timeout: 248 seconds]
kalev has joined #fedora-riscv
somlo has quit [Ping timeout: 248 seconds]
davidlt has joined #fedora-riscv
<davidlt> javierm, what is the best way to reach out to grub2 team? IRC? Matrix? email? private email?
<davidlt> I don't think there is a IRC / Matrix channel.
<davidlt> Ah, I will ping pjones and nfrayer over email.
jcajka has joined #fedora-riscv
zsun has joined #fedora-riscv
<javierm> davidlt: yeah, better to ping them over email or file a BZ
masami has joined #fedora-riscv
masami has quit [Quit: Leaving]
cyberpear has joined #fedora-riscv
zsun has quit [Quit: Leaving.]
zsun has joined #fedora-riscv
<dgilmore> davidlt: with crypto disabled it boots off of mmc, network does not work. but it is progress
<davidlt> dgilmore, network should work with v6.6 IIRC
cyberpear has quit [Quit: Connection closed for inactivity]
<davidlt> Don't know, I don't plan to start testing until RC1 (or RC2) depending what happens.
<davidlt> dgilmore, other good news is that I might need to attempt "a quick switch to UEFI bootflow" in Fedora 40 as I playing with Pungi composes
<dgilmore> davidlt: cool, if you have questions please ask
<dgilmore> I am trying to figure out what the -22 is
<davidlt> dgilmore, we still might hit some issues without GRUB2.12
<davidlt> dgilmore, I would like to pull in the latest GRUB2 RC and gnu-efi 3.0.17 + some backports.
<davidlt> But I don't want to touch them as there are tons of patches (in any distro).
<dgilmore> grub is tricky that way
<davidlt> I think for GRUB2 we have ~350 patches. There is no way I am touching that.
<dgilmore> I do not blame you
<dgilmore> i noticed my linux-next build created a vmlinux.efi
<davidlt> I think my plan is to move to EFI ZBOOT IIRC.
<davidlt> So RISCV doesn't have self uncompressing kernel. So far that was the task for the bootloader to do.
<davidlt> With ZBOOT (aarch64 already switched) it can have a generic self extracting kernel, but it will depends on EFI.
<davidlt> I could quickly nuke EXTLINUX in our disk images, kernel, etc. but there will be some issues we would need to solve before we would be able to boot again.
<dgilmore> It would be nice to have the same boot path
<davidlt> Oh yeah, and we know it works. We just need to get all the bits in Fedora.
<davidlt> systemd-boot would be easier than using GRUB2.
<davidlt> I was planning to use Fedora 40/Rawhide to test early kernels to avoid more mistakes, but I might use it for redoing bootflow
<davidlt> but I might need it anyway to for Pungi composes, as I am building bootable ISOs
zsun has quit [Quit: Leaving.]
<davidlt> ok, next problem, I forgot that for riscv64 we don't have a shim.
<davidlt> or we can spend time on building a shim
<davidlt> someone already attempted to port it, but needs updating
<davidlt> and new lorax is building with adjusted templates
jcajka has quit [Quit: Leaving]
somlo_ has quit [Remote host closed the connection]
somlo has joined #fedora-riscv
davidlt has quit [Ping timeout: 246 seconds]
esv has quit [Remote host closed the connection]
esv has joined #fedora-riscv
esv has quit [Ping timeout: 245 seconds]