Problem running virtualbox in tahrpup
Problem running virtualbox in tahrpup
I'm trying to run virtualbox in tahrpup and this message pops up
- Attachments
-
- capture17517.png
- (81.04 KiB) Downloaded 864 times
you need to download the kernel source which is an sfs file
load this and then there is a way to build the vboxdrv so VirtualBox will start
use the SFS-Loader in puppy linux to load the kernel source SFS file then
in a terminal ->
it is something along these lines.
then restart VirtualBox
load this and then there is a way to build the vboxdrv so VirtualBox will start
use the SFS-Loader in puppy linux to load the kernel source SFS file then
in a terminal ->
Code: Select all
/etc/init.d/vboxdrv setup
then restart VirtualBox
I cann't find /etc/init.d/vboxdrv
And here is the output from log file:
Uninstalling modules from DKMS
removing old DKMS module vboxhost version 4.3.8
------------------------------
Deleting module version: 4.3.8
completely from the DKMS tree.
------------------------------
Done.
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxhost/4.3.8/source ->
/usr/src/vboxhost-4.3.8
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area.....
make KERNELRELEASE=3.14.20 -C /lib/modules/3.14.20/build M=/var/lib/dkms/vboxhost/4.3.8/build......................................................
cleaning build area....
DKMS: build completed.
vboxdrv:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.14.20/kernel/misc/
vboxnetflt.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.14.20/kernel/misc/
vboxnetadp.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.14.20/kernel/misc/
vboxpci.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.14.20/kernel/misc/
depmod.............
DKMS: install completed.
Output from virtualbox.log:
Uninstalling modules from DKMS
removing old DKMS module vboxhost version 4.3.8
-------- Uninstall Beginning --------
Module: vboxhost
Version: 4.3.8
Kernel: 3.14.20 (i686)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
vboxdrv.ko:
- Uninstallation
- Deleting from: /lib/modules/3.14.20/kernel/misc/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
vboxnetflt.ko:
- Uninstallation
- Deleting from: /lib/modules/3.14.20/kernel/misc/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
vboxnetadp.ko:
- Uninstallation
- Deleting from: /lib/modules/3.14.20/kernel/misc/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
vboxpci.ko:
- Uninstallation
- Deleting from: /lib/modules/3.14.20/kernel/misc/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod........
DKMS: uninstall completed.
------------------------------
Deleting module version: 4.3.8
completely from the DKMS tree.
------------------------------
Done.
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxhost/4.3.8/source ->
/usr/src/vboxhost-4.3.8
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area.....
make KERNELRELEASE=3.14.20 -C /lib/modules/3.14.20/build M=/var/lib/dkms/vboxhost/4.3.8/build............
And here is the output from log file:
Uninstalling modules from DKMS
removing old DKMS module vboxhost version 4.3.8
------------------------------
Deleting module version: 4.3.8
completely from the DKMS tree.
------------------------------
Done.
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxhost/4.3.8/source ->
/usr/src/vboxhost-4.3.8
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area.....
make KERNELRELEASE=3.14.20 -C /lib/modules/3.14.20/build M=/var/lib/dkms/vboxhost/4.3.8/build......................................................
cleaning build area....
DKMS: build completed.
vboxdrv:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.14.20/kernel/misc/
vboxnetflt.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.14.20/kernel/misc/
vboxnetadp.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.14.20/kernel/misc/
vboxpci.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.14.20/kernel/misc/
depmod.............
DKMS: install completed.
Output from virtualbox.log:
Uninstalling modules from DKMS
removing old DKMS module vboxhost version 4.3.8
-------- Uninstall Beginning --------
Module: vboxhost
Version: 4.3.8
Kernel: 3.14.20 (i686)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
vboxdrv.ko:
- Uninstallation
- Deleting from: /lib/modules/3.14.20/kernel/misc/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
vboxnetflt.ko:
- Uninstallation
- Deleting from: /lib/modules/3.14.20/kernel/misc/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
vboxnetadp.ko:
- Uninstallation
- Deleting from: /lib/modules/3.14.20/kernel/misc/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
vboxpci.ko:
- Uninstallation
- Deleting from: /lib/modules/3.14.20/kernel/misc/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod........
DKMS: uninstall completed.
------------------------------
Deleting module version: 4.3.8
completely from the DKMS tree.
------------------------------
Done.
Attempting to install using DKMS
Creating symlink /var/lib/dkms/vboxhost/4.3.8/source ->
/usr/src/vboxhost-4.3.8
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area.....
make KERNELRELEASE=3.14.20 -C /lib/modules/3.14.20/build M=/var/lib/dkms/vboxhost/4.3.8/build............
I was looking at the ubuntu forum where I was told to do a:
modprobe vboxdrv on terminal which produced output below. Where do I get vboxdrv for tahrpup?.
modprobe vboxdrv on terminal which produced output below. Where do I get vboxdrv for tahrpup?.
- Attachments
-
- capture32511.png
- (78.63 KiB) Downloaded 367 times
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
Agree with that due to error message posted.rockedge wrote:you need to download the kernel source which is an sfs file
load this and then there is a way to build the vboxdrv so VirtualBox will start
use the SFS-Loader in puppy linux to load the kernel source SFS file then
in a terminal ->it is something along these lines.Code: Select all
/etc/init.d/vboxdrv setup
then restart VirtualBox
To compile stuff in puppy you need
1. Devx
2. Kernel sources
3. Kernel headers
These can be downloaded from usually the same directory tree you got puppy from.
These packages are operating system specific. You need the exact versions produced for your specific version of tahrpup.
I believe some of the tahr pup versions overlap due to the kernel being the same.
The packages are kernel specific.
.
the headers will be in the kernel sources sfs I think. I have done this a few times successfully but it has been awhile......
I just got VirtualBox Version 5.2.18 r124319 (Qt5.9.5) going in
a 32bit BIonic using the 4.17.9 kernel I compiled
first download your matching kernel sources and install using SFS-Load_on_the_Fly mine was 4.17.9 that I already have.
then I downloaded virtualbox-5.2_5.2.18-124319~Ubuntu~zesty_i386.deb
from https://www.virtualbox.org/wiki/Linux_Downloads
then IMPORTANT (you might have to enter it 2x in the terminal)
using the PPM installed
libcurl3
libQt5x11extras
libQt5widgets
libQt5printsupport
now click on the virtualbox-5.2_5.2.18-124319~Ubuntu~zesty_i386.deb and let it install. Now in a terminal
let it finish completely now from the menu or terminal start virtualbox
I just got VirtualBox Version 5.2.18 r124319 (Qt5.9.5) going in
a 32bit BIonic using the 4.17.9 kernel I compiled
first download your matching kernel sources and install using SFS-Load_on_the_Fly mine was 4.17.9 that I already have.
then I downloaded virtualbox-5.2_5.2.18-124319~Ubuntu~zesty_i386.deb
from https://www.virtualbox.org/wiki/Linux_Downloads
then IMPORTANT (you might have to enter it 2x in the terminal)
Code: Select all
addgroup vboxusers
libcurl3
libQt5x11extras
libQt5widgets
libQt5printsupport
now click on the virtualbox-5.2_5.2.18-124319~Ubuntu~zesty_i386.deb and let it install. Now in a terminal
Code: Select all
vboxconfig
Code: Select all
VirtualBox
- Attachments
-
- Screenshot(3).png
- (81.58 KiB) Downloaded 809 times
Virtualbox 5.1.10 - 112026
@gabtech
here VirtualBox 5.1.10 with included kernel modules for K 3.14.20 noPAE I built just right now.
( all included nothing additional to install )
happy virtualboxing
here VirtualBox 5.1.10 with included kernel modules for K 3.14.20 noPAE I built just right now.
( all included nothing additional to install )
happy virtualboxing
- Attachments
-
- virtualbox_5.1.10-112026_600x375.jpg
- VirtualBox 5.1.10-112026
- (114.04 KiB) Downloaded 822 times
Thanks for the latest virtualbox. Just downloaded it and tried to run it; resulting in the output in the attachment. The log file reads:
Makefile:183: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
Makefile:183: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
- Attachments
-
- capture24039.png
- (229.08 KiB) Downloaded 329 times
- perdido
- Posts: 1528
- Joined: Mon 09 Dec 2013, 16:29
- Location: ¿Altair IV , Just north of Eeyore Junction.?
Hi gabtech,gabtech wrote:Thanks for the latest virtualbox. Just downloaded it and tried to run it; resulting in the output in the attachment. The log file reads:
Makefile:183: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again. Stop.
Did you try the SFS from norgo?
To load the SFS
1.Copy the SFS to /mnt/home/
2.Then open the program Menu -->Setup --SFS-Load on-the-fly
3. Load the SFS
After that successfully runs you should have a menu entry usually in Menu -->System --Oracle VM Virtualbox
.
- James186282
- Posts: 270
- Joined: Tue 08 Sep 2009, 19:14
- Location: Minnesota
I have had occasion to figure something out then promptly forget all their weird things I had to do to get it working. This is part of the reason I'm making this. The second reason is that I've gotten tons of help (Which I appreciate) but I really want to know why I'm doing something. For example - why would I need the the devx_xenialpup64_7.5.sfs file loaded? The answer of course is this is the system that lets you compile source code and make kernel modules or programs.
You can use the basic ideas to setup VirtualBox for 32 bit cpus or tahrpup but this is very specific,
How to get VirtualBox working on XenalPup using an AMD Athlon 64 CPU
You need to set up xenialpup to compile programs so for the 7.5 version of xenialpup you need the devx_xenialpup64_7.5.sfs file. You will find it where you found the xenialpup.iso file. The link (Today) is
http://distro.ibiblio.org/puppylinux/puppy-xenial/64/
You will see the .iso for making an install-able xenialpup bootable CD and the devx file to make your maching be able to compile source code.
If you not sure you should verify that you have a 64 bit CPU (like me)
uname -a
Linux puppypc24847 4.9.58 #1 SMP PREEMPT Mon Nov 13 15:54:01 GMT 2017 x86_64 x86_64 x86_64 GNU/Linux
it returns x86_64 (several times) so we know we have a 64 bit CPU.
So assuming you have found the devx_xenialpup64_7.5.sfs file you can load it in with the SFS-Load on-the-fly program. Its pretty cool because once done you can compile source code into programs or as with this case a kernel module.
We need to have the operating system (xenialpup) header files. This is source from the system that we need to make a system kernel file. It assures it will plug into xenialpup You could do uname -a ALL or just uname -r to see the header file version without all the rest
uname -r
*Note if your curious type uname --help and it will spell out all possible commands.
Using the SFS-Load on-the-fly program load the 4.9.58 headers.sfs file. These are the Kernel sources file headers for xenialpup. Verify that your headers match the version you got when you ran uname - r On my machine I loaded the .sfs file using (again) the SFS-load on-the-fly program. So load
kernel_sources-4.9.58-xenialpup64.sfs
Now using Palemoon or Firefox, Chrome etc etc etc go to the VirtualBox download page
https://www.virtualbox.org/wiki/Linux_Downloads
Now you need to know which system xenial pup is based on. Here are some examples
14.04 LTS (Trusty Tahr) *Note LTS means Long Time Supported. Its not a beta test version.
14.10 (Utopic Unicorn)
15.04 (Vivid Vervet)
15.10 (Wily Werewolf)
16.04 LTS (Xenial Xerus) <- THATS IT!!! xenialpup is based on Ubuntu Xenial
I selected the xenial version 16.04 AMD64 .deb file. I double clicked it and it told me everything was set up (Not!) and I could run Virtual box from the menu. This is not correct so back to the terminal I typed
VirtualBox <-note caps on V and B. I got an error informing me that the vboxdrv was not loaded. The reason for this is that I had not compiled a vboxdrv kernel module.
The error message invited me to run sudo /sbin/vboxconfig First we are always root so we don't use sudo. Second running /sbin/vboxconfg will compile a new kernel module. Getting the devx and kernal modules are the first part which is understandable. To actually make it work these are the werid things you need to take care of.
1) If you click to the /etc/rc.d directory you probably won't see subdirectories named rc0.d rc1.d rc2.d rc3.d rc4.d rc5.d rc6.d If you do? Fine other wise you will need to make these directories or virtual box will cough up a hairball. Why it doesn't just make up these directories itself is a mystery. Maybe puppy is the only distro that doesn't have them? I don't know so lets just do it.
2) VirtualBox assumes that we have a vboxusers group setup. To get past it complaining just run.
adduser -D -H vboxusers
Now VirtualBox has its user group and won't spew out error messages.
Now from terminal its ok to try running
/sbin/vboxconfig
If you remembered to load the devx and xenial headers files you should be good! Be patient. It takes a while and it doesn't have any progress bar etc to tell you its doing something.
Assuming this works you have compiled a kernel module based on your operating system and things like your display card. I mention this because if you are setting up (example) a NVIDA native driver you will need to have done this before using vboxconfig to make the kernel module.
I won't detail building an NVIDIA driver file but its similar. You still need the devx .sfs file and the xenialpup headers files .sfs. Then you download the NVIDIA proper source for your display board and execute the nvidia .run file by keyboard. *Note you need to click the exit command on the menu and on the Puppy Log Out menu select Exit to Prompt.
You can use the basic ideas to setup VirtualBox for 32 bit cpus or tahrpup but this is very specific,
How to get VirtualBox working on XenalPup using an AMD Athlon 64 CPU
You need to set up xenialpup to compile programs so for the 7.5 version of xenialpup you need the devx_xenialpup64_7.5.sfs file. You will find it where you found the xenialpup.iso file. The link (Today) is
http://distro.ibiblio.org/puppylinux/puppy-xenial/64/
You will see the .iso for making an install-able xenialpup bootable CD and the devx file to make your maching be able to compile source code.
If you not sure you should verify that you have a 64 bit CPU (like me)
uname -a
Linux puppypc24847 4.9.58 #1 SMP PREEMPT Mon Nov 13 15:54:01 GMT 2017 x86_64 x86_64 x86_64 GNU/Linux
it returns x86_64 (several times) so we know we have a 64 bit CPU.
So assuming you have found the devx_xenialpup64_7.5.sfs file you can load it in with the SFS-Load on-the-fly program. Its pretty cool because once done you can compile source code into programs or as with this case a kernel module.
We need to have the operating system (xenialpup) header files. This is source from the system that we need to make a system kernel file. It assures it will plug into xenialpup You could do uname -a ALL or just uname -r to see the header file version without all the rest
uname -r
*Note if your curious type uname --help and it will spell out all possible commands.
Using the SFS-Load on-the-fly program load the 4.9.58 headers.sfs file. These are the Kernel sources file headers for xenialpup. Verify that your headers match the version you got when you ran uname - r On my machine I loaded the .sfs file using (again) the SFS-load on-the-fly program. So load
kernel_sources-4.9.58-xenialpup64.sfs
Now using Palemoon or Firefox, Chrome etc etc etc go to the VirtualBox download page
https://www.virtualbox.org/wiki/Linux_Downloads
Now you need to know which system xenial pup is based on. Here are some examples
14.04 LTS (Trusty Tahr) *Note LTS means Long Time Supported. Its not a beta test version.
14.10 (Utopic Unicorn)
15.04 (Vivid Vervet)
15.10 (Wily Werewolf)
16.04 LTS (Xenial Xerus) <- THATS IT!!! xenialpup is based on Ubuntu Xenial
I selected the xenial version 16.04 AMD64 .deb file. I double clicked it and it told me everything was set up (Not!) and I could run Virtual box from the menu. This is not correct so back to the terminal I typed
VirtualBox <-note caps on V and B. I got an error informing me that the vboxdrv was not loaded. The reason for this is that I had not compiled a vboxdrv kernel module.
The error message invited me to run sudo /sbin/vboxconfig First we are always root so we don't use sudo. Second running /sbin/vboxconfg will compile a new kernel module. Getting the devx and kernal modules are the first part which is understandable. To actually make it work these are the werid things you need to take care of.
1) If you click to the /etc/rc.d directory you probably won't see subdirectories named rc0.d rc1.d rc2.d rc3.d rc4.d rc5.d rc6.d If you do? Fine other wise you will need to make these directories or virtual box will cough up a hairball. Why it doesn't just make up these directories itself is a mystery. Maybe puppy is the only distro that doesn't have them? I don't know so lets just do it.
2) VirtualBox assumes that we have a vboxusers group setup. To get past it complaining just run.
adduser -D -H vboxusers
Now VirtualBox has its user group and won't spew out error messages.
Now from terminal its ok to try running
/sbin/vboxconfig
If you remembered to load the devx and xenial headers files you should be good! Be patient. It takes a while and it doesn't have any progress bar etc to tell you its doing something.
Assuming this works you have compiled a kernel module based on your operating system and things like your display card. I mention this because if you are setting up (example) a NVIDA native driver you will need to have done this before using vboxconfig to make the kernel module.
I won't detail building an NVIDIA driver file but its similar. You still need the devx .sfs file and the xenialpup headers files .sfs. Then you download the NVIDIA proper source for your display board and execute the nvidia .run file by keyboard. *Note you need to click the exit command on the menu and on the Puppy Log Out menu select Exit to Prompt.
Science is what we understand well enough to explain to a computer.
Art is everything else we do.
[i]Donald Knuth [/i]
Art is everything else we do.
[i]Donald Knuth [/i]