Install "VirtualBox-3.2.12-68 302" in slackware64-current ( kernel 2.6.38.7 )
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Install "VirtualBox-3.2.12-68 302" in slackware64-current ( kernel 2.6.38.7 )
Is there any way to install "VirtualBox-3.2.12-68302" in the "slackware64-current" (Kernel 2.6.38.7) ?
I have problems with the 4.0.x version of VB!
The version "VirtualBox-3.2.12-68302" works fine with my hardware!
I tested using "VB 3.2.12" and Slackware64-13.37 (kernel 2.6.37.6).
I get the warning when I try to install a guest OS in "VB 3.2.12" running slackware64-current ...
Quote:
there is a permission problem with /dev/vboxdrv. Please reinstall
the kernel module by executing
'/etc/init.d/vboxdrv setup'
as root. Users of Ubuntu, Fedora or Mandriva should install the DKMS
package first.
This package keeps track of Linux kernel changes and recompiles the
vboxdrv kernel module if necessary"
and still
Quote:
Failed to open a session for the virtual machine Slackware12.0.
The virtual machine 'Slackware12.0' has terminated unexpectedly during
startup with exit code 1.
Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Machine
Interface:
IMachine {6d9212cb-a5c0-48b7-bbc1-3fa2ba2ee6d2}
thanks
Last edited by afreitascs; 06-21-2011 at 09:25 PM.
Assuming you are running the 64-bit version of VB, execute the following as root and tell us what shows up:
Code:
/etc/rc.d/rc.vboxdrv setup
Here is:
Quote:
root@base1:~# /etc/rc.d/rc.vboxdrv setup
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Trying to register the VirtualBox kernel modules using DKMS ...failed!
(Failed, trying without DKMS)
Recompiling VirtualBox kernel modules ...failed!
(Look at /var/log/vbox-install.log to find out what went wrong)
What does /var/log/vbox-install.log show? Also, what problems do you have with the latest VB 4.x series? It works for me on slackware64-current and kernel 2.6.38.7.
What does /var/log/vbox-install.log show? Also, what problems do you have with the latest VB 4.x series? It works for me on slackware64-current and kernel 2.6.38.7.
Here is :
Quote:
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.38.7/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)
mkdir -p /tmp/vbox.0/.tmp_versions ; rm -f /tmp/vbox.0/.tmp_versions/*
make -f scripts/Makefile.build obj=/tmp/vbox.0
gcc -Wp,-MD,/tmp/vbox.0/linux/.SUPDrv-linux.o.d -nostdinc -isystem /usr/lib64/gcc/x86_64-slackware-linux/4.5.3/include -I/usr/src/linux-2.6.38.7/arch/x86/include -Iinclude -include include/generated/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -O2 -m64 -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -maccumulate-outgoing-args -fstack-protector -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -fno-omit-frame-pointer -fno-optimize-sibling-calls -pg -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -DCC_HAVE_ASM_GOTO -I/lib/modules/2.6.38.7/build/include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -I/tmp/vbox.0/vboxdrv/ -I/tmp/vbox.0/vboxdrv/include -I/tmp/vbox.0/vboxdrv/r0drv/linux -D__KERNEL__ -DMODULE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_AMD64 -DVBOX_WITH_64_BITS_GUESTS -DMODULE -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(SUPDrv_linux)" -D"KBUILD_MODNAME=KBUILD_STR(vboxdrv)" -c -o /tmp/vbox.0/linux/SUPDrv-linux.o /tmp/vbox.0/linux/SUPDrv-linux.c
In file included from /tmp/vbox.0/include/VBox/types.h:30:0,
from /tmp/vbox.0/linux/../SUPDrvInternal.h:35,
from /tmp/vbox.0/linux/SUPDrv-linux.c:31:
/tmp/vbox.0/include/iprt/types.h:97:31: fatal error: linux/autoconf.h: No such file or directory
compilation terminated.
make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxdrv] Error 2
With "vB4" I have a problem I suppose is only occurring with me.
Please look at the link.
You'll probably have to configure your kernel to support this feature. I'm not sure since I have my own kernel .config file and cannot seem to find out on my system if this feature is enabled with the stock kernel.
You'll probably have to configure your kernel to support this feature. I'm not sure since I have my own kernel .config file and cannot seem to find out on my system if this feature is enabled with the stock kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.