This thread is distinct from initramfs size increase, initial suspect is dracut 105 to 107 https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/77F6N5HNCODHACIQ2LQSFQRFWJEQEOYH/#Y3TBCEQKUJ6OUT7NK2MQSHRUSKMX2P3L
I'm noticing quite large rescue initramfs lately but haven't dug into when it started. -rw-------. 1 root root 268553810 Sep 12 23:10 initramfs-0-rescue-2a837d3749fd4397a3107adde82b7518.img What I have noticed is by removing nvidia-gpu-firmware-0:20250808-1.fc43.noarch and rebuilding the [-N, --no-hostonly, Disable host-only mode.] initramfs... -rw-------. 1 root root 137294342 Sep 21 20:34 initramfs-0-rescue-2a837d3749fd4397a3107adde82b7518.img It's quite a bit smaller. There's also amd firmware in the initial rescue firmware. Both are expected for no-hostonly initramfs. The question is, since firmware is getting bigger at a faster rate than most other things, and because no-hostonly and sloppy mode initramfs contain more firmware files - I'm wondering... Should we bump boot volume size for Fedora 43? The last time it was bumped, from 500M to 1G, was 2016. There wasn't a change proposal, it was just suggested we do it on this list, and then changed. While a 1G boot will accommodate 3 kernels and initramfs today, it may not in the near future. And some folks use kdump which adds more initramfs to boot. We could just double it to 2G, but that seems like overkill for systems that are resource constrained. Another idea is to bump boot to 1.2G for Fedora 43. And then commit to revisiting the size more frequently, even as soon as Fedora 44/45. -- Chris Murphy -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
