TL;DR
The Chromebook EC Sensor Hub Code 10 on boards with a gap in the EC motion-sensor table is now pinned down in upstream source, and there is a ready-to-merge fix PR. What is still missing is a re-signed release.
- Bug report with full repro: GOOG0006 Code 10 on boards with an empty EC motion-sensor slot: OnPrepareHardware aborts enumeration instead of skipping · Issue #1 · coolstar/crossensors · GitHub
- Source fix (mergeable / clean, 1 file, +10 -2): Skip empty EC motion-sensor slots in OnPrepareHardware (fixes Code 10 on Redrix) by wfenger · Pull Request #2 · coolstar/crossensors · GitHub
- Request in the repo that actually ships the installers (202 stars): crossensors 1.0.1.0: re-signed release needed for empty EC sensor slot (GOOG0006 Code 10 on Redrix) · Issue #35 · coolstar/driverinstallers · GitHub
- Earlier case write-up on this forum: Redrix's EC Sensor Repair Case
Root cause (confirmed in source, not guessed)
crossensors/crossensors.cpp, OnPrepareHardware():
pDevice->SensorCount = resp.dump.sensor_count;
for (int i = 0; i < pDevice->SensorCount; i++) {
params.cmd = MOTIONSENSE_CMD_INFO;
params.info.sensor_num = i;
status = send_ec_command(...);
if (!NT_SUCCESS(status)) {
return status; // <-- aborts the whole device
}
...
}
return status;
Chrome EC motion-sensor tables are allowed to contain reserved/empty slots, which legitimately answer EC_RES_INVALID_PARAM. On Google Redrix (MrChromebox 2609.3 / redrix_14505.67.0, Windows 11 22621) the EC reports sensor_count = 5 and slot 3 is empty:
slot 0 bma422 accel (lid) OK
slot 1 lsm6dsm accel (base) OK
slot 2 lsm6dsm gyro (base) OK
slot 3 (empty) MOTIONSENSE_CMD_INFO -> EC result 3 (INVALID_PARAM)
slot 4 tcs3400 rgb light OK
Enumeration reaches slot 3, returns failure, and slot 4 is never visited. WDF then fails EvtDevicePrepareHardware, so ACPI\GOOG0006\1 ends up with Code 10 / 0xC00000E5, Windows never gets a Simple Device Orientation Sensor (SensorPresent=0), and native auto-rotation / convertible slate sensing is unavailable. This is not Redrix-specific: any board whose sensor table has a gap hits the same path.
The fix (PR #2)
Two lines, both in OnPrepareHardware():
return status→continueinside the loop, so an empty slot is skipped.return status→return STATUS_SUCCESSafter the loop, otherwise a failure status left over from the last skipped slot would still fail device start.
No new “lid accelerometer required” check: SensorWorkItem() already guards on pDevice->LidSensor != -1, so boards without one keep their existing behaviour.
Why a local binary patch is not a solution
The released crossensors.sys 1.0.1.0 is WHQL-signed (issuer Microsoft Windows Hardware Compatibility Publisher). A 2-byte binary workaround (file offset 0x1978: 78 18 → 90 90) confirms the diagnosis - with it the Sensor Hub starts, the Simple Device Orientation Sensor appears and native auto-rotation works. But any locally modified copy has to be self-signed, which on Windows 11 means keeping testsigning on permanently (kernel drivers must be Microsoft-signed since 1607, and all cross-signing certs expired in 2021):
- turning test mode off → Code 52 /
0xC0000428 - importing the self-signed CA into the trusted root with Secure Boot off → still rejected
- Windows/driver updates silently revert the patch
So the fix has to arrive through a re-signed upstream release (WHQL / attestation), not from a patched binary sitting on one machine.
How you can help
- If your board also has an empty sensor slot, please add your model /
ectool motionsense infooutput to issue #1 - more affected boards makes it easier to prioritise. - If you have a channel to reach CoolStar, a pointer to PR #2 would help.
- I can test any new build on this Redrix and report back here.
中文摘要:Redrix 等机型「Chromebook EC Sensor Hub」报 Code 10 的根因已在上游源码中定位——OnPrepareHardware() 枚举传感器时遇到空槽就直接中止。已提交可直接合并的两行修复 PR,但原厂驱动是 WHQL 签名,本地自签补丁必须常开测试模式,因此仍需官方重签发布才能彻底解决。详见上面三个 GitHub 链接。