DualBoot Fedora/Win11 does not work on my machine. Why is there no GRUB?

Hello, guys! Need your help. I have laptop Acer Aspire E5-771G (hybrid graphics - Intel + NVidia). Windows11 is installed to SSD 2TB (second drive), Fedora37 is installed to HDD 1TB (first drive). Rebooting my laptop after installing Fedora, but there is no GRUB, it is absent, booting Windows11. But if to install Fedora to USB flash-drive, that is OK, there is GRUB menu with Fedora and Windows items. Also, if to install Manjaro in dualboot with Windows, GRUB exists too! So, what is the problem with GRUB in Fedora???

For UEFI, generally Windows and Fedora will share the same /efi partition. It appears that you may be booting to the EFI from the Windows drive but installed Fedora on a separate drive entirely? You might be able to boot to Fedora through your BIOS boot menu in that case, but if you want to be able to boot between them without doing that, then Fedora will need to be setup in the same /efi that Windows uses.

1 Like

Do show the output of efibootmgr. If it shows what I think it does, you can use the efibootmgr program to change the boot order to select grub before the windows loader.

   ~  efibootmgr  :heavy_check_mark:

BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,0005,2001,2002,2003
Boot0001* HDD0: WDC WD10JPVX-22JC3T0	PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(5,GPT,7d19f98e-fbfd-4c4e-8cea-756ee5648d7c,0x800,0x12c000)RC
Boot0005* Windows Boot Manager	HD(1,GPT,635ee55b-31a4-454a-ac80-0a6cfe158e7a,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000061000100000010000000040000007fff0400
Boot0006  rEFInd	HD(1,GPT,cac3dd06-8d0d-11ed-8c9c-2c600c1db815,0x28,0x80000)/File(\EFI\refind\BOOTX64.EFI)
Boot0007  GhostBSD	HD(1,GPT,9af23ff8-f2df-11ec-bbab-2c600c1db815,0x28,0x80000)/File(\EFI\ghostbsd\BOOTX64.EFI)
Boot0008  rEFInd	HD(1,GPT,9af23ff8-f2df-11ec-bbab-2c600c1db815,0x28,0x80000)/File(\EFI\refind\BOOTX64.EFI)
Boot0009  GhostBSD	HD(1,GPT,8350ef5b-f347-11ec-bfb1-2c600c1db815,0x28,0x80000)/File(\EFI\ghostbsd\BOOTX64.EFI)
Boot000A  rEFInd	HD(1,GPT,8350ef5b-f347-11ec-bfb1-2c600c1db815,0x28,0x80000)/File(\EFI\refind\BOOTX64.EFI)
Boot000B  GhostBSD	HD(1,GPT,6878cb71-f38e-11ec-8efb-2c600c1db815,0x28,0x80000)/File(\EFI\ghostbsd\BOOTX64.EFI)
Boot000C  rEFInd	HD(1,GPT,6878cb71-f38e-11ec-8efb-2c600c1db815,0x28,0x80000)/File(\EFI\refind\BOOTX64.EFI)
Boot000D  GhostBSD	HD(1,GPT,1baadad7-f3b2-11ec-b208-2c600c1db815,0x28,0x80000)/File(\EFI\ghostbsd\BOOTX64.EFI)
Boot000E  rEFInd	HD(1,GPT,1baadad7-f3b2-11ec-b208-2c600c1db815,0x28,0x80000)/File(\EFI\refind\BOOTX64.EFI)
Boot000F  rEFInd	HD(1,GPT,e91a9135-17db-11ed-9997-2c600c1db815,0x28,0x12c000)/File(\EFI\refind\BOOTX64.EFI)
Boot0010  GhostBSD	HD(1,GPT,28d44e9b-18ba-11ed-b7b3-2c600c1db815,0x28,0x12c000)/File(\EFI\ghostbsd\BOOTX64.EFI)
Boot0011  rEFInd	HD(1,GPT,28d44e9b-18ba-11ed-b7b3-2c600c1db815,0x28,0x12c000)/File(\EFI\refind\BOOTX64.EFI)
Boot0012  GhostBSD	HD(1,GPT,316b1623-194d-11ed-a32c-2c600c1db815,0x28,0x12c000)/File(\EFI\ghostbsd\BOOTX64.EFI)
Boot0013  rEFInd	HD(1,GPT,316b1623-194d-11ed-a32c-2c600c1db815,0x28,0x12c000)/File(\EFI\refind\BOOTX64.EFI)
Boot0014* Fedora	HD(1,GPT,30fadd49-f527-485c-a68a-f495f66cda9f,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)
Boot0015  GhostBSD	HD(1,GPT,797cb5cb-8d13-11ed-ad1a-2c600c1db815,0x28,0x80000)/File(\EFI\ghostbsd\BOOTX64.EFI)
Boot0016* Fedora	HD(1,GPT,cac3dd06-8d0d-11ed-8c9c-2c600c1db815,0x28,0x80000)/File(\EFI\fedora\shimx64.efi)
Boot0017  rEFInd	HD(1,GPT,797cb5cb-8d13-11ed-ad1a-2c600c1db815,0x28,0x80000)/File(\EFI\refind\BOOTX64.EFI)
Boot0018  GhostBSD	HD(1,GPT,83dd902c-a6db-11ed-9227-2c600c1db815,0x800,0x80000)/File(\EFI\ghostbsd\BOOTX64.EFI)
Boot0019* Fedora	HD(1,GPT,5ac26582-187a-455a-871c-128314886833,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)
Boot001A  rEFInd	HD(1,GPT,83dd902c-a6db-11ed-9227-2c600c1db815,0x800,0x80000)/File(\EFI\refind\BOOTX64.EFI)
Boot001B* Fedora	HD(1,GPT,161d488f-0047-4f45-a9a1-04edbafa0176,0x800,0x1e8000)/File(\EFI\fedora\shimx64.efi)
Boot001C* Fedora	HD(1,GPT,8fb952d2-6329-4436-b474-25b476269b56,0x800,0x111000)/File(\EFI\fedora\shimx64.efi)
Boot001F* Fedora	HD(1,GPT,b1503b2d-0b33-4915-8e04-512f04302418,0x800,0x12c000)/File(\EFI\fedora\shimx64.efi)
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

You need to find the entry corresponding to your Fedora installation.
For this we need to know the partition uuid of the efi file system.

Run

lsblk  -o PATH,PARTUUID,PARTTYPENAME

The uuid you see in this list is the uuid you also find in the output from efibootmgr. If that for example is Boot001B then run

efibootmgr -n 001B

That should boot the Fedora grub entry when you reboot

I will suggest to remove all the other entries except the entries 0001,0005,2001,2002,2003 and the Fedora entry that works.

To remove entry xxxx run

efibootmgr -b xxxx -B
1 Like

Is it enough to move Fedora grub entry up, to the top of the list?

That would normally happen when you install Fedora. I guess that as you have too many entries in the boot list, something didn’t work properly.

Eventually you will need to set the boot order list, which is currently

BootOrder: 0001,0005,2001,2002,2003

That is, MS-Windows followed by DVD, Network, and USB boot.

1 Like

Deleting all entries, except Fedora, saving, rebooting. They appear again… :man_facepalming:




There are many boot managers aside from Grub : Lilo, Syslinux, BURG, efibootmgr … Microsoft is getting picky about security being one of the first partners with Intel for EFI standard. Advice => get away from this as the good solution is what you have done : two operating systems on separate storage devices and use BIOS interface to switch …

If you really want to play with EFI Secure Boot feature use two separate devices. Red Hat/CentOS/Fedora have Microsoft EFI signature following old dispute from Debian concerning FOSS.

EFI with secureboot is fully supported here. You don’t have to use it, but questions about it are valid and welcome here.