>>>>> "m" == madhu <[EMAIL PROTECTED]> writes:
m> hi thanx for U'r interest in this problem.
m> here is the complete /etc/lilo.conf file
m> corresponding to the output in previous mail.
m> boot=/dev/hda
m> map=/boot/map
m> install=/boot/boot.b
m> prompt
m> timeout=50
m> default=linux
m> image=/boot/vmlinuz-2.2.13
m> label=linux-2.2.13
m> root=/dev/hda2
m> read-only
m> image=/boot/vmlinuz-2.2.22
m> label=linux-2.2.22
m> root=/dev/hda2
m> read-only
m> image=/boot/vmlinuz-2.2.5-15
m> label=linux-2.2.5
m> root=/dev/hda2
m> read-only
m> here both linux-2.2.5 and 2.2.13 are getting added and
m> iam able to see them at boot time. linux-2.2.22 is the
m> new image. iam sure that it is an image.
Nothing wrong there I can see, so my suggestion to you is rename
vmlinuz-2.2.22 to vmlinuz-2.2.22.sav.
Then copy vmlinuz-2.2.13 to vmlinuz-2.2.22.
Now re-run 'lilo -v -v' and check the output, if this works
correctly your image must be bad.
Just to double check run:
file vmlinuz-2.2.22.sav
it should return:
vmlinuz-2.2.22.sav: x86 boot sector
>From the README file in /usr/src/linux, which you should read:
- In order to boot your new kernel, you'll need to copy the kernel
image (found in /usr/src/linux/arch/i386/boot/zImage after compilation)
to the place where your regular bootable kernel is found.
So if you compiled it as make zimage you should have this file zImage
which you rename to whatever you want, then copy it to /boot and
change lilo.conf to what you called your new kernel.
--
Ray Curtis Unix Programmer/Consultant Curtis Consulting
mailto:[EMAIL PROTECTED] http://www.clark.net/pub/ray
============================================================================
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
