cryptsetup initramfs-tools hooks conf always sets FRAMEBUFFER=y
Bug #1766745 reported by
Thadeu Lima de Souza Cascardo
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| cryptsetup (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
If cryptsetup is installed, even if no partition is encrypted, the generated initramfs will be much larger than necessary, because all framebuffer/DRM drivers will be included.
This causes systems with low memory to not be able to boot at all. That includes systems that are kdumping. On x86, they usually only have 128M of memory allocated. That makes them fail to decompress the initramfs or OOM very early.
Revision history for this message
| Wladimir Mutel (mwg) wrote | #1 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in cryptsetup (Ubuntu): | |
| status: | New → Confirmed |
To post a comment you must log in.
this bug has its history coming from https:/
it is really still not that well understood why cryptsetup would require initialized framebuffer?
but anyway, damn, who reads these bug reports these days ? storage is still even faster and cheaper than it was 7 years ago. your nvidia.ko of 75 MB size is just a light feather compared to the storage volume you really have on every system you boot on :>