But now I’m dealing with the exact same problem all over again and I could really use some guidance again. I have both linux and linux-lts kernels installed. It used to work that when I changed my loader.conf I could have the latest/newest kernel selected. Now that seems to not work anymore with the release of kernel 7.0.2. Right now I have one linux-lts kernel and now I have two linux kernels, the new 7.0 and still on my system the old 6.19 EOL kernel. I had thought with my current setup and configs, I could also boot into the latest kernel, but even with 7.0 installed, it still defaults to selecting the 6.19 kernel. I thought old kernels got deleted or cleaned up or something, but now I have 3 kernels and ideally I’m really only going to want to use one.
What can I do so that I can boot into the latest kernel like before?
scott@endeavourOS:~$ sudo ls /efi/loader/entries/
a718c5c3b60c42aa9332ecb00ebf37f6-6.18.25-1-lts.conf
a718c5c3b60c42aa9332ecb00ebf37f6-6.18.25-1-lts-fallback.conf
a718c5c3b60c42aa9332ecb00ebf37f6-6.19.14-arch1-1.conf
a718c5c3b60c42aa9332ecb00ebf37f6-6.19.14-arch1-1-fallback.conf
a718c5c3b60c42aa9332ecb00ebf37f6-7.0.2-arch1-1.conf
a718c5c3b60c42aa9332ecb00ebf37f6-7.0.2-arch1-1-fallback.conf
I just want two kernels installed, not this mess. Ideally I’d like everything automated if I could keep all this hands off so to speak. Appreciate any help as this issue has been a reoccurring problem.
Nope, never used a snapshot or rollback, this system was freshly installed like a month ago.
I had originally pressed “D” during boot during the kernel selection process when I was using 6.19. and that allowed me to auto select 6.19 on boot. I don’t know if selecting the “D” option for default I think like “protected” the 6.19 kernel or prevented it from being removed, but I am unsure. I cleared the “D” key setting and used the approach you suggested in my last post and that did seem to work.
But now it’s defaulting to the 6.18-lts kernel instead of the 7.0 (or even the 6.19 which is also a higher kernel) kernel which is what I want, and I feel like I have more kernels than need be installed at the current moment. If there’s any additional info needed, feel free to ask.
This has happened a few times already this month. I think I’ve had to remove an older kernel and old conf files like 3 separate times already in the last month. Never had to manually do that stuff before. Maybe there’s like a kernel hook that’s not working or missing maybe. I feel like I’m an enigma right now huh
Hmm…it looks like it removed it. I wonder if there was an error. Next time the kernel updates, scroll back to this part before closing the terminal and see if there is anything interesting around the part where it says : :: kernel-install removing kernel
Yeah I always check the terminal output during yay updates, but haven’t seen anything noticeable there during kernel updates, but I can double check the next time. It’s just so strange if it is indeed removed, it still shows all 3 kernels during systemds bootloader. I don’t know why my system is being so strange. Even if I uninstalled the lts kernel, I feel like I’d probably still have this issue with kernel updates.
so if I don’t have the 6.19 kernel anymore, but I still see 6.19 systemd boot entries when I boot, I guess I just have stale entry files that I assume are not getting autoremoved when they should be is my guess. It’s good to know it’s not a show stopper, but strange that my old kernel boot entries never seem to get deleted. Well the 6.18-lts kernel old boot entries get autoremoved, but for whatever reason the 6.19 and now 7.0 kernel updates, don’t seem to remove either older efi entries for the kernel and the fallback kernel. I guess I can must manually remove them for now and see what happens next update.
scott@endeavourOS:~$ sudo ls /efi/a718c5c3b60c42aa9332ecb00ebf37f6/
[sudo] password for scott:
6.18.25-1-lts 6.19.14-arch1-1 7.0.3-arch1-1
Just got the latest 7.0.3 update, saw I still have 6.19 as shown above so I deleted that, just forgot about it until now.
/var/log/pacman.log: looks normal to me. I did reinstall both kernels in an attempt to “fix” the hooks or something, but it seems to have maybe resolved itself. I haven’t rebooted just yet, but I think when I do it’ll be on the latest.
