Open werdahias opened 1 month ago
It is the same with a few other modules as well i have tested two on ubuntu that says the same thing.
I confirm I have the same issue
I'm on Debian 12 stable
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
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?
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
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.
Environment
The kernel module for the v4l2 cannot be loaded on a somewhat recent debian distrubtion:
This is because the kernel still expect OpenSSl 1.0 to sign the module during install:
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 ?