https://bugzilla.suse.com/show_bug.cgi?id=1184403 https://bugzilla.suse.com/show_bug.cgi?id=1184403#c2 --- Comment #2 from Martin Rohde --- I didn't install anything yet as I don't have any internet connectivity right after installation. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1184403 https://bugzilla.suse.com/show_bug.cgi?id=1184403#c4 --- Comment #4 from Martin Rohde --- I think it is both. In any case, neither during installation I was prompted to connect to the internet nor was there any possibility to connect after installation of MicroOS. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1184403 https://bugzilla.suse.com/show_bug.cgi?id=1184403#c6 Dario Faggioli changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dfaggioli@suse.com --- Comment #6 from Dario Faggioli --- (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?

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? -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1184403 https://bugzilla.suse.com/show_bug.cgi?id=1184403#c8 --- Comment #8 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. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1184403 https://bugzilla.suse.com/show_bug.cgi?id=1184403#c10 --- Comment #10 from Martin Rohde --- (In reply to Takashi Iwai from comment #9)

(In reply to Martin Rohde from comment #7)

...

I couldn't get the kernel-firmware-iwlwifi installed.

Did you install via transaction-update command? e.g. % transactional-update pkg install kernel-firmware-iwlwifi-*.rpm

Yes, I did. Dario helped me walk through it. I will try again soon to narrow down the issue. Most likely just myself not getting it installed properly. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1184403 https://bugzilla.suse.com/show_bug.cgi?id=1184403#c12 --- Comment #12 from Dario Faggioli --- (In reply to Takashi Iwai from comment #8)

(In reply to Dario Faggioli from comment #6)

...

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.

Ok, great... Thanks for the info!

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.

Totally agree. What I still don't know (and am trying to figure out) is where it is decided what will end up in the install media. Like, using this issue as an example, why isn't the firmware package there? If it's due to the no-recommends thing... Where is it that we set "no-recommends" in such a way that is has this effect? Is it, perhaps, here: https://github.com/yast/skelcd-control-MicroOS/blob/master/control/control.M... ? -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1184403 https://bugzilla.suse.com/show_bug.cgi?id=1184403#c18 --- Comment #18 from Dario Faggioli --- (In reply to Takashi Iwai from comment #17)

Hm, onlyDVD has already Requires: kernel-firmware. So the firmware packages are already on the media, at least.

Yes, I was puzzled about this as well. And in fact, if I try to configure my wireless network card during installation, it works. However, when booting into a freshly installed system, the `kernel-firmware` package *is not* installed, and hence no network. :-( Now, can this be due to the fact that, if we check here: https://build.opensuse.org/package/view_file/Kernel:HEAD/kernel-firmware/ker... we see that the kernel-fimrware (sub)package does not have any "Supplements:" ?

I still don't get how you'd make those firmware packages installed without the help of hardware supplements. Certainly we don't want to install them unconditionally, right?

What do you mean with "without the need of hardware supplements" ? My current line of thinking is that, e.g., on this laptop, we would need the firmware that are in the kernel-firmware-iwlwifi package. On the media, there's no package that provides the proper "Supplements:". In fact, there is kernel-firmware there, but it does not come with any "Supplements:" at all, so it's not installed. The package that has the proper "Supplements" is indeed kernel-firmware-iwlwifi, but it's not present on the media, so it's not installed. But if I put it there, it will be installed, thanks to the fact that it has the proper "Supplements:" for this hardware. Or do I have a bug in my reasoning? -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1184403 https://bugzilla.suse.com/show_bug.cgi?id=1184403#c20 --- Comment #20 from Takashi Iwai --- If that's the case, the fix would be to simply replace Requires: kernel-firmware with Requires: kernel-firmware-all in the patterns. Then all kernel-firmware-* subpackages will be on the media. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1184403 https://bugzilla.suse.com/show_bug.cgi?id=1184403#c22 --- Comment #22 from Takashi Iwai --- Well, this doesn't sound right. First off, if you want to have the split kernel-firmware-* packages on the media, keeping Requires:kernel-firmware makes no sense. kernel-firmware is an all-in-one package containing the *all* raw uncompressed firmware files. You have to drop it from patterns at first. After that, you can put individual kernel-firmware-* packages -- but only if you really want to manage that. For example, with this SR, you still don't put the kernel-firmware-amdgpu; hence the installation on AMD graphics chip would lead to a blank screen. Similarly, the lack of kernel-firmware-bluetooth leads to the lack of BT, the lack of kernel-firmware-ath11k would miss the recent Atheros chip, etc, etc. And, the fact that you have had already kernel-firmware on the media indicate that the media size won't change so much even if you replace it with kernel-firmware-all. kernel-firmware-all is just a meta package of kernel-firmware-* subpackages, and again, kernel-firmware already contains all of those files in it without split. (There is slight difference due to the compression over compressed files, and of course some overhead due to metadata amount, but that's all.) So, my recommendation is to replace Requires:kernel-firmware with Requires:kernel-firmware-all. Or if we want to reduce some firmware files, maybe it's better to create a new pattern-firmware-desktop or such and specify the needed ones there. It'll be useful for the normal installation, not only on MicroOS Desktop, too. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1184403 https://bugzilla.suse.com/show_bug.cgi?id=1184403#c25 --- Comment #25 from Martin Rohde --- Moved to new openSUSE MicroOS category. -- You are receiving this mail because: You are the assignee for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1184403 https://bugzilla.suse.com/show_bug.cgi?id=1184403#c26 --- Comment #26 from Martin Rohde --- This is fixed for me. If there is nothing further to adjust, feel free to close this bug. Thanks a lot! -- You are receiving this mail because: You are the assignee for the bug.