> So it needs to be made opt-in through a kernel
> parameter (which we might set by default, later on).
I only stumbled onto this recently whilst attempting to get a flicker free
boot, i think the kernel param you are looking for is
fbcon=nodefer
6. fbcon=nodefer
If the kernel is compiled with deferred fbcon takeover support, normally
the framebuffer contents, left in place by the firmware/bootloader, will
be preserved until there actually is some text is output to the console.
This option causes fbcon to bind immediately to the fbdev device.
so maybe we could set CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=y
in conjunction with fbcon=nodefer
?
On Fri, 31 Jan 2020 12:03:03 +0100 Ben Hutchings <b...@decadent.org.uk>
wrote:
> Control: reassign src:linux
> Control: forcemerge 926794 -1
>
> On Fri, 2020-01-31 at 19:22 +1100, Julien Goodwin wrote:
> > Package: linux-signed-amd64
> > Version: 5.4.13+1
> > Severity: wishlist
> >
> > Please consider setting CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=y
> > to allow for "flicker free" booting (when combined with appropriate
> > bootloader & plymouth configs).
>
> And there's the problem: this actually looks really bad without those
> config changes. So it needs to be made opt-in through a kernel
> parameter (which we might set by default, later on).
>
> > The upstream patch introducing the behaviour:
> > https://patchwork.kernel.org/patch/10432641/
> >
> > Fedora (29) & Arch are known to set this on their kernels.
>
> Ben.
>
> --
> Ben Hutchings
> 73.46% of all statistics are made up.
>
