Why would Ubuntu decide to differ from other linux distro into not providing efifb into initramfs please? I cannot convince all linux distros specifically into following deprecation plan of fbdev.
What is supposed to be in initramfs prior of LUKS unlock by systemd, so that passphrase prompt is possible for user to input a LUKS passphrase is : efifb/simplefb/simpledrm. Not providing efifb is the issue here. Debian/Fedora/other derivatives do not do that and everything is fine. Heads uses efifb because coreboot can provide efifb compliant console from UEFI GOP driver/libgfxinit for all Intel based iGPU. Heads enforced hacks for a short while to support i915 doube initialization and tainted its kernel to expose FB address to next kernel in kexec call: but this is not desired. HEads having simplefb/simpledrm in its kernel would cause the same double init issue, since kexec/linux kernel is not made to expose fb address anymore. efifb is good enough under first kernel and can provide its fb to kexec call, where kexec is made to use it, can provide it through kexec call to next kernel, and everything is ok if efifb is provided in initramfs before rootfs being available, when systemd is asking user to type LUKS decryption key passphrase. Otherwise, user is left in the dark to type his LUKS key passphrase, which if he does, efifb -> simplefb/simpledrm-> drm drivers are loaded and take over. What is preventing efifb from being packaged into initramfs please? I do not understanding why I have to fight for adding it back. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2104014 Title: CONFIG_FB_EFI needed in initramfs for linuxboot based systems Status in linux package in Ubuntu: Won't Fix Bug description: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965303/comments/39 Otherwise, Heads (coreboot payload enforcing GOP/libgfxinit -> efifb -> kexec into OS initramfs efifb -> main kernel simpledrm -> advanced drm+fb takeover) stays in the dark at pre-LUKS volume unlock prompt. Can CONFIG_FB_EFI be added back in initramfs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2104014/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
