I’ve been using the grub2-breeze-theme from the Fedora distro for a few years. I didn’t update to F40 until last November, and since then the grub2-breeze-theme hasn’t been “kicking in” until later in the boot process I have a 4k screen, CPU is a AMD Ryzen 5 6600H with Radeon Graphics. What happens is:
- Screen starts up with the grub boot menu, in 1024x768 resolution, with the grub menu present, the menu font is big and blocky.
- Systems boots and them dmesg text starts to appear at 1024x768 resolution, the system switches to 4k resolution after this line (approximately):
[ 3.672726] amdgpu: ATOM BIOS: 113-REMBRANDT-X37
This is where the amdgpu driver takes over the video. (Dmesg lines with context below) The dmesg text on the monitor now, as expected, switches to a small, 4k resoultion screen font which is what used to happen after the grub2-breeze-theme splash screen and progress bar went away.
Anyone else seeing their grub themes failing with amdgpu?
I tried erasing and reinstalling the grub2-breeze-theme rpm and no change. I suspect amdgpu has starting doing something that grub2-breeze-theme needs to be tweaked for, if that can be done. From what I can tell the grub2-breeze-theme files have been unchanged for a while (I found gustawho/grub2-theme-breeze on Github and the KDE store, maybe there are others?) My next step might be to hand install one of the various other themes available and see what happens.
Other stuff in /etc/default/grub:
GRUB_GFXMODE=1920x1080 works, font is not too bad
GRUB_TERMINAL_OUTPUT=“gfxterm” instead of “console” had no effect
I’m too checken to increase GRUB_GFXMODE further since I’m not sure what modes the kernel supports with a 4k screen.
Dmesg lines with context:
[ 3.667057] amdgpu 0000:74:00.0: enabling device (0006 → 0007)
[ 3.667260] [drm] initializing kernel modesetting (YELLOW_CARP 0x1002:0x1681 0x1002:0x0124 0xC9).
[ 3.667411] [drm] register mmio base: 0xDC700000
[ 3.667556] [drm] register mmio size: 524288
[ 3.670784] [drm] add ip block number 0 <nv_common>
[ 3.671116] [drm] add ip block number 1 <gmc_v10_0>
[ 3.671388] [drm] add ip block number 2 <navi10_ih>
[ 3.671662] [drm] add ip block number 3
[ 3.671920] [drm] add ip block number 4
[ 3.671922] [drm] add ip block number 5
[ 3.671924] [drm] add ip block number 6 <gfx_v10_0>
[ 3.671926] [drm] add ip block number 7 <sdma_v5_2>
[ 3.671928] [drm] add ip block number 8 <vcn_v3_0>
[ 3.671930] [drm] add ip block number 9 <jpeg_v3_0>
[ 3.672723] amdgpu 0000:74:00.0: amdgpu: Fetched VBIOS from VFCT
[ 3.672726] amdgpu: ATOM BIOS: 113-REMBRANDT-X37
[ 3.738733] usb 1-3.3: device not accepting address 7, error -71
[ 3.739475] usb 1-3.3: WARN: invalid context state for evaluate context command.
[ 3.739650] Console: switching to colour dummy device 80x25
[ 3.746364] amdgpu 0000:74:00.0: vgaarb: deactivate vga console
[ 3.746386] amdgpu 0000:74:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
[ 3.746483] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
[ 3.746507] amdgpu 0000:74:00.0: amdgpu: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
[ 3.746559] amdgpu 0000:74:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF