uname -r in the terminal to make sure you’re running the correct kernel!
In my case 7.0.10-1-arch was being used rather than what I thought: 7.0.10-1-cachyos
In my case using systemd-boot I just had to change the default in the systemd-boot menu on startup
Does anyone know why this may have happened? In my /boot/loader/loader.conf I have
the line default linux-cachyos but this didn’t seem to work properly. I also tried bootctl set-default "" which didnt fix the issue before setting default in the actual boot menu
You don’t set the default kernel in the /boot/loader/loader.conf
You set it in /boot/loader/entries/cachyos.conf (replace cachyos with whatever else to your liking)
Then you set the default to cachyos.conf in /boot/loader/loader.conf
See here for more:
PS. perhaps you could change the title of the topic to something like “How to set the default kernel using systemd-boot” which seems to be more like the issue you are having.
After some experimenting, I found that any non-existing default foo entry specified causes systemd-boot to fall back to, for me, 7.0.10-1-arch which corresponds to entry linux.conf
My /boot/loader/loader.conf had the line default linux-cachyos which does not exist as an entry. Only linux-cachyos.conf, linux.conf existed. I had not changed this before today so I wonder what set it to this?
If this is the case for other users, then they may also be unknowingly running a different kernel than they expected.
I did recently remove cachy-lts using the CachyOS Kernel Manager - I will try adding and removing some kernels to see whether it causes the issue