GRUB doesn't always pick the right video driver

wmbg · 2024-12-01 21:26:48

I've been fighting to get my GRUB resolution right for good time already, and have tried several solutions, but none of them seem to get to fix my problems completely.

Using videoinfo on GRUB can return me two different results

1. 640x480x32, using the Bochs PCI Video Driver (wrong resolution)
2. 1920x1080x32, using the Cirrus CLGD 5446 PCI Video Driver (right resolution)

The first result always comes whenever I turn on/restart my PC normally, the second one only appears when I boot directly from the UEFI menu.

I've already set the framebuffer resolution to 1920x1080x32, as said here
https://wiki.archlinux.org/title/GRUB/T … resolution

Also, CSM has already been disabled in my BIOS.

I don't this makes a difference, but I also have plymouth installed.

cryptearth · 2024-12-01 21:32:53

best guess: you have two grub installs with two different configs and depending on how you start the system it differs which grub gets booted and hence which config is used

wmbg · 2024-12-01 21:40:15

cryptearth wrote:

best guess: you have two grub installs with two different configs and depending on how you start the system it differs which grub gets booted and hence which config is used

How would I be able to see if I have multiple grub installations? Also, I don't think that's possible since all my other configurations are being properly followed, such as the default kernel selected and kernel modules I use.

ewaller · 2024-12-01 22:56:49

What is the output of efibootmgr -u ?

cryptearth · 2024-12-01 23:02:29

give it's a uefi system: call

sudo efibootmgr -v -u

and check its output
also have a look at your partitions and mountpoints: what are your mounpoints for ESP and boot? /efi? /boot? /boot/efi? if you mount something to /boot check if its mounted - get a file listing - unmount /boot and see if something comes up - if so you likely shadow multiple configs

wmbg · 2024-12-01 23:09:17

ewaller wrote:

What is the output of efibootmgr -u ?

BootCurrent: 0004
Timeout: 1 seconds
BootOrder: 0004,0000,0001,0003
Boot0000* Windows Boot Manager  HD(1,GPT,81579670-afa8-4d35-97b3-cbe647c1789e,0x800,0x32000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI䥗䑎坏S
Boot0001* endeavouros   VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0003* ubuntu        VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
Boot0004* UEFI OS       HD(1,GPT,0d680ba3-8e63-44dc-82e9-1e743949b07d,0x800,0x200000)/\EFI\BOOT\BOOTX64.EFI

I guess it's good to say that I'm not using EndeavourOS or Ubuntu, entries 0001 and 0003 are probably from when I had Endeavour and Mint installed.

ewaller · 2024-12-01 23:56:46

Yes, it Should™ use Boot0004 which seems to be your bootloader. But, it does appear that you also have a different boot partition that is shared by Endeavour and Ubuntu. You also seem to have a legacy OS from the American Pacific Northwest. Boot 0000,0001 and 0003 should not normally be used, but you could use them from the EFI boot menu. You mentioned booting from the UEFI menu, are you sure you are picking the correct entry?

wmbg · 2024-12-02 00:08:51

ewaller wrote:

Yes, it Should™ use Boot0004 which seems to be your bootloader. But, it does appear that you also have a different boot partition that is shared by Endeavour and Ubuntu. You also seem to have a legacy OS from the American Pacific Northwest. Boot 0000,0001 and 0003 should not normally be used, but you could use them from the EFI boot menu. You mentioned booting from the UEFI menu, are you sure you are picking the correct entry?

Just checked on the UEFI, boot option 1 is "UEFI OS" (0004) and option 2 is the Windows Boot Manager; These are also the only options available.

Head_on_a_Stick · 2024-12-02 08:03:44

Can you share the output of the plain `set` command from the GRUB command line? If you take photos of the screen and upload it to https://postimages.org/ and share them here using the "thumbnail for forums" link that would be great, thanks.

Strange that there's no specific GRUB entry, perhaps try running the grub-install command again or use efibootmgr to create an entry pointing to grubx64.efi directly.

seth · 2024-12-02 08:44:33

The first result always comes whenever I turn on/restart my PC normally, the second one only appears when I boot directly from the UEFI menu.
I don't this makes a difference, but I also have plymouth installed.

For clarification, are you looking for the GRUB resolution or the framebuffer in use when the system actually boots?

Because

HoaS wrote:

Strange that there's no specific GRUB entry

you've windows, and ubuntu and EOS kernels on a separate partition, there's no sign of any arch or grub installation.
I'll give you that by "arch" you actually mean "EOS", but it doesn't look like you're using grub at all.

And on top of that

1. 640x480x32, using the Bochs PCI Video Driver (wrong resolution)

That's a qemu kernel driver (and likely is the CL one, you don't have such GPU, I presume)
https://wiki.archlinux.org/title/Kernel … _KMS_start

=> Please elaborate on the setup and in particular whether you're trying to boot a VM here.
Selecting the desired driver for the modules hook might do and oc. you can configure the resolution when starting the VM, https://wiki.archlinux.org/title/QEMU#C … resolution

Arch Linux

#1 2024-12-01 21:26:48

GRUB doesn't always pick the right video driver

#2 2024-12-01 21:32:53

Re: GRUB doesn't always pick the right video driver

#3 2024-12-01 21:40:15

Re: GRUB doesn't always pick the right video driver

#4 2024-12-01 22:56:49

Re: GRUB doesn't always pick the right video driver

#5 2024-12-01 23:02:29

Re: GRUB doesn't always pick the right video driver

#6 2024-12-01 23:09:17

Re: GRUB doesn't always pick the right video driver

#7 2024-12-01 23:56:46

Re: GRUB doesn't always pick the right video driver

#8 2024-12-02 00:08:51

Re: GRUB doesn't always pick the right video driver

#9 2024-12-02 08:03:44

Re: GRUB doesn't always pick the right video driver

#10 2024-12-02 08:44:33

Re: GRUB doesn't always pick the right video driver

Board footer