>CachyOS
>Put system to sleep with KoboldCPP still open
>Mouse and keyboard take a very long time to stop glowing
>Not the first time for either of the above, but they didn't cause a problem before
>Wake up computer in the morning
>Incredibly slow, takes several minutes for each small part of the UI to load
>Finally logged in, 2 out of 3 monitors won't render anything
>Last one has all my windows on it for some reason
>System Monitor is on top, glitching out with other windows showing through it semi-randomly, and nothing from the system monitor itself ever being display
>Firefox (being used as a UI for KoboldCPP) has crashed
>Try closing it, closing the console with Kobold, closing the system monitor
>Extremely slow to do anything, even to move the mouse
>All those windows now gone, everything is still half-frozen
>Fuck it, reboot
>Takes a minute
>UI gone, console appears
>[FAILED] Failed to display Plymouth shutdown page
>System is struggling to even shutdown
>After a few minutes, it's finally ready to shutdown
>Except the very last thing it's trying to do is still attempting to close KoboldCPP several times
>Start PC back up
>Still slightly slow to start, but not as bad as before, probably because of improper shutdown diagnostics or something
>Open System Monitor
<llen back to software rendering because hardware acceleration is not available, and visual glitches may appear. Please check your
>The text is cut off, but I can double click to highlight and copy it all
<System Monitor has fallen back to software rendering because hardware acceleration is not available, and visual glitches may appear. Please check your graphics drivers.
>The graphs for system usage aren't rendering, but it still says I'm using some amounts of GPU now and then
>Restarting System Monitor does not return it to normal
Kobold along with everything else was pushing me to 16GiB out of 32GiB of memory. It wasn't generating anything when I put the system to sleep. Does CachyOS just shit itself if you put it to sleep with moderate to heavy RAM usage? Is my GPU fucked now somehow? I'm going to try rebooting again real quick to see if that fixes it.