• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 291
  • Last Modified:

can't boot kernel

I have the Redhat 6.0 distribution.  It comes with kernel 2.2.5-15.

Several weeks ago, I downloaded and compiled 2.2.14.  That worked.

This weekend, I tried to recompile with several changes in the configuration.  But now, when I try to boot with the newly compiled kernel, it fails.  I use LILO, and it looks like:

LILO boot:  linux
loading linux.............

LILO boot:


or something like that.  It never says 'Uncompressing kernel blablabla...'  I am using the bzImage file just like I did the first time when it worked.

Any ideas?
0
red5
Asked:
red5
  • 3
  • 3
1 Solution
 
yngguruCommented:
Did you type 'make mrproper' in the kernel source tree before you recompiled?  This command cleans all the object files that the compiler links and forces the compiler to recompile the WHOLE source tree.  This will also insure that the code does not conflict with any old code left by your previous compilation of the kernel.  After you enter this command though, you will have to reconfigure your kernel.
0
 
red5Author Commented:
I used 'make clean'.  Maybe that's not enough.

Can I copy the .config file before I run this and then copy it back so I don't have to redo all the setup?
0
 
jyu_88Commented:
if you do 'make xconfig', a set of buttons is to allow you to save config to a file or load config from a file. Then you can save the config to somewhere safe. I guess 'make menuconfig' will have some switches to allow you to do the same thing.

'make clean' would be enough.

/usr/src/linux/arch/i386/boot/bzImage should be used.
also, did you run lilo after put new kernel into place??



0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
red5Author Commented:
I did use /usr/src/linux/arch/i386/boot/bzImage

I did *not* run lilo, but I thought I didn't have to since no filenames changed.  (I just replaced the old vmlinuz with the new one)

Maybe I still need to run lilo.
0
 
jyu_88Commented:
I think you need to.

also, it is always a good idea to keep the old trusted kernel in the LILO until you are really sure the new one is working for you. You know that:-)
0
 
red5Author Commented:
Well, I still have the original 2.2.5-15 kernel that came with linux (fortuneately).

I've learned a little about LILO in the last few hours and I definitely need to rerun LILO.

jyu_88 answered this question.  Please submit your comment to run lilo as an answer.

Thanks everyone.
0
 
jyu_88Commented:
here is the answer again,
from LILO's user_guide.ps in /usr/doc/
"You have to rerun lilo everytime you change kernel or lilo.conf or anything mentioned in lilo.conf, you cannot run too many times of LILO:-)"
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now