AMD To Enable Seamless Boot Across Modern Radeon Graphics Hardware

[RussianNeuroMancer]

Wasn't "Plymouth" the one supposed to solve it in the old days?

I also thought that this "flicker free boot" was a thing back in the days when KMS was introduced.

Guys, you talking about avoiding screen flicker during switch from kernel to Xorg/Wayland, while article is about avoiding screen flicker during switch from UEFI to kernel, which is another technical problem entirely. In Intel case it can be enabled with "i915.fastboot=1" (if not enabled by default).

[agd5f]

My boot with AMD hardware is already flicker-free and transitions seamlessly from GRUB to Plymouth to SDDM, so I don't understand what this is supposed to do. Or does openSUSE already ship these patches?

It just skips the modeset if the display config from the bios matches what the driver wants to light up. That said, the driver already structures the modesets to be as minimally invasive as possible so in a lot of cases, you shouldn't notice the modeset anyway.

[shmerl]

My UEFI starts the screen in weird low res, so it flickers anyway, but it does it multiple times (like changing the terminal font for example), so at least less would be better.

[OneTimeShot]

Given that everything should just run at the maximum resolution of whatever monitor is connected, this makes a lot of sense

[kbios]

Is it still only for embedded DisplayPort (eDP)?

[caligula]

I haven't been able to read ANYTHING during the boot process for years. At least RX 5000 series is switching the modes way too many times. Same thing with previous gen Polaris cards.

[Sonadow]

Why the hell is this even an issue.

Are modesetting flickers at boot going to kill someone? Hell no.

[NeoMorpheus]

Current members: whatever, i dont care for flawless out of the box experience, its tour fault that my ngreedia gpu doesn’t do the same thing, fix it!

[yump]

I see why Valve and other appliance IHVs would find this valuable for their brand image, but as the operator of a desktop PC, and occasional support person for other people's PCs, the motherboard vendor's logo persisting on screen long after the firmware has passed control to the bootloader just seems misleading. What if it hangs and makes it look like the wrong party is responsible?

[BraindeadBZH]

Finally