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
omac777_2022 has quit [Read error: Connection reset by peer]
omac777_2022 has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
omac777_2022 has quit [Quit: Leaving]
unlord has quit [*.net *.split]
esv has quit [*.net *.split]
King_InuYasha has quit [*.net *.split]
King_In8 has joined #fedora-riscv
unlord has joined #fedora-riscv
esv has joined #fedora-riscv
davidlt_ has joined #fedora-riscv
davidlt__ has joined #fedora-riscv
davidlt_ has quit [Ping timeout: 248 seconds]
davidlt__ has quit [Ping timeout: 252 seconds]
jcajka has joined #fedora-riscv
zbyszek[m] has joined #fedora-riscv
davide has joined #fedora-riscv
Eighth_Doctor has quit [Quit: Bridge terminating on SIGTERM]
nirik[m] has quit [Quit: Bridge terminating on SIGTERM]
mhroncok has quit [Quit: Bridge terminating on SIGTERM]
davide has quit [Quit: Bridge terminating on SIGTERM]
defolos has quit [Quit: Bridge terminating on SIGTERM]
ol has quit [Quit: Bridge terminating on SIGTERM]
davidlt[m] has quit [Quit: Bridge terminating on SIGTERM]
zbyszek[m] has quit [Quit: Bridge terminating on SIGTERM]
cwt[m] has quit [Quit: Bridge terminating on SIGTERM]
dtometzki has quit [Quit: Bridge terminating on SIGTERM]
cmagina has quit [Quit: Bridge terminating on SIGTERM]
mbohun[m] has quit [Quit: Bridge terminating on SIGTERM]
jim-wilson[m] has quit [Quit: Bridge terminating on SIGTERM]
ahs3[m] has quit [Quit: Bridge terminating on SIGTERM]
Kevinsadminaccou has quit [Quit: Bridge terminating on SIGTERM]
gotmax23 has quit [Quit: Bridge terminating on SIGTERM]
defolos has joined #fedora-riscv
Kevinsadminaccou has joined #fedora-riscv
jim-wilson[m] has joined #fedora-riscv
nirik[m] has joined #fedora-riscv
mhroncok has joined #fedora-riscv
zbyszek[m] has joined #fedora-riscv
ahs3[m] has joined #fedora-riscv
cmagina has joined #fedora-riscv
gotmax23 has joined #fedora-riscv
davide has joined #fedora-riscv
ol has joined #fedora-riscv
davidlt[m] has joined #fedora-riscv
cwt[m] has joined #fedora-riscv
dtometzki has joined #fedora-riscv
Eighth_Doctor has joined #fedora-riscv
mbohun[m] has joined #fedora-riscv
ol has quit [Ping timeout: 246 seconds]
mhroncok has quit [Ping timeout: 252 seconds]
ahs3[m] has quit [Ping timeout: 246 seconds]
mbohun[m] has quit [Ping timeout: 260 seconds]
cwt[m] has quit [Ping timeout: 252 seconds]
zbyszek[m] has quit [Ping timeout: 252 seconds]
dtometzki has quit [Ping timeout: 252 seconds]
davidlt[m] has quit [Ping timeout: 252 seconds]
jim-wilson[m] has quit [Ping timeout: 252 seconds]
davide has quit [Ping timeout: 265 seconds]
Kevinsadminaccou has quit [Ping timeout: 246 seconds]
cmagina has quit [Ping timeout: 264 seconds]
defolos has quit [Ping timeout: 252 seconds]
gotmax23 has quit [Ping timeout: 252 seconds]
Eighth_Doctor has quit [Ping timeout: 252 seconds]
nirik[m] has quit [Ping timeout: 260 seconds]
ahs3[m] has joined #fedora-riscv
mhroncok has joined #fedora-riscv
Kevinsadminaccou has joined #fedora-riscv
gotmax23 has joined #fedora-riscv
cmagina has joined #fedora-riscv
defolos has joined #fedora-riscv
ol has joined #fedora-riscv
mbohun[m] has joined #fedora-riscv
cwt[m] has joined #fedora-riscv
jim-wilson[m] has joined #fedora-riscv
masami has joined #fedora-riscv
davide has joined #fedora-riscv
dtometzki has joined #fedora-riscv
omac777_2022 has joined #fedora-riscv
nirik[m] has joined #fedora-riscv
Eighth_Doctor has joined #fedora-riscv
davidlt[m] has joined #fedora-riscv
zbyszek[m] has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
masami has quit [Quit: Leaving]
omac777_2022 has quit [Ping timeout: 252 seconds]
zsun has joined #fedora-riscv
dgilmore has quit [Ping timeout: 252 seconds]
dgilmore has joined #fedora-riscv
omac777_2022 has joined #fedora-riscv
iooi has quit [Read error: Connection reset by peer]
iooi has joined #fedora-riscv
davidlt has joined #fedora-riscv
davidlt_ has joined #fedora-riscv
zsun has quit [Quit: Leaving.]
davidlt has quit [Ping timeout: 260 seconds]
dtometzki is now known as dti
<davidlt[m]> 115+ hours on GCC 13 build!
<davidlt[m]> Hopefully we have it by the time Monday arrives.
davidlt_ has quit [Ping timeout: 248 seconds]
jcajka has quit [Quit: Leaving]
dti is now known as dtometzki
esv_ has joined #fedora-riscv
esv has quit [Ping timeout: 248 seconds]
esv_ has quit [Quit: Leaving]
<dtometzki> why so long ?
<sharkcz> the hw simply too slow, but I believe 80+ % of time is spend in running the test-suite, I assume it's run also on risc-v
<omac777_2022> it's taking that long because davidlt wants to run it on just one box from what I understood. It's a feature and not a bug.
<omac777_2022> If there is the will and the patience to setup distcc to build whatever riscv64, I would volunteer my little visionfive 2 node to it. Just say the word.
<omac777_2022> I've got a running 256GB nvme on it as well and you can chroot /mnt into it. It doesn't boot off of it yet, but everything else is running ok on the chroot. I haven't tried the gui desktop because I have no uart/usb thingamabob, but it's coming in the mail. LOL
<dtometzki> ok i dont know that test suite runs too
<dtometzki> because my build on VF2 runs faster without test-suite
<dtometzki> but i have to say it is gcc12 and not gcc13 but i will try
davidlt_ has joined #fedora-riscv
davidlt_ has quit [Ping timeout: 252 seconds]
<davidlt[m]> omac777_2022: there is no PCIe driver in U-Boot to boot from NVMe.
<davidlt[m]> PCIe driver for Linux or/and U-Boot will come quite late in the upstreaming process.
<omac777_2022> Thank you davidlt. I'm in no hurry. The chroot /mnt is adequate for the time being.
<omac777_2022> Using my not root is easy as well. su -l davidm and I'm myself again.
<davidlt[m]> The current estimate is that 6.4 kernel might boot on the board. We will know more towards 6.3-rc5/6. That's typically cut off time for new stuff towards linux-next.
<davidlt[m]> A couple of smaller drivers made it into 6.3, but that's it. Nothing major.
<omac777_2022> davidlt, I'm running debian on this vf2. Is there any way, I can chroot into a fedora rootfs on this board? Is there any way I can chroot into a silverblue on this board? I know you weren't keen on this earlier. Perhaps not an image but some kind of rootfs that could help me get closer to that silverbluey goal line :)
<omac777_2022> debian has debootstrap, archlinux has pacstrap, what's the fedora equivalent?
<davidlt[m]> I noticed a couple of folks are attempting to build Silverblue, that would be cool! But I haven't jumped into the discussions (I was attending conferences).
<davidlt[m]> Oh yeah, DNF.
<davidlt[m]> Not documented, but let me check my notes.
<davidlt[m]> sudo dnf install qemu-user-static-riscv
<davidlt[m]> sudo dnf -y --skip-broken --releasever=33 --setopt=install_weak_deps=0 --forcearch=riscv64 --nogpgcheck --installroot=$PWD/tmp_rootfs --repofrompath="fedora-riscv,http://fedora.riscv.rocks/repos-dist/rawhide/latest/riscv64/" --repo=fedora-riscv install @core
<davidlt[m]> You just need to adjust things, but this allows to create rootfs on x86_64 host system.
<davidlt[m]> You can use that for podman, docker, hacking new disk images, etc.
<davidlt[m]> "dnf-install" works here, but thing like "dnf-builddep" doesn't work properly and --forcearch= is ignored here.
<omac777_2022> does the dnf need the qemu package you installed beforehand?
<davidlt[m]> Yes, otherwise post-install scripts will be failing.
<davidlt[m]> You need to run riscv64 binaries that might be executed during installation.
<omac777_2022> crazy question, if there was dnf tool available on the debian sid repo, could I use that?
<davidlt[m]> I don't see why it shouldn't work.
<omac777_2022> I mean straight on the vf2 sid debian, I install dnf and then run your command to point to some directory on that /mnt nvme that has already been chrooted :)
<omac777_2022> Ok I'll go see.
<davidlt[m]> Well, in that case the command is easier, e.g. you don't need --forcearch=
<omac777_2022> root@vf2-sid:/# apt-cache search dnf
<omac777_2022> dnf-doc - Documentation for the DNF package manager (common documentation)
<omac777_2022> dnf - Dandified Yum package manager
<omac777_2022> dnf-data - Dandified Yum package manager (data files)
<omac777_2022> dnf-plugins-core - Core plugins for DNF, the Dandified Yum package manager
<omac777_2022> LOL I'm giving it a go.
<davidlt[m]> If you create a repo file in that case command is much shorter too. It's basically all about changing installroot.
<davidlt[m]> Installing @core group of packages will give you something very minimal.
<davidlt[m]> You could also build kernel RPM and later KS file to generate a new disk image.
<davidlt[m]> Know the kernel StarFive devs are providing is an old one, thus existing defconfing will probably not work.
<davidlt[m]> So adjusting the defconfig is the most annoying part here as Fedora build system will run config checks.
<davidlt[m]> So if you say CONFIG_FOO=y and kernel generates CONFIG_FOO=m it will fail, and you need to adjust.
<omac777_2022> apt-get install dnf
<omac777_2022> Depends: python3-libdnf (>= 0.48.0-1~) but it is not installable
<omac777_2022> python3-dnf : Depends: python3-hawkey (>= 0.48.0-1~) but it is not installable
<omac777_2022> The following packages have unmet dependencies:
<davidlt[m]> Seems dependencies are broken.
<omac777_2022> There are no earlier available packages here.
<omac777_2022> Is dnf all python?
<davidlt[m]> No, it depends on libraries written in C.
<davidlt[m]> Probably Debian repo doesn't have all packages in the right versions.
<davidlt[m]> Finally! This got open sourced: https://github.com/starfive-tech/Tools/tree/master/spl_tool
<omac777_2022> pip install hawkeye
<omac777_2022> Yes for hawkey, but nope for python3-libdnf. Debian install will still fail to install dnf.
<omac777_2022> I'll try to install docker and see if I can run fedora riscv64 there lol
<omac777_2022> I can install podman on the vf2.
<omac777_2022> I got podman.
<davidlt[m]> nirik: do you know which task in Koji is used to assemble Silverblue image?
<davidlt[m]> Some folks are trying to build Silverblue for riscv64. I am trying to understand how this image is being cooked in Koji (or outside). It doesn't have KS file in traditional location, and it's not part of traditional Kojji tasks.
<nirik[m]> pungi does that in runroot koji tasks...
* nirik[m] is kind of busy dealing with branching fallout so can't give more info right now.
<davidlt[m]> That's fine. Enjoy handling those fires :)
omac777_2022 has quit [Quit: Leaving]
hiredman[m] has joined #fedora-riscv
esv_ has joined #fedora-riscv
esv_ is now known as esv