Ignoring BGRT: unexpected or invalid BMP data

Support
1

I get this new dmesg I changed systemd boot message to quiet.
Do i should worry about it?

$ sudo dmesg -l emerg,alert,crit,err,warn
...
[    1.299696] efifb: Ignoring BGRT: unexpected or invalid BMP data
...
2

Yes, worry about everything you don’t understand. :stuck_out_tongue_winking_eye:

1 Like
3

Do this can came from bootsplash? But I removed it and disabled everything related to that. :thinking:
6.4.2 had not this warning (if it is a warning I could really safe ignore it).

4

No idea. Have you researched anything yet?

On my main NVIDIA hybrid laptop, I see the following:

❯ sudo dmesg | grep efifb
[    1.261535] efifb: invalid framebuffer address

My old AMD APU laptop:

❯ sudo dmesg | grep efifb
[    0.437955] pci 0000:04:00.0: BAR 0: assigned to efifb
[    0.710206] efifb: probing for efifb
[    0.710226] efifb: showing boot graphics
[    0.713511] efifb: framebuffer at 0xd0000000, using 8128k, total 8128k
[    0.713513] efifb: mode is 1920x1080x32, linelength=7680, pages=1
[    0.713514] efifb: scrolling: redraw
[    0.713515] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0

Both are using Plymouth and it displays fine. :man_shrugging:

5

it’s solved by removing quiet from grub:
At /etc/default/grub

$ sudo dmesg | grep efifb
[    0.502699] pci 0000:0b:00.0: BAR 0: assigned to efifb
[    1.301234] efifb: probing for efifb
[    1.301247] efifb: framebuffer at 0xd0000000, using 3072k, total 3072k
[    1.301249] efifb: mode is 1024x768x32, linelength=4096, pages=1
[    1.301251] efifb: scrolling: redraw
[    1.301252] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
6

How is what solved? That parameter neither changes what actually happens at boot nor the output of dmesg.

7

It’s not an issue at boot I only get this message at dmesg

8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.