Question: Are you dual booting on this system? I had a similar problem, but
basically the boot information the primary OS gets, must point to your new
kernel image...

if you're not dual booting, please ignore my post.

Ahbaid.

Statux wrote:

> notes for keeping things pretty well organized:
>
> 1) stick to the /boot/vmlinuz-[kernel version] format
> 2) Always define an image with a label of "linux" (which is the default) I
> see you have none listed this way. The one labeled linux will get marked
> as default.. if you simply run 'lilo' you'll see something like:
>
> Added linux *
> Added mynew
>
> etc.
>
> On Wed, 20 Sep 2000 [EMAIL PROTECTED] wrote:
>
> >
> >  Hello Bret,
> >
> >  thanx for U'r reply.
> >
> >  i tried  lilo -v also. but i got the same error again.
> >
> >   sample output of  lilo -v
> >
> >
> >      LILO version 21, Copyright 1992-1998 Werner Almesberger
> >
> >      Reading boot sector from /dev/hda
> >      Merging with /boot/boot.b
> >      Boot image: /boot/vmlinuz-2.2.13
> >      Added linux-2.2.13
> >      Boot image: /boot/vmlinuz-mynew    -----> Image i added
> >      Added mynew                        ----->
> >      No images have been defined.
> >
> >   and when i reboot, iam not able to see the  mynew image that
> >
> >   i added.
> >
> >   any suggestions are welcome.
> >
> > regards
> > Madhu Babu P
> >
> >
> > On Sat, 2 Sep 2000, Bret Hughes wrote:
> >
> > > [EMAIL PROTECTED] wrote:
> > >
> > > >  hello all,
> > > >
> > > >  i have a system already running linux.
> > > >
> > > >  recently i recompiled this system and
> > > >
> > > >  tried to add the new kernel image into
> > > >
> > > >  /boot/.
> > > >
> > > >  i followed the usual sequence for compiling...
> > > >
> > > >    make config
> > > >
> > > >    make dep
> > > >
> > > >    make clean
> > > >
> > > >    make bzImage
> > > >
> > > >    make modules; make modules_install
> > > >
> > > >  then i copied the new image,
> > > >
> > > >    /usr/src/linux/arch/i386/boot/bzImage
> > > >
> > > >  to /boot/vmlinuz-mynew.
> > > >
> > > >  appropriately i added an entry for this in lilo.conf
> > > >
> > > >  something like
> > > >
> > > >     image=/boot/vmlinuz-mynew
> > > >         label=mynew
> > > >         root=/dev/hda2
> > > >         read-only
> > > >
> > > >  then i ran lilo. surprisingly i saw a new message
> > > >
> > > >  that i never saw before in this process......
> > > >
> > > >    "No images have been defined."
> > > >
> > > >  can anybody tell me why???
> > > >
> > > >  i think i'll get a sure answer immediately..
> >
> >
> > > Idon't know but did you run lilo -v ?  It might give a
> > > little more info.
> > >
> > > Bret
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Redhat-list mailing list
> > > [EMAIL PROTECTED]
> > > https://listman.redhat.com/mailman/listinfo/redhat-list
> > >
> >
> >
> >
> > _______________________________________________
> > Redhat-list mailing list
> > [EMAIL PROTECTED]
> > https://listman.redhat.com/mailman/listinfo/redhat-list
> >
>
> --
> **********
> * Statux *
> *************************************************************************
> *               |                                                       *
> * E-Mail:       |   [EMAIL PROTECTED]                                  *
> * ICQ:          |   1732414                                             *
> * Homepage:     |   http://www.geocities.com/reverendstatux/            *
> *               |                                                       *
> *************************************************************************
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to