#17 Kernel Module appletalk not in Modules ...

closed
nobody
None
5
2007-11-21
2005-06-29
Peter Koch
No

Hi,

i need the appletalk Protocol, but the Kernel Modules
are not in the Modules Package. Can anyone help me?

Regards,
Peter

P.S.:
I am using:
Linux virtualix.intern.peterkoch.de 2.6.10-co-0.6.2 #5
Sat Feb 5 10:19:16 IST 2005 i686 i686 i386 GNU/Linux

Discussion

  • peter green

    peter green - 2005-06-29

    Logged In: YES
    user_id=418950

    dowload the 2.6.10 kernel source from kernel.org
    patch it with the colinux patch (patch/linux iirc)
    copy in the kernel config supplied with colinux (i don't
    remember exactly what its called but it shouldn't be too
    hard to find it needs to be put in the kernel source dir
    with the name .config iirc)
    run make menuconfig and make your changes
    run make vmlinux and make modules to build yourself a new
    kernel and set of modules.

     
  • George P Boutwell

    Logged In: YES
    user_id=30412

    Peter,

    Shouldn't be too hard to compile that specific module for
    coLinux kernel.... Roughly speaking what you need to do...

    1) Download coLinux source,
    http://prdownloads.sourceforge.net/colinux/colinux-0.6.2.tar.gz?download
    2) extract above into an directory.
    3) download the 2.6.10 kernel source,
    http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.10.tar.bz2
    (Might be better to use a mirror close to you)
    4) Extract 2.6.10 kernel source
    5) patch kernel source with coLinux patch,
    <path-to-colinux-src>/patch/linux | patch -p1
    6) edit
    <path-to-colinx-patched-kernel>/localversion-cooperative,
    ensure it has co-0.6.2 in it. If it does leave it alone, if
    it doesn't add it.
    7) copy the vmlinux file from the colinux install directory
    into <path-to-colinux-patched-kernel>/vmlinux
    8) from the <path-to-colinux-patched-kernel> make menuconfig
    9) enable the appletalk module
    10) make modules modules_install

    and you should be set...

     
  • George P Boutwell

    Logged In: YES
    user_id=30412

    Ooops... yeah, after you have patched the kernel source and
    before you make menuconfig you need to copy the coLinux
    config as Peter mentioned:

    cp <path-to-colinux-src>/conf/linux-config .config

     
  • peter green

    peter green - 2005-06-29

    Logged In: YES
    user_id=418950

    note that there can be issues if your vmlinux is built with
    a different compiler from your modules so its usually a good
    idea to rebuild both.

     
  • George P Boutwell

    Logged In: YES
    user_id=30412

    Sounds right... But then you have to make sure to copy the
    vmlinux out to the colinux install directory and reboot....
    You might be able to get away without that, but it's
    probably safest to do that. Also, if you have different
    compiler, then you could run into problems with the
    user-land daemons.

     
  • Peter Koch

    Peter Koch - 2005-06-30

    Logged In: YES
    user_id=1256494

    Thanks to all, i will try that ....
    Is Kernel Version 2.6.10 a must, or can i use a newer
    Version?

     
  • George P Boutwell

    Logged In: YES
    user_id=30412

    The kernel patch that is part of the colinux source for
    0.6.2 is for kernel 2.6.10... You could try a newer kernel,
    but then you'd have to adjust the patch for that newer
    kernel. 0.6.3 (there's a snapshot with binaries and source
    at http://www.colinux.org/snapshots ) has 2.6.11 and is
    really quite stable and has a number of improvements over
    0.6.2. I've tried most the recent 2.6.11.x versions against
    with the 2.6.11-0.6.3 patch and all seems well. Currently
    there is no 2.6.12 patch.

     
  • Henry N.

    Henry N. - 2007-11-21
    • status: open --> closed
     
  • Henry N.

    Henry N. - 2007-11-21

    Logged In: YES
    user_id=579204
    Originator: NO

    Outdated now. Have lots of docs about configure and build a custom kernel.
    All finds in source as doc/building and in the Wiki:
    http://colinux.wikia.com/wiki/CoLinuxBuilding

     

Log in to post a comment.