Yes, and is there anything else? You are telling me there is something wrong with my system to cause my default kernel to change when kernels are updated. Trying to track that down before I make a bug report.
OK, I think my old brain has finally grasped what’s going on. When you use default @saved, it does not specific by LTS or non-LTS alone. It’s also using the full kernel version. For example, on my system right now my default kernel is linux-cachyos, as shown here:
$ sudo bootctl list | awk -F [":"] '/title/ {print $2}'
EndeavourOS (Budgie Base) (6.12.49-2-cachyos-lts)
EndeavourOS (Budgie Base) (6.17.0-3-cachyos)
EndeavourOS (Cinnamon Base) (6.12.49-2-cachyos-lts)
EndeavourOS (Cinnamon Base) (6.17.0-3-cachyos)
EndeavourOS (Cosmic Base) (6.12.49-2-cachyos-lts)
EndeavourOS (Cosmic Base) (6.17.0-3-cachyos)
EndeavourOS (KDE Plasma Base) (6.12.49-2-cachyos-lts)
EndeavourOS (KDE Plasma Base) (6.17.0-3-cachyos)
EndeavourOS (KDE Plasma Testing) (6.17.0-3-cachyos)
EndeavourOS (KDE Plasma Testing) (6.17.0-rc7-2-cachyos-rc)
EndeavourOS (Xfce Host) (6.12.49-2-cachyos-lts)
EndeavourOS (Xfce Host) (6.17.0-3-cachyos) (default) (selected)
Now, say I upgrade today and the 6.17.0-4-cachyos kernel is available. When I update, the old entry is removed, the new one installed. This means that the default entry no longer exists. That’s why your not getting the default that you’re expecting.
Alright, now we are getting somewhere!
So I am asking this before waddling my way over to duckduckgo, but is it possible to put wildcards in the default field? Or even regex? Trying to think of a way to automate this so I don’t have to change the default after every update.
Thinking something along the lines of *arch1-1. Can’t use *arch* because then would match on both the arch1-1 and arch1-1-fallback
Also, to revisit a fix that would most likely work in my case, how do you all suggest uninstalling the LTS kernel?
WARNING TO THOSE LOOKING FOR ANSWERS: do not just copy-past the following code into your term and press enter - you could screw up your install or worse!
I generally use pacman -Rsc linux-lts but I am unsure how safe it is (most likely very unsafe)
sudo pacman -Rns linux-lts linux-lts-headers
To Summarize:
Issue in this case could be traced to two very different causes:
- System booting into LTS Kernel after game was played on Non-LTS, possibly corrupting/causing issue with shaders.
- Interference caused by OpenRGB (plugins?) that prevented the game from rendering.
More investigation will have to be done. But for now the quick fixes:
- Remove the LTS kernel if you don’t need it. albersc2’s post on how to do that.
- Close OpenRGB when gaming.
If you look carefully at your original loader.conf, it contains a wildcard for the default entry (based on the machine ID). I believe that will grab the first entry in alphabetical order after getting the list from the wildcard.