Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-383GitHub issuePublicDecided· Out of scope

Galaxy Book6 Pro (NP960XJG): IPU7 webcam is SSLC2000/SC200PC, intel-ipu7-camera assumes OV08X40

Reported by xmgx01 · filed Sep 18, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

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

Galaxy Book6 Pro (NP960XJG): IPU7 webcam is SSLC2000/SC200PC, intel-ipu7-camera assumes OV08X40revision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Samsung Galaxy Book6 Pro NP960XJG-KG1US (PAMB), Intel Core Ultra X7 358H (Panther Lake) + Arc B390, Omarchy 4.0.4-1

What's wrong?

Summary

The built-in webcam on a Samsung Galaxy Book6 Pro never produces frames. Omarchy detects Intel IPU7 and installs the Dell XPS intel-ipu7-camera stack (ov08x40 + icamerasrc device-name=ov08x40-uf + v4l2-relayd@ipu7), but this machine's real sensor is a Samsung SC200PC (ACPI HID SSLC2000), not OmniVision OV08X40.

There is no Linux driver for SSLC2000. ipu-bridge does not list that HID. The media graph has IPU7 CSI/ISYS nodes and no sensor entity. Apps see "Hardware ISP Camera" (/dev/video50) because v4l2loopback creates it; v4l2-relayd cannot start icamerasrc because CamHAL reports no sensors.

This is not the XPS 7.2.x webcam regression fixed in 4.0.4, and it is not the ThinkPad Gen 14 OVTI08F4 _STA=0 case in #6000. The same "no subdev found in graph" failure is present on stock linux 7.2.3-arch1-3 (boot from 2026-08-05) and on linux-omarchy 7.2.5-3.

Hardware / system

  • Machine: Samsung Galaxy Book6 Pro — PAMB (NP960XJG-KG1US, SKU PAMB-960XJG-PTLH-0)
  • BIOS: PAMB.1.5.74.371 (2026-04-09)
  • CPU: Intel Core Ultra X7 358H (Panther Lake)
  • GPU: Intel Arc B390 (xe)
  • IPU: 00:05.0 [8086:b05d] intel-ipu7, firmware intel/ipu/ipu7ptl_fw.bin
  • Real sensor: Samsung SC200PC, ACPI SSLC2000:00 at \_SB_.LNK0, I2C i2c-SSLC2000:00 on bus 3 (i2c_designware.3), privacy LED SSLC2000_00::privacy_led under INT3472:00
  • Placeholder ACPI: OVTI08F4:00–:04 all _STA=0
  • Omarchy: 4.0.4-1
  • Kernels tested:
  • linux 7.2.3.arch1-3 — intel-ipu7 … no subdev found in graph
  • linux-omarchy 7.2.5-3 — same
  • Packages: intel-ipu7-camera 1.0.6-2, v4l2-relayd 0.2.0-2.2, v4l2loopback-dkms 0.15.4-2, jsoncpp 1.9.8-1 (libjsoncpp.so.27; HAL loads)

Debug log: https://gist.github.com/xmgx01/a74ea4e01176caa1fa6d28a184b54888

Symptoms

$ cat /sys/bus/acpi/devices/SSLC2000:00/status
15

$ cat /sys/bus/acpi/devices/SSLC2000:00/path
\_SB_.LNK0

$ cat /sys/bus/i2c/devices/i2c-SSLC2000:00/name
SSLC2000:00

$ ls /sys/bus/i2c/devices/i2c-SSLC2000:00/driver
# no driver bound

$ for d in /sys/bus/acpi/devices/OVTI08F4:*; do
    echo "$(basename $d) status=$(cat $d/status) path=$(cat $d/path)"
  done
OVTI08F4:00 status=0 path=\_SB_.LNK1
OVTI08F4:01 status=0 path=\_SB_.LNK2
OVTI08F4:02 status=0 path=\_SB_.LNK3
OVTI08F4:03 status=0 path=\_SB_.LNK4
OVTI08F4:04 status=0 path=\_SB_.LNK5

$ ls /sys/bus/i2c/drivers/ov08x40/
bind  module  uevent  unbind    # loaded by camera-init, never bound

$ v4l2-ctl --list-devices
ipu7 (PCI:0000:00:05.0):
        /dev/media0

Hardware ISP Camera (platform:v4l2loopback-050):
        /dev/video50

media-ctl -d /dev/media0 -p shows Intel IPU7 CSI2 / ISYS Capture nodes only. No SSLC2000 / ov08x40 sensor entity.

$ journalctl -b -g 'intel-ipu7|parseSensors'
intel-ipu7 0000:00:05.0: CSE authenticate_run done
intel-ipu7 0000:00:05.0: no subdev found in graph
CamHAL[INF] CameraParserInvoker: getAvailableSensors, Found IPU: IPU7
CamHAL[WAR] CameraParserInvoker: parseSensors: No sensors available

v4l2-relayd@ipu7 is running with:

