Very Computer

tia
Jeroen Heijungs

The problem here is that Linux has been booted in a partition above the
1024th cylinders.
Linux does not boot when totally installed above the 1024th cylinder.
That's why you have to type this command in LILO to get it up and running.

All I could tell you is to load the /boot directory in a partition that is
below 1024, and the rest of Linux stays where it is.
This is a trick I have read from the HOWTOS, i'll advise you to go and
have a look at them on the sunsite.unc.edu/mdw/~howtos site for more
explanation.

Good luck,
Florence
?

LILO comes with excellent documentation, and for the purposes of boot
args discussed here, the LILO
append= command is of significant importance when one wants to add a boot
time argument as a permanent
addition to the LILO config file. You simply add something like append =
"vga=ask" to the /etc/lilo.conf file.
It can either be added at the top of the config file, making it apply to
all sections, or to a single system
section by adding it inside an image= section. Please see the LILO
documentation for a more complete
description.

LILO comes with excellent documentation, and for the purposes of boot
args discussed here, the LILO
append= command is of significant importance when one wants to add a boot
time argument as a permanent
addition to the LILO config file. You simply add something like append =
"vga=ask" to the /etc/lilo.conf file.
It can either be added at the top of the config file, making it apply to
all sections, or to a single system
section by adding it inside an image= section. Please see the LILO
documentation for a more complete
description.

And from the same HOWTO the section on hard drive parameters:

The IDE driver accepts a number of parameters, which range from disk
geometry specifications, to support
for advanced or broken controller chips. The following is a summary of
all the possible boot arguments. For
full details, you really should consult the file ide.txt in the
linux/Documentation directory.

 "hdx="  is recognized for all "x" from "a" to "h", such as "hdc".
 "idex=" is recognized for all "x" from "0" to "3", such as "ide1".

 "hdx=noprobe"          : drive may be present, but do not probe for it
 "hdx=none"             : drive is NOT present, ignore cmos and do not
probe
 "hdx=nowerr"           : ignore the WRERR_STAT bit on this drive
 "hdx=cdrom"            : drive is present, and is a cdrom drive
 "hdx=cyl,head,sect"    : disk drive is present, with specified geometry
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 "hdx=autotune"         : driver will attempt to tune interface speed
                                to the fastest PIO mode supported,

Hope this helps.

Quote:>Jeroen,

>The problem here is that Linux has been booted in a partition above the
>1024th cylinders.

The LILO-related files are: bootimage (often called vmlinuz or zImage),
mapfile, message, and chain loader(s).
Of course, boot.b (also known as LILO) gets written on the first sector
of the bootable drive if you're booting the system with LILO,
or on the first sector of a Linux partition if you're starting LILO
via System Commander or the NT boot menu or something.

I don't what Red Hat 5.2 does.  Edit /etc/lilo.conf and make it
do what *you* want, and never mind what Red Hat wants to do.
Lilo has good manpages now, and the file is not hard to read.

Cameron

If you have Windows 95/98 or dos, you can try the following:

1. Copy the kernel image to one of your fat drives, along with
loadlin.exe.
2. Create a batch file that loads the kernel and mounts the file system.
(You can have a boot menu in config.sys that runs the batch file or
loads windows)

That way you don't need lilo, or other boot managers. You can also have
different versions of the kernel for experimenting with the unstable
kernels. Check loadlin docs for help.