Usbcore kernel error #11156
Labels
Comments
|
Hi @Allius27 The typical approach to installing the librealsense SDK from source code on a PC computer where you are using kernel patching would be to follow the instructions at the link below. https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md This would involve first running the kernel patch script and then building librealsense from source code afterwards. It is not usually necessary to add build_usbcore_modules to the kernel patch run instruction or copy and paste drivers. If your project only uses one camera per computer then a way of achieving a consistent installation on multiple computers may be to use CMake to build librealsense from source code with the RSUSB backend installation method, which bypasses the Linux kernel. An RSUSB build of librealsense is therefore not dependent on Linux versions or kernel versions and does not require patching. Instructions for an RSUSB install can be found at #9931 (comment) |
|
I rebuild sdk with -DFORCE_RSUSB_BACKEND And got this dmesg behavior dmesg -w |
|
And after restoring original drivers I got the next command for restoring - sudo apt install --reinstall linux-modules-extra-4.4.0-210-generic dmesg -w |
|
If the linux modules were reinstalled with the command in the comment above then that would likely undo the changes to modules such as uvcvideo that were applied by the patch script. So the patch script would need to be run again to re-patch the reinstalled modules. |
|
wait a minute.. |
|
When using RSUSB you do not need to apply the librealsense patch script to kernel modules, and doing so after the RSUSB installation has completed may break the RSUSB build. You can keep the original modules. |
|
I made some experiments with different realsense examples sdk version is we build it with keys go to install/bin directory LD_LIBRARY_PATH=../lib/ ./rs-color ( rs2_pipeline - c lang ) LD_LIBRARY_PATH=../lib/ ./rs-capture ( rs2::pipeline - c++ lang ) LD_LIBRARY_PATH=../lib/ ./rs-hello-realsense ( rs2::pipeline - c++ lang ) One note. So.. the question is |
|
When changing options with an RSUSB build, there may be occasions when the request to change an option is not heard because RSUSB listens for changes less often than a kernel-patch based build of librealsense. This is discussed at #6952 At #6921 (comment) advice is provided regarding editing the SDK's code to listen for device changes more often. The modified SDK could then be built from its source code. If you are satisfied with how RSUSB performs though then you can ignore the kernel errors. |
|
unfortunately, that advice is acceptable for v2.36.0 release, not for v2.50.0, and not for latest master branch and the second moment. that code works 30 seconds, instead of 15 that 16 seconds and that 18 seconds do you have a tip how to update that for the correct behavior? |
|
If your script works correctly on your other computer - Gigabyte GB-BACE-3160 - with SDK 2.50.0 then that suggests that the script is okay and there is some hidden difference between the configuration of the Gigabyte computer and the computer that the video is looping on. In a past case with two computers of the same model that seemed to have the same configuration, a script worked well on one of the computers but not the other. It was later found that the computer that worked well had newer drivers installed than the computer that the script had problems on. Updating the problematic computer's configuration to match the working computer resolved the problem. |
|
Hi @Allius27 Do you have an update about this case that you can provide, please? Thanks! |
|
I found the reason of additional 15 seconds of waiting frames but when it recognizes as 3.0 there is no troubles thank for advice about -DFORCE_RSUSB_BACKEND compiling key |
|
It's excellent news that you found the source of your problem. Thanks very much for the update! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there.
We changed sdk from version 2.39 to 2.50 on ubuntu16
And now we had extremely strange situation.
Our video is looping, after some experiments we decided, that the reason might be the camera or kernels in our system.
dmesg logs on system startup
Case 1
Case 2
Both cases captured from the same computer.
We are using the same build on the other computer "GIABYTE gb-bace-3160". And we dont have any troubles.
I find out that scripts/patch-realsense-ubuntu-lts.sh contains build_usbcore_modules flag
I triyed call it in such way:
in menuconfig menu I choose "Save", "OK", "Exit" and "Exit"
after build crashed with that text
Our update drivers process looks like:
Any thoughts about usbcore kernel errors?
The text was updated successfully, but these errors were encountered: