FS#60404 - Linux 4.19: Enable fbcon deferred takeover
Attached to Project:
Arch Linux
Opened by Mathias Rav (rav) - Sunday, 14 October 2018, 12:05 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 14 October 2018, 15:22 GMT
Opened by Mathias Rav (rav) - Sunday, 14 October 2018, 12:05 GMT
Last edited by Eli Schwartz (eschwartz) - Sunday, 14 October 2018, 15:22 GMT
|
Details
Linux 4.19 (to be released 2018-10-21) introduces deferred
takeover of the framebuffer console, which is a new feature
to avoid blanking the screen until console text needs to be
printed. Instead, whatever vendor logo was left in the
framebuffer from early boot is retained. By setting
CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=y, a truly
silent boot can be achieved in which the vendor logo is
retained on screen until the login manager is ready to
accept the user's password. This is described in further
detail in the wiki:
https://wiki.archlinux.org/index.php/Silent_boot#Retaining_the_vendor_logo_from_BIOS
I'd like to request that CONFIG_FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER is enabled when Linux 4.19 is packaged for Arch. I'm currently running 4.19.0-rc7 with the option enabled to achieve silent boot, but I'd like to use Arch's official kernel (once 4.19 stable is out). |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Sunday, 14 October 2018, 15:22 GMT
Reason for closing: Not a bug
Additional comments about closing: That's not how it works. The kernel maintainer also reads the headline news for new kernel releases and is presumably capable of deciding whether to enable brand-new settings. Wait until after the kernel is even released before submitting feature requests for it; then wait until after you have any reason to think the maintainer decided against it.
Feel free to request this be re-opened *if* linux 4.19 hits the [testing] repos and this is still not enabled.
Sunday, 14 October 2018, 15:22 GMT
Reason for closing: Not a bug
Additional comments about closing: That's not how it works. The kernel maintainer also reads the headline news for new kernel releases and is presumably capable of deciding whether to enable brand-new settings. Wait until after the kernel is even released before submitting feature requests for it; then wait until after you have any reason to think the maintainer decided against it.
Feel free to request this be re-opened *if* linux 4.19 hits the [testing] repos and this is still not enabled.