Thanks for replying. So, one consequence of this design decision is that if you select a different kernel from the GRUB boot menu, dkms modules will fail to build for that kernel and subsequently won't load. This creates a negative user experience, if the user (like me) expects to be able to switch freely between between kernel versions. This can be especially harmful if (again, as in my case) a new kernel version introduces a regression, and so I try to boot the old version, but now that version doesn't work either due to not loading kernel modules; the result is that no matter what version I select from GRUB, I have a broken system.
So, I would urge you to reconsider that design decision.
In any case, is it possible to re-enable the old behavior of automatically rebuilding kernel modules on boot as necessary?
Mario,
Thanks for replying. So, one consequence of this design decision is that if you select a different kernel from the GRUB boot menu, dkms modules will fail to build for that kernel and subsequently won't load. This creates a negative user experience, if the user (like me) expects to be able to switch freely between between kernel versions. This can be especially harmful if (again, as in my case) a new kernel version introduces a regression, and so I try to boot the old version, but now that version doesn't work either due to not loading kernel modules; the result is that no matter what version I select from GRUB, I have a broken system.
So, I would urge you to reconsider that design decision.
In any case, is it possible to re-enable the old behavior of automatically rebuilding kernel modules on boot as necessary?