On Thu, 2022-12-08 at 12:58 +0000, Peter Robinson wrote: > > I've done a few passes, dropping a bunch of older firmware upstream > that are no longer supported in any stable kernel release, also a > bunch of de-dupe and linking of files rather than shipping of multiple > copies of the same firmware. It's improved things a bit, unfortunately > a lot of the dead firmware was tiny compared to say average modern > devices like GPUs or WiFI. > > The problem with a lot of the firmware, and with the new nvidia "open > driver" which shoves a lot of stuff into firmware in order to have an > upstreamable driver apparently the firmwares there are going to be > 30+Mb each, is that they're needed to bring up graphics/network etc to > even just install so I don't know how we can get around this and still > have a device work enough to be able to install the needed firmware > across the network. > > Ideas on how to solve that problem welcome. Sorry if this is way off, but - do we need the GPU firmwares to run a graphical install on the fallback path, just using the framebuffer set up by the firmware? How crazy would it be to just do that - ship the installer env with no GPU firmware? -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ Anaconda-devel mailing list -- anaconda-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to anaconda-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/anaconda-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
