Comment # 8 on bug 1184403 from Takashi Iwai

(In reply to Dario Faggioli from comment #6)
> (In reply to Takashi Iwai from comment #3)
> > Do you mean that the installer itself has no WiFi support?  Or do you mean
> > about the installed system?
> > 
> Yeah, both (we have reports of other users too).
> 
> > In the former case, it's likely a missing MODULE_FIRMWARE() entry that
> > points to this firmware file.  
> >
> Forgive my ignorance, we're missing a MODULE_FIRMWARE, where?

See an example in bug 1183860.  The firmware files included in the installation
image are determined from the information of modinfo for each included module. 
Each driver module is supposed to declare the relevant firmware names via
MODULE_FIRMWARE() macro in the code.  In the case of the bugzilla entry above
(SLE15-SP3), iwlwifi declared the non-existing firmware version via
MODULE_FIRMWARE(), hence the installation image missed a few of them.

However, looking at the TW iwlwifi 5.11.x module, all MODULE_FIRMWARE() look
correct; and above all, iwlwifi-6000g2a-* has been always correct in the older
kernels, so my early guess was incorrect.  It must be something else, if the
installer really can't provide the WiFi access.

> > For the latter case, it's the selection of a
> > package; kernel-firmware-iwlwifi should be picked up by zypper
> > install-recommends with the package supplement information.
> >
> Oh, that might be due to the fact that in MicroOS we have no-recommends,
> then?

Yes, likely.  In the normal installation, kernel-firmware-all package is
usually installed via recommends.  Also, some other firmware like CPU microcode
is installed in a similar way, IIRC.

So, without recommends installation, many such bits would be missing, and some
can be serious problems; e.g. AMD GPU require the firmware files mandatory, and
it'll lead to a blank screen without it.  Or, the lack of CPU microcode results
in the security hole.

In anyway, if the WiFi works after installing the kernel-firmware-* package,
that's the case.  And it's a different problem from the lack of WiFi in the
installer; if so, we need to open a separate bug report for it, too.