linux-surface / linux-surface

Linux Kernel for Surface Devices
4.53k stars 202 forks source link

[SB2] v4l2 dmks module fails to load #1422

Open werdahias opened 1 month ago

werdahias commented 1 month ago

Environment

The kernel module for the v4l2 cannot be loaded on a somewhat recent debian distrubtion:

sudo modprobe v4l2loopback video_nr=42 card_label="virtualcam" exclusive_caps=1
modprobe: ERROR: could not insert 'v4l2loopback': Key was rejected by service

This is because the kernel still expect OpenSSl 1.0 to sign the module during install:

Loading new v4l2loopback-0.13.1 DKMS files...
Building for 6.8.1-surface-1
Building initial module for 6.8.1-surface-1
/lib/modules/6.8.1-surface-1/build/scripts/sign-file: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
Done.

This means the workaround to sign the module myself does not work as the OpenSSL version is too old. Would you consider bumping openssl in the kernel builds so this can be signed ?

small1 commented 4 weeks ago

It is the same with a few other modules as well i have tested two on ubuntu that says the same thing.

Ramen-LadyHKG commented 3 weeks ago

I confirm I have the same issue

I'm on Debian 12 stable

Ramen-LadyHKG commented 3 weeks ago

It is the same with a few other modules as well i have tested two on ubuntu that says the same thing.

yeah, both my binder, nvidia are unable to sign

Ramen-LadyHKG commented 3 weeks ago

I confirm I have the same issue

I don't have general kernel installed, does the original kernel also use old libcrypto.so.1.1 library?

Ramen-LadyHKG commented 3 weeks ago

Sorry for out topic.

I see that you also have 15" Surface Book 2. I would like to know, is your i7-8650u operate properly?

I have this issue troubling me that the CPU does not turbo boost on load (no thermal issue).

https://github.com/linux-surface/linux-surface/issues/1041

https://bbs.archlinux.org/viewtopic.php?pid=2164410#p2164410

https://www.reddit.com/r/linux4noobs/comments/17w138n/i_cannot_get_turbo_boost_working_on_linux_for_my/?sort=new

StollD commented 3 weeks ago

This means the workaround to sign the module myself does not work as the OpenSSL version is too old. Would you consider bumping openssl in the kernel builds so this can be signed ?

The problem with that is that we then get the same reports, but from the people that still use their 20.04 Ubuntu installs.

We will probably update once 24.04 releases.