Shouldn't mkinitcpio or similar automatically figure out what firmware files you need? At least I was under the impression that is how it works on Arch Linux (which is what I run).
And after initcpio the main system probably has the full linux-firmware (or equivalent) package with everything, so there is no problem there.
So the main remaining issue is with non-rolling release distros and having too new hardware. In which case you probably also need to upgrade at least the kernel and mesa, not just the firmware, so it is going to be a larger operation anyway.
In conclusion, while this is a nice improvement, to me it seems unlikely that you are in a situation where firmware is the only problem. And whatever mechanism your distro provides for the other problems (e.g. HWE packages on Ubuntu, no clue about how that works in Fedora) will probably also deal with the firmware automatically.
And after initcpio the main system probably has the full linux-firmware (or equivalent) package with everything, so there is no problem there.
So the main remaining issue is with non-rolling release distros and having too new hardware. In which case you probably also need to upgrade at least the kernel and mesa, not just the firmware, so it is going to be a larger operation anyway.
In conclusion, while this is a nice improvement, to me it seems unlikely that you are in a situation where firmware is the only problem. And whatever mechanism your distro provides for the other problems (e.g. HWE packages on Ubuntu, no clue about how that works in Fedora) will probably also deal with the firmware automatically.
Comment