-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Troubleshooting Q&A
Wiki ▸ Troubleshooting Q&A
We've grouped together related questions for your convenience
- How do I see which Intel RealSense cameras are connects?
- 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
- Streaming gets stuck on windows
- 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
producesdmesg: uvc kernel module is not loaded
git.launchpad... access timeout
This usually happens when your computer is behind a firewall, try to configure git to use the appropriate proxy server
Linux: Open shell:
$ lsusb | grep 8086
Windows:
- Click the
Win-Key
+X
keys - Choose
Device Manager
- Look under
Imaging devices
for "Intel 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?).
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.
When working on Windows 8.1, make sure you have KB3075872 and KB2919355 installed. These patches are addressing issues with 8.1 video drivers, resolved in Windows 10.
To change the log level of LibRealSense logger, you need to set a local variable named LRS_LOG_LEVEL and initialize it with the desirable log level:
$ export LRS_LOG_LEVEL="<Log Level>"
$ set LRS_LOG_LEVEL="<Log Level>"
- A LibRealSense log will be created even when an application does not activate the LibRealSense logger.
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.
Q: dmesg
shows: uvcvideo: module verification failed: signature and/or required key missing - tainting kernel
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 Make Ubuntu Up-to-date step from the Linux installation guide.
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
Intel® RealSense™ SDK Wiki
- Home
- Troubleshooting Q&A
- Release Notes
- API Changes
- API How-To
- Build Configuration
- Overview of Depth from Stereo
- Post-Processing
- Sample Data for SDK examples
- D400 Series Visual Presets
- Projection in RealSense SDK 2.0
- API Documentation
- About Android Support
- RealSense with Raspberry Pi 3
- RealSense with Raspberry Pi 4
- RealSense with NVidia Jetson
- Using Two Cameras with ROS
- Frame Buffering Management
- Supported Matrix
- Docker