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
esv_ is now known as esv
tg has joined #fedora-riscv
tg has quit [Quit: tg]
_whitelogger has joined #fedora-riscv
<davidlt[m]> Does anyone know how to boot Lichee Pi 4A ?
<davidlt[m]> I think there is T-HEAD SDK (OE/Yocto) stuff, but is that the only thing?
jcajka has joined #fedora-riscv
fuwei has quit [Ping timeout: 256 seconds]
fuwei has joined #fedora-riscv
<dtometzki> It is an image pre installed and you can boot it
<dtometzki> With fastboot you can update the image to an newer one
<davidlt[m]> Where do they those images?
<davidlt[m]> Have you done any benchmarking or this board?
<dtometzki> No at the moment
<dtometzki> You can find the link to the images on wiki.sipped.cm
<dtometzki> Sipeed
<dtometzki> On the images there is no openssh server perinatales
<dtometzki> Preinstalled
<davidlt[m]> Oh, that's annoying.
<davidlt[m]> Someone has a script for custom Fedora 38: https://github.com/chainsx/fedora-riscv-builder
<davidlt[m]> He actually has them available for download too: https://github.com/chainsx/fedora-riscv-builder/releases/tag/20230515-1705
<davidlt[m]> dtometzki: could you try that image once you have some free time?
<davidlt[m]> v6.3.7 kernel was tagged.
<sxa[m]> > Have you done any benchmarking or [Lichee4A]?
<sxa[m]> @davidit I've done a little bot of testing with the board. It built openjdk abour 30% faster than the VF2, but the build for Node.js was about the same duration so YMMV
<sxa[m]> davidlt: and yep I've got the doc from you thanks - will be able to look at it next week :-)
<davidlt[m]> cool
<davidlt[m]> I am surprised that TH1520 is that "slow".
<sxa[m]> I was expecting a bit better too - we'll see if others see the same on other tests I guess
<davidlt[m]> I am still waiting for non-Beta boards.
<davidlt[m]> sxa: btw, my script picked up and rebuild Nodejs 18 and 20.
<davidlt[m]> Those are already in.
<sxa[m]> I'll also point out that the lichee I tested on was pretty much as it came with the stock debian and I haven't attempted any real updates
<sxa[m]> Just enough to get the build bits in place
<davidlt[m]> I would love to see that Fedora image + maybe binutils build.
<davidlt[m]> 30% is a lot, but not that impressive.
<davidlt[m]> It will probably improve after T-HEAD stuff lands in the glibc (if ever).
<davidlt[m]> I just asked way too many questions about MilkV stuff today. They have similar cores (C920 vs C910).
zsun has joined #fedora-riscv
<Entei[m]> davidlt: The max number of cores assignable is being shown as 8. Kernel 6.x onwards I should be able to assign more cores with smp to RISCV machines
<Entei[m]> On my OE image I am able to assign as many cores as I like, that's using kernel 6.2 built with the default kernel config. Is Fedora using a different defconfig for qemu or something?
<davidlt[m]> No, Fedora is capable of using up to 32 cores.
<Entei[m]> Then why does my Qemu complain virt can only use 8 CPUs...?
<davidlt[m]> Is it QEMU that complains?
<davidlt[m]> What QEMU version is it?
<davidlt[m]> I think only the last ~2 QEMU versions allow going above 8 vCPUs.
<Entei[m]> I just left my office...All I remember is some error saying machine virt can use Max 8 CPUs.
<Entei[m]> I am using Fedora 38 as host, so probably qemu 7.2
<davidlt[m]> That should be quite new QEMU.
<Entei[m]> Yeah
<davidlt[m]> So, the default Linux with non-legacy SBI version will default to 64-cores.
<davidlt[m]> Max it can is 512.
<davidlt[m]> U-Boot can only do 32-cores.
<davidlt[m]> OpenSBI will scale up to ~120 cores IIRC.
<davidlt[m]> So we are limited to what U-Boot is able to do, and thus 32-cores in QEMU.
<Entei[m]> Using the same qemu (Fedora 37 though) I am running my OE image with more cores no problem
<davidlt[m]> Just double check what reports that core limited, is it QEMU or not.
<davidlt[m]> Each case it will looks differently.
<davidlt[m]> E.g. if the limit is in U-boot the you would see a bunch of kernel messages that it failed to bring core #XYZ online.
<Entei[m]> davidlt[m]: No it didn't even boot. I reckon the issue was with QEMU
<Entei[m]> I'll can confirm by tomorrow only though
<Entei[m]> Those servers are inaccessible from outside internet
<dtometzki> <davidlt[m]> "dtometzki: could you try that..." <- Hello davidt, iw ill try it this weekend
<davidlt[m]> Entei: I have booted 20 core QEMU instance:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/82bba72f5dcabea93c0f1173aea5b8637aec3ece>)
<davidlt[m]> Ops, -smp 20
<davidlt[m]> But with 21+ I don't get output beyond U-Boot SPL.
<davidlt[m]> So U-Boot proper or OpenSBI probably has an issue.
<davidlt[m]> It used to work all the way up to 32-cores the last time I checked.
jcajka has quit [Quit: Leaving]
<davidlt[m]> FYI to terminate QEMU if it hangs: Ctrl + A X
zsun has quit [Quit: Leaving.]
tg has joined #fedora-riscv
tg has quit [Quit: tg]
tg has joined #fedora-riscv
tg has quit [Quit: tg]
fuwei has quit [Ping timeout: 256 seconds]
fuwei has joined #fedora-riscv
tg has joined #fedora-riscv
tg has quit [Quit: tg]