Boot screen is low resolution

[Luke-Software1024]

After I updated AnduinOS, the GRUB screen and boot screen became lower resolution than normal. I'm not 100% positive, but I think it was reduced to 1024x768. The boot screen also lost the boot logo (BGRT).

[Anduin2017]

Ack. Will be fixed in 2.0.3.

[siyamsec-lab]

I’d be interested in investigating this.

The combination of a lower-resolution GRUB screen and the loss of the BGRT boot logo makes me suspect that the update may have changed something related to GRUB video mode, kernel parameters, or Plymouth/firmware boot handling.

Could you please provide the output of:

cat /etc/default/grub

grep -E 'GRUB_GFX|GRUB_CMDLINE|GRUB_TERMINAL' /etc/default/grub

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

and:

cat /proc/cmdline

For the BGRT/Plymouth side, also:

systemctl status plymouth-start.service

ls /sys/class/graphics/

If the issue appeared immediately after an AnduinOS update, it would also be useful to know:

• AnduinOS version before and after the update
• GRUB package version
• Kernel version
• Whether the machine boots using UEFI
• GPU/device model

As an initial test, I would check whether /etc/default/grub contains an unexpected GRUB_GFXMODE such as 1024x768, and whether the update changed the kernel command line or Plymouth configuration.

I’d prefer to identify the exact configuration change before suggesting a permanent fix, because forcing a GRUB resolution globally could hide the actual regression and may behave differently across hardware.

If we can reproduce the issue, I’d be happy to investigate the relevant package/configuration and submit a proper fix.

[Luke-Software1024]

Output of cat /etc/default/grub command:

# If you change this file or any /etc/default/grub.d/*.cfg file,
# run 'update-grub' afterwards to update /boot/grub/grub.cfg.
# For full documentation of the options in these files, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`( . /etc/os-release && echo ${NAME} )`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
#GRUB_DISABLE_OS_PROBER=false

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE/GOP/UGA
# you can see them in real GRUB with the command `videoinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

Output of grep -E 'GRUB_GFX|GRUB_CMDLINE|GRUB_TERMINAL' /etc/default/grub command:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
#GRUB_TERMINAL=console
#GRUB_GFXMODE=640x480

Output of sudo grub-mkconfig -o /boot/grub/grub.cfg command:

Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/20-anduinos-style.cfg'
Sourcing file `/etc/default/grub.d/99-anduinos-desktop.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-7.0.0-31-generic
Found initrd image: /boot/initrd.img-7.0.0-31-generic
Found linux image: /boot/vmlinuz-7.0.0-28-generic
Found initrd image: /boot/initrd.img-7.0.0-28-generic
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
error: invalid volume.
error: invalid volume.
error: invalid volume.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done

Output of cat /proc/cmdline command:

BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=b3d68d02-8d1b-4770-a2dd-4f50a2ead9a6 ro quiet splash preempt=full

Output of systemctl status plymouth-start.service command:

● plymouth-start.service - Show Plymouth Boot Screen
     Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static)
     Active: active (exited) since Mon 2026-09-07 07:00:54 MST; 5min ago
 Invocation: a522b3292f8242d9bb6788432a30ed7f
    Process: 422 ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCESS)
    Process: 424 ExecStartPost=/usr/bin/plymouth show-splash (code=exited, status=0/SUCCESS)
   Mem peak: 3.3M
        CPU: 8ms

Sep 07 07:00:54 luke-desktop systemd[1]: Starting plymouth-start.service - Show Plymouth Boot Screen...
Sep 07 07:00:54 luke-desktop systemd[1]: Started plymouth-start.service - Show Plymouth Boot Screen.

Output of ls /sys/class/graphics/ command:

fb0  fbcon

AnduinOS upgrade: 2.0.1 -> 2.0.2
GRUB version: 2.14-2ubuntu2.1
Linux kernel version: 7.0.0-31-generic
Boot mode: 64-bit UEFI, no Secure Boot
GPU: NVIDIA GeForce RTX 2060 SUPER

I checked the videoinfo output, and it said 1440x900x32bit was the selected mode?!
Even though 1920x1080 was preferred AND available?!

Oh yeah, this might be useful: I'm using rEFInd to boot GRUB.

[siyamsec-lab]

Thanks for providing the outputs. The additional details make the graphics-mode path more interesting.

/etc/default/grub and /proc/cmdline don't show an obvious forced 1024x768 or other low-resolution setting, and Plymouth itself appears to start successfully.

The most notable clue is that GRUB is selecting 1440x900x32, even though 1920x1080 is available and preferred. Since you're also booting GRUB through rEFInd, I'd like to check whether either the AnduinOS GRUB configuration or rEFInd is influencing the framebuffer/video mode.

Could you also provide:

cat /etc/default/grub.d/20-anduinos-style.cfg
cat /etc/default/grub.d/99-anduinos-desktop.cfg

grep -nE 'gfxmode|gfxpayload|terminal_output|video|1440|1920|900|1080' /boot/grub/grub.cfg

sudo grep -RniE 'GRUB_GFX|gfxmode|gfxpayload|1440|1920|900|1080' \
    /etc/default/grub /etc/default/grub.d /etc/grub.d

And because rEFInd is involved:

sudo grep -RniE 'resolution|graphics|video|mode' /boot/efi/EFI/refind/

If possible, also share the relevant graphics/resolution settings from:

sudo cat /boot/efi/EFI/refind/refind.conf

I'm especially interested in comparing the GRUB configuration generated by 2.0.2 with 2.0.1, because the fact that 1920x1080 is available but 1440x900 is selected may indicate a change in how the framebuffer mode is being inherited or selected.

I agree that forcing GRUB_GFXMODE=1920x1080 should probably not be the permanent fix until we identify what changed.