Troubleshooting Q&A

Wiki ▸ Troubleshooting Q&A

Camera not working\detected

• How do I see which RealSense cameras are connected?
• I connected the camera to the USB port but it is not recognized
• I'm using a virtual machine and the camera is not working

Installation

• Fatal error: libudev.h: when building from sources
• How do I enable librealsense logs?
• GCC Internal Error
• I ran the udev rules script but Linux still get Permission denied
• dmesg shows: uvcvideo: module verification failed: signature and/or required key missing - tainting kernel
• sudo modprobe uvcvideo produces dmesg: uvc kernel module is not loaded
• Kernel patch script fails with fatal error: openssl/opensslv.h

Git

• Git returns access timeout when I try to clone the repository

Python

• CMake shows an error when I try to build with Python bindings

Calibration

• D400 Series Calibration Tools

Any OS: run the rs-enumerate-devices tool shipped with the SDK. It lists every detected device with its serial number, firmware version and USB type.

Linux:

$ lsusb | grep -iE '8086|38e5'

Older SKUs enumerate with vendor ID 8086, newer SKUs with 38e5.

Windows:

1. Click the Win-Key+X keys
2. Choose Device Manager
3. Look under Cameras (or Imaging devices on older Windows builds) for "RealSense" cameras

❗️ Make sure your camera is connected using USB 3.0 ❗️

If your camera is connected via USB 3.0, check to make sure your OS detects the camera (how?). The camera will not work without USB 3.0 (or higher)

Due to the USB 3.0 translation layer between native hardware and virtual machine, the librealsense team does not support installation in a VM. If you do choose to try it, we recommend using VMware Workstation Player, and not Oracle VirtualBox for proper emulation of the USB3 controller.

From version 2.9.0 a new dependency third-party package libudev-dev has to be installed: sudo apt-get install libudev-dev See Release Notes for v2.9.0

To change the log level of the librealsense logger, set an environment variable named LRS_LOG_LEVEL to the desired log level:

Linux:

$ export LRS_LOG_LEVEL="<Log Level>"

Windows:

> set LRS_LOG_LEVEL="<Log Level>"

<Log Level> can be either DEBUG, INFO, WARN, ERROR or FATAL (case-insensitive)

See also Troubleshooting Tips and Tricks for kernel-level tracing on Linux.

The gcc compiler issues the following error while compiling:

gcc: internal compiler error

This might indicate that you do not have enough memory or swap space on your machine. Try closing memory consuming applications, and if you are running inside a VM increase available RAM to at least 2 GB.

First, try re-installing udev rules located in librealsense source directory: sudo cp config/99-realsense-libusb.rules /etc/udev/rules.d/ sudo udevadm control --reload-rules && udevadm trigger

If the issue persists, the cause might be due to the fact that your user is not part of the plugdev group.

This is a standard warning issued since Kernel 4.4-30+, it is only a notification and does not affect module's functionality.

This issue is caused since the patched module kernel version is incompatible with the resident kernel. Verify the actual kernel version with uname -r. Revert and proceed from the Install dependencies step of the Linux installation guide.

Running ./scripts/patch-realsense-ubuntu-lts-hwe.sh (or the other patch-realsense-*.sh scripts) fails with fatal error: openssl/opensslv.h. This is usually caused due to a missing dependency. Install the openssl development package (libssl-dev) as described in the Install dependencies step.

git.launchpad... access timeout

This usually happens when your computer is behind a firewall, try to configure git to use the appropriate proxy server

The following message appears:

Could NOT find PythonInterp (missing: PYTHON_EXECUTABLE)

Please check the following:

• Make sure Python is installed
• On Windows: If you've just installed python, reboot (or log off) and try again
  • Try the answers suggested here: building-opencv-libraries-from-source-files

Python config failure: Python is 32-bit, chosen compiler is 64-bit

If this message appears you should install python 64 bit

• On-Chip (self) calibration is available directly from the RealSense Viewer and via the SDK API. See Self-Calibration for Depth Cameras.
• For the full Dynamic Calibration tools please check the D400 Series Calibration Tools User Guide.