LinuxQuestions.org - [SOLVED] # /etc/rc.d/rc.vboxdrv setup fails on -current

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - # /etc/rc.d/rc.vboxdrv setup fails on -current (https://www.linuxquestions.org/questions/slackware-14/etc-rc-d-rc-vboxdrv-setup-fails-on-current-799132/)

# /etc/rc.d/rc.vboxdrv setup fails on -current

Hi all,

I'm still having problems trying to setup VirtualBox here.

I have a fresh install of Slackware64-current and tried VirtualBox 3.1.6 PUEL. It installs smoothly, but when I start it, it gives out a warning saying vboxdrv is not good and asks to rebuild it using

Code:

# /etc/rc.d/rc.vboxdrv setup

Which fails every time I try running it...

I have already tried

Code:

# cd /usr/src/linux/include/linux

# ln -s ../generated/autoconf.h autoconf.h

And it stills fails to build vboxdrv.

Any tips?

Thanks in advance,
gtludwig

you have to have installed the kernel-source package. If it doesn't build with those sources installed then do this:

Code:

cd /usr/src/linux/arch

ln -s x86 amd64

and "/etc/rc.d/rc.vboxdrv setup" should work.

I have these packages installed:

Code:

root@cpc-5564:~# ls /var/log/packages/kernel-*

/var/log/packages/kernel-firmware-2.6.33-noarch-1

/var/log/packages/kernel-generic-2.6.33-x86_64-1

/var/log/packages/kernel-headers-2.6.33-x86-1

/var/log/packages/kernel-huge-2.6.33-x86_64-2

/var/log/packages/kernel-modules-2.6.33-x86_64-1

/var/log/packages/kernel-source-2.6.33-noarch-1

On your post, you offered a sym link solution. I don't know whether or not it was a typo, but I tried the sym link approach to both x86 and x86_64.

Code:

root@cpc-5564:~# ls -la /usr/src/linux/arch/amd64 

lrwxrwxrwx 1 root root 6 Mar 31 12:03 /usr/src/linux/arch/amd64 -> x86

Code:

root@cpc-5564:~# ls -la /usr/src/linux/arch/amd64 

lrwxrwxrwx 1 root root 6 Mar 31 12:03 /usr/src/linux/arch/amd64 -> x86_64

Still the same result:

Code:

root@cpc-5564:~# /etc/rc.d/rc.vboxdrv setup

WARNING: All config files need .conf: /etc/modprobe.d/sound, it will be ignored in a future release.

Stopping VirtualBox kernel module ...done.

Removing old VirtualBox netadp kernel module ...done.

Removing old VirtualBox netflt kernel module ...done.

Removing old VirtualBox kernel module ...done.

Recompiling VirtualBox kernel module ...done.

Starting VirtualBox kernel module ...failed!

  (modprobe vboxdrv failed. Please use 'dmesg' to find out why)

root@cpc-5564:~#

I checked dmesg once again and right at its end, this pops out:

Code:

 (...)

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

CE: hpet increasing min_delta_ns to 15000 nsec

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

vboxdrv: version magic '2.6.33 SMP preempt mod_unload ' should be '2.6.33 SMP mod_unload '

Still lost here...

now it looks like the kernel module builds, but there should be an install/build log too (in /var/log, if I remember well)...

which kernel are you using? can you do please an

Code:

ls -la /boot

the error message says that the kernel source files you built against do not match the running kernel and it refuses to load the module.

the symlink I suggested was not a typo: x86_64 get create during kernel build as a symlink to x86, so you have to do the symlink to x86.
check also /usr/src/linux-2.6.33/arch

Code:

ls -la /usr/src/linux-2.6.33/arch

I'm using -current stock huge kernel

Code:

gtl@cpc-5564:~$ ls -la /boot/

total 16752

drwxr-xr-x  2 root root    4096 2010-03-31 14:07 ./

drwxr-xr-x 21 root root    4096 2010-03-31 14:04 ../

lrwxrwxrwx  1 root root      37 2010-03-29 07:18 README.initrd -> /usr/doc/mkinitrd-1.4.3/README.initrd

lrwxrwxrwx  1 root root      22 2010-03-31 14:03 System.map -> System.map-huge-2.6.33

-rw-r--r--  1 root root 1757406 2010-03-30 13:58 System.map-custom-2.6.33

-rw-r--r--  1 root root 1512231 2010-02-27 19:45 System.map-generic-2.6.33

-rw-r--r--  1 root root 2508251 2010-03-07 14:36 System.map-huge-2.6.33

-rw-r--r--  1 root root    512 2010-03-29 07:26 boot.0800

-rw-r--r--  1 root root    137 2010-03-29 07:25 boot_message.txt

lrwxrwxrwx  1 root root      18 2010-03-31 14:03 config -> config-huge-2.6.33

-rw-r--r--  1 root root  97511 2010-03-30 13:59 config-custom-2.6.33

-rw-r--r--  1 root root  101662 2010-02-27 19:45 config-generic-2.6.33

-rw-r--r--  1 root root  101615 2010-03-07 14:36 config-huge-2.6.33

-rw-r--r--  1 root root    5040 2010-02-15 00:09 diag1.img

-rw-r--r--  1 root root  17932 2010-02-15 00:09 diag2.img

-rw-------  1 root root  119808 2010-03-31 14:07 map

-rw-r--r--  1 root root  17318 2008-12-08 22:56 slack.bmp

lrwxrwxrwx  1 root root      19 2010-03-31 14:03 vmlinuz -> vmlinuz-huge-2.6.33

-rw-r--r--  1 root root 3180448 2010-03-30 13:58 vmlinuz-custom-2.6.33

-rw-r--r--  1 root root 2511152 2010-02-27 19:45 vmlinuz-generic-2.6.33

-rw-r--r--  1 root root 5173888 2010-03-07 14:36 vmlinuz-huge-2.6.33

I installed VirtualBox PUEL 3.1.4 and the virtualbox-kernel SlackBuild. And it started like a charm.

Thanks for the help!