I tested Laney's patch via the following: - boot a yakkety desktop virtual machine - installed virtualbox-dkms - modified /etc/apt/sources.list for zesty - installed new dkms package - edited /usr/lib/dkms/common.postinst - modified /etc/apt/sources.list for yakkety - ran do-release-upgrade -d - [...] - dkms status
bdmurray@clean-yakkety-amd64:~$ dkms status virtualbox, 5.1.18, 4.10.0-19-generic, x86_64: installed virtualbox, 5.1.18, 4.8.0-26-generic, x86_64: installed Also in /var/log/dist-upgrade/apt.log we can see: Setting up virtualbox-dkms (5.1.18-dfsg-1build1) ...^M Loading new virtualbox-5.1.18 DKMS files...^M Building for 4.8.0-26-generic 4.10.0-19-generic^M Building initial module for 4.8.0-26-generic^M Notice it is building for two kernels now not one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1681566 Title: nvidia-375 DKMS module not recompiled on upgrade to 17.04 Status in dkms package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in virtualbox package in Ubuntu: Confirmed Bug description: When upgrading from 16.10 to 17.04 using `update-manager -d`, the `nvidia-375` DKMS modules are not compiled for the new kernel. The result is that the user must run `apt install --reinstall nvidia-375` and reboot. To reproduce this: - Clean install of 16.10 on a system with NVIDIA graphics - Install `nvidia-375` - Run `update-manager -d`, complete all steps, then reboot - You will be unable to login until running `apt install --reinstall nvidia-375` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1681566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
