Hey everyone, I’m stuck with this annoying problem on my laptop that runs Fedora 41 and Windows. My GRUB menu shows up looking super big compared to my friends’ laptops, which is kind of weird. The main headache is with Windows - if I start it through GRUB, it runs in Legacy mode, but going through BIOS gets me UEFI mode instead. Pretty sure my GRUB isn’t playing nice with UEFI, which is probably messing things up. Anyone know how to fix this? Just want to get Windows working properly!
What does “it runs in legacy mode” mean exactly?
Do you have bit locker enabled in Windows?
Do you have legacy mode enabled in the BIOS? It is call CSM(?) I think.
The size of the grub menu depends on the GPU features and can be configured in grub config.
Means I get the Windows logo when it boots and not my vendor logo, I also have limited screen resolution.
As for GRUB size I assure you its not about the config… I’ve seen it on my friends laptops. I have a FHD screen, the menu doesn’t look like how it should be and I have 2 GPUs
Yes your grub show exactly how is configuration of your system If you have two GPU’s I assume one of is nvidia that optimus systems are difficult to set It is doable but you have to have knowledge
Based on what you are saying GRUB should always look the same right ? well, It isn’t sometimes I get a small interface and sometimes I get a big zoomed interface.
To be specific when I go to the bios and then leave I get the properly scaled (not 100% sure) menu
No. It depends on your hardware, and as you have noticed also if the bios is entered then the environment can change, e.g. GPU can be mode set.
1 Like
alright then, So whats the problem that makes windows boot in legacy mode now ? since its not GRUB
Its the code in the uefi bios and the gpu.
I said that when I run windows from the BIOS, it boots normally.
I’m out of ideas.
FYI when I’m investigating things like this I try and reproduce starting from a cold boot. A warm reboot can have state set that changes the way things work.
2 Likes
I wonder what the boot target looks like in your grub menu.
Also, what do you get when you boot into Fedora, and run efibootmgr in a terminal window?
❯ efibootmgr
BootCurrent: 0009
Timeout: 0 seconds
BootOrder: 0009,0000,0007,0008
Boot0000* Windows Boot Manager HD(1,GPT,eb42143d-ede1-4ff6-8ffa-b658ec3debae,0x800,0x32000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000066000100000010000000040000007fff0400
Boot0007 UEFI: IP4 Qualcomm Atheros PCIe Network Controller PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(d8cb8a83e53c,0)/IPv4(0.0.0.0,0,DHCP,0.0.0.0,0.0.0.0,0.0.0.0)0000424f
Boot0008 UEFI: IP6 Qualcomm Atheros PCIe Network Controller PciRoot(0x0)/Pci(0x1c,0x3)/Pci(0x0,0x0)/MAC(d8cb8a83e53c,0)/IPv6([::],0,Static,[::],[::],64)0000424f
Boot0009* Fedora HD(1,GPT,a84b1f53-4286-4ecd-8598-91270506b076,0x800,0x12c000)/\EFI\FEDORA\SHIM.EFI0000424f
Okay, can we see the result from first part of the request? We need that to do a comparison.
Also, I’m interested that your Fedora boot line, UEFI Boot Manager target Boo0009, contains the pointer to \EFI\FEDORA\SHIM.EFI. Mine points to \EFI\fedora\shimx64.efi. There must be a story there…
Can you further explain this ? Like what are you talking about, what request ?
The part where I wrote this:
You should be able to see what that looks like if you look at /boot/grub2/grub.cfg at search for chainloader and look in the vicinity of where that takes you.
If both boot managers are pointing to bootmgfw.efi, ultimately, then this is not a problem with booting in Legacy mode from Grub.
My setup is dual-boot as well, and I’ve booted WindowsOS from Grub with no problems on more than one occasion, although, I have to confess that it’s been well over a year since I last booted WindowsOS from any boot manager.
Makes no difference. These two files are identical. First was shim.efi, and when later a 32 bit version was needed shimx64.efi and shimia32.efi was created for the 64bit and 32bit version respectively.
Yes, I remember you posting this before. I had checked on my system at the time using sha256sum to confirm it.
I was more interested in how the installer would not uniformly install and configure the efi bootloader among different machines.