#926794 linux-image-4.19.0.0-bpo.4-amd64: Please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel config

Package:
src:linux
Source:
src:linux
Submitter:
Frantisek Novak
Date:
2026-08-03 06:33:02 UTC
Severity:
normal
Tags:
#926794#5
Date:
2019-04-10 13:58:07 UTC
From:
To:
Dear Maintainer,

please enable FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER in kernel configuration to prevent clearing of the framebuffer when the console starts during the boot.

Thanks
Frantisek

#926794#14
Date:
2019-04-12 20:17:15 UTC
From:
To:
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.

#926794#19
Date:
2019-04-12 21:30:17 UTC
From:
To:
Hello Ben,

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.

Regards,
Frantisek

#926794#24
Date:
2020-01-19 13:27:56 UTC
From:
To:
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.

I just stumbled over this and became curious.

Since i currently just directly boot the kernel via EFI stub i followed
https://wiki.debian.org/BuildADebianKernelPackage and did give it a try.
I was quite satisfied with the result.

Are there any situations where this makes something worse?
( I see Ben tested this:
https://salsa.debian.org/kernel-team/linux/commit/
b4995d6607608cd18181f47ee291a39868e678a7 )

Wolfgang

#926794#35
Date:
2025-04-25 09:12:27 UTC
From:
To:
close 926794
thanks

Closing this older bugreport unless there is some recent interest that we still
need to enable it and might need to be rediscussed.

#926794#44
Date:
2026-05-23 10:16:00 UTC
From:
To:
Hi,

yes, this is still something some people want to have, even on Debian.

I tried systemd-boot + plymouth bgrt and it works - except for the black screen
in between.

Other distributions like Fedora, Ubuntu, Arch, have enabled it:

https://github.com/search?q=repo%3Anyrahul%2Flinux-kernel-configs%20FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER&type=code

Jérémy