Kernel Update broke VirtualBox

Sergio Belkin sebelk at gmail.com
Thu Jun 5 01:58:24 UTC 2008


2008/6/4 NoOp <glgxg at sbcglobal.net>:
> On 06/03/2008 06:41 PM, drew einhorn wrote:
>> First time I ran into this problem I flailed around, google found me
>> lots of people with the same problem, but no solution.  At last I
>> discovered the problem was that there was a problem with the
>> dependency on the appropriate VirtualBox modules packages both modules
>> and guest-modules.  So rather than fix the problem, someone removed
>> the dependencies.
>>
>> With the latest kernel update 2.6.24-17-generic -> 2.6.24-18-generic
>> there are not yet any VirtualBox modules for this kernel.  So for the
>> time being I tried editing my grub.conf to use the 2.6.24-17 kernel.
>> Somebody decided they didn't like the name grub.conf and changed it to
>> menu.lst, and decided to remove the symbolic link that was supporting
>> us backward folks who aren't up with the latest and greatest naming
>> conventions.  That's rude and annoying. How expensive is one lousy
>> symbolic link for backward compatibility
>>
>> So will the VirtualBox module packages soon appear?
>>
>> How urgent is the 2-6.24-17 -> 2.6.24-18 upgrade?
>>
>> Should I download the source and figure out how to build my own
>> VirtualBox modules,
>> or should I just wait?
>>
>
> Or you could just follow the instructions in the VirtualBox error popup
> that tells you to run /etc/init.d/vboxdrv setup
> Just remember to use 'sudo /etc/init.d/vboxdrv setup'
>
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>


Other way of doing things is using module-assistant and so on...
-- 
--
Open Kairos http://www.openkairos.com
Watch More TV http://sebelk.blogspot.com
Sergio Belkin -




More information about the ubuntu-users mailing list