How long does it take for a new driver version to reach upstream kernel? #463
-
|
Hello, I never used Windows on my GF63 12UCX, so I never knew that some hardware features were exposed to the system as well. Today, I was looking ad I looked up on GitHub and here I am trying to make it work. How long does it usually take for these updates to be included in the mainline kernel? I'm asking this because I'm using secure boot, and if I want to install this module manually, I would have to blacklist the in-tree driver and sign the new one every time I'm updating (which I don't know how to do at the moment). |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
@martymarty004 or just disable secure boot |
Beta Was this translation helpful? Give feedback.
-
|
Apparently, signing is now managed automatically by I'm happy that it just works, but that still doesn't answer my previous question. |
Beta Was this translation helpful? Give feedback.
-
|
Currently we are restructuring supported device list and thinking about way to support roughly all existing and future models. So no plans to upstream. Upstreamed version supported only battery limit. We don't know how much time will take to upstream new version, which contains many features in comparison to one in kernel. Small patches often applied every minor release of kernel, but upstream of other driver |
Beta Was this translation helpful? Give feedback.
-
Can you make guide about adding keys to BIOS? Open new issue and we will make it official. |
Beta Was this translation helpful? Give feedback.
-
|
Better in this discussion #130 |
Beta Was this translation helpful? Give feedback.
-
|
There isn't much to do, really. So all I had to do was just import it: sudo mokutil --import /var/lib/dkms/mok.pubYou will need to create a password that will be required by MOK Manager after rebooting. You can then easily check if everything is working with: modinfo msi_ec | egrep 'filename|signer|sig_key|vermagic'
filename: /lib/modules/6.16.7-200.fc42.x86_64/extra/msi-ec.ko.xz
vermagic: 6.16.7-200.fc42.x86_64 SMP preempt mod_unload
signer: DKMS module signing key
sig_key: XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
lsmod | grep msi_ec
msi_ec 36864 0
modinfo -n msi_ec
/lib/modules/6.16.7-200.fc42.x86_64/extra/msi-ec.ko.xzFrom what I understand, DKMS will automatically sign the driver again on the next kernel update. |
Beta Was this translation helpful? Give feedback.
-
Okay, that's part which interested me the most. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
@glpnk I can confirm that DKMS automatically handles signing modules on kernel updates: Executing %posttrans scriptlet: kernel-core-0:6.16.8-200.fc42.x86_64
Scriptlet %posttrans terminated: kernel-core-0:6.16.8-200.fc42.x86_64
Scriptlet output:
Sign command: /lib/modules/6.16.8-200.fc42.x86_64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Autoinstall of module acpi_ec/1.0.4 for kernel 6.16.8-200.fc42.x86_64 (x86_64)
Deprecated feature: CLEAN (/var/lib/dkms/acpi_ec/1.0.4/source/dkms.conf)
Building module(s).... done.
Signing module /var/lib/dkms/acpi_ec/1.0.4/build/src/acpi_ec.ko
Installing /lib/modules/6.16.8-200.fc42.x86_64/extra/acpi_ec.ko.xz
Running depmod........ done.
Autoinstall of module msi_ec/0.12 for kernel 6.16.8-200.fc42.x86_64 (x86_64)
Building module(s).... done.
Signing module /var/lib/dkms/msi_ec/0.12/build/msi-ec.ko
Found pre-existing /lib/modules/6.16.8-200.fc42.x86_64/kernel/drivers/platform/x86/msi-ec.ko.xz, archiving for uninstallation
Installing /lib/modules/6.16.8-200.fc42.x86_64/extra/msi-ec.ko.xz
Running depmod....... done.
Autoinstall on 6.16.8-200.fc42.x86_64 succeeded for module(s) acpi_ec msi_ec. |
Beta Was this translation helpful? Give feedback.
Currently we are restructuring supported device list and thinking about way to support roughly all existing and future models. So no plans to upstream.
Upstreamed version supported only battery limit.
We don't know how much time will take to upstream new version, which contains many features in comparison to one in kernel.
Small patches often applied every minor release of kernel, but upstream of other driver
msi-wmi-platformis taking more time, if it's really being pushed to kernel, which I don't know.