(old)Puppy Linux Discussion Forum

KusaNoKaito wrote:I'm using Lucid Puppy 5.1.1 and when running /etc/init.d/vboxdrv setup, all I get is this:

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)

I ideas?

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.

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.

Nevermind version 4.1.0. I ended up skipping right past it, for the most part!

Updated to version 4.1.2
Please see the first post for more details.

I went in and cleaned up (well, a little bit) the scattered HTML pages I had to sort through the packages. It should be a little simpler now.

I also added another simple page the just lists the different packages, because there are some Puppy versions covered only by older packages, namely a few Wary and Quirky releases. It can be easy to just look at the latest VBox page, see nothing for your Puppy and give up.

It's accessible from the main page I link to at the beginning of the thread, and here: all_paks.html

Looking at it, I'm considering deleting all of 4.0.0, 4.0.2, 4.0.4, and 4.1.0. They offer nothing extra in features or compatibility/lack of bugs next to the rest, and I have no packages exclusive to them in terms of kernel or Puppy version, so I don't see the point in hanging on to them. (The rest would remain available, even 3.1.4.) Let me know if anyone needs those packages, otherwise I'll probably delete them in a week or two to save some space.

Asterisk! and Geoffrey - Many thanks.

I have been experimenting with Slacko beta 2, which has the 2.6.37.6 kernel. I downloaded VirtualBox-4.1.0-73009-Linux_x86.run from virtualbox.org, installed the devx file and the kernel sources. VBox compiled with no problems but refused to run because of missing library files.

I had the SDL-1.2.14-i486 package already installed for DosBox so I just downloaded Geoffrey's quirky1.20-libGLU.tar.gz and unpacked the contents into /usr/lib.

Worked perfectly, sound and all.

Keep up the good work!

Removed Placeholder

drblock2 wrote:Asterisk! and Geoffrey - Many thanks.

I have been experimenting with Slacko beta 2, which has the 2.6.37.6 kernel. I downloaded VirtualBox-4.1.0-73009-Linux_x86.run from virtualbox.org, installed the devx file and the kernel sources. VBox compiled with no problems but refused to run because of missing library files.

I had the SDL-1.2.14-i486 package already installed for DosBox so I just downloaded Geoffrey's quirky1.20-libGLU.tar.gz and unpacked the contents into /usr/lib.

Worked perfectly, sound and all.

Keep up the good work!

Cool! Good to know nothing big seems to be broken in Slacko.

I'm always a bit of a reluctant upgrader, so I probably won't move all my things to a Slacko installation for a while yet. I think I might go ahead and compile and package VBox 4.1.2 this weekend anyway, though. I'll be sure to let you all know if and when I do.

@gcmartin: I'll be sending you a PM reply in the next few minutes.

virtualbox-4.1.4-dpup.sfs for all Puppies 5.x.
http://www.murga-linux.com/puppy/viewto ... 055#481055

(UPDATE: 14-Oct-2011) virtualbox-4.1.4-1-dpup.sfs

• Rolled back /opt/VirtualBox/VboxKeyboard.so to that of VirtualBox-3.2.8 because of Japanese keyboard problem.
• Add kernel module for 2.6.32-smp of recent wary.

I installed VirtualBox from quickpet, but when I try to run it I get the message that the kernel driver is not installed and I need to run '/etc/init.d/vboxdrv setup'. I did that but I still get the same error. What now?

Chuck

cprivers wrote:I installed VirtualBox from quickpet, but when I try to run it I get the message that the kernel driver is not installed and I need to run '/etc/init.d/vboxdrv setup'.

depends on the kernel version version of your puppy.
cprivers, what puppy are you using?

Using LUPU-528 kernel 2.6.33.2

Chuck

cprivers wrote:Using LUPU-528 kernel 2.6.33.2

Try virtualbox-4.1.4-1-dpup.sfs at the third post of this topic.
http://www.murga-linux.com/puppy/viewto ... 055#481055

You can load it by the sfs_load at the main menu > Setup > Setup Puppy.

Shinobar,

I didn't know about that trick, so I will have to try it.

