From Newsgroup: alt.os.linux

I upgrade Leap and now when booting I shows the MSI BIOS logo for a few seconds instead of Leap splash screen a few seconds before the login
screen appears. I have never seen anything like that in 25 years of
using linux.
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Fri, 4/10/2026 11:20 PM, Woozy Song wrote:

I upgrade Leap and now when booting I shows the MSI BIOS logo for a few seconds
instead of Leap splash screen a few seconds before the login screen appears. I have never seen anything like that in 25 years of using linux.

Enter the BIOS, find the splash screen setting. Disable it.
Now, a buffer with a picture of the MSI logo is not sitting
in hardware, when the handoff from BIOS to OS is done.

Every motherboard I have ever owned, has had the splash screen
turned off.

If you just enable the screen as an OS, without programming it, it
may display what was in a buffer there previously.

It means something isn't right about how the early OS is handling
the screen, but if the material bothers you, switching off the
splash at source, should cause it to be replaced by something
else you haven't seen before :-) It could be a GOP versus legacy VBIOS
issue of some sort (on the video card), an inability to initialize
the display early on.

When the real OS driver loads, then it takes over and does the
initialization properly.

Years ago, there were a couple video cards that were not VESA compliant.
When the machine started, there were four or five little screens
stuffed into the actual screen, and the startup process was doing
something to deal with the lack of the right VESA mode. And that would be another example of a lack of a proper behavior as the machine starts.
The video cards were made by Matrox. You sometimes see this kind of
weirdness, in virtual machine environments.

Paul
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 2026-04-11 07:57, Paul wrote:

On Fri, 4/10/2026 11:20 PM, Woozy Song wrote:

I upgrade Leap and now when booting I shows the MSI BIOS logo for a few seconds
instead of Leap splash screen a few seconds before the login screen appears. >> I have never seen anything like that in 25 years of using linux.

Enter the BIOS, find the splash screen setting. Disable it.
Now, a buffer with a picture of the MSI logo is not sitting
in hardware, when the handoff from BIOS to OS is done.

Every motherboard I have ever owned, has had the splash screen
turned off.

If you just enable the screen as an OS, without programming it, it
may display what was in a buffer there previously.

It means something isn't right about how the early OS is handling
the screen, but if the material bothers you, switching off the
splash at source, should cause it to be replaced by something
else you haven't seen before :-) It could be a GOP versus legacy VBIOS
issue of some sort (on the video card), an inability to initialize
the display early on.

With my "new" laptop, when I installed openSUSE Leap 15.5 with full encryption, I get the Lenovo logo greeting, a small message about grub
loading at the top , and then the encryption password request; all the
time, with the big Lenovo logo beneath it. I wonder if it is saved in
the ESP partitions.

Otherwise, it means grub doesn't erase the initial screen but uses it. Possibly a new feature.
--
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Sat, 4/11/2026 10:10 AM, Carlos E.R. wrote:

On 2026-04-11 07:57, Paul wrote:

On Fri, 4/10/2026 11:20 PM, Woozy Song wrote:

I upgrade Leap and now when booting I shows the MSI BIOS logo for a few seconds
instead of Leap splash screen a few seconds before the login screen appears.
I have never seen anything like that in 25 years of using linux.

Enter the BIOS, find the splash screen setting. Disable it.
Now, a buffer with a picture of the MSI logo is not sitting
in hardware, when the handoff from BIOS to OS is done.

Every motherboard I have ever owned, has had the splash screen
turned off.

If you just enable the screen as an OS, without programming it, it
may display what was in a buffer there previously.

It means something isn't right about how the early OS is handling
the screen, but if the material bothers you, switching off the
splash at source, should cause it to be replaced by something
else you haven't seen before :-) It could be a GOP versus legacy VBIOS
issue of some sort (on the video card), an inability to initialize
the display early on.

With my "new" laptop, when I installed openSUSE Leap 15.5 with full encryption, I get the Lenovo logo greeting, a small message about grub loading at the top , and then the encryption password request; all the time, with the big Lenovo logo beneath it. I wonder if it is saved in the ESP partitions.

Otherwise, it means grub doesn't erase the initial screen but uses it. Possibly a new feature.

And random observation, wasn't there some exploit related to the splash screen ?

https://www.kaspersky.com/blog/logofail-uefi-vulnerabilities/50160/

"When you turn on a computer, the manufacturer’s logo is displayed on the
screen before the operating system boots. This logo can actually be changed - a
function intended to be used by laptop and desktop manufacturers. But there is
nothing stopping an ordinary user from using it and replacing the default logo
with a different image.

The logo is stored in the code that runs immediately after the computer is
turned on, in the so-called UEFI (Unified Extensible Firmware Interface)
firmware. It turns out that this logo replacement function opens the way for
the device to be seriously compromised - attackers can hack it and subsequently
seize control of the system, and this can even be done remotely. The possibility
of such an attack — named LogoFAIL — was recently discussed by experts at Binarly.

In this article, we’ll try to explain it in simple terms, but let’s first recall
the dangers of so-called UEFI bootkits."
...
"This includes, for example, setting the logo resolution so that this parameter
ends up beyond the limits defined in the handling code. This leads to a
calculation error and ultimately results in data being written from the image file
into the area for executable data. This data will then be executed with
maximum privileges."
...
"some computer models from major manufacturers were not susceptible to this attack,
replacing the logo in their UEFI is essentially blocked. Among these models are a
number of Apple laptops and Dell devices."

