Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
XPS 14 (Panther Lake): Windows Hello IR camera (Himax HM1092) has no Linux driver
Reported by jorgemanrubia · filed Aug 27, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
The XPS 14 (DA14260, Panther Lake) has two cameras. The RGB one works — OV08X40, mainline driver, Intel IPU7 stack. The Windows Hello IR one doesn't work at all. It's a Himax HM1092 (ACPI HIMX1092), and there's no Linux driver for it anywhere. Not mainline. Not intel/ipu6-drivers (it has the siblings — HM11B1, HM2170, HM2172 — just not this one). Not intel/ipu7-drivers. Same wall others are hitting on Dell machines: intel/ipu7-drivers#26.
I tried writing the driver myself, adapted from the sibling Himax drivers. It compiles, binds, and powers the INT3472 PMICs — but the sensor never answers on i2c. My read: power or ownership is gated by the Intel CVS controller (INTC10E1), not INT3472 alone. And the HM1092 init/mode registers aren't public, so even a powered sensor can't produce frames.
Two things would fix this, in order:
- Dell/Intel upstream an HM1092 driver plus the one-line ipu-bridge entry for the
HIMX1092HID. They've done exactly this for the sibling parts. - Short of that: the register-level datasheet/init sequence and the CVS power-on sequence. I'll finish the driver and submit it upstream myself.
cc @spencerbull — you suspected a Panther Lake MIPI enablement gap not yet tackled upstream, and asked for this issue. Here it is. Happy to test on real hardware and share everything: driver source, ACPI findings, logs.
Omarchy 4.0.0-1, kernel 7.1.8-arch1-2-ptl.
View raw text
The XPS 14 (DA14260, Panther Lake) has two cameras. The RGB one works — OV08X40, mainline driver, Intel IPU7 stack. The Windows Hello IR one doesn't work at all. It's a Himax HM1092 (ACPI `HIMX1092`), and there's no Linux driver for it anywhere. Not mainline. Not intel/ipu6-drivers (it has the siblings — HM11B1, HM2170, HM2172 — just not this one). Not intel/ipu7-drivers. Same wall others are hitting on Dell machines: intel/ipu7-drivers#26. I tried writing the driver myself, adapted from the sibling Himax drivers. It compiles, binds, and powers the INT3472 PMICs — but the sensor never answers on i2c. My read: power or ownership is gated by the Intel CVS controller (`INTC10E1`), not INT3472 alone. And the HM1092 init/mode registers aren't public, so even a powered sensor can't produce frames. Two things would fix this, in order: 1. Dell/Intel upstream an HM1092 driver plus the one-line ipu-bridge entry for the `HIMX1092` HID. They've done exactly this for the sibling parts. 2. Short of that: the register-level datasheet/init sequence and the CVS power-on sequence. I'll finish the driver and submit it upstream myself. cc @spencerbull — you suspected a Panther Lake MIPI enablement gap not yet tackled upstream, and asked for this issue. Here it is. Happy to test on real hardware and share everything: driver source, ACPI findings, logs. Omarchy 4.0.0-1, kernel 7.1.8-arch1-2-ptl.
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 09:37 UTC