I just did a fresh install of Windows, then installed EndeavourOS + i3wm. Each OS has it’s own dedicated drive. The first thing of note after installing was that the BIOS no longer had a splash screen where I could enter the BIOS from. It just goes straight to booting.
When booting, GRUB is low-resolution. If I boot into EOS, somewhere in the systemd startup process the resolution fixes itself. If I boot into W11, however, the screen stays the same resolution and I can’t fix it from Windows’ display settings.
But if I enter the BIOS (UEFI) from the GRUB option or the Windows Recovery Environment, I can then boot either into GRUB or straight into Windows with absolutely no resolution issues at all. Everything is at native resolution.
Windows is not coexistence-freindly. One of the things ist does, is to not shutdown completely. So if you start, it is NOT a cold start, and many hardware initialization is skipped. You might run into various problems. Switch off fast boot in windows is strongly recommended. The thing is: you will not notice that it is slower without “fast boot”, a rogue who thinks evil…
Booting Windows from UEFI menu (Quick Boot Menu) is a good practice, when multi-booting with Linux.
This issue is one of the reasons.
If there is a way to fix the Grub resolution, it may be found inside the BIOS options, since Linux has not started yet, when Grub menu starts. It sounds like a hardware/firmware vendor problem.
I was hopeful this’d be the answer, but it changes nothing. Could it be something to do with the fact that I chose for the drive to be encrypted when I installed?
Unfortunately, my BIOS is pretty bare when it comes to settings. I’ve dualbooted W11 and EOS (Gemini) on this computer before, and am only running into this problem after I’ve done a wipe of all hard drives. The hard drive wipe doesn’t make much sense to change anything, though, right?
Thinking of drivers, is it possible I need to install a driver somewhere so that my display is initialized correctly? I always assumed drivers only really came into play when actually booting to Linux/Windows.
If encryption does not work, you just get a hang boot because it cannot mount partition. If it finds the key and decrypts everything, i don’t see any reason for changed resolution. Grub hands over control to the Windows boot mechanism. That thing is responsible for whatever settings and hardware init is done.