hi,
sorry if i didn't mention the fact that
i actually added two images...
image=vmlinuz-2.2.13 --> initially exusting image
...
image=vmlinuz-2.2.22 --> the image that i compiled and added.
...
image=vmlinux-2.2.15 --> another
On Wed, 06 Sep 2000, Leonard den Ottolander wrote:
> Hello Madhu,
>
> > though the problem is solved, iam still unable
> > to understand why it was not including that
> > single image(the one i added newly).
>
> If lilo fails in *any* respect it will not write the bootsector, as to avoid
>
Hello Madhu,
> though the problem is solved, iam still unable
> to understand why it was not including that
> single image(the one i added newly).
If lilo fails in *any* respect it will not write the bootsector, as to avoid
writing a corrupt one. Well, I guess John said that
On Tue, 05 Sep 2000, [EMAIL PROTECTED] wrote:
> hello John,
>
> i think you understood what i wanted to say.
>
> when i ran lilo, it added the image that is
>
> below the new image in lilo.conf file.
>
> then why can't it do with the one i added(new image).
>
[snip]
> now when lilo can
hello John,
i think you understood what i wanted to say.
when i ran lilo, it added the image that is
below the new image in lilo.conf file.
then why can't it do with the one i added(new image).
let me explain again.
look at this sample lines of code of /etc/lilo.conf
image=/bo
On Tue, 05 Sep 2000, [EMAIL PROTECTED] wrote:
> though the problem is solved, iam still unable
> to understand why it was not including that
> single image(the one i added newly).
> why just that image was missing in the options
> at boot time.
>
> anybody can tell why this happened.
>
Bec
hello all,
thanx for your help.
atlast the problem got solved...
as all of you mentioned, it was problem
with the missing DEFAULT entry.
i.e. there must be an entry corresponding
to the line
default=x
so I changed the above line to
default=linux-2.2.13
which is the fir
> "wwep" == Ward William E PHDN <[EMAIL PROTECTED]> writes:
>> From this, it appears to me to be obvious
wwep> Your default is wrong... there is no image that
wwep> you have labeled as linux. You need to change
wwep> default=linux to default=linux-2.2.22 (or whatever
wwep> you wish to m
Ray Curtis
Cc: [EMAIL PROTECTED]
Subject: Re: Urgent:No images have been defined.
hi thanx for U'r interest in this problem.
here is the complete /etc/lilo.conf file
corresponding to the output in previous mail.
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
defau
On Tue, 05 Sep 2000, [EMAIL PROTECTED] wrote:
> hi thanx for U'r interest in this problem.
>
> here is the complete /etc/lilo.conf file
>
> corresponding to the output in previous mail.
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> default=linux
>
I see one
> "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> i
Leonard den Ottolander wrote:
> Hi Bret,
>
> > Rearrange the lines in your lilo.conf to :
> >
> > label=mynew
> > image=/boot/vmlinuz-mynew
> > root=/dev/hda2
> > read-only
>
> For a moment I thought you we're right. But no, image always comes before
> label. Chec
Hello Madhu,
> default=linux
> label=linux-2.2.13
> label=linux-2.2.22
> label=linux-2.2.5
That helps! Your default entry shows a label that is no longer existent.
Delete the default entry (in which case the first entry is booted by default),
or enter a
Hello Madhu,
> i insist on the point that only the new image that
>
> i added after recompilation is not getting added.
That is incorrect. Nothing is being added, lilo writes nothing, so the old
situation persists. See my other mail for the answer to your problem.
Hi Bret,
> Rearrange the lines in your lilo.conf to :
>
> label=mynew
> image=/boot/vmlinuz-mynew
> root=/dev/hda2
> read-only
For a moment I thought you we're right. But no, image always comes before
label. Check your lilo.conf. Please don't confuse me again ;
hi,
there is a line that specifies the default image.
i had sent a mail just now to the mailing list
that has the /etc/lilo.conf file in it.
please have a look at that.
i insist on the point that only the new image that
i added after recompilation is not getting added.
thanx for
hi thanx for U'r interest in this problem.
here is the complete /etc/lilo.conf file
corresponding to the output in previous mail.
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux
image=/boot/vmlinuz-2.2.13
label=linux-2.2.13
root=/dev/hda2
On Wed, Sep 20, 2000 at 12:35:36PM +0530, [EMAIL PROTECTED] wrote:
>
> hi,
>
> you can see the output of lilo -v -v down here.
>
> it does gave somewhat clear info of what is going on.
>
>
> $lilo
>
> LILO version 21, Copyright 1992-1998 Werner Almesberger
>
> Reading boot sector f
Hello Madhu,
I think it would be usefull if you send us your lilo.conf. And you might want
to put your clock back :).
Bye,
Leonard.
___
Redhat-list ma
[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
>
>ma
> "m" == madhu <[EMAIL PROTECTED]> writes:
m> hi,
m> you can see the output of lilo -v -v down here.
m> it does gave somewhat clear info of what is going on.
m> $lilo
m> LILO version 21, Copyright 1992-1998 Werner Almesberger
m> Reading boot sector from /dev/hda
m> Merging w
hi,
you can see the output of lilo -v -v down here.
it does gave somewhat clear info of what is going on.
$lilo
LILO version 21, Copyright 1992-1998 Werner Almesberger
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Secondary loader: 8 sectors.
Boot image: /boot/v
hi,
i didn't get what you are trying to say.
what is this "dual booting".
iam just adding a new image of the kernel
in /etc/lilo.conf and trying to get an option
of which image to use when i boot.
what is that you are trying to say, can U explain it.
> "m" == madhu <[EMAIL PROTECTED]> writes:
m> Hello Bret,
m> thanx for U'r reply.
m> i tried lilo -v also. but i got the same error again.
m> sample output of lilo -v
m> LILO version 21, Copyright 1992-1998 Werner Almesberger
m> Reading boot sector from /dev/hda
m>
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:
>
>
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 se
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
[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
>
>ma
28 matches
Mail list logo
