On Sun, 11 Nov 2007 18:00:51 +0000
Adam Trickett <adam.trickett@???> wrote:
> On Sunday 11 Nov 2007, Jack Knight wrote:
> > john lewis wrote:
> > >
> > > I am wondering if a recent kernel update may have messed
> > > things up. I am going to purge virtualbox-ose
> > > virtualbox-ose-source and then re-install them
> >
> > Hmm.
> >
> > I think it more likely you need to rebuild the Vbox kernel
> > modules. There is help on the VBox wiki as well as elsewhere.
> > For the purposes of trying things out though, I'd be inclined to
> > use the binary install - if in doubt email them about t&c's -
> > they are very anti-draconian. I did just that and asked about a
> > couple of commercial licenses for the (albeit unspecified)
> > purpose of writing an article, and the prompt reply was that it
> > fell in the category of "personal use" even though I had enquired
> > in the capacity of a company officer about commercial usage.
>
> Changing kernel will break it for sure. Rebuilding the kernel
> module under Debian is a 20 seconds job.
>
> sudo m-a prepare
> sudo m-a a-i virtualbox-ose
> sudo modprobe vboxdrv
done that with the addition of -f to force a rebuild of the modules
but still no joy with loading the XPPro-vdi
I created a new vdi using an iso image for the debian-kde4.beta but
get the same error messages when I try to run it.
I'll try getting the binary and see if that works any better.
--
John Lewis
Debian (Sid) with the GeneWeb genealogy package
