intel / intel/ipu7-camera-hal

Regression on IPU7 / OV02C10 (Lunar Lake): camera works on HAL e4a08b1, black frames on b94eee8

Open
#52 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
10
Forks
26
Avg merge
11h 47m
Merged PRs (30d)
1

Description

**Hardware**
- Dell XPS 13 9350 (2024), Intel Core Ultra 5 226V (Lunar Lake)
- Sensor: OmniVision OV02C10 (ACPI OVTI02C1) via Intel IPU7 (PCI 8086:645d)

**OS / kernel**
- Ubuntu 24.04, kernel 6.17.0-1025-oem

**Summary**
A userspace HAL/imaging-lib snapshot bump regressed the camera. The sensor still
enumerates (kernel detects it, /dev/video0 loopback present) but every app receives
black frames — the icamerasrc/v4l2-relayd pipeline no longer delivers.

**Last good → first bad** (packages from ppa:oem-solutions-group/intel-ipu7)
- libcamhal-ipu7x: 0~git202605200138.e4a08b1 (works)
→ 0~git202606180621.b94eee8 (black frames)
- libia-* set: 0~git202604230632.cead732 (works)
→ 0~git202606170948.d235697 (black frames)
So the regression is in ipu7-camera-hal between e4a08b1 and b94eee8,
and/or the ipu7-camera-bins / libia-* set between cead732 and d235697.

**Kernel side unchanged and healthy across the regression**
dmesg: "intel-ipu7 ...: Found supported sensor OVTI02C1:00" / "Connected 1 cameras".
Firmware authenticates fine. No kernel update was involved.

**Recovery**
Reverting the whole *ipu7x* userspace set to Dell's validated somerville build
(libcamhal-ipu7x 0~git202510170946.ec24db2, libia-* 0~git202509280950) restores
a working camera on the same kernel.

Contributor guide

Open the contributing guide

Research direction

Reproduce the black frames on the Dell XPS 13 with OV02C10 using the icamerasrc/v4l2-relayd pipeline and confirm sensor enumeration remains healthy. Compare ipu7-camera-hal from e4a08b1 to b94eee8 and the libia/ipu7-camera-bins sets from cead732 to d235697, then narrow the regression to the responsible userspace change. Done means the affected package set delivers non-black frames without reverting the kernel.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.