How to install DMC firmware

[fred44nl]

my Debian machine has a fresh install with Debian 9.0 and has been updated from time to time.
in sudo dmesg I find:

[ 3.994310] i915 0000:00:02.0: firmware: failed to load i915/bxt_dmc_ver1_07.bin (-2)

[ 3.994325] i915 0000:00:02.0: Failed to load DMC firmware [https://01.org/linuxgraphics/intel-linu ... -firmwares], disabling runtime power management.

how much does this matter ??
if it does matter much, how do I install bxt_dmc_ver1_07.bin ??

[Head_on_a_Stick]

how do I install bxt_dmc_ver1_07.bin ??

Use this search function to find the package containing that file:

https://www.debian.org/distrib/packages#search_contents

Or do it locally (fnar!):

https://wiki.debian.org/WhereIsIt

[spoiler alert!]firmware-misc-nonfree[/spoiler alert!]

[fred44nl]

ok, thank you
so, bxt_dmc_ver1_07.bin should be in /lib/firmware/i915
however, I do have /lib/firmware, but there is folder i915 in there.

do I just make that folder ??
and copy bxt_dmc_ver1_07.bin in it ??
or is there an more official installation procedure ??

[Head_on_a_Stick]

Code: Select all

# apt install firmware-misc-nonfree

[stevepusser]

If you have more ????, the Debian wiki entry on firmware will answer those.

[fred44nl]

Code: Select all

# apt install firmware-misc-nonfree

this installs a large amount of drivers, where I only need one.
is there a way to install one single driver ??
that is, apart from starting over and add the driver while installing Debian.

[sunrat]

Code: Select all

# apt install firmware-misc-nonfree

this installs a large amount of drivers, where I only need one.
is there a way to install one single driver ??
that is, apart from starting over and add the driver while installing Debian.

Firmware is not drivers. Firmware is a tiny binary file that gets loaded on the device whereas drivers are kernel modules.
That package takes a whole 7MB once installed. If you don't have 7MB to spare, you could download the package, extract the firmware and put it in /lib/firmware (I think that's where it goes from memory.)

[fred44nl]

after adding the required firmware packages, I was left with:

[ 4.992448] [drm] GuC firmware load skipped

looked for a solution and found this:

sudo nano /etc/modprobe.d/i915.conf
options i915 enable_guc_loading=1 enable_guc_submission=1

problem solved, but now my kernel is tainted.

[ 3.945069] Setting dangerous option enable_guc_loading - tainting kernel
[ 3.945074] Setting dangerous option enable_guc_submission - tainting kernel

how big a problem is this ??
is there another way to solve skipping GuC firmware ??

[Head_on_a_Stick]

how big a problem is this ?

Not as big a problem as your apparent inability to do some basic research.

Pro tip: enter "tainted kernel linux" into a search engine and read the stackexchange link at the top of the list.

And please stop using multiple question marks, it's really irritating me.

[cronomorfo]

I have a similar issue than the original poster:

Code: Select all

sudo journalctl -b -1 -p 3
abr 20 08:49:57 SYSTEM kernel: ACPI Error: [_SB_.PCI0.RP01.PXSX] Namespace lookup failure, AE_NOT_FOUND (20160831/ps
abr 20 08:49:57 SYSTEM kernel: ACPI Error: Method parse/execution failed [\] (Node ffffffffb9d1f8a0), AE_NOT_FOUND (
abr 20 08:50:14 SYSTEM kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xfed40080-0xfed40fff]
abr 20 08:50:14 SYSTEM kernel: i2c_hid i2c-FTE1001:00: error in i2c_hid_init_report size:633 / ret_size:0
abr 20 08:50:14 SYSTEM kernel: i2c_hid i2c-FTE1001:00: error in i2c_hid_init_report size:131 / ret_size:0
abr 20 08:50:14 SYSTEM kernel: i915 0000:00:02.0: firmware: failed to load i915/skl_dmc_ver1_26.bin (-2)
abr 20 08:50:14 SYSTEM kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1d40822c)
abr 20 08:50:15 SYSTEM kernel: nouveau 0000:01:00.0: DRM: Pointer to TMDS table invalid
abr 20 08:50:15 SYSTEM kernel: nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
abr 20 08:50:18 SYSTEM avahi-daemon[629]: chroot.c: open() failed: No such file or directory
abr 20 08:50:19 SYSTEM bluetoothd[604]: Failed to obtain handles for "Service Changed" characteristic
abr 20 08:50:19 SYSTEM bluetoothd[604]: Sap driver initialization failed.
abr 20 08:50:19 SYSTEM bluetoothd[604]: sap-server: Operation not permitted (1)
abr 20 08:50:24 SYSTEM kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1940822c)
abr 20 08:50:28 SYSTEM minissdpd[822]: setsockopt(udp, IP_ADD_MEMBERSHIP)(0.0.0.0): No such device
abr 20 08:50:39 SYSTEM kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1940822c)
abr 20 08:50:55 SYSTEM kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1940822c)
abr 20 08:51:06 SYSTEM kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1940822c)
abr 20 08:51:22 SYSTEM kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1940822c)
abr 20 08:51:51 SYSTEM kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1940822c)
abr 20 08:51:59 SYSTEM bluetoothd[604]: a2dp-sink profile connect failed for 00:00:00:03:9C:F0: Protocol not availab
abr 20 08:52:49 SYSTEM kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1940822c)
abr 20 08:53:13 SYSTEM kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1940822c)
abr 20 08:53:46 SYSTEM kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1940822c)
abr 20 09:02:58 SYSTEM kernel: nouveau 0000:01:00.0: priv: HUB0: 10ecc0 ffffffff (1940822c)
abr 20 09:03:01 SYSTEM kernel: watchdog: watchdog0: watchdog did not stop!

