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
cmuellner has quit [Quit: Leaving]
bkeys1 has joined #fedora-riscv
bkeys has quit [Ping timeout: 248 seconds]
bkeys1 is now known as bkeys
bkeys has quit [Remote host closed the connection]
jimwilson_ has quit [Ping timeout: 244 seconds]
jimwilson has joined #fedora-riscv
jimwilson has quit [Ping timeout: 276 seconds]
jimwilson has joined #fedora-riscv
zsun has joined #fedora-riscv
zsun has quit [Quit: Leaving.]
zsun has joined #fedora-riscv
davidlt has joined #fedora-riscv
<davidlt[m]> Okay, let's wait for a new kernel.
<davidlt[m]> GRUB2.12 should be released this October
davidlt has quit [Ping timeout: 255 seconds]
zsun has quit [Quit: Leaving.]
davidlt has joined #fedora-riscv
davidlt has quit [Ping timeout: 244 seconds]
davidlt has joined #fedora-riscv
<rwmjones> davidlt[m]: is there a way to adjust the clock speed on unmatched, similar to
<rwmjones> echo 1500000000 > /sys/devices/platform/soc/10000000.prci/rate
<rwmjones> on unleashed?
<rwmjones> (that file doesn't exist, and i don't see anything similar)
<davidlt[m]> no, you would need to recompile u-boot
<davidlt[m]> well technically it doesn't exist on Unleashed too :) it was never upstreamed :)
<rwmjones> ah ok, was wondering if reducing clock speed would help with stability here
<rwmjones> I've rebooted both boards at the moment
<davidlt[m]> it might be just a kernel bug, let's wait for v5.18.4
<rwmjones> sure, np
<davidlt[m]> you could compile and run stress-ng for a few hours, or a day
<rwmjones> yeah I will try stress-ng
<davidlt[m]> we need to update that f33 to have a newer stuff
<rwmjones> stressor is running on nujive
<davidlt[m]> I typically run all the stressors with some -t seconds value
<davidlt[m]> but we need an updated stable f33 to start building without too many issues
<rwmjones> stress-ng matrix been running on nujive for 90 mins or so, and everything totes fine, so looks like kernel issue
* rwmjones is going to run nbdkit builds in a loop (on nujive)
davidlt has quit [Ping timeout: 240 seconds]
droidrage has quit [Ping timeout: 240 seconds]