# ZED X One GS not detected

**URL:** <https://community.stereolabs.com/t/zed-x-one-gs-not-detected/11422>\
**Category:** Hardware\
**Tags:** jetson\
**Created:** [June 9, 2026, 10:16am UTC](https://community.stereolabs.com/t/zed-x-one-gs-not-detected/11422 "2026-06-09T10:16:13Z")\
**Posts on this page:** 4\
**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/zed-x-one-gs-not-detected/11422/1 "2026-06-09T10:16:13Z")

</div>

Hi [Stereolabs](https://www.stereolabs.com/),

We are still debugging the ZEDBox Mini / ZED X camera detection issue on our Jetson Orin NX system.

Background:  
We previously saw that the system was booting with the Super Mode DTB:

The active [Stereolabs](https://www.stereolabs.com/) boot entry used:

FDT /boot/dtb/kernel\_tegra234-p3768-0000+p3767-0001-nv-super.dtb

and:

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

Based on your previous advice that Super Mode may cause issues with the Mini Carrier / ZEDBox Mini setup, we tested a normal DTB.

We added a separate boot entry without modifying the existing one:

LABEL [Stereolabs](https://www.stereolabs.com/)-normal-test

using the same kernel, initrd, APPEND line and ZEDBox Mini overlay, but with:

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

The normal DTB exists locally and its compatible strings are:

Current result on the normal DTB is that no zed device are detected.

The [Stereolabs](https://www.stereolabs.com/)-related kernel modules are loaded:

```auto
$ lsmod | grep -Ei "sl_|zed|max929"
sl_zedxone_uhd 40960 0
sl_zedx 28672 0
sl_zedxhdr 24576 0
sl_max9295 16384 3 sl_zedxhdr,sl_zedxone_uhd,sl_zedx
sl_max9296 36864 4 sl_zedxhdr,sl_zedxone_uhd,sl_max9295,sl_zedx
tegra_camera 217088 6 nvhost_isp5,nvhost_nvcsi_t194,sl_zedxhdr,sl_zedxone_uhd,nvhost_vi5,sl_zedx
videodev 249856 7 v4l2_async,sl_zedxhdr,videobuf2_v4l2,tegra_camera,sl_zedxone_uhd,videobuf2_common,sl_zedx

```

But with dmesg it still shows the same I2C / MAX9296 failure:

```auto
i2c i2c-2: of_i2c: modalias failure on /bus@0/i2c@3180000/zedxone_uhd_ser@44
i2c i2c-2: Failed to create I2C device for /bus@0/i2c@3180000/zedxone_uhd_ser@44
i2c i2c-2: of_i2c: modalias failure on /bus@0/i2c@3180000/zedxone_uhd@1a
i2c i2c-2: Failed to create I2C device for /bus@0/i2c@3180000/zedxone_uhd@1a

sl_max9296 2-0048: Driver Version : v1.4.2
sl_max9296 2-0048: write_reg_Dser: addr = 0x10, val = 0x80
sl_max9296 2-0048: write_reg_Dser: addr = 0x10, val = 0x21
sl_max9296: probe of 2-0048 failed with error -1

bmi088: probe of 2-004b failed with error -5
bmi088: probe of 2-003b failed with error -5

```

And ZED Explorer still detects nothing:

```auto
$ /usr/local/zed/tools/ZED_Explorer --all
No ZED detected

```

System details:

```auto
L4T: R36.4.7
Kernel: 5.15.148-tegra
Ubuntu: 22.04.5
ZED SDK: 5.1.2
Stereolabs package: stereolabs-zedbox-mini 1.4.2-SL-MAX9296-ZEDBOX-MINI-L4T36.4.0

```

Important observation:  
Earlier we inspected the live device tree and the ZEDBox Mini overlay. It looks like the overlay creates both complete suffixed nodes and incomplete/non-suffixed nodes, for example:

Complete-looking nodes:

```auto
zedxone_uhd_0@1a
zedxone_uhd_ser_0@44

```

but also suspicious incomplete nodes:

```auto
zedxone_uhd@1a
zedxone_uhd_ser@44

```

The kernel errors specifically reference the non-suffixed nodes:

```auto
zedxone_uhd@1a
zedxone_uhd_ser@44

```

These appear to be missing required properties such as compatible and/or reg, which matches the of\_i2c: modalias failure messages.

So after testing the normal DTB, the conclusion is:

1. The camera stack still fails in the exact same way with normal-mode

2. The failure appears to be related to the ZEDBox Mini overlay / device-tree nodes and/or the MAX9296 probe.

Dp you have any suggestions?

Specifically:

- Is [stereolabs](https://www.stereolabs.com/)-zedbox-mini 1.4.2-SL-MAX9296-ZEDBOX-MINI-L4T36.4.0 expected to work on L4T R36.4.7 / kernel 5.15.148-tegra?

- Are the non-suffixed nodes zedxone\_uhd@1a and zedxone\_uhd\_ser@44 expected to exist in the live device tree?

- If they are dummy/placeholder nodes, should they be disabled or removed from the active I2C bus?

- Is the sl\_max9296: probe of 2-0048 failed with error -1 caused by the invalid/dummy serializer/sensor phandles?

- Is there a newer ZEDBox Mini overlay/driver package for this exact L4T version?

- Should we patch the DTBO, downgrade/upgrade the [Stereolabs](https://www.stereolabs.com/) package, or do a full normal-mode reflash with a specific JetPack/L4T version?

---

<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 9, 2026, 2:01pm UTC](https://community.stereolabs.com/t/zed-x-one-gs-not-detected/11422/2 "2026-06-09T14:01:25Z")

</div>

Hi @hatfalk  
Welcome to the [StereoLabs](https://www.stereolabs.com/) community.

> [@hatfalk](#):
>
> ```auto
> zedxone_uhd_0@1a
> zedxone_uhd_ser_0@44
> 
> ```

Are you using a ZED X One GS or a ZED X One 4K? They are different models that have different multi-camera setup requirements.

Are the cameras detected when they are connected singularly?

> [@hatfalk](#):
>
> Is [stereolabs](https://www.stereolabs.com/)-zedbox-mini 1.4.2-SL-MAX9296-ZEDBOX-MINI-L4T36.4.0 expected to work on L4T R36.4.7 / kernel 5.15.148-tegra?

Yes, it is.

Why are you modifying the device tree if you are using a [StereoLabs](https://www.stereolabs.com/) device? This is not normally required.

---

<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 10, 2026, 2:38pm UTC](https://community.stereolabs.com/t/zed-x-one-gs-not-detected/11422/3 "2026-06-10T14:38:44Z")

</div>

Hey, thank you for quick reply. We are using ZED X One GS. They are not detected when connected singularly.  
Just saw it complaining about probe failures and thought had something do with the DTBO iguess. linked to the dmesg log.

---

<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 11, 2026, 8:41am UTC](https://community.stereolabs.com/t/zed-x-one-gs-not-detected/11422/4 "2026-06-11T08:41:18Z")

</div>

> [@hatfalk](#):
>
> We are using ZED X One GS

I recommend you uninstall the current driver:  
`sudo dpkg --purge stereolabs-zedbox-mini`  
Then reboot, and download and install the latest ZED X Driver v.1.4.2 for L4T 36.4.x (JetPack 6.1 & 6.2.1).

Finally, download and install the latest ZED SDK v5.3.1.

After a reboot, you should be able to open the cameras with `ZED_Studio`, `ZED_Explorer`, and `ZED_Depth_Viewer`.

If problems persist, I recommend you reflash the device and reinstall all the software from scratch:

> **[Flash your ZED Box Mini | StereoLabs](https://docs.stereolabs.com/docs/products/embedded/zed-box-mini/reset-update)**
