Re: adding modules to kernel

From: Adam Hardy (adam.ant_at_cyberspaceroad.com)
Date: 08/29/05

  • Next message: ali_at_arles-electrique.de: "Re: Re: Flush ip_conntrack" 
    Date: Mon, 29 Aug 2005 10:28:13 +0100
To: debian-user@lists.debian.org

    Bob Proulx on 29/08/05 03:35, wrote:
    >
    > * You are not using --append-to-version. You should because otherwise
    > your package versions will be simply 2.6.12 or similar and won't
    > have any way to differentiate them from each other.
    >
    > These questions can all be answered in the docs here:
    >
    > http://newbiedoc.sourceforge.net/system/kernel-pkg.html
    >

    Right. Having read that and also the man page, I got the following
    advice which confused my simple caffeine starved brain. What do I do if
    I only want to compile a module which I forgot in xconfig? Can I avoid
    the complete compile??

    Quote man:
      --append_to_version foo
    [snip.....]
    Please note that you must run a make-kpkg clean after configuring the
    kernel using make (x|menu)?config, since that creates the file
    include/linux/version.h without the append_to_version data (foo). This
    file won't be updated by the make-kpkg run (make-kpkg creates version.h
    if it doesn't exist, but doesn't touch if exists), so the final kernel
    will _not_ have the append_to_version data in its version number it
    shall look for the modules and symbols in all the wrong places. The
    simplest solution is either to remove include/linux/version.h after
    configuring and before compiling, or running make-kpkg clean after
    configuring, before compiling. 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: ali_at_arles-electrique.de: "Re: Re: Flush ip_conntrack"

    Relevant Pages

    • Re: Problem with compiling kernel
      ... and got to the stage where it said to run this: "fakeroot make-kpkg clean" ... Run the command as "sudo fakeroot make-kpkg clean"? ... The list ethicist is going to get me for this but I always compile my kernels logged in as root. ... Processor type and features -> Preemption Model (Preemptible Kernel (Low-Latency Desktop)) ...
      (Debian-User)
    • Re: How do I use the linux-headers with the linux-source?
      ... The above is from my compiled and installed kernel tree whereas if I move it to a backup and untar a new tree the file does not exist. ... here is the procedure I followed to compile the kernel: ...
      (Debian-User)
    • Re: reiserfs
      ... >> Compiling the kernel is easy. ... The hard part is configuring it the first ... You will also need to compile in scsi-emulation and scsi-cdrom. ... Micha Feigin ...
      (Debian-User)
    • Re: Could not find any loop device
      ... > when I was configuring the kernel. ... > what I need to compile in. ... `'` proud Debian admin and user ...
      (Debian-User)
    • Re: Firestarter cant find IPtables
      ... >> Don't compile it into the kernel, you need to build it as modules. ... When configuring the kernel with menuconfig, ... I know I'm a little behind on the thread, but if you compile the parent as ...
      (alt.os.linux)