I’ll continue trying to find a solution for this issue.
For now I will leave this query open until a solution is found.
If anyone else has a suggestion to expedite the resolution please post here. Thanks.
Ok, I’ve made some progress on this issue. The initrd line in the runtime grub menu is different to the grub.cfg file generated from the update grub process.
The line generated correctly in the file /boot/grub/grub.cfg is
initrd /boot/intel-code.img /boot/initramfs-6.12-x86_64.img
but the runtime grub boot menu is showing as
initrd /boot/intel-code.img
so missing the second part of the instruction.
When I edit the running grub menu file and add the missing instruction the system boots ok.
Is this a grub issue ?
This may be a very dumb question:
what is the runtime grub boot menu?
1 Like
Sorry my terminology may not be correct here. The menu that appears at boot time.
There should be names of kernels, Extended Options, UEFI Firmware Settings and possibly Memory Test, not this.
Or do you mean it appears when you hit “E” for edit the command line?
Yes edit the command line using “E”.
Basically the line appears to be different to the /boot/grub/grub.cfg file
I’d check the contents of each file in /etc/mkinitcpio.d/
ls /etc/mkinitcpio.d/
cat /etc/mkinitcpio.d/*.preset
probably better one at a time
for linux612:
cat /etc/mkinitcpio.d/linux612.preset
And examine the output of:
sudo mkinitcpio -P
and
sudo update-grub
Don’t know whether you already did that for yourself - it isn’t here to see.
These things happen when there is more than one Grub installation (for example, a second Linux system on the same computer).
One attempted installation is enough to cause the problem. 
Simply put, your grub searches for the config-file and finds one, but it’s not the one that got updated when the system was updated.
3 Likes
Hi there, yes I checked all of those and they appear to be fine.
The grub.cfg generated by the system appears to be correct but is not being displayed correctly when booting. I just noticed that the version of the grub menu displayed when booting is 2.02 whereas the current version used in Manjaro is 2.2.14rc1-3. It looks as if the main grub menu is being loaded from a different partition whereas the Manjaro grub menu created is from partition sda3. I’m wondering if there is a conflict caused by the older version not supporting microcode options.
It’s likely rather like @andreas85 just said.
2 Likes
Yes I think that’s what’s going on here.
If that is the case, It’s not a conflict.
It’s simply the wrong boot loader used.
There is a script/program which would likely fix that
when run from within the current Manjaro system:
install-grub
It’s needs to be installed first, it’s not present by default.
Or perhaps change the boot order from UEFI settings …
3 Likes
I changed the boot order. It’s now reading the correct grub menu.
2 Likes
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.