Salix Forums

Linux for the Lazy Slacker
https://forum.salixos.org/

Strange Virtualbox problem

https://forum.salixos.org/viewtopic.php?t=3737

Page 2 of 3

Re: Strange Virtualbox problem

Posted: 20. Jul 2012, 17:55
by impatiens
Thanks for your help, guys. I installed the right kernel-source, and /etc/rc.d/rc.vboxdrv setup still fails. My vbox-install.log now looks like this:

Code: Select all

make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/3.3.6/build modules
/usr/src/linux-3.3.6/arch/x86/Makefile:81: stack protector enabled but no compiler support
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/lib/gcc/i486-slackware-linux/4.4.4/include -I/usr/src/linux-3.3.6/arch/x86/include -Iarch/x86/include/generated -Iinclude  -include /usr/src/linux-3.3.6/include/linux/kconfig.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 -mno-red-zone -mcmodel=kernel -maccumulate-outgoing-args -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -fno-optimize-sibling-calls -pg -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -I/lib/modules/3.3.6/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
/tmp/vbox.0/linux/SUPDrv-linux.c:1: error: code model ‘kernel’ not supported in the 32 bit mode
/tmp/vbox.0/linux/SUPDrv-linux.c:1: sorry, unimplemented: 64-bit mode not compiled in
make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxdrv] Error 2

Re: Strange Virtualbox problem

Posted: 21. Jul 2012, 11:30
by laprjns
Looks like there is architecture mismatch. Are you sure your not trying to run the 64 bit version of Virtualbox on an x86 machine? Or maybe you installed the wrong kernel-source.
make KBUILD_VERBOSE=1 SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 CONFIG_MODULE_SIG= -C /lib/modules/3.3.6/build modules
/usr/src/linux-3.3.6/arch/x86/Makefile:81: stack protector enabled but no compiler support
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/lib/gcc/i486-slackware-linux/4.4.4/include -I/usr/src/linux-3.3.6/arch/x86/include -Iarch/x86/include/generated -Iinclude -include /usr/src/linux-3.3.6/include/linux/kconfig.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 -mno-red-zone -mcmodel=kernel -maccumulate-outgoing-args -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -fno-omit-frame-pointer -fno-optimize-sibling-calls -pg -include /tmp/vbox.0/include/VBox/SUPDrvMangling.h -I/lib/modules/3.3.6/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
/tmp/vbox.0/linux/SUPDrv-linux.c:1: error: code model ‘kernel’ not supported in the 32 bit mode
/tmp/vbox.0/linux/SUPDrv-linux.c:1: sorry, unimplemented: 64-bit mode not compiled in
make[2]: *** [/tmp/vbox.0/linux/SUPDrv-linux.o] Error 1
make[1]: *** [_module_/tmp/vbox.0] Error 2
make: *** [vboxdrv] Error
Please post the output of "uname -r"

Re: Strange Virtualbox problem

Posted: 21. Jul 2012, 12:19
by Shador
Post apart from that the output of:

Code: Select all

slapt-get -search '^kernel-'

Re: Strange Virtualbox problem

Posted: 21. Jul 2012, 19:50
by impatiens
Okay, here is the output of those commands, plus uname -a:

Code: Select all

