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
_whitelogger_ has joined #fedora-riscv
xen0n has joined #fedora-riscv
esv has quit [Remote host closed the connection]
fuwei has joined #fedora-riscv
fuwei has quit [Client Quit]
davidlt has joined #fedora-riscv
fuwei has joined #fedora-riscv
fuwei has quit [Quit: Konversation terminated!]
fuwei has joined #fedora-riscv
fuwei has quit [Ping timeout: 260 seconds]
fuwei has joined #fedora-riscv
fuwei has quit [Quit: Konversation terminated!]
fuwei has joined #fedora-riscv
fuwei has quit [Remote host closed the connection]
<rwmjones> does anyone know what's going on with the dtb / u-boot here ...
<rwmjones> specifically why doesn't it boot option 1?
<rwmjones> there is no filed called "qemu-riscv.dtb" anywhere on the entire filesystem
<rwmjones> & I assumed that qemu provides the dtb itself through memory pointed to by a0(?)
<rwmjones> so no file should be needed?
<rwmjones> hmm maybe "Bad Linux RISCV Image magic!" is not referring to the dtb but to the kernel ...
<rwmjones> yeah that must be it, this doesn't look right ...
<rwmjones> /boot/vmlinuz-6.2.16-300.0.riscv64.fc38.riscv64: gzip compressed data, max compression, from Unix, original size modulo 2^32 36054016
<rwmjones> /boot/vmlinuz-6.5.4-300.0.riscv64.fc39.riscv64: PE32+ executable (EFI application) RISC-V 64-bit (stripped to external PDB), for MS Windows, 2 sections
<rwmjones> ^^ davidlt: is the kernel being built correctly in Fedora 39?
<rwmjones> hmm maybe we're supposed to only boot with EFI now?
<davidlt> rwmjones, F39 kernels are EFI ZBOOT, UEFI firmware is required
<davidlt> This looks like QEMU and technically this should work with EDK2 (and U-boot, but I didn't get to test it)
<rwmjones> yes it's a qemu vm
<rwmjones> one I've been upgrading since F37
<davidlt> I haven't finish this work on bootflow thus F39 (and above) kernels will not work in existing setup
<rwmjones> ok thanks
<davidlt> and yes, I am already thinking about building a new kernel in F38 (because of this)
<rwmjones> yeah so the background to this is I'm having a problem with KVM and I wanted to try a newer kernel to see if that would fix it
<rwmjones> but actually I'll try newer qemu first (since the crash is in qemu for some reason)
<rwmjones> by "KVM" I mean KVM emulated by qemu-system-riscv64 on x86-64 host
<davidlt> Yeah, which surprisingly is still called KVM :)
<davidlt> I am getting busy (more and more) with Fedora 38 -> Fedora 40 mass rebuild, thus no ETA on a new kernel or finish UEFI bootflow
<davidlt> and Fedora 39 is basically F38 + minimal changes (incl. kernel)
<davidlt> I really planned to use F39 and F40 for different experiments, but that was taking too long
* davidlt wants that 16-core P670..
<rwmjones> yup!
<davidlt> Someone posted dates for RTL freeze and tapeout (not really confirmed)
<davidlt> It does seem that this chip is not even at RTL freeze
<davidlt> Thus I am not sure I trust that 9-10 months statement
fuwei has joined #fedora-riscv
fuwei has quit [Quit: Konversation terminated!]
zsun has joined #fedora-riscv
esv has joined #fedora-riscv
zsun has quit [Quit: Leaving.]
fuwei has joined #fedora-riscv
kalev has quit [Ping timeout: 260 seconds]
kalev has joined #fedora-riscv
kalev has quit [Ping timeout: 245 seconds]
davidlt has quit [Ping timeout: 252 seconds]
kalev has joined #fedora-riscv
davidlt has joined #fedora-riscv
davidlt has quit [Ping timeout: 240 seconds]
tibbs has quit [Quit: ZNC 1.8.2 - https://znc.in]
tibbs has joined #fedora-riscv