Grub2 resolution during boot

English Install/Boot/Login
1

I’m struggling to set proper grub resolution after a fresh tumbleweed install. ‘videoinfo’ can’t list the possible video modes for grub:


grub> videoinfo
error: can't find command `videoinfo'.

even if i boot up and enter ‘[FONT=courier new]hwinfo --framebuffer’ in a terminal i get no information about the possible grub resolutions. Here is my output:[/FONT]


xxxxx@linux-zkr0:~> sudo hwinfo --framebuffer
 
02: None 00.0: 11001 VESA Framebuffer                           
  [Created at bios.459]
  Unique ID: rdCR.7Tnva6o_5vD
  Hardware Class: framebuffer
  Model: "(C) 1988-2010, Advanced Micro Devices POLARIS20"
  Vendor: "(C) 1988-2010, Advanced Micro Devices, Inc."
  Device: "POLARIS20"
  SubVendor: "AMD ATOMBIOS"
  SubDevice: 
  Revision: "01.00"
  Memory Size: 48 MB
  Memory Range: 0x00000000-0x02ffffff (rw)
  Config Status: cfg=no, avail=yes, need=no, active=unknown

The strange thing is, when i boot the NET-Install from usb, the resolution for grub is recognized correctly. After finishing the installation and reboot, my grub resolution is too low and i don’t know how to see the possible resolutions. Is there missing something, or am I using the wrong commands to display the possible video modes?
I tested an ubuntu-live iso and ‘[FONT=courier new]videoinfo’ lists me the possible resolutions with my prefered one (1440x900). So i suppose it is somehow opensuse related…

My system:
GPU: AMD RX 570
EFI-Partition
secure-boot enabled[/FONT]

2

You are likely using signed EFI image (which you get if you enable secure boot support in YaST bootloader module and which is enabled by default). This image does not include videoinfo command. May be it should. You may consider opening bug report.

The strange thing is, when i boot the NET-Install from usb, the resolution for grub is recognized correctly.

I do not understand what “recognized” means here. Did you specify GRUB resolution when booting? If yes, how? If no, what exactly “recognized” means?

I tested an ubuntu-live iso and ‘[FONT=courier new]videoinfo’ lists me the possible resolutions with my prefered one (1440x900).

So did you try explictly setting this resolution in YaST bootloader module?

So i suppose it is somehow opensuse related
[/FONT]
The fact that command videoinfo is missing is surely openSUSE specific. Otherwise I do not quite understand the problem. Make a photo of good grub screen and bad grub screen for comparison.

3

Try to see if these Rpm are missing

sudo zypper in   v4l-tools    xf86-video-fbdev

and then try again

sudo hwinfo --framebuffer

You can change the resolution from yast> boat loader> eccc

4

On a (TW) system I have here, following the 20190209 snapshot (which had an update for grub2), the resolution for the graphical splash/boot menu is no longer correctly set when using the “Autodetect by grub2” option, I’ve had to explicitly set the correct screen resolution. ( TW 20190209 appears to have broken autodetect screen resolution for the graphical boot menu... - Install/Boot/Login - openSUSE Forums )

Maybe the OP is seeing the same problem?

5

You are right. After some testing I confirm that enabling secure boot causes that the [FONT=courier new]videoinfo command can‘t be found. Probably, like you said, the command is not included in the EFI image (good to know btw;).[/FONT]
When I find some time I will file a bug report.

… what exactly “recognized” means?

Like tannington guessed in the post before I meant that the autodetect option by GRUB2 does not work properly (at least on my system). I specify nothing in GRUB when booting.
My screen resolution is 1440x900, but GRUB menu is displayed at 1024x768. I know it is only a cosmetic problem, though it is hard to troubleshoot what is causing the wrong resolution when videoinfo does not work (and I even don‘t have a clue why videoinfo is not working).

In Yast bootloader module my screen resolution is not listed either image. It doesn’t display the full row of possible resolutions my monitor&GPU combination can handle.

I can set the right resolution manually in etc/default/grub with

 GRUB_GFXMODE="1440x900"

after running

grub2-mkconfig -o /boot/grub2/grub.cfg

boot menu is displayed correctly with my preferred resolution (1440x900)

6

That gives me the same output

7

I thought that since the “sudo hwinfo --framebuffer” command did not detect any resolution something was missing, but it is not so, I do not understand why it does not detect any resolution, I if I execute the command I have this

sudo hwinfo --framebuffer
[sudo] password di root: 
02: None 00.0: 11001 VESA Framebuffer                           
  [Created at bios.459]
  Unique ID: rdCR.ZHYCUIiP_mD
  Hardware Class: framebuffer
  Model: "NVIDIA GF119 Board - 13100004"
  Vendor: "NVIDIA Corporation"
  Device: "GF119 Board - 13100004"
  SubVendor: "NVIDIA"
  SubDevice: 
  Revision: "Chip Rev"
  Memory Size: 14 MB
  Memory Range: 0x01000000-0x01dfffff (rw)
  Mode 0x0300: 640x400 (+640), 8 bits
  Mode 0x0301: 640x480 (+640), 8 bits
  Mode 0x0303: 800x600 (+800), 8 bits
  Mode 0x0305: 1024x768 (+1024), 8 bits
  Mode 0x0307: 1280x1024 (+1280), 8 bits
  Mode 0x030e: 320x200 (+640), 16 bits
  Mode 0x030f: 320x200 (+1280), 24 bits
  Mode 0x0311: 640x480 (+1280), 16 bits
  Mode 0x0312: 640x480 (+2560), 24 bits
  Mode 0x0314: 800x600 (+1600), 16 bits
  Mode 0x0315: 800x600 (+3200), 24 bits
  Mode 0x0317: 1024x768 (+2048), 16 bits
  Mode 0x0318: 1024x768 (+4096), 24 bits
  Mode 0x031a: 1280x1024 (+2560), 16 bits
  Mode 0x031b: 1280x1024 (+5120), 24 bits
  Mode 0x0330: 320x200 (+320), 8 bits
  Mode 0x0331: 320x400 (+320), 8 bits
  Mode 0x0332: 320x400 (+640), 16 bits
  Mode 0x0333: 320x400 (+1280), 24 bits
  Mode 0x0334: 320x240 (+320), 8 bits
  Mode 0x0335: 320x240 (+640), 16 bits
  Mode 0x0336: 320x240 (+1280), 24 bits
  Mode 0x033d: 640x400 (+1280), 16 bits
  Mode 0x033e: 640x400 (+2560), 24 bits
  Mode 0x0345: 1600x1200 (+1600), 8 bits
  Mode 0x0346: 1600x1200 (+3200), 16 bits
  Mode 0x034a: 1600x1200 (+6400), 24 bits
  Mode 0x034b: 1280x720 (+1920), 8 bits
  Mode 0x034c: 1280x720 (+3840), 16 bits
  Mode 0x034d: 1280x720 (+7680), 24 bits
  Mode 0x0360: 1280x800 (+1280), 8 bits
  Mode 0x0361: 1280x800 (+5120), 24 bits
  Config Status: cfg=no, avail=yes, need=no, active=unknown
8

I expected a similar output than yours. But unfortunately it isn’t. And I don’t know why. I’m using an AMD GPU and i thought it should run out of the box without issues.