Having to rerun the build multiple times Is certainly a different bug. I would say that is important to fix.
Do we have an understanding for what is happening there? When you run modinfo on the next boot is the module not there? Is something deleting it? If we were to add an init script or upstart job, that would just be a band aid to the real problem at hand. On Jul 15, 2010 3:15 PM, "Kat Amsterdam" <[email protected]> wrote: The problem is that the module has to be rebuilt at every reboot of the system. The system does not remember the same module of the same kernel. Real World situation: Every day that I go to work I need to run a virtual machine on my laptop. Every day when I start up the laptop I have to rebuild the kernel module (which takes 5-10 minutes). In previous versions of Ubuntu when I would start the laptop (using the same kernel) the vitual machine would "just work" Doing this every day has become a major irritator. The kernel module should only have to be built one time, when a kernel has changed... Ubuntu Lucid should keep the kernel module each time, so I don't have to rebuild every day. I understand the need for speed (10 second from power off to desktop is excellent). but I don't understand why an already built module is not rememberd by the current kernel Thus this is still a bug. -- dkms is not processing vboxdrv must do manually https://bugs.launchpad.net/bugs/600517 You rece... -- dkms is not processing vboxdrv must do manually https://bugs.launchpad.net/bugs/600517 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