icamerasrc device-name=ov08x40-uf sharpness=80 ev=-1 saturation=10 ! videoflip method=rotate-180

and repeatedly logs gst_element_set_state: assertion 'GST_IS_ELEMENT (element)' failed.

camera-init.service is hardcoded:

ExecStart=/bin/bash -c "modprobe intel_cvs && sleep 2 && modprobe ov08x40 && modprobe v4l2loopback"

ipu-bridge supported ACPI IDs include OVTI08F4 and other OmniVision HIDs. SSLC2000 is not among them.

What I tried / ruled out

  • Restarting camera-init.service and [email protected] — no change.
  • Stock Arch linux 7.2.3.arch1-3 vs linux-omarchy 7.2.5-3 — same no subdev found in graph on both (journal from 2026-08-05 onward).
  • The 4.0.4 jsoncpp/libjsoncpp.so.26 HAL break from #11358 is fixed here: ldd /usr/lib/libcamhal/plugins/ipu75xa.so resolves libjsoncpp.so.27. CamHAL still finds no sensors.
  • Forcing ov08x40 onto this I2C node is not a workaround. The chip ID at 0x300a is 0x2000 (SC200PC), OmniVision-style map but not OV08X40.

Root cause

  1. Missing upstream sensor driver. Same laptop family is already filed upstream: intel/ipu7-drivers#62 (Galaxy Book6 Pro NP960XJG, SSLC2000, I2C 0x36 bus 3, chip ID 0x2000). Related: intel/vision-drivers#39 (Book6 Ultra).
  2. Omarchy IPU7 install path is XPS/OV08X40-only. Presence of IPU7 + disabled OVTI08F4 ACPI nodes is enough to install intel-ipu7-camera, start camera-init/v4l2-relayd@ipu7, and advertise /dev/video50. On this Samsung the OV08X40 nodes are placeholders (_STA=0); the live device is SSLC2000. Users get a camera picker entry that can never start.

Suggested direction

A full working camera needs an SC200PC/SSLC2000 v4l2 subdev driver plus HAL/relayd config (not ov08x40-uf). Until that exists, Omarchy can still:

  1. Detect SSLC2000 (and/or DMI Galaxy Book6) separately from OVTI08F4 with _STA=15.
  2. Avoid installing/enabling the XPS ov08x40 relay so browsers do not list a dead "Hardware ISP Camera".
  3. Track Book6 as a known-unsupported IPU7 sensor, similar to other hardware-gated camera packages.

Happy to test patches on this machine.

View raw text
### System details

Samsung Galaxy Book6 Pro NP960XJG-KG1US (PAMB), Intel Core Ultra X7 358H (Panther Lake) + Arc B390, Omarchy 4.0.4-1

### What's wrong?

## Summary

The built-in webcam on a Samsung Galaxy Book6 Pro never produces frames. Omarchy detects Intel IPU7 and installs the Dell XPS `intel-ipu7-camera` stack (`ov08x40` + `icamerasrc device-name=ov08x40-uf` + `v4l2-relayd@ipu7`), but this machine's real sensor is a Samsung SC200PC (`ACPI HID SSLC2000`), not OmniVision OV08X40.

There is no Linux driver for `SSLC2000`. `ipu-bridge` does not list that HID. The media graph has IPU7 CSI/ISYS nodes and no sensor entity. Apps see "Hardware ISP Camera" (`/dev/video50`) because `v4l2loopback` creates it; `v4l2-relayd` cannot start `icamerasrc` because CamHAL reports no sensors.

This is **not** the XPS 7.2.x webcam regression fixed in 4.0.4, and it is **not** the ThinkPad Gen 14 `OVTI08F4` `_STA=0` case in #6000. The same "no subdev found in graph" failure is present on stock `linux 7.2.3-arch1-3` (boot from 2026-08-05) and on `linux-omarchy 7.2.5-3`.

## Hardware / system

- Machine: Samsung Galaxy Book6 Pro — PAMB (`NP960XJG-KG1US`, SKU `PAMB-960XJG-PTLH-0`)
- BIOS: `PAMB.1.5.74.371` (2026-04-09)
- CPU: Intel Core Ultra X7 358H (Panther Lake)
- GPU: Intel Arc B390 (`xe`)
- IPU: `00:05.0` `[8086:b05d]` `intel-ipu7`, firmware `intel/ipu/ipu7ptl_fw.bin`
- Real sensor: Samsung SC200PC, ACPI `SSLC2000:00` at `\_SB_.LNK0`, I2C `i2c-SSLC2000:00` on bus 3 (`i2c_designware.3`), privacy LED `SSLC2000_00::privacy_led` under `INT3472:00`
- Placeholder ACPI: `OVTI08F4:00`–`:04` all `_STA=0`
- Omarchy: `4.0.4-1`
- Kernels tested:
  - `linux 7.2.3.arch1-3` — `intel-ipu7 … no subdev found in graph`
  - `linux-omarchy 7.2.5-3` — same
