VirtualBox on 64-bit Salix14

[andyprice]

Hoping for some help with this one. I've recently installed 64-bit Salix14 on an HP ProBook 6450b. Running nicely but I've hit a problem getting VirtualBox to work.

I downloaded the latest generic VB installer (VirtualBox-4.2.12-84980-Linux_amd64) and ran it (after installing kernel-source) and the install seemed to go okay. But when I try to create and set up a machine it throws up an error:

"The VirtualBox Linux kernel driver(vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module...

lsmod shows no vboxdrv loaded. When I execute /etc/rc.d/rc.vboxdrv setup it chugs away and finishes with the following lines:

Recompiling VirtualBox kernel modules ...done.
Starting VirtualBox kernel modules ...failed!
(modprobe vboxdrv failed. Please use 'dmesg' to find out why)

The last lines of dmesg are:

[ 1347.026065] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[ 2091.618938] vboxdrv: version magic '3.2.45 SMP mod_unload ' should be '3.2.29 SMP mod_unload '

I've googled and can't find anything definitive, but I think it's the last of the two entries which is giving the problem as the message about "uses 32-bit capabilities" seems quite common on the net and is often said to be harmless.

Has anyone had the same problem with VBox on 64 bit? Anyone know how to overcome it?

Thanks
Andy

[gapan]

You have kernel 3.2.29 and kernel-source 3.2.45 or vice-versa. They should be the same.

[andyprice]

Thanks for the quick reply Gapan. I need more help before this gets messy!

When I first intalled VBox it complained about no headers so I did slapt-get -i kernel-source thinking I needed them. Seemed to go ok, and VBox installed, but then complained about the wrong version as in previous post.

After your reply I checked with uname -r and saw my kernel is 3.2.29. Checked in Gslapt and saw that two versions of kernel-source were installed - 3.2.29 and 3.2.45 (which I installed) so I removed 3.2.45 with removepkg and retried installing VBox. Now it complains about missing header files again:

VirtualBox Version 4.2.12 r84980 (2013-04-12T10:28:02Z) installer
Please install the build and header files for your current Linux kernel.
The current kernel version is 3.2.29
Problems were found which would prevent VirtualBox from installing.

When I look in Gslapt it shows that BOTH kernel-source packages are now "Not Installed / Excluded" along with the 3.2.45 version of kernel-headers, while the 3.2.29 version of kernel-headers is Installed / Excluded.

How do I put this right?

Thanks
Andy

[gapan]

You need either:
1. kernel 3.2.29 + kernel-source 3.2.29
2. kernel 3.2.45 + kernel-source 3.2.45

Code: Select all

# slapt-get -i kernel-source-3.2.29

for the first one.

[andyprice]

Thanks Gapan, I'm sorted now. I had to specify the full name in slapt-get ... kernel-source-3.2.29-noarch-1, otherwise it couldn't find the package.
The root cause of my problem was that I originally installed the kernel-source package without stating the version required - I just did slapt-get -i kernel-source. Unfortunately it gave me the wrong one.
Andy