Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 09-05-2012, 03:55 PM   #1
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slackware 12.2, scientific linux 6.4, knoppix 7.2, salix 14.1
Posts: 910

Rep: Reputation: Disabled
Non-smp kernel not sane - problems with a compilation of the kernel modules

Yesterday I switched to the non-smp generic kernel on my Slackware 12.2 virtual machine (VirtualBoxv4.1.18). I've got troubles with the compilation of the GuestAdditions. I investigated the cause and I found such thing. Here is a part from the script which compiles GuestAddition kernel modules
KERN_VER=`uname -r`
echo $KERN_DIR
if [ -d "$KERN_DIR" ]; then
    KERN_REL=`make -sC $KERN_DIR --no-print-directory kernelrelease 2>/dev/null || true`
           if [ -z "$KERN_REL" -o "x$KERN_REL" = "x$KERN_VER" ]; then
            return 0
    printf "\nThe headers for the current running kernel were not found. If the
following\nmodule compilation fails then this could be the reason.\n"
This is the part called 'the sanity' check. The script for non-smp kernel returns the line after the 'printf' command. The problem is that the
'KERN_REL' always have the value with '-smp' postfix added. But for non-smp kernel there is no '-smp' postfix. On my machine
bash$ uname -r
 echo $KERN_REL
The problem is that compiled modules have inappropriate format and won't be loaded during the boot.
Old 09-05-2012, 04:34 PM   #2
Senior Member
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,364

Rep: Reputation: 833Reputation: 833Reputation: 833Reputation: 833Reputation: 833Reputation: 833Reputation: 833
I'm guessing you're running into this:
Originally Posted by CHANGES_AND_HINTS.TXT
If you decide to use one of the non-SMP kernels, you will need to follow the
instructions in /extra/linux- 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 follow those instructions to prepare the kernel source for non-smp module compilation.
1 members found this post helpful.
Old 09-05-2012, 04:45 PM   #3
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slackware 12.2, scientific linux 6.4, knoppix 7.2, salix 14.1
Posts: 910

Original Poster
Rep: Reputation: Disabled
Thanks. Nice hint I will follow this. Running -smp kernel on the virtual machine with one processor is rather pointless...


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
no kernel modules found for aBiNg Slackware 4 12-19-2011 10:36 AM
[SOLVED] No kernel modules found for Linux pejobe Slackware 3 06-08-2010 12:59 PM
Non-SMP kernel modules for SMP kernel: Best practice? gargamel Slackware 9 12-29-2008 01:13 PM
No kernel modules found for Linux w1k0 Slackware 11 12-23-2008 02:24 PM

All times are GMT -5. The time now is 08:01 AM.

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