For those who use Wayland and autostart, don't forget to edit
/etc/sddm.conf.d/kde_settings.conf
from KDE5: Session=plasmawayland
to Plasma6: Session=plasma
to confirm the exact name, check what is available under /usr/share/wayland-sessions/
if you're stuck, try pacman -Q | grep -i kde and pacman -Q | grep -i plasma and remove everything related, then fresh install plasma-meta or plasma group and it should work
to confirm the exact name, check what is available under /usr/share/wayland-sessions/
if you're stuck, try pacman -Q | grep -i kde and pacman -Q | grep -i plasma and remove everything related + remove orphans , then fresh install plasma-meta or plasma group and it should work
Happened once around two years ago, s botched update from mainstream or something like that. Made me learn systemd boot which is simple and never EVER use grub again
AMD is the gold standard for general user PCs in the last 5+ years. Intel simply cannot compete at the same energy expenditure/performance. At the same/close price/performance, Intel either burn a small thermonuclear power plant to deliver comparable performance, or simply is worse compared to similar Ryzens
Ryzens are like aliens compared to what AMD used to be before them
So I'd go with them
As for the GPU, if you want to use Linux forget Nvidia
Yeah, it's advertised as 160hz and even amdgpu_top (which uses xrandr or something like it) says 159.96hz is the first preferred mode, the second being 100hz
I had this problem before with a Nvidia card which reset to 144hz after an update and I could never enable it again. However it's a mystery as to why it boots up at 160hz in systemd-boot console, and goes back to 144hz when entering KDE or turning the display off
I finally switched to AMD after 3 years in Linux, and man I didn't even know I was suffering until I booted with AMD and didn't have to take care of several env variables and separate modules for hw acc
That'd be over 1TB with zram on