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.

Sign up for GitHub

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

Jump to bottom

Doesn't work with Linux, only Ubuntu Linux. #6650

Closed
andrewhodel opened this issue Jun 19, 2020 · 12 comments
Closed

Doesn't work with Linux, only Ubuntu Linux. #6650

andrewhodel opened this issue Jun 19, 2020 · 12 comments
Labels
installation

Comments

@andrewhodel
Copy link
Contributor

  • 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..>

I've replaced the instances of generic with my kernel version for linux-headers in scripts/patch-realsense-ubuntu-lts.sh and it still reports Unsupported kernel version 4.19.0-8-amd64 . The patches are maintained for Ubuntu16 (Xenial) with LTS kernel versions 4.4, 4.8, 4.10, 4.13 and 4.15

Is there some reason for this, not supporting Linux and only supporting Ubuntu Linux?

I hate to install a distribution of Linux based on the one I normally use, Debian.
@andrewhodel
Copy link
Contributor Author

Dug deeper in #6651 will create a patch for Ubuntu once patch for 4.16.1 is fixed.

@MartyG-RealSense
Copy link
Collaborator

MartyG-RealSense commented Jun 19, 2020 •
edited
Loading

Hi @andrewhodel I see that you closed the case, but I will share the answer that I was working on anyway. :)

There is a "backend" installation method that requires an internet connection and SDK 2.30.0 or newer, but is not dependent on Linux versions or kernel versions, and does not require patching.

First, download the source code of an SDK version by going to the 'Releases' page and downloading the 'Source code' zip file from the "Assets" file list at the bottom of each version's details.

https://github.com/IntelRealSense/librealsense/releases/

image

Once the source code zip for the SDK version that you want to install has been extracted from the zip file, follow the instructions in the link below to build Librealsense without dependence on Linux versions, kernels or patches.

#6368 (comment)

@andrewhodel
Copy link
Contributor Author

andrewhodel commented Jun 19, 2020 via email

@andrewhodel
Copy link
Contributor Author

andrewhodel commented Jun 19, 2020 via email

@andrewhodel
Copy link
Contributor Author

andrewhodel commented Jun 19, 2020 via email

@MartyG-RealSense
Copy link
Collaborator

Yes, the process that I specified is designed for source code installation. DKMS packages have their own installation process.

I do understand your frustration. The instructions try to meet the needs of as wide an audience as possible on multiple types of computer / computing device, though there are cases where further support may be required to successfully complete an installation.

@andrewhodel
Copy link
Contributor Author

andrewhodel commented Jun 19, 2020 via email

@MartyG-RealSense
Copy link
Collaborator

MartyG-RealSense commented Jun 19, 2020 •
edited
Loading

Ubuntu is the most widely used Linux platform, though we do provide options for other forms of Linux and create specialist solutions for platforms such as Raspberry Pi and Nvidia Jetson.

I cannot speak for the creators of the documentation, but I can assure that they try to do their best for everyone and give individual specialist support on the forum where necessary.

Thanks for your patience, it really is appreciated!

@andrewhodel
Copy link
Contributor Author

andrewhodel commented Jun 19, 2020 via email

@MartyG-RealSense
Copy link
Collaborator

I am on the Support team and are not involved with development decisions, so I cannot comment on that point. I recommend raising the points in your open case. Thanks.

@ev-mp
Copy link
Collaborator

ev-mp commented Jun 20, 2020 •
edited
Loading

@andrewhodel hello,
I've followed the PR you submitted as I wasn't sure about its purpose or to whom it was addressed.
Here it seem to be the proper context for reply -

I've replaced the instances of generic with my kernel version for linux-headers in scripts/patch-realsense-ubuntu-lts.sh and it still reports Unsupported kernel version 4.19.0-8-amd64 . The patches are maintained for Ubuntu16 (Xenial) with LTS kernel versions 4.4, 4.8, 4.10, 4.13 and 4.15
Is there some reason for this, not supporting Linux and only supporting Ubuntu Linux?

That is not correct. Librealsense2 SDK and RealSense Depth cameras and is in no way limited for Ubuntu.They can and be deployed on any Linux distribution and platform that satisfy the following minimal requirements: Kernel 4.4+/ GCC ~4.8 and USB2/3 port according to the camera model.
Most of the camera and SDK functions become available immediately upon installation without patches - Device enumeration, controls, data streaming.

The kernel patches are intended to enable advanced capabilities unique to Realsense devices, and also to fill kernel gaps for functionalities that are yet-to-be implemented or buggy. Still, the core feature that justifies the existence of those patches is the frame metadata.
As for the selected distribution - we maintain patches for Ubuntu LTS kernels in a form of script and also as a precompiled DKMS module. Both methods are functionally-equivalent but for obvious reasons we recommend DKMS as the preferred installation method (Documentation).
In addition to the patches provided by Intel for Ubuntu there are multiple patches that were generated and provided by community. Unfortunately those tend to become obsolete as in most cases community members do not update them after the initial submissions.
And this is the core distinction - the officially-"maintained" patches are being updated continuously and reflect the up-to-date state of all the supported devices/required functionalities. So when the need arise they are used as a baseline for a new port by maintainers or community.

I just don't understand why your instructions on Github and on the Intel
SDK site are so terrible.

The online documentation is being checked and updated periodically. Can you provide specific examples?

Why don't you just tell people to rebuild the kernel, apply the patches
needed and use the kernel they built?
Then it works with any Linux distribution or version that supports the
library versions (so 4.18.1+ or whatever).

Because not only it is not precise, It is actually the is opposite of the message we convey:

  • We do not require the users to apply kernel patches. The users are free to experiment with the default settings, and for many users this is sufficient.
    Ubuntu users have a certain advantage as they have the kernel patches/installation package ready for them already. But, as pointed above by @MartyG-RealSense , for users that don't use Ubuntu
    the SDK provides a "driver-less" build. This configuration delivers all the "extra" functionality (metadata) without touching the kernel. Currently this is the recommended method for RaspberryPi and Tegra boards. Additionally we are open for collaboration and ready to provide technical assistance for users that port the patches to other kernels/distros.
  • For most* distributions it is unnecessary - the patches apply to several loadable modules so it is technically inefficient to rebuild the whole kernel to replace those 6-7 *.ko modules.
    **There are several exceptions for this case, such as Tegra or Yocto distros, but they also have dedicated handling/installation guidance.

@andrewhodel
Copy link
Contributor Author

andrewhodel commented Jun 20, 2020 via email

@ev-mp ev-mp mentioned this issue Jun 23, 2020
Merged
@ttencate ttencate mentioned this issue Aug 15, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
installation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@andrewhodel @ev-mp @MartyG-RealSense