2001-02-02 20:36:40

by newsreader

[permalink] [raw]
Subject: did 2.4 messed up lilo?

I'm not sure whether this problem is related
to 2.4 kernel.

I've installed kernels 2.4.0-prex to 2.4.1 on
the following machines. All are now running 2.4.1.
Judging from my past experience posting here I'm giving much
information

- compaq prolinea p-90 de4x5 driver 1 gig quantum drive cmd 640 controller
- dell optiplex p-133 hp-pcplus driver 8 gig seagate cmd 640 controller
- ibm p-133 de4x5 driver maxtor 4 gig

All partitions are reiserfs. except for dell box linux is
the only system and root is on /dev/hda1. dell's root is on
/dev/hda7 with /dev/hda1 occupied by the unmentionable.

Soon after I've installed 2.4.xx lilo stopped working
properly. Unfortunately I'm not sure whether it
started with as soon as any 2.4 installed or on subsequent
installation.

What happens is the lilo does not give you any prompt
any more. My /etc/lilo.conf, of course, have proper
timeout parameter which were working before with 2.2.18.

On compaq it does not even boot at all from hard drive.
I'm using a floopy to boot and run that box. Others
just boot right into the default specified in /etc/lilo.conf

I would not be complaining if it weren't for the fact
that lilo does not obey kernel parameters any more. On
ibm box I need to append="hdc=ide-scsi" to use
my cd-rw drive. The system boots with the right
kernel but I cannot use cd-rw because it apparently
is not looking at the kernel parameters.

I also am no good at installing lilo on a floppy.

I apologize in advance if this problem is not 2.4 related.

FYI I've also installed 2.4 on celeron 566 without
this problem. I'm just not running 2.4 on this one
just because I cannot make the graphics card
operate under 2.4

Thanks in advance







2001-02-02 20:56:20

by Chris Mason

[permalink] [raw]
Subject: Re: did 2.4 messed up lilo?



On Friday, February 02, 2001 03:36:18 PM -0500 [email protected]
wrote:

> I'm not sure whether this problem is related
> to 2.4 kernel.
>

I suspect it is a reiserfs problem, and that you are using lilo older than
21.6. Are you mounting /boot with -o notail?

Regardless, I'm willing to bet upgrading to lilo 21.6 will solve this. It
calls an ioctl reiserfs provides to unpack small files, and I've seen it
fix this exact problem on one of my devel boxes (no lilo prompt, append
lines in lilo.conf ignored).

-chris

2001-02-03 01:47:53

by Miles Lane

[permalink] [raw]
Subject: Re: did 2.4 messed up lilo?

Chris Mason wrote:
>
> On Friday, February 02, 2001 03:36:18 PM -0500 [email protected]
> wrote:
>
> > I'm not sure whether this problem is related
> > to 2.4 kernel.
> >
>
> I suspect it is a reiserfs problem, and that you are using lilo older than
> 21.6. Are you mounting /boot with -o notail?
>
> Regardless, I'm willing to bet upgrading to lilo 21.6 will solve this. It
> calls an ioctl reiserfs provides to unpack small files, and I've seen it
> fix this exact problem on one of my devel boxes (no lilo prompt, append
> lines in lilo.conf ignored).

I also found this patch for lilo 21.6:


http://industrial-linux.org/distro/download/lilo-21.6-glibc-2.2-reiserfs.patch

Perhaps someone familiar with the lilo and reiserfs code could explain
whether or not this patch is really needed.

Miles

2001-02-03 01:56:14

by Miles Lane

[permalink] [raw]
Subject: Re: did 2.4 messed up lilo?

Hmm. I just downloaded the lilo 21.6 source and the patch appears to
have
already been applied. I got 21.6 from:

http://ftp.cnr.it/Linux/system/boot/lilo/lilo-21.6.1.tar.gz

Miles Lane wrote:
>
> Chris Mason wrote:
> >
> > On Friday, February 02, 2001 03:36:18 PM -0500 [email protected]
> > wrote:
> >
> > > I'm not sure whether this problem is related
> > > to 2.4 kernel.
> > >
> >
> > I suspect it is a reiserfs problem, and that you are using lilo older than
> > 21.6. Are you mounting /boot with -o notail?
> >
> > Regardless, I'm willing to bet upgrading to lilo 21.6 will solve this. It
> > calls an ioctl reiserfs provides to unpack small files, and I've seen it
> > fix this exact problem on one of my devel boxes (no lilo prompt, append
> > lines in lilo.conf ignored).
>
> I also found this patch for lilo 21.6:
>
> http://industrial-linux.org/distro/download/lilo-21.6-glibc-2.2-reiserfs.patch
>
> Perhaps someone familiar with the lilo and reiserfs code could explain
> whether or not this patch is really needed.
>
> Miles
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> Please read the FAQ at http://www.tux.org/lkml/

