# Does not detect ZED X Ones

**URL:** <https://community.stereolabs.com/t/does-not-detect-zed-x-ones/11423>\
**Category:** Hardware\
**Tags:** jetson\
**Created:** [June 9, 2026, 10:16am UTC](https://community.stereolabs.com/t/does-not-detect-zed-x-ones/11423 "2026-06-09T10:16:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hatfalk](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/h/59ef9b/32.png) [@hatfalk](https://community.stereolabs.com/u/hatfalk)\
**Post date:** [June 9, 2026, 10:16am UTC](https://community.stereolabs.com/t/does-not-detect-zed-x-ones/11423/1 "2026-06-09T10:16:18Z")

</div>

Hi!

We still have issue detecting our ZED X ones

System/context:

```auto
Jetson Orin NX
ZEDBox Mini / MAX9296 setup
L4T: R36.4.7
Kernel: 5.15.148-tegra
Ubuntu: 22.04.5
ZED SDK: 5.1.2
stereolabs-zedbox-mini: 1.4.2-SL-MAX9296-ZEDBOX-MINI-L4T36.4.0

```

The original issue is still:

```auto
No /dev/video*
ZED_Explorer --all -> No ZED detected

```

and in dmesg:

```auto
of_i2c: modalias failure on /bus@0/i2c@3180000/zedxone_uhd_ser@44
of_i2c: modalias failure on /bus@0/i2c@3180000/zedxone_uhd@1a
sl_max9296: probe of 2-0048 failed with error -1

```

Initially we suspected this might be caused by the system booting with the Super DTB:

```auto
/boot/dtb/kernel_tegra234-p3768-0000+p3767-0001-nv-super.dtb

```

so we added a separate test boot entry using the normal DTB:

```auto
FDT /boot/tegra234-p3768-0000+p3767-0001-nv.dtb

```

However, the camera issue stayed the same:

```auto
No /dev/video*
ZED_Explorer --all -> No ZED detected
sl_max9296: probe of 2-0048 failed with error -1

```

We then decompiled the installed overlay:

```auto
/boot/tegra234-p3768-camera-zedbox-mini-sl-overlay.dtbo

```

Found that the malformed nodes seem to be present in the DTBO itself, not just as a runtime artifact.

The overlay contains complete-looking nodes:

```auto
zedxone_uhd_0@1a
zedxone_uhd_ser_0@44

```

but it also contains non-suffixed/incomplete nodes:

```auto
zedxone_uhd@1a
zedxone_uhd_ser@44

```

The non-suffixed serializer is explicitly labeled in ` __symbols__ ` as:

```auto
dummy_zedxone_uhd_ser

```

From the decompiled DTS:

```auto
complete sensor:
zedxone_uhd_0@1a
compatible = "stereolabs,zedxone_uhd"
reg = <0x1a>
phandle = <0x4a>

complete serializer:
zedxone_uhd_ser_0@44
compatible = "stereolabs,sl_max9295"
reg = <0x44>
camera-sensors = <0x4a>
phandle = <0x39>

malformed / dummy-like sensor:
zedxone_uhd@1a
phandle = <0x3f>
missing compatible
missing reg

malformed / dummy serializer:
zedxone_uhd_ser@44
camera_model = "zedone4k"
zedx-id = "-1"
camera-sensors = <0x3f>
phandle = <0x3e>
missing compatible
missing reg

```

`dtc` also warns that the malformed `zedxone_uhd@1a` and `zedxone_uhd_ser@44` nodes have unit addresses but no `reg`.

The part that looks especially suspicious is that `max9296_a@48` has:

```auto
camera-serializers = <0x35 0x36 0x37 0x38 0x39 0x3a 0x3b 0x3c 0x3d 0x3e>;

```

where:

```auto
0x39 -> complete zedxone_uhd_ser_0@44
0x3e -> dummy/non-suffixed zedxone_uhd_ser@44

```

So the MAX9296 node seems to reference both the complete serializer and the dummy serializer.

This seems to match the live boot errors:

```auto
of_i2c: modalias failure on .../zedxone_uhd_ser@44
of_i2c: modalias failure on .../zedxone_uhd@1a
sl_max9296: probe of 2-0048 failed with error -1

```

Could you confirm whether this is expected?

Specifically:

1. Is `dummy_zedxone_uhd_ser` supposed to be included in the active `camera-serializers` list of `max9296_a@48`?

2. Should the non-suffixed nodes `zedxone_uhd@1a` and `zedxone_uhd_ser@44` exist as enabled I2C children even though they lack `compatible` and `reg`?

3. Is there a newer/fixed ZEDBox Mini DTBO or driver package for L4T R36.4.7?

4. Should we use a different driver package / JetPack version / L4T version for this setup?

5. Could this MAX9296 probe failure be caused by the physical GMSL link, cable, camera power, or wrong port/channel configuration?

6. Would you recommend a full normal-mode reflash, or is this more likely to reproduce the same issue if the same overlay is installed again?

thank you:)

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [June 10, 2026, 9:41am UTC](https://community.stereolabs.com/t/does-not-detect-zed-x-ones/11423/2 "2026-06-10T09:41:03Z")

</div>

Hi @hatfalk  
Please run `sudo ZED_Diagnostic --dmesg` and post here the content of the `dmesg.log` report file that it generates.

Please also list the cameras that you want to connect to the ZED Box Mini device.  
“ZED X Ones” is too generic. The ZED Box Mini has different behaviors when using ZED X One GS, ZED X One 4K, and ZED X One S.  
Please read more here:

> **[Supported GMSL2 camera combinations - ZED Box Mini Connectivity - Stereolabs](https://www.stereolabs.com/docs/embedded/zed-box-mini/connectivity#supported-gmsl2-camera-combinations)**
>
> It is possible to connect only one camera to each single GMSL2 port. | Connection Ports # Front side # Power connector Ethernet connector Power LED indicator Reset button Force Recovery button Left side # \[optional\] Wi-Fi antenna connectors Rear side...
