Strange Virtualbox problem

You have a problem with Salix? Post here and we'll do what we can to help.
User avatar
laprjns
Salix Warrior
Posts: 1113
Joined: 28. Aug 2009, 01:30
Location: Connecticut USA

Re: Strange Virtualbox problem

Post by laprjns »

impatiens wrote:I decided I'm going to install the 64-bit version of Salix. That should solve this problem, right?
Yes it should. You need the following
  • 64 Bit version of Salix

    64 bit kernel and it's corresponding kernel-source package (you'll get the correct kernel on the install, but will need to install the kernel-source via slapt-get)

    and the 64 bit version of VirtualBox
“The past was erased, the erasure was forgotten, the lie became the truth.”
― George Orwell, 1984
impatiens
Posts: 18
Joined: 17. Jul 2012, 23:09

Re: Strange Virtualbox problem

Post by impatiens »

Thanks for being patient with me.

I installed the Fluxbox Live CD originally, and didn't realize it wasn't 64-bit. I guess I shouldn't assume things. I'll most likely use Shador's kernel and kernel-source again, since that's definitely much easier than trying to install my wireless drivers manually.

ETA: Or not. Wifi actually worked out of the box this time.

ETA2: It worked! Thanks a lot, guys! And thanks for putting up with me.
impatiens
Posts: 18
Joined: 17. Jul 2012, 23:09

Re: Strange Virtualbox problem

Post by impatiens »

Alright, I went back to the x86 version of Salix. I installed the kernel-source. I downloaded the x86 version of Virtualbox. I have a problem with vboxdrv again, so I run /etc/rc.d/rc.vboxdrv setup:

Code: Select all

root[impatiens]# /etc/rc.d/rc.vboxdrv setup
Stopping VirtualBox kernel modules ...done.
Uninstalling old VirtualBox DKMS kernel modules ...done.
Removing old VirtualBox pci kernel module ...done.
Removing old VirtualBox netadp kernel module ...done.
Removing old VirtualBox netflt kernel module ...done.
Removing old VirtualBox kernel module ...done.
Trying to register the VirtualBox kernel modules using DKMS ...failed!
  (Failed, trying without DKMS)
Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)
I run dmesg and find this:

Code: Select all

[  504.968779] vboxdrv: version magic '2.6.37.6-smp SMP mod_unload 686 ' should be '2.6.37.6 mod_unload 486 '
[  505.041869] vboxdrv: version magic '2.6.37.6-smp SMP mod_unload 686 ' should be '2.6.37.6 mod_unload 486 '
[  513.045822] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[  596.565131] vboxdrv: version magic '2.6.37.6-smp SMP mod_unload 686 ' should be '2.6.37.6 mod_unload 486 '
[ 1030.501179] vboxdrv: version magic '2.6.37.6-smp SMP mod_unload 686 ' should be '2.6.37.6 mod_unload 486 '
[ 1303.747210] vboxdrv: version magic '2.6.37.6-smp SMP mod_unload 686 ' should be '2.6.37.6 mod_unload 486 '
[ 2326.661927] vboxdrv: version magic '2.6.37.6-smp SMP mod_unload 686 ' should be '2.6.37.6 mod_unload 486 '
User avatar
laprjns
Salix Warrior
Posts: 1113
Joined: 28. Aug 2009, 01:30
Location: Connecticut USA

Re: Strange Virtualbox problem

Post by laprjns »

impatiens wrote:Alright, I went back to the x86 version of Salix.
How did you do this? A complete re-install?
I installed the kernel-source.
Please post the out put of "slapt-get -se ^kernel- | grep yes". Here's what mine looks like:

Code: Select all

root[arch]# slapt-get -se ^kernel- | grep yes
kernel-firmware-2.6.37.6-noarch-2 [inst=yes]: kernel-firmware (Firmware installed by the kernel)
kernel-huge-smp-2.6.37.6_smp-i686-2 [inst=yes]: kernel-huge-smp (a fully-loaded SMP Linux kernel)
kernel-modules-smp-2.6.37.6_smp-i686-2 [inst=yes]: kernel-modules (SMP Linux kernel modules)
kernel-source-2.6.37.6_smp-noarch-2 [inst=yes]: kernel-source (Linux kernel source)
“The past was erased, the erasure was forgotten, the lie became the truth.”
― George Orwell, 1984
impatiens
Posts: 18
Joined: 17. Jul 2012, 23:09

Re: Strange Virtualbox problem

Post by impatiens »

Yeah, a complete reinstall. That seemed like the simplest way to get WINE working, and I realized I really don't use 64-bit programs much, and I only have 4 GB RAM.

Here's the output of that command:

Code: Select all

root[impatiens]# slapt-get -se ^kernel|grep yes
kernel-firmware-2.6.37.6-noarch-2 [inst=yes]: kernel-firmware (Firmware installed by the kernel)
kernel-headers-2.6.37.6_smp-x86-2 [inst=yes]: kernel-headers (Linux kernel include files)
kernel-huge-2.6.37.6-i486-2 [inst=yes]: kernel-huge (a fully-loaded single processor Linux kernel)
kernel-modules-2.6.37.6-i486-2 [inst=yes]: kernel-modules (single CPU Linux kernel modules)
kernel-source-2.6.37.6_smp-noarch-2 [inst=yes]: kernel-source (Linux kernel source)
It looks like I have i486 instead of i686. Presumably, I need the i686 kernel and modules for Virtualbox to work.
User avatar
laprjns
Salix Warrior
Posts: 1113
Joined: 28. Aug 2009, 01:30
Location: Connecticut USA

Re: Strange Virtualbox problem

Post by laprjns »

Well, you need to be consistent. You have the single core kernel installed with the multiple core kernel-source. Assuming that you have a multi-core processor, install the kernel-huge-smp-2.6.37.6_smp-i686-2 kernel along with the corresponding kernel-source package. If not install the kernel-huge-2.6.37.6-i486-2 kernel along with it's corresponding kernel-source.
“The past was erased, the erasure was forgotten, the lie became the truth.”
― George Orwell, 1984
Post Reply