Hi all, quick question regarding kernel switching. Currently kernel versions 4.19 and 5.4 seem to be installed, my system is running on version 4.19 and I want to switch to the newer 5.4 version.
Problem is I do not see the option on Grub - every boot selection available is for the 4.19 version (also under the Advanced options menu). How can I use the newer kernel? Tried the Manjaro Settings Manager, all the kernels are there and are listed as “Installed” but there is no option to switch. Also tried running “sudo update-grub”, but still no boot option with the 5.4 version.
The system is up to date, all packages updated to their latest versions, last updated today morning. Any help is appreciated, I thank you very much in advance for your time. Below some system information in case it’s useful. (On my computer I have 2 separate installations of Manjaro and one Windows 10 installation - the other Manjaro installation has not been used and/or updated for many months now).
$ uname -a
Linux manjaro 4.19.139-1-MANJARO #1 SMP Tue Aug 11 16:10:08 UTC 2020 x86_64 GNU/Linux
$ sudo update-grub
Generating grub configuration file …
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found Arch Linux (rolling) on /dev/nvme0n1p11
Found Manjaro Linux (20.1) on /dev/nvme0n1p9
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found Arch Linux (rolling) on /dev/nvme0n1p11
Found Manjaro Linux (20.1) on /dev/nvme0n1p9
Adding boot menu entry for UEFI Firmware Settings …
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
You are probably booting with the GRUB of the other Manjaro installation, or the one installed by Arch. Try reinstalling GRUB to the EFI system partition from within the Manjaro installation you’re using.
This was it indeed. I was booting with the GRUB of the other Manjaro installation. Never crossed my mind. Now it makes total sense if course - the second distro which I do not use anymore was installed after the one that I am using, therefore I was unknowingly booting with the GRUB of that installation.
Just one minor thing - I tried running the command as is and got an “unknown option: --no-fs-codes” error, I assume you meant “no-rs-codes” - if so maybe it would make sense to correct it so as to not confuse any future users.
In any case I ran the command without said option at all (couldn’t understand from the manual what exactly it does) but it seems to have done the trick, so hopefully it did not matter.
Again, thank you both for your effort and time.
P.S. If any of you has any idea why I might be getting duplicate boot entries in the GRUB menu now, would be grateful for any insight. I believe this somehow also has to do with having 2 separate Manjaro installations, and 2 boot partitions (the second Manjaro installation has its own dedicated boot partition). I’ve been seeing the duplicates for quite some time on the console output every time I would run “sudo update-grub”, though I never actually saw the boot options on the actual boot menu of course since I was seeing the boot menu of the other GRUB.
This is the output:
$ sudo update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found Arch Linux (rolling) on /dev/nvme0n1p11
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found Arch Linux (rolling) on /dev/nvme0n1p11
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
And this is my hard drive configuration:
/dev/nvme0n1p1 650 MB Boot partition for Manjaro installation 1 + Windows (EFI)
/dev/nvme0n1p2 128 MB Microsoft reserved
--> /dev/nvme0n1p3 97,2 GB Windows (NTFS)
/dev/nvme0n1p4 29,6 GB Linux swap
/dev/nvme0n1p5 669,6 GB Home directory (ext4)
/dev/nvme0n1p6 990 MB Windows recovery environment
/dev/nvme0n1p7 14,4 GB Windows recovery environment
/dev/nvme0n1p8 1,2 GB Windows recovery environment
--> /dev/nvme0n1p9 105,1 GB Manjaro installation 1 (main, in use) (ext4) **
/dev/nvme0n1p10 512 MB Boot partition for Manjaro installation 2 (EFI)
--> /dev/nvme0n1p11 34,6 GB Manjaro installation 2 (NOT in use) (ext4) **
Again I thank you very much in advance for any help.
Well spotted, friend! Yes, it was a typo, and I have corrected it now in my other post.
Well, when the option is omitted, GRUB writes Reed-Solomon error-correcting codes to the master boot record, but in combination with a UEFI boot, this may lead to spurious error messages. That’s why the option exists to omit the Reed-Solomon codes when writing GRUB to an EFI system partition.
Yes, this is because the os-prober module scans your drive for installed operating systems and then adds them all to the GRUB configuration. So your GRUB menu now has boot options for both Manjaro installations, and for each of the installed kernels in either installation.
Yes, it was a typo, and I have corrected it now in my other post. 
