jaeger changed the topic of #crux-arm to: CRUX-ARM 3.6 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-6 | Logs: https://libera.irclog.whitequark.org/crux-arm/
frinnst has quit [Ping timeout: 256 seconds]
<jaeger> Unrelated, I bought a little GPS module for setting up an NTP source for fun
frinnst has joined #crux-arm
<beerman> ah! nicwe
<beerman> never type before coffee.. ☕️
<beerman> i think kodi not working is really a kodi problem, not a wayland problem, I mean that could happen on any platform when mesa updates internal stuff, right? I was more talking about the general feel of it, which I think is just very fast
<jaeger> Sure, in theory it could... but right now it's only doing that on wayland :)
<jaeger> I don't know where the problem lies, just commenting on the experience so far
<jaeger> Mostly it seems good
<beerman> I guess it's mesa changing internals, it just happens. And: not just qayland, also gbm :p though there the screen turns green real quick 😂
guido_rokepo has joined #crux-arm
genpaku has quit [Read error: Connection reset by peer]
genpaku has joined #crux-arm
frinnst has quit [Ping timeout: 252 seconds]
frinnst has joined #crux-arm
guido_rokepo has quit [Quit: guido_rokepo]
<beerman> qt6-webengine heavily swaps again 😄
<jaeger> I have to disable half my cores to build it :P
<jaeger> Well, maybe not on a pi... would just take a lot of RAM/swap, I guess
<beerman> we will see how it goes, right now, it does 6 or 7 jobs over distcc
<beerman> it will probably die at some point
<beerman> how many cores is half your cores again? 😄 because neither my (ancient) notebook as well as my desktop and the build hosts I have used so far (ryzen3200g and that crazy proliant with 16 cores) have no problems with neither qt5- nor qt6-webengine
<jaeger> 16 on one host, 8 on the other
<beerman> 16 is half, nice 😄
* beerman cries in old hardware
<jaeger> meson/ninja uses too many threads for the available RAM in those cases
<jaeger> heh
<jaeger> That one is a ThreadRipper 2950x for reference
<beerman> ah, right, i forgot for a second that you got one of those
<jaeger> Maybe if I put a lot more RAM in it it would be easier but I just disable the threads for that build and reenable them after
<jaeger> A threadripper is not a cost-effective buy anymore, CPUs have increased core/thread count so much even since then
<jaeger> At the time I bought it it made sense... now desktop CPUs have the same or more
<beerman> true, its one thing i am happy about holding off for so long
<jaeger> If I had known how the desktop CPU market would go at the time, I would not have bought it :)
<jaeger> But at this point I just keep it because selling it would not be worth the money right now
<beerman> i can imagine
<jaeger> Well, can't get my $12 USB GPS device to do anything at all, so not sure
<jaeger> It gets very hot, too
<jaeger> Might try to hook it up via gpio instead