modprobe: FATAL: Module videodev is in use about librealsense HOT 7 CLOSED

Hi @rastinp Can you confirm whether or not you attempted to apply a kernel patch script such as ./scripts/patch-realsense-ubuntu-lts-hwe.sh before you used the sudo apt-get install librealsense2-dkms command? An apt-get package install does not need a patch script to be applied because the patch is already bundled in the packages.

from librealsense.

Hi @MartyG-RealSense,
yes, I can confirm this.
Using lsmod I see that the videodev is used by

videodev v4l2_async, v4l2_fwnode, ov13858

from librealsense.

Thanks very much for the information. If the kernel has been patched, would it be possible for you to change to another kernel version so that the kernel becomes unpatched and then repeat sudo apt-get install librealsense2-dkms

from librealsense.

I switched to another kernel (6.2.0-26-generic) but the problem still appears.
It again throws the error that the videodev is in use, which is actually the case:

videodev v4l2_async, ov13858
mc v4l2_async, videodev, ov13858

I am not sure what the ov13858 (camera module or graphic card) and the mc is. There is no camera attached to the NUC but I extended the NUC with a second ETH+2xUSB.

from librealsense.

ov13858 is an OmniVision image sensor but not one of the OmniVision sensors used in RealSense 400 Series cameras for its RGB and infrared sensors. My research indicates that this component is referenced in videodev listings on computers that do not have a RealSense camera attached, such as laptops with a built-in webcam (though your NUC is not a laptop). Some PC desktop computer monitor screens have a webcam built into them, so you could check whether the screen being used with your NUC has this feature.

from librealsense.

I am not sure why the ov13858 module is installed automatically.
However, I solved now the issue, by deactivating the module ov13858 using
sudo modprobe -r ov13858

Afterwards, the librealsense2-dkms installed without any issue.
Thanks a lot @MartyG-RealSense for your support.

from librealsense.

You are very welcome, @rastinp - it's great to hear that you achieved a solution. Thanks very much for the update!

from librealsense.