[Bug 2149806] Re: Huawei MateBook X Pro 2024 - integrated IPU6 camera fails: INT3472:02 "Failed to get GPIO", no sensor appears in media graph

** Description changed: On a Huawei MateBook X Pro 2024, the integrated MIPI/IPU6 webcam does not function on a Ubuntu 24.04-based system. - The IPU6 stack loads, userspace components work, and a loopback camera - device is created, but the physical camera sensor never appears in the - media graph. The key kernel error is: + ## System info + - **Laptop**: Huawei MateBook X Pro 2024 + - **CPU**: Intel Core Ultra 7 155H (Meteor Lake) + - **OS**: Zorin OS 18.1 Pro (Ubuntu 24.04 base) + - **Kernels tested**: + - `6.17.0-22-generic` + - `6.17.0-1017-oem` + The IPU6 stack loads, userspace components work, and a loopback camera device is created, but the physical camera sensor never + appears in the media graph. + + The key kernel error is: + + ```text int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 - This reproduces on both: - - - 6.17.0-22-generic - - 6.17.0-1017-oem - - ## System - - - Laptop: Huawei MateBook X Pro 2024 - - CPU: Intel Core Ultra 7 155H - - OS: Zorin OS 18.1 Pro (Ubuntu 24.04 based) - - ## What works + ## What works The following components are installed and functional: - gstreamer1.0-icamera - libcamhal-ipu6epmtl - v4l2-relayd - IPU6 kernel modules A userspace-facing virtual camera is created as: - Intel MIPI Camera on /dev/video0 - gst-inspect-1.0 icamerasrc succeeds. + Also: - ## What fails + - gst-inspect-1.0 icamerasrc succeeds + + ## What fails The integrated sensor is never brought up. In media-ctl -p -d /dev/media0, only: - Intel IPU6 CSI2 0..5 - Intel IPU6 ISYS Capture 0..47 appear. No actual sensor entity appears (for example no ov01a10, ov01a1s, ov13b10, hi556, etc.). As a result, /dev/video0 exists but only outputs black frames. - ## dmesg + ## dmesg int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE intel-ipu6 0000:00:05.0: CSE authenticate_run done intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 - ## media-ctl observation + ## Possible sensor information from ACPI tables + + I still cannot identify the physically probed sensor with certainty, because no sensor entity appears in media-ctl and the failure + happens before sensor probe completes. + + However, scanning the ACPI tables shows that the firmware contains + references to multiple OmniVision sensor IDs, including: + + - OVTI01AS + - OVTI01A0 + - OVTI13B1 + + and also camera-related strings such as: + + - CAM0 + - CAM1 + - CAMERA_V1P8S1 + - CAMERA_V3P3S1 + + So the system firmware appears to describe at least one OmniVision-based camera path, but the exact sensor model cannot currently be + confirmed from Linux. + + ## media-ctl observation media-ctl -p -d /dev/media0 shows only CSI2 and ISYS capture entities, but no camera sensor entity at all. - ## Additional notes + ## Conclusion - I also tested the OEM kernel (6.17.0-1017-oem) and the failure is - unchanged, including the same INT3472:02 GPIO error. - - This looks like a platform-specific INT3472 / GPIO / ACPI issue - preventing the camera sensor from being initialized. + This reproduces unchanged on both tested kernels and looks like a platform-specific INT3472 / GPIO / ACPI issue preventing the + camera sensor from being initialized. ** Description changed: On a Huawei MateBook X Pro 2024, the integrated MIPI/IPU6 webcam does not function on a Ubuntu 24.04-based system. - ## System info - - **Laptop**: Huawei MateBook X Pro 2024 - - **CPU**: Intel Core Ultra 7 155H (Meteor Lake) - - **OS**: Zorin OS 18.1 Pro (Ubuntu 24.04 base) - - **Kernels tested**: - - `6.17.0-22-generic` - - `6.17.0-1017-oem` +   ## System info +   - **Laptop**: Huawei MateBook X Pro 2024 +   - **CPU**: Intel Core Ultra 7 155H (Meteor Lake) +   - **OS**: Zorin OS 18.1 Pro (Ubuntu 24.04 base) +   - **Kernels tested**: +     - `6.17.0-22-generic` +     - `6.17.0-1017-oem` - The IPU6 stack loads, userspace components work, and a loopback camera device is created, but the physical camera sensor never - appears in the media graph. +   The IPU6 stack loads, userspace components work, and a loopback camera + device is created, but the physical camera sensor never appears in the + media graph. - The key kernel error is: +   The key kernel error is: - ```text - int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO - int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 +   int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO +   int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 - ## What works + ## What works - The following components are installed and functional: + The following components are installed and functional: - - gstreamer1.0-icamera - - libcamhal-ipu6epmtl - - v4l2-relayd - - IPU6 kernel modules +   - gstreamer1.0-icamera +   - libcamhal-ipu6epmtl +   - v4l2-relayd +   - IPU6 kernel modules - A userspace-facing virtual camera is created as: + A userspace-facing virtual camera is created as: - - Intel MIPI Camera on /dev/video0 +   - Intel MIPI Camera on /dev/video0 - Also: + Also: - - gst-inspect-1.0 icamerasrc succeeds +   - gst-inspect-1.0 icamerasrc succeeds - ## What fails + ## What fails - The integrated sensor is never brought up. In media-ctl -p -d + The integrated sensor is never brought up. In media-ctl -p -d /dev/media0, only: - - Intel IPU6 CSI2 0..5 - - Intel IPU6 ISYS Capture 0..47 +   - Intel IPU6 CSI2 0..5 +   - Intel IPU6 ISYS Capture 0..47 - appear. + appear. - No actual sensor entity appears (for example no ov01a10, ov01a1s, + No actual sensor entity appears (for example no ov01a10, ov01a1s, ov13b10, hi556, etc.). - As a result, /dev/video0 exists but only outputs black frames. + As a result, /dev/video0 exists but only outputs black frames. - ## dmesg + ## dmesg - int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO - int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 - intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE - intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE - intel-ipu6 0000:00:05.0: CSE authenticate_run done - intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 +   int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO +   int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 +   intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE +   intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE +   intel-ipu6 0000:00:05.0: CSE authenticate_run done +   intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 - ## Possible sensor information from ACPI tables + ## Possible sensor information from ACPI tables - I still cannot identify the physically probed sensor with certainty, because no sensor entity appears in media-ctl and the failure - happens before sensor probe completes. + I still cannot identify the physically probed sensor with certainty, + because no sensor entity appears in media-ctl and the failure happens + before sensor probe completes. - However, scanning the ACPI tables shows that the firmware contains + However, scanning the ACPI tables shows that the firmware contains references to multiple OmniVision sensor IDs, including: - - OVTI01AS - - OVTI01A0 - - OVTI13B1 +   - OVTI01AS +   - OVTI01A0 +   - OVTI13B1 - and also camera-related strings such as: + and also camera-related strings such as: - - CAM0 - - CAM1 - - CAMERA_V1P8S1 - - CAMERA_V3P3S1 +   - CAM0 +   - CAM1 +   - CAMERA_V1P8S1 +   - CAMERA_V3P3S1 - So the system firmware appears to describe at least one OmniVision-based camera path, but the exact sensor model cannot currently be - confirmed from Linux. + So the system firmware appears to describe at least one OmniVision-based + camera path, but the exact sensor model cannot currently be confirmed + from Linux. - ## media-ctl observation + ## media-ctl observation - media-ctl -p -d /dev/media0 shows only CSI2 and ISYS capture entities, +   media-ctl -p -d /dev/media0 shows only CSI2 and ISYS capture entities, but no camera sensor entity at all. - ## Conclusion + ## Conclusion - This reproduces unchanged on both tested kernels and looks like a platform-specific INT3472 / GPIO / ACPI issue preventing the - camera sensor from being initialized. + This reproduces unchanged on both tested kernels and looks like a + platform-specific INT3472 / GPIO / ACPI issue preventing the camera + sensor from being initialized. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149806 Title: Huawei MateBook X Pro 2024 - integrated IPU6 camera fails: INT3472:02 "Failed to get GPIO", no sensor appears in media graph Status in linux package in Ubuntu: New Bug description: On a Huawei MateBook X Pro 2024, the integrated MIPI/IPU6 webcam does not function on a Ubuntu 24.04-based system.   ## System info   - **Laptop**: Huawei MateBook X Pro 2024   - **CPU**: Intel Core Ultra 7 155H (Meteor Lake)   - **OS**: Zorin OS 18.1 Pro (Ubuntu 24.04 base)   - **Kernels tested**:     - `6.17.0-22-generic`     - `6.17.0-1017-oem`   The IPU6 stack loads, userspace components work, and a loopback camera device is created, but the physical camera sensor never appears in the media graph.   The key kernel error is:   int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO   int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16 ## What works The following components are installed and functional:   - gstreamer1.0-icamera   - libcamhal-ipu6epmtl   - v4l2-relayd   - IPU6 kernel modules A userspace-facing virtual camera is created as:   - Intel MIPI Camera on /dev/video0 Also:   - gst-inspect-1.0 icamerasrc succeeds ## What fails The integrated sensor is never brought up. In media-ctl -p -d /dev/media0, only:   - Intel IPU6 CSI2 0..5   - Intel IPU6 ISYS Capture 0..47 appear. No actual sensor entity appears (for example no ov01a10, ov01a1s, ov13b10, hi556, etc.). As a result, /dev/video0 exists but only outputs black frames. ## dmesg   int3472-discrete INT3472:02: error -EBUSY: Failed to get GPIO   int3472-discrete INT3472:02: probe with driver int3472-discrete failed with error -16   intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE   intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE   intel-ipu6 0000:00:05.0: CSE authenticate_run done   intel-ipu6 0000:00:05.0: IPU6-v4[7d19] hardware version 6 ## Possible sensor information from ACPI tables I still cannot identify the physically probed sensor with certainty, because no sensor entity appears in media-ctl and the failure happens before sensor probe completes. However, scanning the ACPI tables shows that the firmware contains references to multiple OmniVision sensor IDs, including:   - OVTI01AS   - OVTI01A0   - OVTI13B1 and also camera-related strings such as:   - CAM0   - CAM1   - CAMERA_V1P8S1   - CAMERA_V3P3S1 So the system firmware appears to describe at least one OmniVision- based camera path, but the exact sensor model cannot currently be confirmed from Linux. ## media-ctl observation   media-ctl -p -d /dev/media0 shows only CSI2 and ISYS capture entities, but no camera sensor entity at all. ## Conclusion This reproduces unchanged on both tested kernels and looks like a platform-specific INT3472 / GPIO / ACPI issue preventing the camera sensor from being initialized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149806/+subscriptions