> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.stereolabs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.stereolabs.com/_mcp/server.

# Troubleshooting

Here are some common issues that you could face with your ZED Box 2.

If you are unable to resolve your issue using the following suggestions, please reach out to us at [support@stereolabs.com](mailto:support@stereolabs.com) for further assistance.

## ZED Box 2 not booting

If your ZED Box 2 does not turn on after a shutdown, follow these steps to diagnose the issue.

### 1. Check Power Connection

Try these steps to force a boot:

* Switch off the power source and unplug the power terminal block.
* Check with a voltmeter that the voltage of the power source is between **10V and 32V**, and that the polarity matches the [power input pinout](/docs/products/embedded/zed-box-series/zed-box-2/connectivity#power-input).
* Check that the wires are firmly tightened in the terminal block.
* If the voltage is correct, replug the terminal block and switch on the power source, otherwise fix your power source.

### 2. Check the Power LED Status

Locate the power LED on the rear panel and determine its status:

#### **🟢 LED is ON**

* This indicates a **software issue**.
* The ZED Box 2 software may have been corrupted due to an improper shutdown or the internal disk may be full.
* **Solution:**
  * Connect to the device through the [Serial Console](/docs/products/embedded/zed-box-series/zed-box-2/serial-console) to check the boot messages, and use `df -h` to check whether the internal disk is full.
  * If the issue persists, contact [StereoLabs Support](mailto:support@stereolabs.com) for further assistance.

#### **⚫ LED is OFF**

* If you have already tried the [power connection procedure](#1-check-power-connection), this suggests a possible **file system** or **hardware** failure.
* **Solution:**
  * Contact [StereoLabs Support](mailto:support@stereolabs.com) for further assistance.

> **Warning**
>
> Always shut down the device properly by software before removing power to avoid file system corruption.

---

## The GMSL2 cameras are not detected

If one or more GMSL2 cameras are not detected by the ZED SDK:

* Check that the cameras were connected **before** powering on the ZED Box 2. GMSL2 cameras are not hot-pluggable: after any change, reboot the device or restart the ZED X daemon with `sudo systemctl restart zed_x_daemon.service`.
* Check that each FAKRA connector is fully inserted, with a "click".
* Check that your configuration is supported, according to the [multi-camera configurations](/docs/products/embedded/zed-box-series/zed-box-2/using-gmsl#multi-camera-configurations) table.
* Check that the GMSL2 driver is installed and matches your L4T version: `dpkg -l | grep stereolabs`. Reinstall it if needed, as described in [Using GMSL](/docs/products/embedded/zed-box-series/zed-box-2/using-gmsl#gmsl-driver).
* List the detected cameras with `ZED_Explorer --all`.

---

## The CAN interface does not receive any frame

* Check that the interface is up, with the correct bit rate: `ip -details link show type can`.
* Check that `CAN_H` (pin #7) and `CAN_L` (pin #2) are not swapped, and that the `GND` of the ZED Box 2 (pin #6) is connected to the ground of the bus.
* Check that both ends of the bus are terminated with a 120 Ω resistor.
* Check that at least one other node acknowledges the frames on the bus: on a bus with no other active node, the interface enters the error-passive or bus-off state. Reset it with:

  ```bash
  sudo ip link set can0 down
  sudo ip link set can0 type can bitrate 500000 restart-ms 100
  sudo ip link set can0 up
  ```

---

## The WiFi does not work anymore after a system update

After operating system updates, the WiFi module on the ZED Box 2 may stop working.

This issue occurs when the Ubuntu Software Updater or apt installs an incorrect WiFi driver.

**Solution**

Follow these steps to remove the incorrect firmware file and reload the correct driver:

### Remove the incorrect firmware file

Run the following command to delete the problematic firmware file:

```bash
sudo rm /lib/firmware/iwlwifi-ty-a0-gf-a0-66.ucode
```

Now you can reboot the device (`sudo reboot`) to automatically load the correct driver, or load it manually without rebooting.

### Unload the incorrect driver

Unload the currently loaded (incorrect) WiFi driver:

```bash
sudo modprobe -r iwlwifi
```

### Load the correct driver

Reload the correct default WiFi driver:

```bash
sudo modprobe iwlwifi
```

After completing these steps, your WiFi module should function properly again.

---

## Error: "Package nvidia-l4t-kernel is not configured yet" while installing the ZED X Driver

After upgrading the ZED Box 2 with `sudo apt upgrade`, reinstall the ZED X Driver to restore full compatibility.

In some cases, the reinstallation can fail with the dependency error shown below:

```bash
dpkg: dependency problems prevent configuration of stereolabs-zedbox-duo:
 stereolabs-zedbox-duo depends on nvidia-l4t-rt-kernel (>= 5.15.148-rt-tegra-36.4.0-20240912212859) | nvidia-l4t-kernel (>= 5.15.148-tegra-36.4.0-20240912212859); however: 
  Package nvidia-l4t-rt-kernel is not installed.
  Package nvidia-l4t-kernel is not configured yet.
 stereolabs-zedbox-duo depends on nvidia-l4t-rt-kernel (<= 5.15.148-rt-tegra-36.4.4-20250616085344) | nvidia-l4t-kernel (<= 5.15.148-tegra-36.4.4-20250616085344); however: 
  Package nvidia-l4t-rt-kernel is not installed.
  Package nvidia-l4t-kernel is not configured yet.

dpkg: error processing package stereolabs-zedbox-duo (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing: 
 stereolabs-zedbox-duo
```

To resolve this issue, you can follow these steps:

> **Warning**
>
> This procedure resets the dpkg package metadata (maintainer scripts and file lists) of **all** installed packages. Use it only as a last resort, when `sudo dpkg --configure -a` and `sudo apt-get -f install` alone do not solve the problem.

```bash
sudo apt-get autoclean # Clean up the package cache
sudo mv /var/lib/dpkg/info/ /var/lib/dpkg/backup/ # Back up the info directory
sudo mkdir /var/lib/dpkg/info/ # Create a new info directory
sudo apt-get update # Update the package list
sudo apt-get -f install # Fix broken dependencies
```

This process will clean up the package cache, back up the existing package information, create a new directory for package information, update the package list, and fix any broken dependencies that may be causing the issue. After completing these steps, you should be able to install the ZED X Driver without encountering the "Package nvidia-l4t-kernel is not configured yet" error.

---

## Chromium and Firefox browser issues with Jetson Linux (L4T) 36.4.4 - JP 6.2.1

Upgrading to Jetson Linux (L4T) 36.4.4 - JP 6.2.1 introduces Snapd 2.70, which breaks all Snap packages with the following error:

```bash
cannot set capabilities: Operation not permitted
```

For this reason, the Chromium and Firefox browsers, and other Snap-based applications, fail to launch.

This occurs because Jetson Orin devices ship with a minimal kernel that lacks certain security features required by Snapd 2.70 and newer.

To resolve this issue, revert Snapd to an earlier working version:

```bash
snap download snapd --revision=24724
sudo snap ack snapd_24724.assert
sudo snap install snapd_24724.snap
sudo snap refresh --hold snapd
```

For more information, refer to [this page of the JetsonHacks website](https://jetsonhacks.com/2025/07/12/why-chromium-suddenly-broke-on-jetson-orin-and-how-to-bring-it-back/).

---

## Contact Support

If you are unable to resolve your issue, please visit our [community forum](https://community.stereolabs.com/) or contact [support@stereolabs.com](mailto:support@stereolabs.com) for further assistance.