I use r8168-dkms to get support for my Ethernet adapter. It looks like the sign-file binary provided by the 6.0.8 kernel is linked with libcrypto.so.1.1 whereas my fully updated system has libcrypto.so.3 . Without sign-file working, dkms doesn’t sign the r8168 module and the linux kernel doesn’t automatically install it at startup. I managed to fix this issue by recompiling sign-file by hand but I’m guessing this should somehow be fixed upstream. This seems to be a minor breaking change for all of the kernel versions I have installed, 5.15, 5.10, 5.4 all suffer from it as well
EDIT: It looks like installing openssl-1.1 also fixes it, but I’m not sure whether adding that as a dependency or recompiling sign-file is the better solution
Looks like someone forgot to rebuild some kernels…
$ ldd /usr/lib/modules/**/sign-file
libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0x00007f5c05e00000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f5c05c19000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f5c062b8000)
libcrypto.so.3 => /usr/lib/libcrypto.so.3 (0x00007f561e400000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f561e219000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f561ea03000)
libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0x00007f1c48400000)
libc.so.6 => /usr/lib/libc.so.6 (0x00007f1c48219000)
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f1c48895000)
You should remove it when this is fixed.
IIRC, they wrote somewhere that they finally removed all dependencies on
openssl-1.1 in packages, looks like they missed some…
This is just manjaro pushing kernels from unstable/testing that were built before that. But they did rebuild 5.19 for some reason.
@cactus1 you can install kernel/headers from unstable if you want quick fix.