initramfs-tools ignores the FRAMEBUFFER option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Fix Released
|
High
|
Andy Whitcroft | ||
Bionic |
Fix Released
|
High
|
Brian Murray |
Bug Description
[Impact]
initramfs-tools would always include all "framebuffer" drivers/firmware inside initramfs, which was making it ever more huge. In some systems with low memory, that would even prevent systems to boot. kdump, for example, had an impact.
[Test case]
Different systems on different arches were tested. When cryptsetup (or cryptsetup-
[Regression Potential]
Systems may not boot because of missing drivers. Users may have a different experience during boot because of missing "framebuffer" drivers.
==================
initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu6
ProcVersionSign
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar 24 18:06:24 2016
InstallationDate: Installed on 2016-02-16 (37 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209)
PackageArchitec
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in initramfs-tools (Ubuntu): | |
milestone: | none → ubuntu-16.03 |
tags: | added: patch |
tags: | added: rls-bb-incoming |
Changed in initramfs-tools (Ubuntu Bionic): | |
assignee: | nobody → Brian Murray (brian-murray) |
status: | New → In Progress |
importance: | Undecided → High |
description: | updated |
tags: | removed: rls-bb-incoming |
no longer affects: | initramfs-tools (Ubuntu Xenial) |
I am attaching the output of the following command: img-`uname -r` | grep drm
lsinitramfs /boot/initrd.