_STILL_ battling with compiling a custom Kernel - Redhat

This is a discussion on _STILL_ battling with compiling a custom Kernel - Redhat ; I originally posted this a few weeks ago: > I was able to build the kernel, and build the initrd file to go with it. > After much fiddling, I was even able to get both to boot/load via Grub ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: _STILL_ battling with compiling a custom Kernel

  1. _STILL_ battling with compiling a custom Kernel

    I originally posted this a few weeks ago:

    > I was able to build the kernel, and build the initrd file to go with it.
    > After much fiddling, I was even able to get both to boot/load via Grub
    > (I had to remove the 'label' that Redhat defauts to for the root drive
    > name, and make a few other small changes).
    >
    > However, this kernel is "broken". My ethernet connection no longer
    > works. My Nvidia driver won't recompile. Several services fail upon
    > boot. I get warnings that I can't use my USB and firewire connections
    > (not that I actually use either, but, it's the principle of the matter).
    > Iptables also apparently fails (although that may be a side effect of
    > the bad e0 port).


    Checking over the error messages, I worked out that the compoments
    that were 'supposed' to load as modules weren't actually loading. I
    read over both the Redhat kernel rebuilding READMEs, and the Custom
    Kernel FAQ. But, I couldn't find any in depth discussion of
    troubleshooting the modules.

    I did come up with this:

    Build the Modules
    There is one more step needed for the build process, however. You have
    created the kernel, but now you need to create all the loadable
    modules if you have them configured. Be aware that typical
    distribution kernels tend to have almost ever feature installed, plus
    a few others for good measure. These can typically take and hour or so
    to build on our Athlon XP1800. The stock kernels are somewhat leaner
    by default and take, on average, 25 minutes to compile. To build the
    modules we run: $ make modules

    Again, lots of messages will scroll by on the screen. Here also the
    2.6.0 series is less talkative, outputting only summary information.
    Once the modules are built they can be installed. If you were building
    as a non-privileged user you will now need to switch to root to
    complete this next step: $ su
    password:
    $ make modules_install

    The freshly baked modules will be copied into
    /lib/modules/KERNEL_VERSION.


    On my install, a ls of /lib/modules shows there may or may not be an
    appropriate directory:

    dh03 8] modules > ls -a /lib/modules
    ../ 2.4.20-18.1.caps/ 2.4.20-18.9custom/ 2.4.20-20.9/ 2.4.20-27.9/
    2.4.20-30.9/ 2.4.20-8/ 2.6.0/
    .../ 2.4.20-18.9/ 2.4.20-19.9/ 2.4.20-24.9/
    2.4.20-27.9custom/ 2.4.20-30.9custom/ 2.4.25/


    my kernel is 2.4.20-30.9.

    Should there actually be a 2.4.20-30custom/ directory (if so, that
    could be the 'problem' right there???)

    If the modules directory is missing...what sort of things 'could'
    cause that to happen when I do type 'make modules' / 'make
    modules_install' as root and I'm not being given any error messages
    that the modules _aren't_ doing what they're supposed to do?!?

    Gwen




  2. Re: _STILL_ battling with compiling a custom Kernel

    In article , Gwen Morse wrote:
    > On my install, a ls of /lib/modules shows there may or may not be an
    > appropriate directory:
    >
    > dh03 8] modules > ls -a /lib/modules
    > ./ 2.4.20-18.1.caps/ 2.4.20-18.9custom/ 2.4.20-20.9/ 2.4.20-27.9/
    > 2.4.20-30.9/ 2.4.20-8/ 2.6.0/
    > ../ 2.4.20-18.9/ 2.4.20-19.9/ 2.4.20-24.9/
    > 2.4.20-27.9custom/ 2.4.20-30.9custom/ 2.4.25/
    >
    >
    > my kernel is 2.4.20-30.9.
    >
    > Should there actually be a 2.4.20-30custom/ directory (if so, that
    > could be the 'problem' right there???)


    If the kernel is 2.4.20-30.9, then the directory will be 2.4.20-30.9/

    Often kernel patches you may find for kernels will change the name
    (as listed in the source files) and one has to know what it is.
    (they may add "custom" or something)

    > If the modules directory is missing...what sort of things 'could'
    > cause that to happen when I do type 'make modules' / 'make
    > modules_install' as root and I'm not being given any error messages
    > that the modules _aren't_ doing what they're supposed to do?!?


    If the kernel is 2.4.20-30.9, they get installed in 2.4.20-30.9/

+ Reply to Thread