The binary packages for different Puppy versions don't include the sources to compile the kernel drivers; I cut them out to save some size. That's why it complains the files aren't present.KusaNoKaito wrote:I'm using Lucid Puppy 5.1.1 and when running /etc/init.d/vboxdrv setup, all I get is this:
I ideas?Code: Select all
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. Stopping VirtualBox kernel modules ...done. Uninstalling old VirtualBox DKMS kernel modules/etc/init.d/vboxdrv: line 284: /opt/VirtualBox/src/vboxhost/do_dkms: No such file or directory ...done. Trying to register the VirtualBox kernel modules using DKMS/etc/init.d/vboxdrv: line 302: /opt/VirtualBox/src/vboxhost/do_dkms: No such file or directory ...failed! (Failed, trying without DKMS) Recompiling VirtualBox kernel modules ...failed! (Look at /var/log/vbox-install.log to find out what went wrong)
If things work properly, you shouldn't need to compile them. (You should be using the package "virtualbox-4.0.6-k2.6.33.2.lupu5.pet" if you're running Lucid 511 with the regular kernel, by the way.)
If you do need to compile the kernel drivers, though, you can always download the "virtualbox-4.0.6-all_kernels.pet" package, which does not include already-compiled drivers but still has the source included in the package, and which will compile the drivers during installation of the dot-pet. (Just make sure you have the kernel source module and devx module installed for your Puppy version.)
(Lucid Puppy's kernel source is here.)
I am preparing packages for VBox version 4.1.0 as we speak. The "all_kernels" package has already been prepared and uploaded. I'll update the thread title and post once everything is in place.
In the meantime, if you want to get started right away (8)), you can go to http://www.silverdollarsolutions.com/Pu ... Box-4.1.0/, but you'll have to fend for yourself until I've uploaded the HTML guide page.