**Hardware/environment (for the record, since the bug report left the model field blank):** ``` Model: Dell XPS 13 9350 CPU: Intel(R) Core(TM) Ultra 7 258V (Lunar Lake) BIOS: 1.22.0 (2026-06-01) Camera: Intel Lunar Lake IPU [8086:645d] (rev 04) at 00:05.0, subsystem Dell 1028:0dab Sensor: OV02C10 (OVTI02C1) OS: Ubuntu 26.04.1 LTS ```
**Kernels tested (both fail identically):** ``` 7.0.0-1013-oem (linux-image-7.0.0-1013-oem 7.0.0-1013.13) 7.0.0-31-generic (linux-image-7.0.0-31-generic 7.0.0-31.31, generic-hwe-26.04 flavor) ``` **Relevant package versions on this system:** ``` linux-modules-ipu7-generic-hwe-26.04 7.0.0-31.31+2 linux-modules-usbio-generic-hwe-26.04 7.0.0-31.31+2 linux-main-modules-ipu7-7.0.0-31-generic 7.0.0-31.31+2 linux-main-modules-usbio-7.0.0-31-generic 7.0.0-31.31+2 libcamhal-ipu7x 0~git202510170946.ec24db2-1~ubuntu24.04.1 libia-* (ipu7x AIQ/AIC stack) 0~git202509280950.09ccd02-1~ubuntu24.04.1 ``` On `7.0.0-1013-oem`, `modinfo intel_ipu7`/`modinfo gpio_usbio` both report `vermagic: 7.0.0-1013-oem` — confirmed these are built for the running kernel, not stale/mismatched modules from another ABI. **Test 1 — `7.0.0-1013-oem`, cold boot (Sep 16):** ``` intel_ipu7: module is from the staging directory, the quality is unknown, you have been warned. intel-ipu7 0000:00:05.0: Found supported sensor OVTI02C1:00 intel-ipu7 0000:00:05.0: Connected 1 cameras int3472-discrete INT3472:00: cannot find GPIO chip INTC10B5:00, deferring (repeats ~20x, ~1s) usbcore: registered new interface driver usbio-bridge gpio_usbio.usbio-gpio usbio.usbio-gpio.0: [Firmware Bug]: GPIO 4 is not in FW pins bitmap int3472-discrete INT3472:00: GPIO type 0x02 unknown; the sensor may not work ``` Webcam: black frames, no activity LED. **Test 2 — `7.0.0-1013-oem`, later boot (Sep 21, 17:28):** identical sequence and outcome to Test 1. **Test 3 — `7.0.0-31-generic` (Sep 21, 17:37), to rule out an oem-vs-generic backport gap:** ``` intel_ipu7: module is from the staging directory, the quality is unknown, you have been warned. intel-ipu7 0000:00:05.0: Found supported sensor OVTI02C1:00 ov02c10: loading out-of-tree module taints kernel. int3472-discrete INT3472:00: cannot find GPIO chip INTC10B5:00, deferring (repeats ~30x, ~2s) usbcore: registered new interface driver usbio-bridge intel_ipu7_isys: module is from the staging directory, the quality is unknown, you have been warned. intel_ipu7_psys.psys intel_ipu7.psys.40: IPU psys probe done. int3472-discrete INT3472:00: GPIO type 0x02 unknown; the sensor may not work ``` Webcam: still black frames, same failure. **Analysis:** Camera fails identically on both kernel flavors, which rules out a simple "oem hasn't picked up a fix generic already has" explanation. The `[Firmware Bug]: GPIO 4 is not in FW pins bitmap` message from `gpio_usbio` appeared on both `oem` boots but not on the `generic` boot — the exact deferred-probe timing/ordering varies boot to boot (1s vs 2s of retries, extra probe-order-dependent lines like the `ov02c10` taint notice and the `psys probe done` line shifting position), so that message looks like a secondary, nondeterministic symptom rather than the root cause. The one line that is **100% consistent across all three boots, both kernel flavors**: ``` int3472-discrete INT3472:00: GPIO type 0x02 unknown; the sensor may not work ``` That's the actual load-bearing failure: `int3472-discrete` cannot resolve/handle a GPIO of type `0x02` for this sensor's power/reset line on this platform, regardless of exactly how the underlying `gpio_usbio` pin request fails underneath it, and regardless of kernel build. Given both `intel_ipu7`/`intel_ipu7_isys` are loaded from staging and this is very recent Lunar Lake IPU7 hardware-enablement code, my best guess is either (a) `int3472-discrete`'s GPIO-type handling doesn't yet have a case for whatever value `0x02` represents when the GPIO provider is a USBIO-backed controller (as opposed to the older native-platform GPIO controllers this driver presumably originally targeted), or (b) this laptop's ACPI tables report a GPIO type value the driver was never taught to expect. Someone with access to the `int3472-discrete` source and this platform's decoded ACPI GPIO resource list (`_DSM`/`_CRS` for `INT3472:00`) would be able to tell which. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167477 Title: [Firmware Bug]: GPIO 4 is not in FW pins bitmap + GPIO type 0x02 unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-7.0/+bug/2167477/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
