Bug 1161183 - Reduce kernel firmware file installations
Reduce kernel firmware file installations
Status: NEW
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem
Current
Other Other
: P5 - None : Enhancement (vote)
: ---
Assigned To: Dominique Leuenberger
E-mail List
https://trello.com/c/e667Ev1A
:
Depends on: 1146769
Blocks:
  Show dependency treegraph
 
Reported: 2020-01-17 12:22 UTC by Lukas Ocilka
Modified: 2020-03-05 17:12 UTC (History)
11 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
locilka: needinfo? (dimstar)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Ocilka 2020-01-17 12:22:59 UTC
+++ This bug was initially created as a clone of Bug #1143959 +++

Currently kernel-firmware package contains the full contents of uncompressed files and its footprint is significant large, over 400MB.
For reducing this installation size, we can try the following:

- Compress firmware files:
5.3 kernel got a new feature to support loading the XZ-compressed firmware files.  We can package the compressed files instead of the raw files.

- Split kernel-firmware package to several packages:
Instead of the all-in-one package, we may split per functionality or such.

https://bugzilla.suse.com/show_bug.cgi?id=1143959#c10 says:

As the fix for kernel-default-base is done, the rest is about the handling of Recommends:kernel-firmware in kernel-default.rpm.  And from now on, I'd toss this to YaST guys, who have a better idea about installation.

Reassigned to Stefan for now, but feel free to push back if inappropriate.

As discussed earlier, we may move the recommends into patterns, or implement something in YaST, so that user can choose the optimized for the current hardware or comprehensive / safe with all files.

The decision is on PjM/Release Managers

- YaST / Installer is not the only way to install / upgrade the system
- The decision which firmware packages to install CAN, but should not be by
  default taken by the user (they can already select packages manually, BTW)
- It's quite an expert option going against "Simplify things"
- The decision and efforts need to be aligned and documented

IMO worth a feature request
Comment 1 Lukas Ocilka 2020-01-17 12:41:04 UTC
Lubos, Ludwig, Dominique, PjM/RM decision (and driving) needed here.
Please, take over. This is now TW only, but will end up in SLE.
Comment 2 Lubos Kocman 2020-02-11 09:03:07 UTC
Hello team,

are we talking about all architectures or just Intel? I recall from RHEL that s390x used to have some 32MB requirements or so and the Installer guys always had to fight with kernel module exclusion list.

Lubos
Comment 4 Takashi Iwai 2020-02-11 09:23:12 UTC
It should be architecture-agnostic, and note that this entry is about kernel firmware, not kernel modules.
Comment 5 Ludwig Nussel 2020-03-05 17:12:55 UTC
missed the needinfo on me. *shrug*. Go ahead :)