I'm starting to get a little frustrated with this issue.  Probably
because I'm confused somewhere here.  I am trying to build a custom
kernel, and I can do that fine.  The problem is that the new kernel
modules don't seem to install correctly.  I still have symbolic links to
all the old modules.

I'm using RH 5.1 with all pertinent errata insalled.  I have the 2.0.35
kernel source, headers, etc, and everthing else kernel related in the
proper directories.

Here's what I'm doing which is straight from the RedHat manual and from
my reading of Kernal HOWTOs and other related HOWTOs.

As root (not su'd to root) I enter the /usr/src/linux directory.  Then I
issue a "make mrpoper" from there.  Fine.  Then I "startx" so that I can
use xconfig.  Then I type xconfig from there to start making the config
file for the new kernel. I select all my options from there, then choose
save and exit. All is fine so far.

The following is what I do next:

        make dep
        make clean
        make boot
        make modules
        rm -rf /lib/modules/2.0.35-2-old

NOTE:  The above step trouble me.  I don't think it's correct. I think
it should be 2.0.35-2 instead of the same with the -old extension.  I
believe I've tried this both ways though, with the same result

        mv /lib/modules/2.0.35-2 /lib/modules/2.0.35-2-old
        make modules_install
        mv /boot/vmlinuz /boot/vmlinuz.old
        cp /usr/src/linux/arch/i386/boot/zImage /boot/vmlinuz
        pico /etc/lilo.conf (to edit the file and check config)
        /sbin/lilo

Okay, all my symbolic links for the modules still refer to the old
kernel, in this case, 2.0.35-2. Argh!  So I get a few complaints in the
boot messages about that.

This whole process takes maybe 20 minutes start to finish (I've been
through the danged config screens so many time now I can do it in my
sleep).  Plus my AMD K6 300 clocked at 342mhz (66 X 5, turbo enabled)
with 64mb of SDRAM zips right along through the compiling, etc.

So it's not a big deal to do this until I get it right...I just want it
to work correctly dang it.  The really strange thing is that I did a
"locate sound.o" because I downloaded and installed the OSS sound config
trialware, and I get symbolic links to kernels 2.0.34-6 and 2.0.35.2
coming up, even after I recursively deleted the directories.

How do I get rid of those?  I'm assuming that if I can get this right
that those links will be taken care of. How can I remove them?  Is there
a way to view all the symoblic links that I'm interesed in for the
kernel and modules?  Can I just clean out all the old kernel stuff and
modules and make the kernel and modules so that I don't have all that
crap lying around in the directories?

Help! :-)

James

Reply via email to