<mbohun[m]>
(the pidgin installation that was my last action yesterday afternoon, the `ip -4 -o a` below that, those were my desperate cries for help from this morning, after i noticed on a diff box that the ssh connection to HiFive Unmatched is lost, and came to investigate)
esv_ is now known as esv
davidlt has joined #fedora-riscv
jcm__ has quit [*.net *.split]
pbrobinson has quit [*.net *.split]
drewfustini has quit [*.net *.split]
jbowen has quit [*.net *.split]
jbowen has joined #fedora-riscv
drewfustini has joined #fedora-riscv
jcm__ has joined #fedora-riscv
pbrobinson has joined #fedora-riscv
davidlt_ has joined #fedora-riscv
<davidlt[m]>
Morning
<davidlt[m]>
PINE64 Star64 will be available in November (aka next month) IIUC from their October update (their blog).
<davidlt[m]>
All machines had their capacity reduces from 2.0 -> 1.5. This is to avoid situation were two jobs land on your builders, and one of them is never built but highly expensive package (e.g. llvm14). This typically results in prolonged build time and sometimes to fails due to memory exhaustion.
jcajka has joined #fedora-riscv
<davidlt[m]>
mbohun: that would be something new. Well, desktop image isn't being actively tested these days. But in CLI environment I have never seen NetworkManager issues, and I move tons of data via these boards.
<mbohun[m]>
so far it happened only once; plus you are correct normally i boot into runlevel 3, and i have never seen any "weird" issues there, all these "weird problems" (except that riscv-user-cant-change-password) happen only while GNOME session is active.
<davidlt[m]>
Things will improve with time as there more RISC-V Linux users :)
<davidlt[m]>
Once VisionFive V2, Star64, HorseCreek shows up. More folks will join, more bug reports, which will lead (in time) to a higher quality software experience.
<davidlt[m]>
I would expect F37/F38 images already provide a better experience, but TBD.
<davidlt[m]>
I have been building as crazy non-stop for some weeks now.
<davidlt[m]>
Hmm... It looks like settings capacity 2.0 -> 1.5 did not yield expected result, but I will keep monitoring.
<davidlt[m]>
Two jobs continue to land even if both have combined weight well above 1.5 capacity of the host.
<davidlt[m]>
TL;DR I think nothing really changed, and manual baby sitting is still required.
<davidlt[m]>
I consumed close to 300G / day on Saturday (or was it Friday?).
<davidlt[m]>
I see a path towards ~500G / day of moved data. I might need to hook that 4TB SSD for cache sooner than later, I guess.