(I know there are additional issues, but I'm trying to go one by one, as I don't understand them)

The thing is: I followed the steps described for the original post, found the bin file on the firmware-misc-nonfree, installed the firmware-misc-nonfree package as described, and I get the same "i915 0000:00:02.0: firmware: failed to load i915/skl_dmc_ver1_26.bin" error.

I looked at the Debian Wiki data on firmware and found it a little sparse.

I'd appreciate if you could provide some orientation.

[stevepusser]

Since you're hijacking this thread, why don't you try the methods listed above to find what package contains that firmware file?

https://www.debian.org/distrib/packages#search_contents

Hint: it's the same exact package as before, too.

[cronomorfo]

Hi Steve,
I'm aware that it's in the same package. If you give my post a second look, you'll notice I managed to figure that out. I actually tried the same method than the original poster, and considering that the issue still stands, I thought it was reasonable to ask.

I'll try to be more explicit on the steps I took, which are the following:
1. I searched for the firmware using Whereisit. It was on firmware-misc-nonfree, as mentioned
2. I executed sudo aptitude install firmware-misc-nonfree, which, I think, should have the same effect than apt, as stated in the solutiojn above
3. I rebooted the OS

The issue persists, that error being the message "kernel: i915 0000:00:02.0: firmware: failed to load i915/skl_dmc_ver1_26.bin (-2)" shown during startup.

Is there any other step I may be missing here?

Also:

Since you're hijacking this thread

I thought it was a best practice to expand on a thread on a given issue when/if the thread is a method to solve a given issue when it may be helpful for future inquiries (such as when a given method does not seem to work). Since I'm new to the forum, please let me know if I'm at fault here.

[Head_on_a_Stick]

The issue persists, that error being the message

Is your video card actually working?

The device will go through a list of firmware and may fail with some but then succeed with another file, check the entire journal to get the full picture.

[cronomorfo]

Is your video card actually working?

I'm not sure on how to check that out.

The device will go through a list of firmware and may fail with some but then succeed with another file, check the entire journal to get the full picture.

The entire journal for today only is ~2k lines. Any option I should add to focus on what could be important?

[Head_on_a_Stick]

I'm not sure on how to check that out.

Code: Select all

# apt install vainfo
vainfo

Or maybe do some benchmarks.

Any option I should add to focus on what could be important?

Grep it for "i915", perhaps?

[cronomorfo]

vainfo

I'm not entirely sure on how to interpret the results, but here we go:

Code: Select all

~$ vainfo     
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.39 (libva 1.7.3)
vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 1.7.3
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Simple            : VAEntrypointEncSlice
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointEncSliceLP
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointEncSliceLP
      VAProfileH264MultiviewHigh      : VAEntrypointVLD
      VAProfileH264MultiviewHigh      : VAEntrypointEncSlice
      VAProfileH264StereoHigh         : VAEntrypointVLD
      VAProfileH264StereoHigh         : VAEntrypointEncSlice
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointEncPicture
      VAProfileVP8Version0_3          : VAEntrypointVLD
      VAProfileVP8Version0_3          : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice

Grep it to i915, perhaps?

Got it:

Code: Select all

sudo journalctl -b | grep i915
abr 20 09:03:45 nua kernel: i915 0000:00:02.0: firmware: direct-loading firmware i915/skl_dmc_ver1_26.bin
abr 20 09:03:45 nua kernel: [drm] Finished loading i915/skl_dmc_ver1_26.bin (v1.26)
abr 20 09:03:45 nua kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
abr 20 09:03:45 nua kernel: [drm] Initialized i915 1.6.0 20160919 for 0000:00:02.0 on minor 1
abr 20 09:03:45 nua kernel: i915 0000:00:02.0: fb0: inteldrmfb frame buffer device

Looks to me that it's actually running, but it's strange. Perhaps the OS managed to find the firmware after booting?
Well, if that's the case, thanks for your patience and help.

[Head_on_a_Stick]

I'm not entirely sure on how to interpret the results, but here we go

Yours is much longer than mine

[srz11]

By any chance did you install a backport kernel? If you are running a backport kernel you also need to install the backport

Code: Select all

firmware-misc-nonfree

package:

Code: Select all

apt -t bullseye-backports install firmware-misc-nonfree

I was stumped by the same issue until I figured this out. After the update I now see:

Code: Select all

sudo cat /sys/kernel/debug/dri/0/i915_dmc_info

fw loaded: yes
path: i915/kbl_dmc_ver1_04.bin
Pipe A fw support: no
Pipe A fw loaded: no
Pipe B fw support: no
Pipe B fw loaded: no
version: 1.4

[sunrat]

@srz11 you realise you replied to a 5 year old topic? This is generally discouraged.
What you say may be true for Bullseye, but for current Bookworm there is no backports version of firmware-misc-nonfree.