Hi, I had virtualbox-ose runny on a ubuntu hardy box. Then the recent kernel update 2.6.24-17 -> 2.6.24-18 broke it.
First I googled for a solution and found several suggestions that don't work. Apparently there were some tools designed to solve this problem. But they were broken, and somebody decided to remove them instead of fixing them. Saw some comments somewhere about how there were package dependencies, but they didn't work, so they were removed. The problem is that we need modules compiled for the current kernel, and so far there is no package available in the hardy repositories with modules compiled for 2.6.24-18. Which breaks some of the commonly recommended solutions Somebody removed "setup" from /etc/init.d/vboxdrv this breaks another commonly recommended solution. somebody suggested: > sudo apt-get install virtualbox-ose-source > sudo m-a update > sudo m-a prepare > sudo m-a a-i virtualbox-ose > sudo /etc/init.d/vboxdrv restart which did solve the problem. Although I do wonder if the package I build using this procedure will be replaced at the appropriate time when new packages hit the repositories. >From what I see in google folks struggle with this problem everytime a new kernel comes out and waste their time trying solutions that don't work, until they either give up, or finally stumble across a correct solution. If nothing else you need to publish a correct solution, and peform the voodoo to make sure it comes up high on google's search results. Better yet solve the problems instead of just deleting the broken solutions and leaving your users to figure it out on their own. -- Drew Einhorn
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
