I compiled myself a 2.4.22 kernel, and there were some errors. The errors occurred basically in the phase. the errors were:

• In the make install phase
• /lib/modules/<ref_to_kernel_version> is not a directory (I'm supposing this caused the next one)
• mkinitrd failed - this presumably was the one that caused the next one(s)
• make[1]: *** [install] error 1 (and 2)
  and in the make modules install phase
• warning: 1 of 13 computed checksums did not match (repeated a number of times
• and yet again mkinitrd failed and make[1]: *** [install] error 1 and 2

I suppose that from this it's obvious that grub was not updated - initrd is something that's needed for gunzipping the vmlinuz compressed kernel - or I may be wrong.

is this a problem with my machine (athlon XP 2400+ thoroughbread). I used a kernel-2.4.22-athlon.config file to load into xconfig. I first studied the current .config file from /boot to get some idea what I'm supposed to do.

Any ideas, folks? Do we have kernel development experts here?

Okay, since nobody ventures a guess here, I'll just try to reproduce the error.

For background, I did install the kernel development package (all of it) from a 6 week old downloaded and tested redhat 9.0 install package.

I've got the same problem going on. I ran an error file with:

make modules 2> install_err.err

I assumed this would give me a sexy layout out of what exactly went wrong but it's just a bunch of illegible gibberish.

Only difference between our issues is that mine occurred while building the modules. Some friendly advice ~ If you've got slick moves like me and manage to get the new kernel into the grub config, don't run it. It's not pretty. I would know.

I studied the error output from build phases, and there was nothing but a list of compiler complaints and warnings about minor issues that I suppose never totally go away.

It was specifically from make install command that I got specific error messgages, the center of them appearing to be that there was no subdirectory in /lib/modules/ corresponding to my new kernel. So, a slick puppy that I am , I just manually created that and run install again.

now the process sailed through without actual "error" messages and grub.conf got updated w/ apparently correct looking information. But when I boot, I get This I take to mean that there could be a grub boot line option that could save me, but I'm not yet experienced enough to know what exactly to offer.

So, what I'm doing is with intermittent and