[REDRIX] Camera sensor HI556 (INT3537) fails with Code 10 (STATUS_DEVICE_POWER_FAILURE) on MrChromebox-2606.1 in Windows

Support Windows Support
1

System Details

Device: HP Elite Dragonfly Chromebook (REDRIX, Google_Brya family)
OS: Windows 11 Pro 24H2 (x64) (also reproduced on Build 28000)
Firmware Type: UEFI Full ROM
Firmware Version: MrChromebox-2606.1
Internal storage type: NVMe

Summary of the Issue

The MIPI camera sensor ACPI\INT3537\0 (Hynix HI556) fails to start in Windows Device Manager with Code 10 (0xC000009E: STATUS_DEVICE_POWER_FAILURE).

Key Investigation & Diagnostic Context:

  1. Hardware is 100% verified working: Booted into an Ubuntu 24.04 Live USB on the exact same machine, and dmesg confirms intel-ipu6 successfully initializes CSE authentication and detects the sensor (Found supported sensor INT3537:00, IPU6-v3[465d] hardware version 5).

  2. A/B Comparison with another identical Redrix: I have another identical HP Dragonfly Chromebook (Redrix) running MrChromebox-2603.1 where the camera works flawlessly with the exact same driver stack (iacamera64 + hi556.sys 63.22000.16989.1 + SerialIO 30.100.2417.30 + crosec).

  3. Driver stack on Windows is clean: Intel AVStream Camera (DISPLAY\INT3480), IPU (PCI\VEN_8086&DEV_465D), and I2C Host Controller (PCI\VEN_8086&DEV_51EA) all show Status OK (Code 0). The failure only occurs when hi556.sys attempts to execute the ACPI power-on sequence (_PS0 / _DSM / GPIO power rail toggle) on MrChromebox-2606.1.

Steps to Reproduce

  1. Flash MrChromebox-2606.1 UEFI Full ROM on HP Elite Dragonfly Chromebook (REDRIX).

  2. Install Windows 11 24H2 (or 23H2/22H2).

  3. Install standard Alder Lake Chromebook drivers:

    • Intel Serial IO I2C / GPIO drivers (iaLPSS2_I2C_ADL / iaLPSS2_GPIO2_ADL).

    • crosec driver package.

    • Intel MIPI Camera & HI556 sensor drivers (IntelMipiCamera installer).

  4. Open Device Manager → Check System Devices → Camera Sensor HI556 (ACPI\INT3537\0).

Expected Behavior

The Camera Sensor HI556 (ACPI\INT3537\0) should power on properly and show Status: OK (Code 0), allowing the Windows Camera app to stream video (as it does on firmware MrChromebox-2603.1).

Additional Logs & IDs

  • Faulting Device Instance Path: ACPI\INT3537\0

  • Parent I2C Controller: PCI\VEN_8086&DEV_51EA&SUBSYS_72708086&REV_01\3&11583659&0&AA

  • Kernel-PnP Event: Event 411: Problem 0xA, Problem Status 0xC000009E

  • Linux dmesg verification output:

    [ 12.629236] intel-ipu6 0000:00:05.0: Found supported sensor INT3537:00
[ 12.629350] intel-ipu6 0000:00:05.0: Connected 1 cameras
[ 12.630697] intel-ipu6 0000:00:05.0: Sending BOOT_LOAD to CSE
[ 12.640088] intel-ipu6 0000:00:05.0: Sending AUTHENTICATE_RUN to CSE
[ 12.711877] intel-ipu6 0000:00:05.0: CSE authenticate_run done
[ 12.711886] intel-ipu6 0000:00:05.0: IPU6-v3[465d] hardware version 5
2

roll back to the previous firmware and verify it works under Windows, to rule out something specific to that install. if it works, dump the ACPI for both versions so I can compare. I’m pretty sure nothing changed though.

3

My bad on the earlier post — I pasted some raw AI debug output without really checking it first, which made things way more confusing than they needed to be.

I went ahead and dumped/disassembled the DSDT and SSDT tables with iasl from both machines (the working 2603.1 and the failing 2606.1). Turns out you called it — the CAM0 / INT3537 block is literally identical. The minor SSDT diffs were just unrelated stuff like DPTF, S0ix, and RTD3 on other I2C buses, none of which touch the camera’s I2C2. fw_config and EC versions match up across both units too. I also flashed this unit back to 2603.1 just to be 100% sure, and the issue was still there.

So yeah, firmware is definitely ruled out. Still trying to figure out why this specific board is throwing that power-up error on Windows, but I’m going to set up camera capture under Ubuntu next to see if I can actually pull video frames there and narrow it down.

Thanks for the sanity check and for maintaining the firmware!

4

different boards did use different camera sensors IIRC, worth comparing between the two units