Unable to set Manjaro Grub as default

thats not working

Some UEFI firmwares require a bootable file at a known location
you can copy an already installed GRUB EFI executable to the default/fallback path

cp /boot/efi/EFI/Manjaro/grubx64.efi /boot/efi/EFI/BOOT/BOOTX64.EFI

Here’s one way to boot Manjaro from Ubuntu’s grub (since you have Ubuntu grub)

  1. Boot to Ubuntu, At Ubuntu terminal,
sudo touch /boot/grub/custom.cfg
  1. Open up this file, add entries below and save the file.

menuentry "Manjaro - multiboot " {
               insmod part_gpt
               insmod ext2
               search --no-floppy  --fs-uuid --set=root 2664046d-cb22-4b33-978b-bb2061effc53
               chainloader /boot/grub/x86_64-efi/core.efi
     }


menuentry "Manjaro - chainload " {
               insmod part_gpt
               insmod fat
               search --no-floppy  --fs-uuid --set=root 4BBD-3C9E
               chainloader /EFI/Manjaro/grubx64.efi
     }


menuentry "Manjaro - configfile "  {
    insmod part_gpt
    insmod ext2
    search --no-floppy  --fs-uuid --set=root 2664046d-cb22-4b33-978b-bb2061effc53
    configfile /boot/grub/grub.cfg
}

  1. Reboot.
    It should boot up to Ubuntu’s grub and at bottom of grub menu are these 3 additional entries.
    Configfile may not work if you are using Ubuntu’s shim (secureboot) but try out all, starting with chainload, multiboot and configfile.

ps" I’m still waiting for your computer make and model.
It may be tied up with Microsoft (and shim).

2 Likes

OP had said he had done…

Same thing. Only better.

This is a path and file created by Microsoft. Next Boot or Update by Microsoft can and will replace it because it is considered (rightfully) compromized. DO NOT TOUCH THESE FOLDERS!

No. It is not. It is the disk boot file for the device.
Nothing to do with microsoft.
The thing about your method, calvous, is that you are asking people to use Windows boot through Easybcd and then to Manjaro grub.

I’ll remember to ask you if anyone wants to do specifically that.

And you’re using Microsoft Surface Pro :smile:

As I said, I am still investigating. But this files and folders are no subject to be changed by commands other than efibootmgr or bcdedit. And I absolutely disadvice to use Easybcd. This is very confusing for uneducated users.
Modern (or NowADays) PCs and Laptops and Tablets like the Surface are infiltrated with Microsofts !11@#$44@#$. Therfore use Microsoft’s tools to kick itself. It’s just one command on the powershell and by the way the one to install rEFIind. Check this:

BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0005,0001,0000,0002
Boot0000* Internal Storage	FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(50670071-478f-4be7-ad13-8754f379c62f)SDD.
Boot0001* USB Storage	FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(50670071-478f-4be7-ad13-8754f379c62f)USB.
Boot0002* PXE Network	FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(50670071-478f-4be7-ad13-8754f379c62f)PXE.
Boot0003* SurfaceFrontPage	FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5)/FvFile(4042708a-0f2d-4823-ac60-0d77b3111889)VOL+.
Boot0005* Manjaro x64	HD(1,GPT,79e30bbe-bc06-43db-a1cb-98e69ff8dda1,0x800,0x82000)/File(\EFI\Manjaro\grubx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................

Last line done by ‘bcdedit’. Win10 won’t touch it.

And BTW: I bought that Surface Pro for the amazing screen (3:2). Where all others have the completely useless (when you want to get some work done) 16:9. I HATE THAT :face_with_symbols_over_mouth:

Exactly. Your system will use only GUID a881d567-6cb0-4eee-8435-2e72d33e45b5.
So you will have no choice.
Some Lenovo’s are like that, BTW.
The rest of us don’t need to follow, or use your method (unless they want to - suckers :grin:).

The matter of fact is @gohlip, every other request here is about the issue of Manjaro not booting after install. We have to come up with a solution. And we should tag this to the very top of all forums reading “Here is how to!”

I understand. But to reply to you properly, it will require a very long response.
But being the polite guy that I am :rofl:, I acknowledge your comment but defer any response.

Cheers.

Wow. All three of them worked! Thanks! The only drawback is that you have to select Manjaro in Ubuntu grub and then in the Manjaro grub, but I can live with that. It’s now time investigate how to set Manjaro as the first option in the Ubuntu grub.

P.S. My computer is a Toshiba P55B, and no, secure boot is disabled.

Good. At least you now can boot to Manjaro with less hassles.
And you and I now want to see if you can boot the way it should be (no hassles).
Now, to repeat and clarify, you had said in your first post that you had done

Yet, efibootmgr gets you.

You manjaro bootentry is there, but it is not in first in the bootorder despite having the commands done. It may be that your Toshiba P55B needs some tweaking at your bios-setup.

As anuj said,

See if there is any uefi bios-setup there that can make the ‘manjaro’ as first in bootorder.
You may have to explore any settings in ‘advanced’, ‘set admin’ (password’?) and then ‘boot’ sections. If you find and fix it, please report back here with detailed instructions, possibly with screen shots. And I will document it.
That will help others with a similar setup as yours.
If @anuj can add more points on this, that will be great.

Cheers.

ps: The following links on other computers may give some hints.

  1. Asus
  2. HP link 1
  3. HP link 2
  4. MSI
    Set boot to UEFI (DO NOT USE CSM)
    Set TPM to 2.0 with 1.x compatibility

New message. You said you did

sudo efibootmgr -o 0006,0000,0004
where you said 0006 is the manjaro bootentry

Can you try again with
efibootmgr
and see what is the manjaro bootentry?
Is it 0003 or 0006 or both?

Then do
sudo efibootmgr -o 0003,0006,0000,0004

Whichever applies. Put in 2 simultaneous (consecutive) manjaro entries if there are multiples.
Report back. Thanks. Then try bios-set-up if not successful.
When reboot, always provide new ‘efibootmgr’. (efibootmgr -v would be better)

So, from Manjaro I did

**$ efibootmgr -v

and got

BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0000,0005,0001,0002,0004,0003,0006,0007,0008
Boot0000* ubuntu	HD(1,GPT,0b92f5d9-9346-4725-9e99-65a55902654f,0x22,0x1007de)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0003* manjaro	HD(1,GPT,0b92f5d9-9346-4725-9e99-65a55902654f,0x22,0x1007de)/File(\EFI\manjaro\grubx64.efi)
Boot0004* Windows Boot Manager	HD(1,GPT,0b92f5d9-9346-4725-9e99-65a55902654f,0x22,0x1007de)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0005* UEFI: IP4 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0006* UEFI: IP6 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0007* UEFI: IP4 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0008* UEFI: IP6 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv6([::]:<->[::]:,0,0)..BO

Then:

**$ sudo efibootmgr -o 0003,0000,0004

and got

BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0003,0000,0004
Boot0000* ubuntu
Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller
Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller
Boot0003* manjaro
Boot0004* Windows Boot Manager
Boot0005* UEFI: IP4 Realtek PCIe GBE Family Controller
Boot0006* UEFI: IP6 Realtek PCIe GBE Family Controller
Boot0007* UEFI: IP4 Realtek PCIe GBE Family Controller
Boot0008* UEFI: IP6 Realtek PCIe GBE Family Controller

Then, checking again

**$ efibootmgr -v

I got

BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0003,0000,0004
Boot0000* ubuntu	HD(1,GPT,0b92f5d9-9346-4725-9e99-65a55902654f,0x22,0x1007de)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0003* manjaro	HD(1,GPT,0b92f5d9-9346-4725-9e99-65a55902654f,0x22,0x1007de)/File(\EFI\manjaro\grubx64.efi)
Boot0004* Windows Boot Manager	HD(1,GPT,0b92f5d9-9346-4725-9e99-65a55902654f,0x22,0x1007de)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0005* UEFI: IP4 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0006* UEFI: IP6 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0007* UEFI: IP4 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0008* UEFI: IP6 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv6([::]:<->[::]:,0,0)..BO

However, after rebooting, the output of that command is

BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0000,0005,0001,0002,0004,0003,0006,0007,0008
Boot0000* ubuntu	HD(1,GPT,0b92f5d9-9346-4725-9e99-65a55902654f,0x22,0x1007de)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* UEFI: IP4 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0002* UEFI: IP6 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0003* manjaro	HD(1,GPT,0b92f5d9-9346-4725-9e99-65a55902654f,0x22,0x1007de)/File(\EFI\manjaro\grubx64.efi)
Boot0004* Windows Boot Manager	HD(1,GPT,0b92f5d9-9346-4725-9e99-65a55902654f,0x22,0x1007de)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0005* UEFI: IP4 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0006* UEFI: IP6 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0007* UEFI: IP4 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0008* UEFI: IP6 Realtek PCIe GBE Family Controller	PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(600292427622,0)/IPv6([::]:<->[::]:,0,0)..BO

I tried to change it from Ubuntu, but I encounter the same output after rebooting, the order is not changed at all.

Maybe you should try from within WinOS with bcdedit.

No! You misunderstand. OP can already boot to Manjaro from uBUNTU GRUB.
It’s regressive :rofl: to do just that.
From booting from Ubuntu grub to booting from Windows boot.
That’s regressive and more hassles.

Yes, it is the same whether done from Ubuntu or from Manjaro.
It now seems that bootorder number has finally stuck at 0003.
Previously it was 0006.

Thanks for confirming this.

So, please check if you can find a way through bios-setup as my earlier post.
Good luck. Let us know, ya and if cannot find a way, it’s okay too, take your time and
Cheers!

Then use this entry; first put into Ubuntu’s custom.cfg together with above 3 entries,


menuentry "Manjaro - vmlinuz " {
               insmod part_gpt
               insmod ext2
               search --no-floppy  --fs-uuid --set=root 2664046d-cb22-4b33-978b-bb2061effc53
               linux	/boot/vmlinuz-4.17-x86_64 root=UUID=2664046d-cb22-4b33-978b-bb2061effc53 rw
               initrd	/boot/intel-ucode.img /boot/initramfs-4.17-x86_64.img
     }


Note I used kernel 4.17. Change to the kernel you have.
Each time there is a change in kernel, modify this entry.

A few ways, but the safest and easiest, is to treat grub 2 like grub-legacy.
Use 1 of the 3 (now 4) entries that you like and just copy into the top entry of /boot/grub/grub.cfg.
Note like grub-legacy, any change in kernel, grub-install or update-grub will revert back without this added entry (custom.cfg will remain intact). Redo adding this entry, like in grub-legacy.

Also note there will be warnings against doing this and changing in KDE now will require command SUDO_EDITOR=kate sudoedit /boot/grub/grub.cfg
to override the KDE ‘protection against ourselves’ they wanted us to have (which we can still override).

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by Bytemark