Run sudo dracut to create the initramfs and report what errors you see.
Iāve been having the same issue for ages where EVERY update I need to dracut regenerate all, on two different laptops. Looked into the logs and Evdi is what throws a dkms error. (Iāve got display link drivers installed on both machines for work docks)
I am running dkms-3.1.8 though, which according to this thread should fail the update entirely, rather than allow a broken update to go through.
Yep, evdi was my issue as well, I updated it to the latest version, letās see if it works for next kernel update.
I still keep having this issue, it just reappeared recently and each update I have to generate the initramfs. Where do I track down whatās causing this?
It has so far always been an issue with a DKMS built module that fails to build on a new kernel. Is that the case for you as well?
Yeah it looks like that is still the case, keeps happening to the XONE module.
I am not sure why it is failing on that consistently.
Jul 20 11:17:26 fedora dkms[1612]: (bad exit status: 2)
Jul 20 11:17:26 fedora dkms[2655]: Error! Bad return status for module build on kernel: 6.15.6-200.fc42.x86_64 (x86_64)
Jul 20 11:17:26 fedora dkms[2655]: Consult /var/lib/dkms/xone/v0.3-101-gaeb27e6/build/make.log for more information.
Jul 20 11:17:26 fedora dkms[1275]: Autoinstall on 6.15.6-200.fc42.x86_64 failed for module(s) xone(10).
Jul 20 11:17:26 fedora kernel: cdc_acm 1-3.4:1.2: ttyACM0: USB ACM device
Jul 20 11:17:26 fedora kernel: usbcore: registered new interface driver cdc_acm
Jul 20 11:17:26 fedora kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Jul 20 11:17:26 fedora dkms[2657]: Error! One or more modules failed to install during autoinstall.
Jul 20 11:17:26 fedora dkms[2657]: Refer to previous errors for more information.
Jul 20 11:17:26 fedora systemd[1]: dkms.service: Main process exited, code=exited, status=11/n/a
Jul 20 11:17:26 fedora systemd[1]: dkms.service: Failed with result 'exit-code'.
Jul 20 11:17:26 fedora systemd[1]: Failed to start dkms.service - Builds and install new kernel modules through DKMS.
Looks like there is an update for the driver I will rebuild and wait for the next kernel update.
As you are using an out-of-tree kernel module you will need to check that your driver code is up to date for each kernel.
Fedora does not do that for you.
1 Like
No, but my understanding of the issue that is raised above, and the fix that should have been released, is that in the event of an incompatible kernel module, then dkms should throw an error, and no broken boot entries should be created.
There is a problem with some out of date kernel modules, but fedora isnāt supposed to fail silently. Booting into a broken system is a much worse experience than having a system fail to update kernel
As I understand it there is a issue with the order that things are installed that makes it very hard to prevent the entry being added. Iām not sure if that issue is being worked on.