- Packages: `intel-ipu7-camera 1.0.6-2`, `v4l2-relayd 0.2.0-2.2`, `v4l2loopback-dkms 0.15.4-2`, `jsoncpp 1.9.8-1` (`libjsoncpp.so.27`; HAL loads)

Debug log: https://gist.github.com/xmgx01/a74ea4e01176caa1fa6d28a184b54888

## Symptoms

```
$ cat /sys/bus/acpi/devices/SSLC2000:00/status
15

$ cat /sys/bus/acpi/devices/SSLC2000:00/path
\_SB_.LNK0

$ cat /sys/bus/i2c/devices/i2c-SSLC2000:00/name
SSLC2000:00

$ ls /sys/bus/i2c/devices/i2c-SSLC2000:00/driver
# no driver bound

$ for d in /sys/bus/acpi/devices/OVTI08F4:*; do
    echo "$(basename $d) status=$(cat $d/status) path=$(cat $d/path)"
  done
OVTI08F4:00 status=0 path=\_SB_.LNK1
OVTI08F4:01 status=0 path=\_SB_.LNK2
OVTI08F4:02 status=0 path=\_SB_.LNK3
OVTI08F4:03 status=0 path=\_SB_.LNK4
OVTI08F4:04 status=0 path=\_SB_.LNK5

$ ls /sys/bus/i2c/drivers/ov08x40/
bind  module  uevent  unbind    # loaded by camera-init, never bound

$ v4l2-ctl --list-devices
ipu7 (PCI:0000:00:05.0):
        /dev/media0

Hardware ISP Camera (platform:v4l2loopback-050):
        /dev/video50
```

`media-ctl -d /dev/media0 -p` shows Intel IPU7 CSI2 / ISYS Capture nodes only. No `SSLC2000` / `ov08x40` sensor entity.

```
$ journalctl -b -g 'intel-ipu7|parseSensors'
intel-ipu7 0000:00:05.0: CSE authenticate_run done
intel-ipu7 0000:00:05.0: no subdev found in graph
CamHAL[INF] CameraParserInvoker: getAvailableSensors, Found IPU: IPU7
CamHAL[WAR] CameraParserInvoker: parseSensors: No sensors available
```

`v4l2-relayd@ipu7` is running with:

```
icamerasrc device-name=ov08x40-uf sharpness=80 ev=-1 saturation=10 ! videoflip method=rotate-180
```

and repeatedly logs `gst_element_set_state: assertion 'GST_IS_ELEMENT (element)' failed`.

`camera-init.service` is hardcoded:

```
ExecStart=/bin/bash -c "modprobe intel_cvs && sleep 2 && modprobe ov08x40 && modprobe v4l2loopback"
```

`ipu-bridge` supported ACPI IDs include `OVTI08F4` and other OmniVision HIDs. `SSLC2000` is not among them.

## What I tried / ruled out

- Restarting `camera-init.service` and `[email protected]` — no change.
- Stock Arch `linux 7.2.3.arch1-3` vs `linux-omarchy 7.2.5-3` — same `no subdev found in graph` on both (journal from 2026-08-05 onward).
- The 4.0.4 jsoncpp/`libjsoncpp.so.26` HAL break from #11358 is **fixed** here: `ldd /usr/lib/libcamhal/plugins/ipu75xa.so` resolves `libjsoncpp.so.27`. CamHAL still finds no sensors.
- Forcing `ov08x40` onto this I2C node is not a workaround. The chip ID at `0x300a` is `0x2000` (SC200PC), OmniVision-style map but not OV08X40.

## Root cause

1. **Missing upstream sensor driver.** Same laptop family is already filed upstream: [intel/ipu7-drivers#62](https://github.com/intel/ipu7-drivers/issues/62) (Galaxy Book6 Pro `NP960XJG`, `SSLC2000`, I2C `0x36` bus 3, chip ID `0x2000`). Related: [intel/vision-drivers#39](https://github.com/intel/vision-drivers/issues/39) (Book6 Ultra).
2. **Omarchy IPU7 install path is XPS/OV08X40-only.** Presence of IPU7 + disabled `OVTI08F4` ACPI nodes is enough to install `intel-ipu7-camera`, start `camera-init`/`v4l2-relayd@ipu7`, and advertise `/dev/video50`. On this Samsung the OV08X40 nodes are placeholders (`_STA=0`); the live device is `SSLC2000`. Users get a camera picker entry that can never start.

## Suggested direction

A full working camera needs an SC200PC/SSLC2000 v4l2 subdev driver plus HAL/relayd config (not `ov08x40-uf`). Until that exists, Omarchy can still:

1. Detect `SSLC2000` (and/or DMI `Galaxy Book6`) separately from `OVTI08F4` with `_STA=15`.
2. Avoid installing/enabling the XPS `ov08x40` relay so browsers do not list a dead "Hardware ISP Camera".
3. Track Book6 as a known-unsupported IPU7 sensor, similar to other hardware-gated camera packages.

Happy to test patches on this machine.

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 15:08 UTC