At what feels utterly random times, my system begins to stutter, sometimes coming onto a full freeze, but there are no errors or warnings when it’s coming.
It happens both with x11 and Wayland, playing games that are heavy on the CPU and sometimes just being idle while I do something away from the computer.
It has happened with the Catchy-kernel, the regular arch one, the regular LTS and the regular zen, to name a few.
Just in case it could be that, I have flashed the BIOS to it’s most recent version; the problem persists.
I am genuinely at the end of my rope with this.
If you have any suggestions or can help me trouble shoot it, I’d be really thankful.
Let me know if there are any logs that could be useful and if possible where to find them.
Only thing I’ve ever found to do is to start replacing parts, well and making sure everything is property seated.
Of course then, you may end up with a 2nd pc
Unfortunately, I have a similar problem, with occasional horizontal stripes appearing. Sometimes more, sometimes less. Let’s hope for the best and wait until a professional takes care of the problem. But it’s a real shame when you look at the hardware.
journalctl -f on a terminal should display all logs in realtime and catch the error in question when it happens again and begin the investigation there i suppose
The most plausible causes, it could be disk IO operations (I doubt it, plenty of ram)
It could be the cable to your monitor
It could be the system switching from dedicated video card to integrated video card software / driver conflict, a condition like that can be triggered in idle mode, after specified time when the computer enters power saving mode (instead of power save balance performance, or sleep mode.
At least issue this command as root:
fstrim -va
To make sure the disks are trimmed.
Make sure to disable any experimental uncertain flags if in your web browser (if you did that)
Also there is a package you could find to control when and why the system must use which video card. I don’t remember the name but it is easy to find. Good luck!
❯ fstrim -va
fstrim: /var/tmp: FITRIM ioctl fehlgeschlagen: Die Operation ist nicht erlaubt
~
❯
I had read that rocm can cause errors in connection with internal and external GPU, but I cannot find the appropriate switch in the bios to deactivate the integrated GPU. There are also big differences between the official Asrock bios description and the pictures, compared to my bios. Still so many issues, but one after the other.
I will now look for the tool to disable the internal GPU …
After a good 6 month test phase with Suse, Kubuntu, Manjaro, MX Linux, Debian and Arch, each of which I have always destroyed, the possibilities for customization to my wishes are best covered here, and I have not yet managed to destroy the system . I’m still playing around with the local LLMs, but I’ve already learned more about them and been able to set up tools for them here than under the other distributions combined. A big thank you to you guys, also to the developers in the background for the great experience with CachyOS. And also thanks to the community and all the other people who contribute to this project and help it grow.
PS: I have just tried to document the flickering via screenshot, but nothing can be seen on the picture, although the error persists.
I had my integrated GPU disabled before because it was giving me issues with Steam under PikaOS, but I had this very same slowdown/ freeze issues there, so I don’t think it’s that
It might be an issue with some fancy setting on the BIOS that doesn’t play well with Linux.
You can find the boot.logs manually under root/var/log
there you will also find older ones called boot.log1, boot.log2 etc, look at the creation date to find older ones.
Dieser Befehl listet alle Logfiles im System auf
This bashcommand shows all *.log’s of the System
sudo find /var/log /var/lib /home -type f -name "*.log" -exec du -b {} + | tee logfiles.txt | awk '{print $2 ": " $1 " Bytes"}; {sum += $1} END {print "\nGesamtgröße aller Log-Dateien:", sum, "Bytes"}'
Erklärung des Befehls:
Deutsch:
sudo: Gibt die notwendigen Rechte frei, um alle Systembereiche zu durchsuchen.
find: Sucht nach Dateien im gesamten Dateisystem.
/var/log: Durchsucht das Systemverzeichnis für Logs.
/var/lib: Durchsucht das Verzeichnis für Anwendungsdaten.
/home: Durchsucht das Benutzerverzeichnis.
-type f: Filtert nur Dateien aus (keine Verzeichnisse).
-name "*.log": Sucht nach Dateien mit der Endung .log.
-exec du -b {} +: Führt den Befehl du -b für jede gefundene Log-Datei aus, um deren Größe in Bytes zu bestimmen.
tee logfiles.txt: Speichert die Ergebnisse in einer Datei namens logfiles.txt, während sie gleichzeitig auf dem Bildschirm angezeigt werden.
awk '{print $2 ": " $1 " Bytes"}': Formatiert die Ausgabe, um den Dateinamen und dessen Größe in lesbarer Form anzuzeigen.
{sum += $1} END {print "\nGesamtgröße aller Log-Dateien:", sum, "Bytes"}': Zählt die Gesamtgröße aller Log-Dateien und gibt sie am Ende aus.
Zusätzliche Hinweise:
Der Befehl benötigt sudo, da er Systemverzeichnisse durchsucht.
Die Ausgabe wird sowohl auf dem Bildschirm angezeigt als auch in die Datei logfiles.txt gespeichert.
Mit du -b werden die Dateigrößen in Bytes angezeigt. Wenn Sie die Größe in KB, MB oder GB anzeigen möchten, können Sie du -h verwenden.
Englisch:
sudo: Grants the necessary permissions to search all system areas.
find: Searches for files in the entire filesystem.
/var/log: Searches the system directory for logs.
/var/lib: Searches the directory for application data.
/home: Searches the user directory.
-type f: Filters only files (no directories).
-name "*.log": Looks for files with the .log extension.
-exec du -b {} +: Executes the du -b command for each found log file to determine its size in bytes.
tee logfiles.txt: Saves the results to a file named logfiles.txt, while also displaying them on the screen.
awk '{print $2 ": " $1 " Bytes"}': Formats the output to show the filename and its size in a readable format.
{sum += $1} END {print "\nTotal size of all log files:", sum, "Bytes"}': Sums up the total size of all log files and displays it at the end.
Additional notes:
The command requires sudo as it searches system directories.
The output is both displayed on the screen and saved in the logfiles.txt file.
With du -b the file sizes are displayed in bytes. If you want to display the size in KB, MB or GB, you can use du -h.
I just got one of those stutters, though only for a moment, and checking journalctl -f got me this little error:
Mar 11 22:08:30 cachyos-x8664 kwin_wayland[3015]: kwin_libinput: Libinput: event4 - USB Optical Mouse: client bug: event processing lagging behind by 24ms, your system is too slow
Could it be that the culprit of these problems is my bloody mouse of all things?