https://www.theregister.com/2023/12/01/uefi_image_parser_flaws/

Fri 1 Dec 2023 // 20:12 UTC

Dubbed "LogoFail"

"LogoFAIL differs from BlackLotus or BootHole threats because it doesn't break
runtime integrity by modifying the bootloader or firmware component,"

Showing the splash then, may be an attempt to use the human operators eyeballs to
identify modification of the image. That is all I can think of as a justification
for showing it when GRUB shows up.

Paul
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

Paul,

"This includes, for example, setting the logo resolution so that this parameter ends up beyond the limits defined in the handling code.

Wasn't that at one time the whole problem with UEFI, it allowing arguments
to overflow the alotted space for it. ? AFAIK they fixed that, but it
looks like that some of it still lingers.

But going back to the OPs post :

Do you have any idea why his upgraded OS suddenly keeps showing the boot-screen instead of clearing/overwriting it ? A setting that got
changed as a result of the upgrading process ? A video-driver that got changed ? Something else ?

Regards,
Rudy Wieser


--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On Sun, 4/12/2026 3:40 AM, R.Wieser wrote:

Paul,

"This includes, for example, setting the logo resolution so that this
parameter ends up beyond the limits defined in the handling code.

Wasn't that at one time the whole problem with UEFI, it allowing arguments to overflow the alotted space for it. ? AFAIK they fixed that, but it looks like that some of it still lingers.

But going back to the OPs post :

Do you have any idea why his upgraded OS suddenly keeps showing the boot-screen instead of clearing/overwriting it ? A setting that got changed as a result of the upgrading process ? A video-driver that got changed ? Something else ?

Regards,
Rudy Wieser

Nothing in here.

https://en.wikipedia.org/wiki/Booting_process_of_Linux

"default BGRT theme"

https://www.reddit.com/r/linuxquestions/comments/1iyh0hx/grub2_and_bootlogo_with_uefi_logo/

And specific to SUSE, there is a reference to BGRT in this thread.

https://forums.opensuse.org/t/system-boot-screen-question/152498?page=2

plymouth-set-default-theme --list

bgrt
breeze
breeze-text
details
fade-in
script
solar
spinfinity
spinner
text
tribar

plymouth-set-default-theme
bgrt

Paul
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: alt.os.linux

On 2026-04-11 22:43, Paul wrote:

On Sat, 4/11/2026 10:10 AM, Carlos E.R. wrote:

On 2026-04-11 07:57, Paul wrote:

On Fri, 4/10/2026 11:20 PM, Woozy Song wrote:

...

With my "new" laptop, when I installed openSUSE Leap 15.5 with full encryption, I get the Lenovo logo greeting, a small message about grub loading at the top , and then the encryption password request; all the time, with the big Lenovo logo beneath it. I wonder if it is saved in the ESP partitions.

Otherwise, it means grub doesn't erase the initial screen but uses it. Possibly a new feature.

And random observation, wasn't there some exploit related to the splash screen ?

Huh? I don't remember.

https://www.kaspersky.com/blog/logofail-uefi-vulnerabilities/50160/

"When you turn on a computer, the manufacturer’s logo is displayed on the
screen before the operating system boots. This logo can actually be changed - a
function intended to be used by laptop and desktop manufacturers. But there is
nothing stopping an ordinary user from using it and replacing the default logo
with a different image.

The logo is stored in the code that runs immediately after the computer is
turned on, in the so-called UEFI (Unified Extensible Firmware Interface)
firmware. It turns out that this logo replacement function opens the way for
the device to be seriously compromised - attackers can hack it and subsequently
seize control of the system, and this can even be done remotely. The possibility
of such an attack — named LogoFAIL — was recently discussed by experts at Binarly.

In this article, we’ll try to explain it in simple terms, but let’s first recall
the dangers of so-called UEFI bootkits."
...
"This includes, for example, setting the logo resolution so that this parameter
ends up beyond the limits defined in the handling code. This leads to a
calculation error and ultimately results in data being written from the image file
into the area for executable data. This data will then be executed with
maximum privileges."
...
"some computer models from major manufacturers were not susceptible to this attack,
replacing the logo in their UEFI is essentially blocked. Among these models are a
number of Apple laptops and Dell devices."

https://www.theregister.com/2023/12/01/uefi_image_parser_flaws/

Fri 1 Dec 2023 // 20:12 UTC

Dubbed "LogoFail"

"LogoFAIL differs from BlackLotus or BootHole threats because it doesn't break
runtime integrity by modifying the bootloader or firmware component,"

No, I had no idea.

Showing the splash then, may be an attempt to use the human operators eyeballs to
identify modification of the image. That is all I can think of as a justification
for showing it when GRUB shows up.

Oh. I have to say, that I like seeing the logo there.

My preference would be the penguins walking on the pole, moving around. openSUSE enabled that thing randomly, but with probability much higher
around year end. But it was a grub-1 feature, grub-2 lost it.

With full disk encryption, the initial grub code has to decrypt the rest
of the booting code, it takes time before the boot menu appears. Or if hibernated, a very long time while the encrypted swap and /boot is read
to load the kernel before the actual load of the hibernation image. So
seeing the Lenovo logo all the time, same as with Windows, I find nice.
--
Cheers, Carlos.
ES🇪🇸, EU🇪🇺;
--- Synchronet 3.21f-Linux NewsLink 1.2