You are probably using systemd-boot and not grub if you don’t have grub-mkconfig.
If so, the EOS wiki describes how to change the default booted entry for systemd-boot by editing /efi/loader/loader.conf. You can’t move it to the top, but you have it highlighted by default.
Nothing stupid about your question
I am not sure whether I am using systemd boot of grub. Now, when I refer to grub I mean the “menu” (that’s an overstatement) that is displayed in white monochrome against a black background and that lists Endeavour OS, Endeavour something else, and now also LTS kernel 6.6.72.
If my use of “grub” is wrong in this context, what is the right designation?
When I want to open ``, nano shows “directory does not exist”.
I checked in the file explorer, and indeed the loader directory does not appear in the /etc directory, therefore the loader.conf file does not exist.
I have no idea what I did because I did not do any delete or cut actions.
Is it possible to manually add (with root privileges, of course) a loader directory, then with e.g. xed create a file with those 4 original lines I reported? i.e.
default 4acb3ccd578940f4b1d99d71b59ee048*
timeout 5
console-mode auto
reboot-for-bitlocker 1
Er… Seems we are assuming that because you are using EndeavourOS, you are also using Systemd-Boot. So, let’s find out for sure. Post the output of the following, please:
pacman -Q | grep -A 0 -E "(grub|systemd|dracut|mkinitcpio|linux|headers)"
From the wiki I have learned that the default boot entry can be set with this command sudo bootctl set-default ID, whereby the ID can be established with sudo ls /efi/loader/entries.
Since I want the LTS kernel to be at the top, this the procedure I will implement.
@dalto I implemented that and it works – “of course”, you will say
Thanks a lot for your help, and all those extremely useful, invaluable pieces you have written.