Ubuntu Support Template
Ubuntu Version:
26.04 LTS
Desktop Environment (if applicable):
GNOME
Problem Description:
I have a system with an Ultra 125H CPU and integrated graphics. After installing Ubuntu 26, the Lenovo logo flashes three times during startup before the user login screen appears. Why does the logo flash three times? Can this be fixed?
Relevant System Information:
Screenshots or Error Messages:
sudo dmesg | tail -20
What I’ve Tried:
Before Posting:
@sss-xxx Welcome to Ubuntu Discourse 
I edited your title to make it something more descriptive so users will know what the problem is and can offer help.
Once you get to the login screen are you able to successfully login and get to the desktop?
Is this your first Ubuntu install? Has this happened before?
Thanks
I can log in to the system; I used to use Windows, but now I’ve switched to Ubuntu.
@rubi1200 I can log in to the system; I used to use Windows, but now I’ve switched to Ubuntu.
It’s not a dual-boot setup; I formatted the entire hard drive to install Ubuntu
Does the system work OK once you login?
Yes,it is work.but the Lenovo logo flashes three times on the startup screen. @Actionparsnip
According to my Googling, seems to be a graphical mismatch between the GRUB bootloader and your graphics drivers, or issues with proprietary (Nvidia/AMD) drivers struggling to initialize early in the boot sequence
You could set GRUB to a different resolution to maybe solve the flicker
You could, alternatively, go with a text based bootup, disable the GUI splash, and it should be a bit smoother.
Could the official team optimize the system installer’s bootloader? Or are there any plans to do so?
I’ll give it a try.tks.
If you open Software & Updates>Additional Drivers tab you will see if Ubuntu is running on a proprietary video driver. You may even be offered an alternative proprietary video driver. Changing video drivers may solve this.
If we disable the proprietary video driver then Ubuntu will run on an open source video driver the next time we boot. The open source video drivers can be as capable as the proprietary video driver. It also may solve the problem.
I have an older Lenovo Thinkpad with an AMD APU and integrated graphics and I’ve just rebooted to see what the Lenovo logo does. Depending on what you count as “flashing”, mine does too, i.e. when the boot logo gets accompanied by the Ubuntu logo: screen goes black briefly and comes back with both the Lenovo and Ubuntu logos.
It’s a somewhat long standing challenge to do “flicker free boot” and it’s related to the graphics handover between the boot loader an Linux proper. For some it works for others it doesn’t. It’s a minor cosmetic issue and you shouldn’t sweat it, least of all try to “fix” it; that’s an exercise in frustration at the very least, especially for a new user. Just live with it. Your machine seems to sport rather recent hardware, which tends to exhibit teething issues when it comes to Linux support; they will get better with time.
You might want to enable the Hardware Enablement (HWE) stack to benefit from future kernel and graphics upgrades to newer major versions.
………ok, thanks reply.
Ok,i will try it,tks.
In you /etc/default/grub, do you have the following parameter set:
GRUB_GFXPAYLOAD_LINUX="keep"
Also, at the end of your
GRUB_CMDLINE_LINUX_DEFAULT=...
after the “splash” reference, add one of the following as applicable to your context:
amdgpu.sg_display=0 # for AMD
i915.fastboot=1 # for Intel iGPUs
Naturally, after making those changes, be sure to run
sudo update-grub
then reboot.
@sss-xxx You have received a few opinions and ideas about what you can possibly do to rectify the situation.
I am not going to add to that.
However, what I do strongly suggest is that if you decide to try one of the possible resolutions then please write it down somewhere so that if it goes wrong or produces results you are not satisfied with, then you can go back and undo whatever change you made.
This is something users should make a habit of; backup important data before changes, document what fixes or workaround you applied and keep it safe.
In the event something does go wrong it is then very easy to come back here and say I tried X but got Y.
This will make it much easier for the volunteer users to help you.
Thanks
It’s better to leave /etc/default/grub alone, so as to not be prompted on upgrades what to do, should there be a newer version of it. That’s why we have config drop-ins (the files in .d directories).
For example:
sudo mkdir -p /etc/default/grub.d/
sudo tee /etc/default/grub.d/flickerfree-boot.cfg >/dev/null <<'EOF'
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT amdgpu.sg_display=0 i915.fastboot=1"
EOF
sudo update-grub
(never forget to put $GRUB_CMDLINE_LINUX_DEFAULT in there too, otherwise you overwrite any previous settings from the main config or previous drop-ins)
BTW, I believe that at least the i915.fastboot=1 is redundant, because it’s the default anyway, from what I gathered in the thread about it. Same as GRUB_GFXPAYLOAD_LINUX="keep", but it’s been like that since long before the flickerfree boot initiative.
From the documentation of the amdgpu module parameter, it looks like sg_display=0 is for other purposes. There shouldn’t be any memory pressure at boot time. Is there any proof that it works toward removing boot “flicker”?
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.fastboot=1"
It will still flash.
Out of curiosity, are you using the identical file for the background image for each of
Don’t know if using the file at the same fullpath source location for all 3 image-load instances would help.
The GRUB reference to “splash” refers to the second instance above.