Bug#926794: linux-image-18.104.22.168-bpo.4-amd64: Please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel config
as this does not have any direct impact on any other components I think it can be enabled independently. This is because the first write to the console bounds it to the FB and the output behavior works as usual.
On other hand, I definitely agree with you that other components has to be updated as well in order to be possible to fully use this feature. At least, the screen must be captured prior the display driver is loaded and the Systemd runs the console initialization in order to be possible to restore the vendor logo displayed by EFI shell after mentioned tasks. Also, components such as Plymouth should be updated in order to be possible to use the “UEFI” theme. Unfortunately, the list of components can be more wide and I can’t even imagine the foll set of them.
I asked to enable it independently because it currently prevents us from customization of the boot process while the standard Debian Kernel build is in use. We can do it only in case we recompile the Kernel on our own. It is not optimal for the productional environments.
> On 12 Apr 2019, at 22:17, Ben Hutchings <[hidden email]> wrote:
> On Wed, 10 Apr 2019 15:58:07 +0200 Frantisek Novak <
> [hidden email]> wrote:
>> Package: linux-image-22.214.171.124-bpo.4-amd64
>> Version: linux-image-4.19.0-0-bpo.4-amd64
>> Severity: wishlist
>> Dear Maintainer,
>> please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel
> configuration to prevent clearing of the framebuffer when the console
> starts during the boot.
> I tried it a few months back and I don't think we should do this in the
> kernel in isolation. We would also need to make the boot loader silent
> by default, and we might need to update themes as well.
> If you want this to happen, please propose those changes in the other
> packages after the buster release.
> Ben Hutchings
> Hoare's Law of Large Problems:
> Inside every large problem is a small problem struggling to get out.