Comment 2 for bug 1811157

This is not an issue with the kernel itself, but with the update process. Presumably this needs to be solved by changing the way the kernel is packaged, without touching the kernel itself.

I just ran into this issue again. It appears to affect all DKMS modules (I am also running anbox, installed from a third-party repo, and it is also affected). I was able to solve this by running `sudo apt-get --reinstall install` for all my DKMS modules after a kernel upgrade, but before rebooting. This reinstalls a module for every kernel on the machine, i.e. the old and the new one.

The way to fix this is probably the following:

* After installing a new kernel, gather a list of all DKMS modules which were installed via deb packages.
* Then run `sudo apt-get --reinstall install` for the DKMS module packages.

The only difficulty might be to determine a list of DKMS module packages currently on the machine. If there is no other way, a solution might be to require all DKMS module packages to add their name to a text config file, and pull the list of modules to reinstall from that file.

Would that kind of packaging-only change be taken care of by the kernel devs? If so, where can I reach them? If not, who maintains the deb package spec for the kernel?