2001-02-03 05:14:42

by newsreader

[permalink] [raw]
Subject: Re: did 2.4 messed up lilo?


I've now installed 21.6 downloaded from metlab
and all seems to be ok now... well at
least the dell box.. compaq boot sector may
have been blown off for some reason..it won't
boot at all athough this time it's a different
way of being stuck like LI instead of LILO.
I will try ibm box in the morning when the traffic
is light.


On Fri, Feb 02, 2001 at 05:58:21PM -0800, Miles Lane wrote:
> Hmm. I just downloaded the lilo 21.6 source and the patch appears to
> have
> already been applied. I got 21.6 from:
>
> http://ftp.cnr.it/Linux/system/boot/lilo/lilo-21.6.1.tar.gz
>
> Miles Lane wrote:
> >
> > Chris Mason wrote:
> > >
> > > On Friday, February 02, 2001 03:36:18 PM -0500 [email protected]
> > > wrote:
> > >
> > > > I'm not sure whether this problem is related
> > > > to 2.4 kernel.
> > > >
> > >
> > > I suspect it is a reiserfs problem, and that you are using lilo older than
> > > 21.6. Are you mounting /boot with -o notail?
> > >
> > > Regardless, I'm willing to bet upgrading to lilo 21.6 will solve this. It
> > > calls an ioctl reiserfs provides to unpack small files, and I've seen it
> > > fix this exact problem on one of my devel boxes (no lilo prompt, append
> > > lines in lilo.conf ignored).
> >
> > I also found this patch for lilo 21.6:
> >
> > http://industrial-linux.org/distro/download/lilo-21.6-glibc-2.2-reiserfs.patch
> >
> > Perhaps someone familiar with the lilo and reiserfs code could explain
> > whether or not this patch is really needed.
> >
> > Miles
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to [email protected]
> > Please read the FAQ at http://www.tux.org/lkml/

2001-02-03 11:27:54

by newsreader

[permalink] [raw]
Subject: Re: did 2.4 messed up lilo?

Just to let everyone knows that 21.6 also
fix the problem on ibm box. I can now
mount cdr drive. Thank you.

On Sat, Feb 03, 2001 at 12:14:09AM -0500, [email protected] wrote:
>
> I've now installed 21.6 downloaded from metlab
> and all seems to be ok now... well at
> least the dell box.. compaq boot sector may
> have been blown off for some reason..it won't
> boot at all athough this time it's a different
> way of being stuck like LI instead of LILO.
> I will try ibm box in the morning when the traffic
> is light.
>
>
> On Fri, Feb 02, 2001 at 05:58:21PM -0800, Miles Lane wrote:
> > Hmm. I just downloaded the lilo 21.6 source and the patch appears to
> > have
> > already been applied. I got 21.6 from:
> >
> > http://ftp.cnr.it/Linux/system/boot/lilo/lilo-21.6.1.tar.gz
> >
> > Miles Lane wrote:
> > >
> > > Chris Mason wrote:
> > > >
> > > > On Friday, February 02, 2001 03:36:18 PM -0500 [email protected]
> > > > wrote:
> > > >
> > > > > I'm not sure whether this problem is related
> > > > > to 2.4 kernel.
> > > > >
> > > >
> > > > I suspect it is a reiserfs problem, and that you are using lilo older than
> > > > 21.6. Are you mounting /boot with -o notail?
> > > >
> > > > Regardless, I'm willing to bet upgrading to lilo 21.6 will solve this. It
> > > > calls an ioctl reiserfs provides to unpack small files, and I've seen it
> > > > fix this exact problem on one of my devel boxes (no lilo prompt, append
> > > > lines in lilo.conf ignored).
> > >
> > > I also found this patch for lilo 21.6:
> > >
> > > http://industrial-linux.org/distro/download/lilo-21.6-glibc-2.2-reiserfs.patch
> > >
> > > Perhaps someone familiar with the lilo and reiserfs code could explain
> > > whether or not this patch is really needed.
> > >
> > > Miles
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > > the body of a message to [email protected]
> > > Please read the FAQ at http://www.tux.org/lkml/