https://bugzilla.suse.com/show_bug.cgi?id=1184767 Bug ID: 1184767 Summary: Several firmwares missing when installing MicroOS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: dfaggioli@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After finishing installing MicroOS on my laptop, I have this in dmesg: dario@Palanthas-eth:~> dmesg |grep firmware [ 0.073533] Spectre V2 : Enabling Restricted Speculation for firmware calls [ 2.964996] i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2 [ 2.964998] i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. Disabling runtime power management. [ 2.964999] i915 0000:00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/... [ 66.877346] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 66.928640] r8152 4-1.4:1.0: Direct firmware load for rtl_nic/rtl8153a-3.fw failed with error -2 [ 66.928646] r8152 4-1.4:1.0: unable to load firmware patch rtl_nic/rtl8153a-3.fw (-2) [ 67.153449] bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2 [ 67.906512] ath10k_pci 0000:3a:00.0: Failed to find firmware-N.bin (N between 2 and 6) from ath10k/QCA6174/hw3.0: -2 [ 67.906552] ath10k_pci 0000:3a:00.0: could not fetch firmware files (-2) And WiFi and Bluetooth are not working. All the firmware related messages go away if I install the following packages: - kernel-firmware-iwlwifi - kernel-firmware-realtek - kernel-firmware-i915 - kernel-firmware-bluetooth - kernel-firmware-ath10k The message about regulatory.db goes away if I install the crda package This is related to bug 1184403 with the only difference that there the missing firmware is in kernel-firmware-iwlwifi. Also, it looks like this shouldn't happen, according to bug 1174521, as it's marked as fixed, but the problem seems to still be there -- You are receiving this mail because: You are the assignee for the bug.