librealsense2-dkms for 6.12 kernels?

[chlohr]

Hello,
If I understand correctly, the noble/librealsense2-dkms package is intended for 6.8.0 kernels. Is there a version for more recent kernels (e.g., 6.12.xx)?

Regards

[MartyG-RealSense]

Hi @chlohr There is not currently support with librealsense DKMS package installations for kernel 6.12. If you build the SDK from source code with the libuvc backend installation method though then the kernel version will not matter as a libuvc installation of librealsense bypasses the kernel and does not require the application of a kernel patch.

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

This installation method provides a pre-made installation script called libuvc_installation.sh

https://github.com/IntelRealSense/librealsense/blob/master/scripts/libuvc_installation.sh

[chlohr]

Hi @MartyG-RealSense
Thank you very much for your quick response.

I'm facing compilation errors regarding libcurl:
[ 81%] Linking CXX executable ../../release/rs-depth-quality
/usr/bin/ld: ../../libcurl/libcurl_install/lib/libcurl.a(psl.c.o): in function Curl_psl_destroy': psl.c:(.text+0x21): undefined reference to psl_free'
/usr/bin/ld: ../../libcurl/libcurl_install/lib/libcurl.a(psl.c.o): in function Curl_psl_use': psl.c:(.text+0xb9): undefined reference to psl_latest'
...

I'm not sure to understand why a video driver needs libcurl.
But maybe the libuvc backend doesn't offer a replacement for the native kernel driver, in a modular way, but recompiles the entire SDK and tools. Is that it?

Are there any packages already compiled for this backend?

Best regards

[MartyG-RealSense]

If libcurl errors occur during source code compilation of the SDK then they can usually be resolved by adding the flag below to line 46 of the libuvc_installation.sh script. This flag disables the offering of suggestions about SDK updates that can be performed online.

-DCHECK_FOR_UPDATES=OFF

The libuvc method installs dependencies automatically over the internet instead of the user having to install the dependencies themselves manually. When installing from source code without using the libuvc method to bypass the kernel, that is called a 'native backend' installation of the SDK.

librealsense packages are based on the native backend rather than libuvc.

[Nir-Az]

@chlohr just to add some more info about "I'm not sure to understand why a video driver needs libcurl"

When you compile the SDK tools like the realsense-viewer, you compile more than a video driver, you build an application.
The current use of libcurl in the realsense vieweris to download a versions DB stored on cloud for announcing the user of new FW/SW

If you wish to get just the SDK, compile with -DBUILD_EXAMPLES=OFF -DBUILD_TOOLS=OFF

[chlohr]

Thanks, I was able to compile everything.
Unfortunately my SR300 is not detected. Is there a way?

[MartyG-RealSense]

Support for the retired SR300 camera model ended after librealsense 2.50.0. So you should compile version 2.50.0 in order for the SR300 to be detected.

https://github.com/IntelRealSense/librealsense/releases/tag/v2.50.0

[chlohr]

Many thanks for the indication!
I compile it with -DFORCE_LIBUVC=true to be able to use it on recent kernels. The SR300 is detected, and seems to work like a charm with the viewer.
(May I suggest providing a dedicated libuvc_installation.sh ?)

Best regards!

[MartyG-RealSense]

I'm pleased to hear that you were able to get your SR300 detected!

Do you mean a dedicated libuvc_installation.sh version for SR300, please? If you do then such a version would not be provided unfortunately as retired camera models do not receive updates for them in the SDK.

[chlohr]

I mean a libuvc_installation.sh dedicated to librealsense 2.50.0
I think it's important to be able to continue to use legacy devices (that do the job) on modern systems (with new kernel, new python, new ros, & co.)
It is also reassuring when you buy new devices to be sure that you will be able to use them for a long time. ;-)

Best regards

[MartyG-RealSense]

In theory, it should be possible for RealSense users to create their own dedicated install script for SR300 if they remove lines 35-39 from the libuvc_installation.sh script (so that the script does not try to download and install the latest SDK version) and then download the source code folder for 2.50.0 and place the modified script in the source code folder's root directory (usually 'librealsense > librealsense' in the source code folder structure), and run it, libuvc_installation.sh should install 2.50.0 from the source code folder.

https://github.com/IntelRealSense/librealsense/blob/master/scripts/libuvc_installation.sh#L35-L39

The RealSense team does aim to provide long-term support in the SDK for older camera models whenever it is practical to do so. It becomes more difficult to continue support for models whose technology differs significantly from the 400 Series range, such as SR300, L515 and T265 and it also makes the SDK larger in download size and more complex to test before each new release. I completely understand your perspective though.