Missing firmware for Intel VPU on Intel Meteor Lake platforms
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
HWE Next |
New
|
Undecided
|
Unassigned | |||
linux-firmware (Ubuntu) | Status tracked in Mantic | |||||
Jammy |
Fix Released
|
High
|
You-Sheng Yang | |||
Mantic |
Fix Released
|
High
|
You-Sheng Yang |
Bug Description
[SRU Justification]
[Impact]
Missing firmware blobs for Intel VPU support on Intel Meteor Lake platform.
intel_vpu 0000:00:0b.0: enabling device (0000 -> 0002)
intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2
intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2
intel_vpu 0000:00:0b.0: Failed to initialize VPU device: -2
intel_vpu: probe of 0000:00:0b.0 failed with error -2
[Fix]
Upstream Intel VPU linux driver project https:/
[Test Case]
Intel VPU support on Intel Meteor Lake platform is part of the OpenVino framework. It takes many more other components to be installed before VPU on MTL may release its power. Here we simply test the firwmare can be found and loaded.
[Where problems could occur]
Intel VPU firmware is to be loaded by kernel but used by user land frameworks. While OpenVino is not (yet?) supported natively, this firmware blob alone has no observerible effect yet.
[Other Info]
While MTL is supported by v6.5 kernel or above, only oem-6.5 and Mantic are nominated by default.
========== original bug report ==========
Intel Meteor Lake platform supports VPU natively and the driver has been upstreamed in v6.3. A few more steps to enable VPU support in https:/
[ 68.602028] intel_vpu 0000:00:0b.0: enabling device (0000 -> 0002)
[ 68.604010] intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2
[ 68.604013] intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2
[ 68.604263] intel_vpu 0000:00:0b.0: Failed to initialize VPU device: -2
[ 68.604272] intel_vpu: probe of 0000:00:0b.0 failed with error -2
The firmware blob can be retrieved by `git lfs pull` from a clone of aforementioned driver repository. The install path would be /lib/firmware/
tags: | added: kern-7772 |
description: | updated |
description: | updated |
tags: | added: verification-needed-jammy |
While this targets linux-oem- 6.5/jammy, linux-firmware/ jammy is nominated.