06.12.2020 19:51, ASSI пишет:

While troubleshooting some other issue, I've ran into this problem again that's been bugging me for a while: depending on exactly how I boot up my system it'll come up with different graphics modes in Grub2. If I either enter the BIOS setup before or enter the Grub2 command line and then exit to the menu, it will (most often) chose the native resolution of my monitor (1920x1080), otherwise it'll be stuck at 1024x768. On

If you do not set preferred resolution, grub will prefer existing setup otherwise it will prefer whatever EDID says. This matches what you describe - if your firmware set up resolution before calling grub, it will use it, otherwise may be your monitor supplies broken EDID (or EDID is completely faked by firmware).

another system it is flipping between 800x600, 1280x1024 and whatever the native resolution of the display is (2560x1600 and lately 3840x2160). In the 4k mode a few lines on the bottom of the screen are blank (where the explanation for the keys to edit the command line go) in the graphical menu, but that's no problem so far. Now, I can force

It is not clear under which conditions it happens, but in any case - either grub inherits resolution from your firmware or grub iterates through list of resolutions returned by firmware. In both cases there is not much that can be done.

the resolution in the grub defaults file, but I'd rather have it chose the correct resolution in "auto" mode all the time. Both are Haswell IGP if that matters. I am using secure boot, so no joy with videoinfo on the grub command line…

grub does not care about real hardware - it is using EFI GOP protocol and so cannot really do more than firmware offers.