So title is pretty self explanatory. I’m still a noob with Linux on a lot of fronts and tried to troubleshoot the problem but to no avail. Whenever I’m playing a game fullscreen the game freezes after a while. Journalctl yields practically nothing. Now I know that this used to be and still I suppose is an issue with the compositor. I am on an X11 session due to Wayland lacking yet options to control the fans better for Nvidia and also I’m currently with the proprietary drivers since well… the others didnt work all that great. Just to clarify I use the nvidia and nvidia-utils packages since the dkms spat out a few errors back a few months when I was using it with Hyprland on Wayland. Mind you Wayland didn’t have any issues except the issue with no fan support meaning a lot of those games would struggle to work well and the graphics card just overheats.
Here’s summary from neofetch on my system’s details and do ask me for anything that may be helpful since I can’t think of anything at the top of my head at the moment that could help:
This command (detailed here) carries a bit more useful information about drivers used, BIOS revisions, CPU temps, space available, etc. You can share the link the command generates here, so we can review it.
inxi -Fxxc0z | eos-sendlog
I know you mentioned journalctl had little to offer, but if you wouldn’t mind sharing it, it may still point to something. After a freeze, immediately reboot and run this to retrieve the last 50 entries from the last session log:
journalctl -b -1 | tail -n 50 | eos-sendlog
If using the standard kernel (which it appears you are), that should be ok. Using the dkms version however, would give you flexibility to easily try other kernels, such as the LTS, without having to install kernel specific Nvidia drivers each time. You might try installing the dkms versions again, and let us know if that produces errors?
When installing the dkms version, you must have the kernel headers installed for any installed kernel, first. Eg, for the standard kernel:
Hey so first of all thanks for not berating me for not providing enough info because I just saw how vaguely I’ve expressed what the problem is. Now to the situation at hand. Here’s the results from the first log file: https://0x0.st/XxTd.txt
Second log file is this: https://0x0.st/XxTR.txt
Just to clarify I currently am using the LTS Kernel since I found out that the main Arch linux kernel is currently experiencing those same issues.
A workaround but not complete to this is to turn off compositing for games by adding kwin rules for each of them but KDE Plasma seems to lack the option to switch it off for all fullscreen apps which is something I’d need in those cases. Either way I’ve removed the DKMS drivers since before they caused several other issues and I’ve tried the Zen kernel - not much of a difference.
Problems seem to be happening lot less often on LTS with proprietary Nvidia drivers but it’s still there and it’s really confusing.
For the headers I do have both of them - on LTS and Mainline Arch kernels.
Once again thanks for the help and mostly patience. I’ll keep those commands as well for future use!
The log you shared looks to be from a clean shutdown. I’m not sure if perhaps I misunderstood what you meant by “constant freezes”. The command I shared retrieves the journal log from the prior session (assuming it had to be reset due to total freeze).
If it’s a hard lock, where you need to force reset the system, after the reset run this immediately to get the previous session logs:
journalctl -b -1 | tail -n 50 | eos-sendlog
If the freeze is momentary and you still have system access, to get the current session logs: