Should modules for different kernels differ?

I'm trying to build acpi_call-git from the AUR. The build seems to go rather too smoothly. I uninstalled a custom kernel (which I only have for debugging) which leaves the standard Arch and Arch LTS kernels installed. I have the headers installed for both kernels:
$ pacman -Qs linux-[lts-]*headers
local/linux-headers 3.11.4-1
Header files and scripts for building modules for Linux kernel
local/linux-lts-headers 3.10.15-1
Header files and scripts for building modules for Linux-lts kernel
What is confusing me is that the package seems to build identical modules for the two kernels and I am not sure whether that's right:
$ diff pkg/acpi_call-git/usr/lib/modules/extramodules-3.11-ARCH/acpi_call.ko.gz pkg/acpi_call-git/usr/lib/modules/extramodules-3.10-lts/acpi_call.ko.gz
$ echo $?
Shouldn't there be a difference between the two? That is, I know that you typically need modules which match the kernel - otherwise the modules can't be loaded. So presumably if building module M for kernel K1 produces M1, and building module M for kernel K2 produces M2, then M1 cannot be identical with M2.
Is there a problem here or am I just horribly confused?

If the kernel functions (especially the specifications) used by acpi_call haven't changed, then the module could indeed be the same for both kernels.
You'd have to check the kernel commits for acpi related changes to be sure.

Similar Messages

  • Nvidia module for custom kernel

    Hi all. I've compiled a custom kernel using abs according to the instructions on the wiki, but I'm having a hard time installing the nvidia module using the instructions on the Nvidia page of the wiki. The install always aborts complaining of not being able to find the kernel source. I do have the kernel-headers installed:
    [[email protected] greg]# pacman -Ss linux-headers
    core/linux-headers 3.1.5-1 [installed]
        Header files and scripts for building modules for linux kernel
    I've also edited the nvidia.install and PKGBUILD files to point to the correct version file:
    [[email protected] ~]$ cat /lib/modules/3.1.5-1-test/extramodules/version
    I've really searched hard, but can find no remedy. Any ideas?
    Thanks in advance.

    From what I can see, the only installable package that was built is linux-test-3.1.5-1-x86_64.pkg.tar.xz. That's with the PKGBUILD file supplied from /var/abs/core/linux as per the wiki.
    Last edited by pressman57 (2011-12-18 21:50:00)

  • Script to easily build modules for custom kernels

    I got bored, and thought of this ages ago. I have no use for it now, but i'm sure someone else will.
    abs-module $modulename $kernel
    $modulename is any kernel module that's available in /var/abs, so if you have some that arent in a default abs, put em in /var/abs/local and they will be spotted by this.
    $kernel is the name of the kernel that you want to compile for. this can be found with 'uname -r'. If $kernel is not specified, then it will default to what you are running now.
    this will only work for module packages that have a variable called _kernver which sets the kernel it will be compiled for. I know all the winmodems, ATi and drivers I maintain do, not sure about some of the others. nvidia won't work.
    #! /bin/bash
    # Set the variables up
    current="`uname -r`"
    # Check things
    if [ -z "$module" ]; then
    echo "No module specified"
    return 1
    if [ -z "$kernel" ]; then
    echo "No kernel specified, building for: $current"
    if [ ! -e "/lib/modules/$kernel/build" ]; then
    echo "Specified kernel is not installed"
    return 1
    # Check if module exists
    origdir="`find /var/abs -type d -name $module`"
    if [ -z "$origdir" ]; then
    echo "Specified module does not exist"
    return 1
    # Prepare to build
    if [ -d "$newdir" ]; then
    rm -rf "$newdir"
    cp -R $origdir $newdir
    cd $newdir
    source PKGBUILD
    if [ -z "$_kernver" ]; then
    echo "PKGBUILD does not have $_kernver."
    return 1
    sed "s/$_kernver/$kernel/g" -i PKGBUILD
    sed "s/pkgname=$pkgname/pkgname=$pkgname-$kernel/g" -i PKGBUILD
    # Build!
    # Post build messages/install
    if [ $? = 0 ]; then
    package="`find $newdir -name *pkg.tar.gz`"
    # variable is at top
    if [ "$pacman" = "1" ]; then
    pacman -U $package
    echo "Package is ready to install: $package"
    echo "Build failed"
    sorry if there's any stupid bash in there, i'm tired. and yeah, I know it's a tad verbose and spacy, but it seems to works fine.

    Iphitus > I'm looking 4 something like your script that will allow me to load spca5xx when running my custom kernelbeyond
    Unfortunetely spca5xx seems not to be manageable by your abs-module script, as its PKGBUILD doesn't have a variable called _kernver.
    Log :
    /usr/bin/abs-make-module spca5xx
    No kernel specified, building for: 2.6.17-beyond-LLEWELLYN
    PKGBUILD does not have .
    /usr/bin/abs-make-module: line 52: return: can only `return' from a function or sourced script
    sed: -e expression #1, char 0: no previous regular expression
    ==> Making package: spca5xx-2.6.17-beyond-LLEWELLYN 0.60.00-2 (Sun Jul 23 11:44:52 CEST 2006)
    ==> Validating source files with MD5sums
        spca5xx-20060501.tar.gz ... Passed
    ==> Extracting Sources...
    ==>     tar --use-compress-program=gzip -xf spca5xx-20060501.tar.gz
    tar: spca5xx-20060501/drivers: implausibly old time stamp 1970-01-01 01:00:00
    ==> Starting build()...
    ./PKGBUILD: line 13: cd: /var/abs/local/spca5xx-2.6.17-beyond-LLEWELLYN/src/spca5xx-2.6.17-beyond-LLEWELLYN-20060501: No such file or directory
    make: *** No targets specified and no makefile found.  Stop.
    ==> ERROR: Build Failed.  Aborting...
    Build failed

  • [Solved]catalyst-rt module for realtime kernel

    I've compiled and intstalled the rtkernel with the directions posted here:
    My laptop uses an ati card and needs catalyst drivers. The fglrx module works fine with the vanilla kernel and pacman does not install it for the rt kernel(I think they are not compatible?) so I think I need the catalyst-rt module(also while installing the kernel, the pkgbuild told me that I needed catalyst-rt).
    I could find no packages named catalyst-rt in the repos, but AUR database has one:
    But I think there is a problem with the install. After I compile the package and run it with "pacman -U", it complains about an unexpected EOF because of an unmatched quote mark. I've extracted the generated "catalyst-rt-8.5-2-i686.pkg.tar.gz" file to see if I can come up with something, there is indeed a missing quote in one of the echo statements in the contained catalyst-rt.install file. I tried fixing and retarring it but pacman complained about missing metadatas  in the package. This is my 3rd day with arch(and one of those days my Internet connection was broken) so I don't have many clues.
    I figure that there are very few people running ati drivers on a rt kernel here(searching for catalyst-rt yields to nothing) but maybe you can help me fix the issue myself, or maybe there is an easier way to use catalyst with an rt kernel?
    Any help will be greatly appreciated. Thanks!
    Last edited by pyramind (2008-07-27 18:47:04)

    Ok, some more progress:
    As I said, the vanilla kernel works fine with the catalyst drivers. Fully accelerated etc. When working with vanilla kernel if I say " dmesg | grep fglrx", the output is fine:
    fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
    [fglrx] vendor: 1002 device: 71c5 count: 1
    [fglrx] Maximum main memory to use for locked dma buffers: 1898 MBytes.
    [fglrx] PAT is enabled successfully!
    [fglrx] module loaded - fglrx 8.50.3 [Jun 2 2008] with 1 minors
    [fglrx] Reserved FB block: Shared offset:0, size:1000000
    [fglrx] Reserved FB block: Unshared offset:1000000, size:5000
    [fglrx] Reserved FB block: Unshared offset:ffbf000, size:40000
    [fglrx] Reserved FB block: Unshared offset:ffff000, size:1000
    [fglrx] Reserved FB block: Shared offset:0, size:1000000
    [fglrx] Reserved FB block: Unshared offset:1000000, size:5000
    [fglrx] Reserved FB block: Unshared offset:ffbf000, size:40000
    [fglrx] Reserved FB block: Unshared offset:ffff000, size:1000
    As you can see, the loaded version is fglrx 8.50.3 [Jun  2 2008].
    Now if I try the same on rt-kernel with catalyst-rt drivers loaded, the loaded version is shown as the incompatible fglrx 8.49.7 [May 12 2008] version.
    The package PKGBUILD downloads is ati-driver-installer-8-5-x86.x86_64
    So I assume that should be at least 8.5? Where does this loaded 8.49.7 come from?
    I'm checking /lib/modules/<myrtkernel>/ to see if there are any other fglrx.ko floating around but there is only one, the one installed from the package built with
    Since I'm not very competent with linux, I'm hoping some of you can show me some directions. I may try packaging a new ati driver to check but if ati-driver-installer-8-5-x86.x86_64 is actually 8.49, which one should I try then? 8-6? 8-7? I quite don't understand.
    Last edited by pyramind (2008-07-27 18:24:34)

  • Loading modules for old kernel during boot up

    After a kernel update I noticed this message during boot
    Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
    modprobe -r [-n] [-i] [-v] <modulename> ...
    modprobe -l -t <dirname> [ -a <modulename> ...]
    And taking a look at everything.log this came out
    May 24 13:57:54 localhost kernel: Pid: 1772, comm: modprobe Tainted: G         C  2.6.37-ARCH #1
    May 24 14:31:25 localhost kernel: Pid: 1952, comm: modprobe Tainted: G         C  2.6.37-ARCH #1
    May 24 14:34:45 localhost kernel: Pid: 1872, comm: modprobe Tainted: G         C  2.6.37-ARCH #1
    May 24 14:54:53 localhost kernel: Pid: 1966, comm: modprobe Tainted: G         C  2.6.37-ARCH #1
    May 24 15:14:03 localhost modprobe: FATAL: Could not load /lib/modules/2.6.37-ARCH/modules.dep: No such file or directory
    Jun 13 13:34:20 localhost modprobe: FATAL: Could not load /lib/modules/2.6.38-ARCH/modules.dep: No such file or directory
    I am using 2.6.39 kernel.
    Could anybody help me solve this??

    slytux wrote:
    Samana, what does your error message say?  Do you have anything in /lib/modules/2.6.39-ARCH/misc/ ?
    You can also try rebuilding the initrd image as jni suggested.
    mkinitcpio -p kernel26
    I have no "misc" folder in 2.6.39-ARCH
    The error is like a resonse from bad syntax when running a modprobe command
    Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
    modprobe -r [-n] [-i] [-v] <modulename> ...
    modprobe -l -t <dirname> [ -a <modulename> ...]
    I rebuilt the image and got a few errors in autodetect that might be a clue.
    # mkinitcpio -p kernel26
    ==> Building image "default"
    ==> Running command: /sbin/mkinitcpio -k 2.6.39-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
    :: Begin build
    :: Parsing hook [base]
    :: Parsing hook [udev]
    :: Parsing hook [autodetect]
    WARNING: All config files need .conf: /etc/modprobe.d/oldusbload, it will be ignored in a future release.
    WARNING: All config files need .conf: /etc/modprobe.d/oldusbload, it will be ignored in a future release.
    :: Parsing hook [pata]
    :: Parsing hook [scsi]
    :: Parsing hook [sata]
    :: Parsing hook [filesystems]
    :: Generating module dependencies
    :: Generating image '/boot/kernel26.img'
    :: Image generation successful
    ==> SUCCESS
    ==> Building image "fallback"
    ==> Running command: /sbin/mkinitcpio -k 2.6.39-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
    :: Begin build
    :: Parsing hook [base]
    :: Parsing hook [udev]
    :: Parsing hook [pata]
    :: Parsing hook [scsi]
    :: Parsing hook [sata]
    :: Parsing hook [filesystems]
    :: Generating module dependencies
    :: Generating image '/boot/kernel26-fallback.img'
    :: Image generation successful
    ==> SUCCESS
    Note that the error does not show up when I boot in fallback mode. So it looks like the error has something to do with autodetect. But I have no idea what it is. I am going to try to get rid of the oldusbload and see what happens. [NOTE: Getting rid of oldusbload did n
    ot fix the error]
    Last edited by Samana (2011-07-09 17:46:02)

  • Is it possible to compile NVIDIA for multiple kernels simultaneously?

    Hi all,
    First, the reference is … tom_kernel, as well as a small discussion I started at
    Basically, currently the nvidia-beta (and I'm sure the rest of the nvidia scripts) use `uname -r` to obtain the current kernel name, which is then used for the rest of the PKGBUILD. Its relatively trivial to alter that to the name of whichever kernel, meaning there's no problem compiling nvidia.ko for kernel26-ice from within kernel26 itself, and to alter the name of the package so that your nvidia-beta package does not need to be over-written (you then have two nvidia.ko, each for their own kernel.
    My question is, is it possible for a single PKGBUILD to compile nvidia.ko for all kernels currently installed (probably through looking at either /lib/modules or /usr/src)? This would mean only one maintainer is needed for nvidia-beta or nvidia-17xx or whichever series, and the same PKGBUILD could be used on any system, even those with multiple kernels.
    I'm not very familiar with the limitations of PKGBUILDs, or the rules governing what they may or may not do (for example, accessing and checking the machine itself outside the fakeroot?), so this may be nonsense, if so feel free to point it out. Another idea would be for a simple bash script to create as many PKGBUILDs as required, based on the most recent nvidia-beta PKGBUILD, simply sed-replacing uname -r with the appropriate kernel names and modifying the PKG name.

    it's not difficult to do but I DO NOT recommend to do it (see my notes below the code).
    pkgdesc="NVIDIA beta drivers for kernel26."
    arch=('i686' 'x86_64')
    [ "$CARCH" = "i686" ] && ARCH=x86 && NV=0
    [ "$CARCH" = "x86_64" ] && ARCH=x86_64 && NV=0
    depends=(kernel26 nvidia-utils-beta)
    conflicts=('nvidia-96xx' 'nvidia-71xx' 'nvidia-legacy')
    [ "$CARCH" = "x86_64" ] && md5sums=('33967a6d452c562bb8af02b0734ebf22')
    # Read list of installed kernels
    KERNELS=`ls -1 /lib/modules`
    # Extract the nvidia drivers
    cd $startdir/src/
    sh NVIDIA-Linux-${ARCH}-${pkgver}-pkg${NV}.run --extract-only
    cd NVIDIA-Linux-${ARCH}-${pkgver}-pkg${NV}
    cd usr/src/nv
    ln -s Makefile.kbuild Makefile
    # Now build modules for each kernel
    for KERNEL in $KERNELS; do
    echo "Building for ${KERNEL}"
    # Compile the module
    make SYSSRC=/lib/modules/${KERNEL}/build module || return 1
    # Install kernel module
    mkdir -p $startdir/pkg/lib/modules/${KERNEL}/kernel/drivers/video/
    install -m644 nvidia.ko $startdir/pkg/lib/modules/${KERNEL}/kernel/drivers/video/ || return 1
    # Clean
    make clean || return 1
    # arg 1: the new package version
    post_install() {
    KERNELS=`ls -1 /lib/modules`
    for KERNEL in $KERNELS; do
    depmod -v $KERNEL > /dev/null 2>&1
    # arg 1: the new package version
    # arg 2: the old package version
    post_upgrade() {
    post_install $1
    rmmod nvidia || echo 'In order to use the new nvidia module, exit Xserver and unload it manually.'
    # arg 1: the old package version
    post_remove() {
    KERNELS=`ls -1 /lib/modules`
    for KERNEL in $KERNELS; do
    depmod -v $KERNEL > /dev/null 2>&1
    $op $*
    PS: I haven't test it because I don't use multiple kernels
    But be aware of possible problems. Some modifications may influence kernel functionalities, so once you compile a driver for kernel26-xyz on kernel26-zyx the module may not work on kernel26-xyz or may cause unexpected issues.
    You also should not (you possibly even won't be able to) build module for different release version (eg. build for 2.6.28 on 2.6.29) due changes in kernel headers.
    I'm also not sure if it is safe to generate module dependencies for another kernel then you are currently running.
    As you can see above, it is not problem to make such a PKGBUILD, but it also brings too many problems and it's too dangerous that it is better to stay at current model "module package for each kernel". So if you want to you may try to use this PKGBUILD, but I strictly warn everyone else that it may cause more harm then use so don't blame me if something goes wrong. You were warned .
    Last edited by ProgDan (2009-04-30 13:48:06)

  • Oracle firewire modules for Redhat Linux 2.6.9-34.EL

    I need oracle firewire modules for Redhat Linux 2.6.9-34.EL. Can you please help where can I find firewire modules for this kernel.

    According to you should not need any additional kernel module support. You may need to install the libraw1394 RPM packages, but you can get those from your distribution media or from ULN, if your are subscribed.

  • How to programmatically resize vi for different screen resolutions ?

         I have been struggling with this,How can i built a vi that should run for different screen resolutions (on different pc's).
    There are several threads on forum , But i dont find the exact solution for it.
    I have already tried with VI properties in the VI but i dont think its working.
    Can someone please help me ?
    Thanks and regards,
    Shivkant Paswan

    Yup it is a pain to use panes, but that is the easiest method I've found which meets my requirements.  Learn to use panes and splitters effectively, and then learn their limitations and workaround when you find those limitations.  In general LabVIEW should handle multi-resolutions, and resizing better but these are the tools we have today.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • Virtualbox doesn't compiles "vboxdrv" module for 2.6.24 kernel

    I installed Virtualbox, however I cannot launch any OS because the vboxdrv module doesn't exists for the latest kernel (I found another module for the 2.6.23 kernel); so the GUI says that I should execute this:
    /etc/init.d/vboxdrv setup
    However that file doesn't exists. I already tried to uninstall virtualbox and reinstalling from pacman, but still no luck.
    What should I do? Is this a bug?
    Thanks in advance.

    I think that's where the confusion  is.  When I got the package from AUR it had:
    -rw-r--r-- 1 ralvez users  217 2008-01-08 15:58 interfaces
    -rw-r--r-- 1 ralvez users 3596 2008-01-20 11:38 PKGBUILD
    -rwx------ 1 ralvez users  174 2007-12-30 04:23 vbox_build_module
    -rw-r--r-- 1 ralvez users 2384 2007-12-30 07:39 vbox.install
    -rw-r--r-- 1 ralvez users 2179 2007-12-30 07:31 vboxnet.patch
    So the patch file is there (in bold text) ... and is not executable is a text file. That's why I'm asking if I have to do something with it to make the whole thing work.
    Since it is just a plain text file if I try to use it as an upgrade patch it fails with error:
    loading package data... error: error while reading package vboxnet.patch: Unrecognized archive format: Invalid or incomplete multibyte or wide character
    error: failed to add target 'vboxnet.patch'
    So, I'm stuck. I see no way to solve the problem.
    Edit: On re-reading your post I wonder what package from core are you referring to? I was under the impression that when we use AUR we are "fetching" files not from core but form the AUR source.
    Am I wrong?
    Last edited by ralvez (2008-02-13 22:50:31)

  • Compiling STREAM module for 64-bit kernel

    I am trying to compile a STREAM module for Solaris. The results I get when I execute "isalist" and "isainfo -kv" are:
    -"sparcv9+vis sparcv9 sparcv8plus+vis sparcv8plus sparcv8 sparcv8-fsmuld sparcv7 sparc"
    -"64-bit sparcv9 kernel modules"
    The host is a Ultra5_10 with SunOS 5.7 sun4u sparc.
    First I tried to compile the module with gcc 2.8.1 but altough the compilation apparentelly finisihed OK I did not get to load the module. Later I read that, gcc so far does not generate binaries for 64-bit sparc.
    So I installed the Sun WorkShop 5 environment (try version) and I tried to compile my sources with the following line:"cc -D_KERNEL -xarch=v9 -xcode=abs32 -xregs=no%appl -x03 -I. -I/usr/include -c mymodule.c"
    but I get a huge list of errors such as:
    "/usr/include/sys/thread.h/, line73:warning: volatile is a keyworkd in
    ANSI C"
    "/usr/include/sys/thread.h/, line 73:sintax error before or at:volatile"
    so if I compile adding the directire "-D_ASM" to the previous line, the list of errors descreases to 2 lines:
    "/usr/include/sys/kstat.h, line 52: sintax error before or at: hrtime_t"
    "/usr/include/sys/kstat.h, line 52: cannot recover from previous errors".
    I have also tried adding directives such as: -D_LP64 -D__sparcv9 -D_POSIX_C_SOURCE, -D_XOPEN_SOURCE but I do not get to compile it successfully.
    Could someone be so kind to give me a clue of what I am doing wrong, and what should I do in order to compile it??.
    The header files I have included right now in my ".c" are:
    #include <sys/stream.h>
    #include <sys/conf.h>
    #include <sys/modctl.h>
    #include <sys/kmem.h>
    #include <sys/cmn_err.h>
    #include <sys/ddi.h>
    #include <sys/sunddi.h>
    If I do not add the directives -I. -I/usr/include to the compile line above I get the following error:
    "/usr/include/sys/modctl.h, line 185: major, argument mismatch"
    "/usr/include/sys/cred.h, line 51: sintax error before or at: uint_t"
    But this is because the environment it is taken the /usr/ucbinclude as default include path instead of the "/usr/include". �which one should I consider?.
    Thank in advance for your support.
    Looking forward to hearing from you.
    (could you please send to me the answeres to this e-mail:[email protected]??)

    Maybe a file I can edit that says to run the Garmin stuff in 32-bit mode?
    Right or control click the Garmin application (or utility) then click: Get Info
    In the Get Info window under the General tab, if it can be enabled you should see:
    Open in 32-bit mode.
    Activity Monitor (Applications/Utilities) shows all apps running in 64 bit. If it doesn't have 64 bit under Kind on the right, then it's running in 32 bit mode.

  • Proper method for building kernel modules? [solved]

    I am attempting to build a custom kernel module for a PCI express interface to an FPGA.  However, I seem to be running into some issues with getting the standard kernel module makefile to work correctly.  Here is my makefile:
    # object files to build
    obj-m += nnic.o
    nic-objs += nnic_driver.o
    make -C /lib/modules/$(shell uname -r)/build M=$(pwd) modules
    make -C /lib/modules/$(shell uname -r)/build M=$(pwd) clean
    However, the first time I ran 'make', I got this output:
    make -C /lib/modules/3.14.1-1-ARCH/build M= modules
    make[1]: Entering directory '/usr/lib/modules/3.14.1-1-ARCH/build'
    Makefile:608: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler
    scripts/kconfig/conf --silentoldconfig Kconfig
    *** Error during update of the configuration.
    /usr/lib/modules/3.14.1-1-ARCH/build/scripts/kconfig/Makefile:36: recipe for target 'silentoldconfig' failed
    make[3]: *** [silentoldconfig] Error 1
    /usr/lib/modules/3.14.1-1-ARCH/build/Makefile:512: recipe for target 'silentoldconfig' failed
    make[2]: *** [silentoldconfig] Error 2
    scripts/ /usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile: No such file or directory
    make[2]: *** No rule to make target '/usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile'. Stop.
    /usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/Makefile:183: recipe for target 'archheaders' failed
    make[1]: *** [archheaders] Error 2
    make[1]: Leaving directory '/usr/lib/modules/3.14.1-1-ARCH/build'
    Makefile:7: recipe for target 'all' failed
    make: *** [all] Error 2
    After poking around online, I decided to try running make as root.  I got the following output:
    make -C /lib/modules/3.14.1-1-ARCH/build M= modules
    make[1]: Entering directory '/usr/lib/modules/3.14.1-1-ARCH/build'
    scripts/kconfig/conf --silentoldconfig Kconfig
    scripts/ /usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile: No such file or directory
    make[2]: *** No rule to make target '/usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile'. Stop.
    /usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/Makefile:183: recipe for target 'archheaders' failed
    make[1]: *** [archheaders] Error 2
    make[1]: Leaving directory '/usr/lib/modules/3.14.1-1-ARCH/build'
    Makefile:7: recipe for target 'all' failed
    make: *** [all] Error 2
    Now, when runing 'make' as a normal user, I get:
    make -C /lib/modules/3.14.1-1-ARCH/build M= modules
    make[1]: Entering directory '/usr/lib/modules/3.14.1-1-ARCH/build'
    Makefile:608: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler
    scripts/ /usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile: No such file or directory
    make[2]: *** No rule to make target '/usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/syscalls/Makefile'. Stop.
    /usr/lib/modules/3.14.1-1-ARCH/build/arch/x86/Makefile:183: recipe for target 'archheaders' failed
    make[1]: *** [archheaders] Error 2
    make[1]: Leaving directory '/usr/lib/modules/3.14.1-1-ARCH/build'
    Makefile:7: recipe for target 'all' failed
    make: *** [all] Error 2
    I have the linux-headers package installed.  I do not need to build the whole kernel, only this small module.  What am I missing here?  What is the correct procedure for this?
    Last edited by alex.forencich (2014-04-25 08:16:31)

    Sigh, found the problem.  Should be $(PWD) and not $(pwd) in my makefile.

  • Which kernel module for Intel PRO/100 S Desktop Adapt

    Which kernel module I should load for support LAN Card "Intel® PRO/100 S Desktop Adapter" Board ID "751767-004" , Based on Controller 82550

    Finded in /usr/src/linux-2.6.5/drivers/net/Kconfig
    config E100
        tristate "Intel(R) PRO/100+ support"
        depends on NET_PCI && PCI
        select MII
          This driver supports Intel(R) PRO/100 family of adapters, which
          Controller  Adapter Name                       Board IDs
          82558       PRO/100+ PCI Adapter               668081-xxx,
          82558       PRO/100+ Management Adapter        691334-xxx,
          82558       PRO/100+ Dual Port Server Adapter  714303-xxx,
          82558       PRO/100+ PCI Server Adapter        710550-xxx
          82550       PRO/100 S Server Adapter           752438-xxx
          82559                                          A56831-xxx,
          82550       PRO/100 S Desktop Adapter          751767-xxx
          82559                                          748592-xxx,
          82559       PRO/100+ Server Adapter            729757-xxx
          82559       PRO/100 S Management Adapter       748566-xxx,
          82550       PRO/100 S Dual Port Server Adapter A56831-xxx
          82551       PRO/100 M Desktop Adapter          A80897-xxx
          PRO/100 S Advanced Management Adapter
          CNR         PRO/100 VE Desktop Adapter         A10386-xxx,
          PRO/100 VM Desktop Adapter         A14323-xxx,
          To verify that your adapter is supported, find the board ID number
          on the adapter. Look for a label that has a barcode and a number
          in the format 123456-001 (six digits hyphen three digits). Match
          this to the list of numbers above.
          For more information on how to identify your adapter, go to the
          Adapter & Driver ID Guide at:
 … /21397.htm
          For the latest Intel PRO/100 network driver for Linux, see:

          More specific information on configuring the driver is in
          To compile this driver as a module, choose M here and read
          <file:Documentation/networking/net-modules.txt>.  The module
          will be called e100.

  • Trouble building kernel module for sensor support

    Hi, I'm new here but have been using Arch for a while.  Recently, I decided to install Arch on an old laptop (Toshiba A70) and have managed to work out most of the kinks to where it runs nicely.  Unfortunately, ACPI support is spotty and the /sys/class/thermal directory gives me only cooling_device0.  I installed the lm-sensors package and ran sensors-detect, which yielded no results.  Although the laptop runs smoothly otherwise, I would like to know the CPU's temp so that I would be able to set up a fan control scheme and CPU scaling (so far it's stuck at the lowest frequency, and that's kind of a big deal for me since the laptop runs on an archaic mobile P4 chip).
    Sorry for the story but I felt some context was necessary.  I did manage to find a kernel module that would connect those sensors to ACPI for me (, however I'm having trouble building it on the latest kernel.  Here is the output from running make:
    make -C /lib/modules/3.16.1-1-ARCH/build SUBDIRS=/root/omnibook-2.20070211 modules
    make[1]: Entering directory '/usr/lib/modules/3.16.1-1-ARCH/build'
    CC [M] /root/omnibook-2.20070211/init.o
    In file included from /root/omnibook-2.20070211/init.c:26:0:
    /root/omnibook-2.20070211/laptop.h:25:3: warning: initialization from incompatible pointer type
    .callback = dmi_matched,
    /root/omnibook-2.20070211/laptop.h:25:3: warning: (near initialization for ‘omnibook_ids[0].callback’)
    /root/omnibook-2.20070211/laptop.h:34:3: warning: initialization from incompatible pointer type
    .callback = dmi_matched,
    /root/omnibook-2.20070211/laptop.h:34:3: warning: (near initialization for ‘omnibook_ids[1].callback’)
    /root/omnibook-2.20070211/laptop.h:43:3: warning: initialization from incompatible pointer type
    .callback = dmi_matched,
    // I left out most of the 'incompatible pointer type' warnings since they repeat for a while.
    /root/omnibook-2.20070211/laptop.h:1001:3: warning: (near initialization for ‘omnibook_ids[108].callback’)
    /root/omnibook-2.20070211/init.c: In function ‘dmi_matched’:
    /root/omnibook-2.20070211/init.c:141:16: warning: assignment discards ‘const’ qualifier from pointer target type
    laptop_model = dmi_get_system_info(DMI_PRODUCT_VERSION);
    /root/omnibook-2.20070211/init.c: In function ‘omnibook_init’:
    /root/omnibook-2.20070211/init.c:281:3: error: implicit declaration of function ‘create_proc_entry’ [-Werror=implicit-function-declaration]
    proc_entry = create_proc_entry(feature->name, pmode, omnibook_proc_root);
    /root/omnibook-2.20070211/init.c:281:14: warning: assignment makes pointer from integer without a cast
    proc_entry = create_proc_entry(feature->name, pmode, omnibook_proc_root);
    /root/omnibook-2.20070211/init.c:290:13: error: dereferencing pointer to incomplete type
    proc_entry->data = feature;
    /root/omnibook-2.20070211/init.c:291:13: error: dereferencing pointer to incomplete type
    proc_entry->read_proc = &procfile_read_dispatch;
    /root/omnibook-2.20070211/init.c:293:14: error: dereferencing pointer to incomplete type
    proc_entry->write_proc = &procfile_write_dispatch;
    /root/omnibook-2.20070211/init.c:294:13: error: dereferencing pointer to incomplete type
    proc_entry->owner = THIS_MODULE;
    cc1: some warnings being treated as errors
    scripts/ recipe for target '/root/omnibook-2.20070211/init.o' failed
    make[2]: *** [/root/omnibook-2.20070211/init.o] Error 1
    Makefile:1333: recipe for target '_module_/root/omnibook-2.20070211' failed
    make[1]: *** [_module_/root/omnibook-2.20070211] Error 2
    make[1]: Leaving directory '/usr/lib/modules/3.16.1-1-ARCH/build'
    Makefile:88: recipe for target 'omnibook.ko' failed
    make: *** [omnibook.ko] Error 2
    I have honestly no idea what to make of any of this and would really appreciate any help towards a solution.  Thanks for reading

    Welcome to Arch Linux
    That looks like it is a 2.6 kernel module
    Did you try either of these AUR offerings?
    [email protected]$odin ~ 1001 %packer -Ss omnibook
    aur/omnibook-git 20110911-9 (7)
    Kernel module for HP OmniBook,Pavilion,Toshiba and Compal ACL00 laptops
    aur/omnibook-svn-zen 268-1 (1)
    Kernel module for HP OmniBook, Pavilion, Toshiba and Compal ACL00 laptops
    [email protected]$odin ~ 1002 %
    Last edited by ewaller (2014-08-23 23:33:53)

  • ASM module for kernel 2.4.21-27EL

    Does anybody know from where I can download ASM module (RPM or source) for kernel 2.4.21-27EL . I managed to install ocfs module with that kernel using ENBD - project for network shared storage, but the ASM module for kernels 2.4.21x is compiled for 2.4.21-19
    the source supports only 2.4.19...
    Any idea anybody?

    Hi, please send me the error log file,
    Message was edited by:

  • User exit for different modules

    Hi Everybody,
      I want to search for all User Exits for different moldules.
    Like for SD, can we find that?
    I know there is some way , Goto Se80, then.....
    Please help me guys, its Urgent....
    Will be rewarded.
    Thanks in advance.

    Go To Se84..
    Give Program Name .
    In the Tree U Will Have Option Called Enhancements
    This Shows What R the Enhancements Available For That Program Or Transaction
    User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
    The naming standard of function modules for functionmodule exits is:
    EXIT_<program name><3 digit suffix>
    The call to a functionmodule exit is implemented as:
    CALL CUSTOMER.-FUNCTION <3 digit suffix>
    To find a Exit.
    Goto Transaction -- Find The Package
    SMOD >f4>Use the Package here to Find the Exits In the Package.
    Else if you Want to search by Application Area wise ,
    There is one more tab to find the Exits in the Respective Application Area.
    Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
    Now Run ur Transaction to Check if it Triggers.
    Thats it..
    Suppose you need to find out all the user exits related to a tcode.
    1. Execute the Tcode.
    2. Open the SAP program.
    3. Get the Development Class.
    4. Execute Tcode SE84.
    5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
    6. Enter the Development class and execute.
    Check out this thread..
    The specified item was not found.
    1. Type the transaction : system->status-> <PROG. NAME>
    2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
    3. Open CMOD utilities->SAP enhancements
    EDIT->All selections
    4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
    5. The displayed list contains the enhancements names for the transaction You were looking for.
    6. Create a project in CMOD and the code in default include->activate.
    which gives the list of exits for a tcode
    For information on Exits, check these links
    These links will help you to learn more on user exits.
    Also please check these threads for more details about user exits.
    Re: Screen exit
    user exit and customer exit
    user exit
    1. Document on UserExits in FI/CO
    2. Finding User Exits...
    3. List of all User Exits...
    Reward Points if found helpfull..
    Chandra Sekhar.

Maybe you are looking for

  • Slow PS3 Connection on WRT300N

    Hi, I have just added a PS3 to my wireless network, but the connection is really slow; Has anybody had any experience with similar problems? 

  • HT1918 What I have to do to unblock my payment method?

    Hi, It seems there was a problem with my previous transaction (most probably insufficient funds - but i had deposited money on my card after the situation) and now I need to unblock my payment method. The same method is not accepted. If I enter an al

  • How do I identify the path and contents of a Code Interface Node

    I have an inherited a VI file that contains a CIN. If i double left click on the CIN icon nothing happens. Single right click and the menu options do not provide a way to identify the path/contents of the CIN. How can I found exactly what is going on

  • Motion Tween Scaling a UILoader loaded Image

    Hello: I know how to make an image scale up upon a button click. If it is possible, what is difference in the actionScript code if the image has been loaded using the UILoader ? Currently I have the Component scaling up upon a button click but the Co

  • How File Path will be decided for downloading Interactive form

    Hi, I have error like... temp\webdynpro\web\local\DynPro6\Components\com.dynpro.DynPro6\PurchaseRequisition.pdf (The system cannot find the path specified) Can any busy suggest how the path will be decided for local and