possible missing firmware SOLVED

[MagicPoulp]

I installed gnome and I got strange errors

I think this firmware is for intel skylake but I have installed firmware-misc-nonfree from buster(even if my kernel is from buster-backports).
What does those warnings mean?

Code: Select all

update-initramfs: Generating /boot/initrd.img-5.7.0-0.bpo.2-amd64
W: Possible missing firmware /lib/firmware/i915/skl_huc_2.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_2.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_huc_4.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/cml_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_huc_9.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_huc_9.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/ehl_guc_33.0.4.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.0.12.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_guc_35.2.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_dmc_ver1_09.bin for module i915
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_06.bin for module i915

[mm3100]

It is probably just harmless warnings, since you have backported kernel it wants firmware from backports too. You can install those packages from backport, or ignore messages.

[Head_on_a_Stick]

Check if you actually need that firmware:

Code: Select all

# dmesg | grep firmware

[stevepusser]

You think wrong. Only the "skl" files are for Skylake. Kabylake is "kbl", for instance.

There is a simple answer to your issue, but I won't give it to you until you clean up your posts and use code tags--including your older posts.

[MagicPoulp]

sudo dmesg | grep firmware

Code: Select all

[    0.080917] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    1.105219] GHES: APEI firmware first mode is enabled by APEI bit.
[    1.412841] i915 0000:00:02.0: firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin
[    1.413455] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[ 1222.422406] (NULL device *): firmware: direct-loading firmware i915/kbl_dmc_ver1_04.bin


OK I use code and not quote sorry.

[Head_on_a_Stick]

Looks like all the required firmware is loaded. I await stevepusser's reply with great antici...

[stevepusser]

.......pation! (shout-out to Rocky Horror Picture Show?)


The simple answer is if you use a kernel from backports, use the firmware packages in backports, too. Not that complicated.

[Head_on_a_Stick]

...pation!

Well that was a bit of an anticlimax — mm3100 already said that...

[stevepusser]

...pation!

Well that was a bit of an anticlimax — mm3100 already said that...

Apparently it often needs to be repeated and repeated and repeated.

[MagicPoulp]

This does not seem to me evident...

No firmware is missing in the kernel log... so it seems the backports kernel just have a different list that seems to be backward compatible with the stable packages for firmwares.

By definition, a backport works with the other packages from stable. if there is a dependency then it should be clear.

If I take the firmwares in backports, maybe something stops working because of a breaking change in a certain firmware... I mean in theory. Probably not since we just update to latest and that is good.

[arid]

It's time for my "You cannot be serious!" post again.

You have to ask yourself; "Is my computer functional today?"

If you have even a modicum interest in your operating system, you will have noticed from time to time or even permanently, error notices.

Again, see 2nd paragraph above.

If you insist on dwelling on this non-problem and asking and following advice on a forum, then I promise you, you will have a real problem and you will deserve the consequences.

If it ain't broke, don't fix it.

[Head_on_a_Stick]

shout-out to Rocky Horror Picture Show?

Yes indeed, well spotted. I'm a massive fan, I even dress up for it when it's on TV. #cannotunsee

By definition, a backport works with the other packages from stable. if there is a dependency then it should be clear.

The firmware listed isn't a dependency as such, it's just that the kernel has drivers and it knows that some of them only work fully with non-free firmware. If the user doesn't have the hardware then they don't need the firmware.

And anyway the kernel package is in the main (official) repository component and that cannot have dependencies that are in the non-free or contrib (unofficial) components: https://www.debian.org/doc/debian-polic ... chive-area

[stevepusser]

By definition, a backport works with the other packages from stable. if there is a dependency then it should be clear.

Not in the case for kernel non-free firmware. A newer kernel will have updated and entirely new drivers which may require a newer firmware file. This has been the case for many years.

Also, certain other packages from backports will depend on certain other previously backported packages. Freecad is an example. This has also always been the case. I'll excuse you, since you haven't done any backporting yourself, but anyone that has done much backporting will run into this.

[RU55EL]

Install:

Code: Select all

# apt install firmware-misc-nonfree

firmware-misc-nonfree

Then, if you want to confirm that firmware is not missing:

Code: Select all

# update-initramfs -u

[MagicPoulp]

I do not have an error to fix, just warnings. But ok it seems reasonable to take the non-free firmwares from backports.

Recently, gnome allowed me to update my bios with the mouse without asking to enter my sudo password. That was weird.