root[impatiens]# uname -r 
3.3.6
root[impatiens]# slapt-get -search '^kernel-'
kernel-firmware-2.6.33.4-noarch-1 [inst=yes]: kernel-firmware (Firmware installed by the kernel)
kernel-firmware-20120508git-noarch-1ab [inst=no]: kernel-firmware (Firmware for the kernel)
kernel-firmware-20120520git-noarch-1ab [inst=no]: kernel-firmware (Firmware for the kernel)
kernel-generic-2.6.33.4-i486-1 [inst=no]: kernel-generic (a general purpose single processor Linux kernel)
kernel-generic-smp-2.6.33.4_smp-i686-1 [inst=no]: kernel-generic-smp (a general purpose SMP Linux kernel)
kernel-headers-2.6.33.4-x86-1 [inst=yes]: kernel-headers (Linux kernel include files)
kernel-headers-2.6.33.4_smp-x86-1 [inst=no]: kernel-headers (Linux kernel include files)
kernel-headers-3.3.5-x86-2ab [inst=no]: kernel-headers (Linux kernel include files)
kernel-headers-3.3.6-x86-1ab [inst=no]: kernel-headers (Linux kernel include files)
kernel-huge-2.6.33.4-i486-1 [inst=no]: kernel-huge (a fully-loaded single processor Linux kernel)
kernel-huge-recent-3.3.5-x86_64-1ab [inst=no]: huge (a fully-loaded SMP Linux kernel)
kernel-huge-recent-3.3.6-x86_64-1ab [inst=no]: kernel-huge-recent (a fully-loaded SMP Linux kernel)
kernel-huge-smp-2.6.33.4_smp-i686-1 [inst=yes]: kernel-huge-smp (a fully-loaded SMP Linux kernel)
kernel-modules-2.6.33.4-i486-1 [inst=no]: kernel-modules (single CPU Linux kernel modules)
kernel-modules-recent-3.3.5-x86_64-1ab [inst=no]: modules (Linux kernel modules)
kernel-modules-recent-3.3.6-x86_64-1ab [inst=no]: kernel-modules-recent (Linux kernel modules)
kernel-modules-smp-2.6.33.4_smp-i686-1 [inst=yes]: kernel-modules (SMP Linux kernel modules)
kernel-source-2.6.33.4_smp-noarch-1 [inst=yes]: kernel-source (Linux kernel source)
kernel-source-recent-3.3.5-noarch-2ab [inst=no]: source (Linux kernel source)
kernel-source-recent-3.3.6-noarch-1ab [inst=no]: source (Linux kernel source)
root[impatiens]# uname -a
Linux darkstar 3.3.6 #2 SMP Sun May 20 20:55:20 CEST 2012 x86_64 Intel(R) Core(TM) i3 CPU       M 380  @ 2.53GHz GenuineIntel GNU/Linux
I know I went to the x86_64 link when I went to download the kernel-source. The old kernel (2.6.33.4) is x86. Is that an issue?

Re: Strange Virtualbox problem

Posted: 21. Jul 2012, 20:52
by Shador
Did you upgrade your kernel outside of the package management? Because no 3.3.6 kernel is listed as installed just the stock kernel.

Re: Strange Virtualbox problem

Posted: 21. Jul 2012, 21:04
by impatiens
I guess not. How would I go about fixing that problem?

Sorry if I'm a little dense. I'm still trying to figure out life outside the *buntus.

Re: Strange Virtualbox problem

Posted: 21. Jul 2012, 21:08
by Shador
I don't know what you did. If you install stuff outside the package management only you can tell what you did. Unless you can tell me what you did and thus I know what's going on, I won't make blind suggestions what to do. So what did you do to get that 3.3.6 kernel?

Re: Strange Virtualbox problem

Posted: 21. Jul 2012, 21:25
by impatiens
Oh, now I get what you're asking. I didn't use the package management system to upgrade the kernel. I used Firefox to download everything, extracted the files, put everything in the right place, and ran the included shell scripts.

Re: Strange Virtualbox problem

Posted: 21. Jul 2012, 21:38
by laprjns
impatiens wrote:

Code: Select all

Linux darkstar 3.3.6 #2 SMP Sun May 20 20:55:20 CEST 2012 x86_64 Intel(R) Core(TM) i3 CPU       M 380  @ 2.53GHz GenuineIntel GNU/Linux
So your hardware is x86_64
The old kernel (2.6.33.4) is x86
This implies that you have Salix x86 OS installed
I know I went to the x86_64 link when I went to download the kernel-source
So you installed the x86_64 kernel and sources. Strike this, I see that you do have the x86 kernel and sources installed.
Is that an issue?
Yes. If your operating system is x86 then you need to install Shador's x86 kernel and kernel-source packages. And you will need to download and install the x86 version of Virtualbox.

Re: Strange Virtualbox problem

Posted: 21. Jul 2012, 21:52
by impatiens
I decided I'm going to install the 64-bit version of Salix. That should solve this problem, right?
All times are UTC
Page 2 of 3

Powered by phpBB® Forum Software © phpBB Limited