Tap Shift or Esc during boot to make sure to get a GRUB menu.
FRom there Select your preferred kernel.
(This may be under ‘advanced’)
After you are sure you are booted into your preferred kernel
( uname -a )
Then you may proceed to delete the old kernels.
It should have done it automatically, but could you type sudo update-grub and ensure the additional kernels are well listed in the newly generated grub config?
After that, it should be available at reboot in Grub advanced menu.
Do you have a file /boot/grub/grub.cfg.new and if so what is its content?
The .new is created whenever you have a typo in any of the grub files used to create grub.cfg. I once forgot a closing } in 40_custom. It then showed error as last line which did not help much, but it may show error line. Also could be in /etc/default/grub, if line not correct.
My system was up to date @omano - and more updates were available this morning 2021-10-16
I installed those also.
@Falav I did a sudo update-grub Then restart my computer. No new kernels listed in the GRUB menu.
I paste the output below, and noticed the following line:
/usr/bin/grub-probe: error: unknown filesystem.
When I installed manjaro I chose the F2FS (Flash-Friendly File System)
Maybe F2FS is somehow related.
> sudo update-grub
>
> Generating grub configuration file ...
> Found linux image: /boot/vmlinuz-5.14-x86_64
> Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.14-x86_64.img
> /usr/bin/grub-probe: error: unknown filesystem.
> Found initrd fallback image: /boot/initramfs-5.14-x86_64-fallback.img
> Found linux image: /boot/vmlinuz-5.13-x86_64
> Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.13-x86_64.img
> Found initrd fallback image: /boot/initramfs-5.13-x86_64-fallback.img
> Found linux image: /boot/vmlinuz-5.10-x86_64
> Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
> Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
> Warning: os-prober will be executed to detect other bootable partitions.
> Its output will be used to detect bootable binaries on them and create new boot entries.
> Adding boot menu entry for UEFI Firmware Settings ...
Though I am reluctant to post it’s content here in a public forum. Contains numbers and stuff, perhaps related to disk encryption. Should I remove/censor anything before posting? I am unsure and slightly paranoid.
I selected the F2FS (Flash-Friendly File System) when I installed Manjaro. Thought it would be a good choice for my Samsung SSD - Not using the BTRFS file system at this time.
Will check to see if my system is up to date. When I get another chance tomorrow.
Update - I sort of solved my Linux Kernel problem. The lazy way though, by reinstalling Manjaro. This time I chose the EXT4 file system, instead of F2FS
Not sure what caused original issue. I suspect the absence of grub-f2fs package is somehow responsible. It’s available in the AUR, but is out-of-date. Be careful because I really don’t know.