Good idea; i wonder why it has not been ran on upgrade (as it usually do) sudo dpkg-reconfigure virtualbox-dkms [sudo] password for oem: Loading new virtualbox-5.0.16 DKMS files... Building only for 4.4.0-20-generic Building initial module for 4.4.0-20-generic Done.
vboxdrv: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.4.0-20-generic/updates/dkms/ vboxnetadp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.4.0-20-generic/updates/dkms/ vboxnetflt.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.4.0-20-generic/updates/dkms/ vboxpci.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.4.0-20-generic/updates/dkms/ depmod......... DKMS: install completed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571210 Title: virtualbox[1239]: * No suitable module for running kernel found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571210/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