I clicked on the SFS to mount it but still couldn't run VirtualBox. I then tried to auto-mount the SFS using BootManager, but I got an error saying that there are no SFS files in directory /mnt/home (or they all have the wrong *_nnn.sfs version number). I moved the file to /mnt/home but got the same error message trying to load it with BootManager.

Chuck

I mounted the SFS, and when it asked me if I wanted to run it, I answered 'yes', but nothing happened. I then ran virtualbox from a terminal and got the "vboxdrv kernel module is not loaded" message.

I ran "/etc/init.d/vboxdrv setup" got:

"Stopping VirtualBox kernel modules:Uninstalling old VirtualBox DKMS kernel modules:Removing old VirtualBox pci kernel module:Removing old VirtualBox netadp kernel module:Removing old VirtualBox netflt kernel module:Removing old VirtualBox kernel module:Trying to register the VirtualBox kernel modules using DKMS:
Error! Bad return status for module build on kernel: 2.6.33.2 (i686)
Consult the make.log in the build directory
/var/lib/dkms/vboxhost/4.1.4/build/ for more information.

DO YOU HAVE make INSTALLED???

Recompiling VirtualBox kernel modules:

The make.log:

DKMS make.log for vboxhost-4.1.4 for kernel 2.6.33.2 (i686)
Mon Oct 17 18:29:32 GMT-8 2011
/usr/sbin/dkms: line 28: make: command not found

I also have /kernel_src_L4-2.6.33.2-patched.sfs loaded, so I thought the "make" command would be in that.

Lost & confused at this point. I had VirtualBox running in Ubuntu Lucid in about 15 minutes, but I wanted to use Puppy. After about 4 hours of trying, I'm not sure it's worth the trouble.

cprivers wrote: I then ran virtualbox from a terminal and got the "vboxdrv kernel module is not loaded" message. .

Is it all the error message?
I guess the problem comes from the conflict of old VirtualBox PET or something and the new SFS.

1. Remove all the VirtualBox PET and SFS.
2. Remove '/lib/modules/2.6.33.2/misc/vbox*.ko' if they are exists.
3. Then retry the new SFS.

READ THIS if you want to start from the beginning.
If you are installing Puppy in 'Full' install style, it is not easy to recover the original state.
It may be not used to for the newcomer from other Linux, but the 'Frugal' install style is recommended for Puppy. 'Frugal' install makes 'pupsave' file in which all modification is packed. You can easily recover the original state with running 'pfix=ram' boot option.

Thanks. I'll try removing everything. I usually do a frugal install, but this time I wanted to use the whole hard disk because I wanted to run virtual machines. I figured that VB would create the files in the pupsave file, and I don't know how to make it put the files somewhere else.

Chuck

cprivers wrote:I figured that VB would create the files in the pupsave file, and I don't know how to make it put the files somewhere else.

You can change 'Default Machine Folder' to /mnt/home/VirtualBox or somewhere.
The setting is at VirtualBox menubar, File>>Preferences>>General.

Thanks. That should help.

Chuck

I haven't forgotten about you all! Honest!

I've been far busier than I'd like with my non-Puppy life, but I have made some VBox 4.1.4 packages for several versions. I'll upload them sometime tonight, and update the thread. (I'll make sure shinobar's package is mentioned with the relevant information, too. Might mirror it, too.)

The VMware Player thread will get updated soon, too, though I can't promise tonight.

Some 4.1.4 packages added. Waiting to download latest Wary, Quirky & Slacko to build and upload more.

TheAsterisk! wrote:I haven't forgotten about you all! Honest!

I've been far busier than I'd like with my non-Puppy life, but I have made some VBox 4.1.4 packages for several versions. I'll upload them sometime tonight, and update the thread. (I'll make sure shinobar's package is mentioned with the relevant information, too. Might mirror it, too.)

The VMware Player thread will get updated soon, too, though I can't promise tonight.

Some 4.1.4 packages added. Waiting to download latest Wary, Quirky & Slacko to build and upload more.

I am looking forward for the Virtualbox for Slacko puppy 5.3

I hope it will be available soon