I've build Dkms in Fedora I've used before under Ubuntu for my DVB cards. Fedora use weak-updates for previous kernel module loading, and this contains wrong symlinks to the newest Kernel module instead the relevant kernel module. Example, I got update to kernel 5.8 today. The module for kernel 5.8 works , but i have, as example for previous kernel : ls -l /lib/modules/5.7.17-200.fc32.x86_64/weak-updates lrwxrwxrwx. 1 root root 54 4 sept. 10:21 stb0899.ko.xz -> /lib/modules/5.8.4-200.fc32.x86_64/extra/stb0899.ko.xz instead: lrwxrwxrwx. 1 root root 54 4 sept. 10:21 stb0899.ko.xz -> /lib/modules/5.7.17-200.fc32.x86_64/extra/stb0899.ko.xz (module is in correct place but wrong symlink) So when i boot to previous kernel, modules loading fails . I know i can manually change the symlinks of each line at each kernel update, but this is not the purpose of dkms ,isen't it ? Can you correct the dkms routine ?
No Answer ?
I've found the solution for my modules. Thanks to the internet because no help from Fedora teams nor DKMS manual pages. The normal way is to not use weak-updates for DKMS. As Fedora /CentOs and I presume Redhat use weak-updates as default conf, you have to add in each dkms.conf a line : NO_WEAK_MODULES="true" or NO_WEAK_MODULES="yes" Tested this morning for kernel updates, ow previous kernel modules are loading If a maintainer comes here please tell the dev team to update the dkms manual page!
FEDORA-2020-f876bb28c8 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f876bb28c8
FEDORA-EPEL-2020-6c6bb5bdfc has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6c6bb5bdfc
FEDORA-2020-3776969d93 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-3776969d93
FEDORA-EPEL-2020-ad3fed49e0 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ad3fed49e0
FEDORA-2020-f876bb28c8 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f876bb28c8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f876bb28c8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-6c6bb5bdfc has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6c6bb5bdfc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-3776969d93 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-3776969d93` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-3776969d93 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-ad3fed49e0 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-ad3fed49e0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-3776969d93 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-f876bb28c8 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
I've got finally updated dkms with updated manual, definitively solved !
FEDORA-EPEL-2020-6c6bb5bdfc has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-ad3fed49e0 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.