LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 01-05-2011, 05:05 AM   #1
Gavin Harper
Member
 
Registered: Feb 2010
Location: Finland
Distribution: Slackware
Posts: 169

Rep: Reputation: 24
VirtualBox 4 Slackware Current (x86) (No Kernel Modules)


I have installed the new VirtualBox 4 in Slackware current (x86)from the binary on VirtualBox.org (As I have done since Version 3.x.x).

The issue is that when I go to start a VM, I get the error that the kernel modules cannot be found even though everything succeeded without glitch on the install.

Does anyone know the reason for this?

Thanks
 
Old 01-05-2011, 05:14 AM   #2
bathory
Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 10,973

Rep: Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343
Try
Code:
modprobe vboxdrv
If it doesn't work, run:
Code:
/etc/rc.d/rc.vboxdrv setup
Regards
 
Old 01-05-2011, 05:29 AM   #3
rpedrica
Member
 
Registered: Nov 2008
Location: Cape Town
Distribution: Slackware64 -current
Posts: 208

Rep: Reputation: 27
and then /etc/rc.d/rc.vboxdrv start
 
Old 01-05-2011, 06:03 AM   #4
Gavin Harper
Member
 
Registered: Feb 2010
Location: Finland
Distribution: Slackware
Posts: 169

Original Poster
Rep: Reputation: 24
bash-4.1# /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)
bash-4.1# modprobe vboxdrv
FATAL: Module vboxdrv not found.
bash-4.1# /etc/rc.d/rc.vboxdrv start
Starting VirtualBox kernel modules ...failed!

bash-4.1# cat /var/log/vbox-install.log
Makefile:178: *** Error: /usr/src/linux (version 2.6.35.7-smp) does not match the current kernel (version 2.6.35.7). Stop.

Last edited by Gavin Harper; 01-05-2011 at 06:08 AM.
 
Old 01-05-2011, 07:04 AM   #5
bathory
Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 10,973

Rep: Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343
Your current running kernel (2.6.35.7) does not match the kernel sources installed in your system (2.6.35.7-smp), that vboxdrv is trying to use in order to compile the kernel modules.
I'm always use my self compiled kernels, but I guess you have to install the same smp kernel (kernel-generic-smp-2.6.35.7_smp-i686-1) to match the kernel-source installed package.
 
Old 01-05-2011, 08:19 AM   #6
Gavin Harper
Member
 
Registered: Feb 2010
Location: Finland
Distribution: Slackware
Posts: 169

Original Poster
Rep: Reputation: 24
Interesting! This has never been an issue prior to this version.
 
Old 01-05-2011, 08:02 PM   #7
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,298

Rep: Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722
Quote:
Originally Posted by CHANGES_AND_HINTS.TXT
Use one of the provided generic kernels for daily use. Do not report
bugs until/unless you have reproduced them using one of the stock
generic kernels. You will need to create an initrd in order to boot
the generic kernels - see /boot/README.initrd for instructions.
The huge kernels are primarily intended as "installer" and "emergency"
kernels in case you forget to make an initrd. For most systems, you
should use the generic SMP kernel if it will run, even if your system is
not SMP-capable. Some newer hardware needs the local APIC enabled in the
SMP kernel, and theoretically there should not be a performance penalty
with using the SMP-capable kernel on a uniprocessor machine, as the SMP
kernel tests for this and makes necessary adjustments. Furthermore, the
kernel sources shipped with Slackware are configured for SMP usage, so you
won't have to modify those to build external modules (such as NVidia or
ATI proprietary drivers) if you use the SMP kernel.

If you decide to use one of the non-SMP kernels, you will need to follow the
instructions in /extra/linux-2.6.35.7-nosmp-sdk/README.TXT to modify your
kernel sources for non-SMP usage. Note that this only applies if you are
using the Slackware-provided non-SMP kernel - if you build a custom kernel,
the symlinks at /lib/modules/$(uname -r)/{build,source} will point to the
correct kernel source so long as you don't (re)move it.
You should probably switch to the generic-smp kernel as bathory suggested, but compiling any kernel module would have failed if you were running the non-smp kernel without patching the source (or without running your own kernel).
 
Old 01-06-2011, 04:10 AM   #8
ppr:kut
Slackware Contributor
 
Registered: Aug 2006
Location: Netherlands
Distribution: Slackware
Posts: 366

Rep: Reputation: 94
iirc virtualbox' kernel drivers currently have a bug where they cannot be compiled if dkms is not installed. Not sure if 4.0 is affected or not, but I do think so.
 
Old 01-06-2011, 04:28 AM   #9
bathory
Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 10,973

Rep: Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343
Hi,

Quote:
iirc virtualbox' kernel drivers currently have a bug where they cannot be compiled if dkms is not installed. Not sure if 4.0 is affected or not, but I do think so.
FYI I've installed vbox 4.0 in my box running the latest 2.6.37 kernel and they compile just fine. They just look for DKMS support (like the previous versions of vbox) and since there isn't any, they build as normal kernel modules.

Regards
 
Old 01-06-2011, 04:48 AM   #10
ppr:kut
Slackware Contributor
 
Registered: Aug 2006
Location: Netherlands
Distribution: Slackware
Posts: 366

Rep: Reputation: 94
Quote:
Originally Posted by bathory View Post
Hi,


FYI I've installed vbox 4.0 in my box running the latest 2.6.37 kernel and they compile just fine. They just look for DKMS support (like the previous versions of vbox) and since there isn't any, they build as normal kernel modules.

Regards
Perfect, thanks! Maybe it's the guest addition drivers then, or it has already been resolved. Anyway, if it works everything's fine
 
Old 01-06-2011, 05:05 AM   #11
bathory
Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 10,973

Rep: Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343
Guest additions on guest winXP are working too.
The only difference in 4.0, is that usb support is now in an extension pack. You need to run:
Code:
VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.0.0-69151.vbox-extpack
to install it

Regards
 
Old 01-06-2011, 07:02 AM   #12
Gavin Harper
Member
 
Registered: Feb 2010
Location: Finland
Distribution: Slackware
Posts: 169

Original Poster
Rep: Reputation: 24
So how would one switch to an SMP enabled kernel?

I have been using Slackware and the same script (Give or take versioning changes) to set up my clean installs for a long time with no issues with VBox or kernel choice.

Advice would be greatly appreciated!
 
Old 01-06-2011, 09:59 AM   #13
bathory
Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 10,973

Rep: Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343Reputation: 1343
@Gavin
Quote:
So how would one switch to an SMP enabled kernel?
I guess you have to install the following packages:
Quote:
kernel-generic-smp-2.6.35.7_smp-i686-1.txz
kernel-modules-smp-2.6.35.7_smp-i686-1.txz
kernel-firmware-2.6.35.7-noarch-1.txz (maybe)
and add as the 1st entry in lilo.conf the vmlinuz-generic-smp-2.6.35.7-smp

Have a look at this thread here at LQ, to see how to create a initrd, if you need one.
 
Old 01-06-2011, 10:56 AM   #14
Gavin Harper
Member
 
Registered: Feb 2010
Location: Finland
Distribution: Slackware
Posts: 169

Original Poster
Rep: Reputation: 24
Thanks!

I actually did some a little messing around with a clean install and for whatever reason, my USB installer was defaulting to the non-smp kernel.

I reinstalled with the smp kernel and everything works flawlessly.

Thank you for your time and pointers!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
slackware x86 -current + radeon: temporary screen corruption with kde4 applications melmothX Slackware 23 09-12-2009 06:26 PM
Slackware-Current x64 & x86 + Nvidia SqdnGuns Slackware 7 05-24-2009 11:34 AM
New current kernel 2.6.29.1 on VirtualBox bgeddy Slackware 5 04-15-2009 08:27 PM
Virtualbox kernel modules won't load after updating kernel in openSUSE 11.0 JamesHall Suse/Novell 6 02-03-2009 05:36 PM
Can't Compile VirtualBox 1.6.6 In Slackware Current Woodsman Slackware 8 12-18-2008 03:36 PM


All times are GMT -5. The time now is 05:44 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration