[NTLUG:Discuss] configuring lilo

[Bug Hunter]

  OK.  First, run mkbootdisk to generate a boot disk in case everything
craters.  Even if you can't boot from your hard drive, it should let you
boot from the floppy.

  I'll give you some possible, but improbable scenarios, then give you my
best guess as to how you can make it work with the least effort:

improbable #1:
   do an fdisk /dev/hd*    where * is a,b,c, depending upon your hard
disk.  (look in /etc/fstab)

  see if you have a /boot partition (you probably don't).

  The goal here is to get the linux kernel file *located* at a spot below
cylinder 1024.  If you have a partition that is 1 and is below the 1024
cylinder count, then you are good to go.  If it is perhaps the swap
partition, you can run "swapoff" and turn off swap, then change the file
type to linux, run mke2fs on it, mount it under /bootx, and put your
kernel on it, then run lilo, pointing to the kernel in that directory.
 
improbable #2
  
  the old kernel is located below cylinder 1024.  If you find that the new
kernel and the old kernel are the exact same size, you can copy the new
kernel over the old kernel using the same file name, then rename it.  then
rerun lilo.  If you do this, you will possibly have the kernel located
below cylinder 1024, and you can boot with the new kernel.

possible #1

  locate grub (from google: http://www.gnu.org/software/grub/)
and install it. It can handle cylinders > 1024.

absolutely certain #1 (will work, takes time)

  save your data somewhere.  rerun linux install from cd's.  manually
partition and create a 20 megabyte partition #1, make it linux fs, mount
it under the directory /boot.  All new kernels go into this directory, and
are guaranteed to be under cylinder 1024.  Your upgrade will then work.

bug
  

On Mon, 24 Dec 2001 falconjetflyer at netscape.net wrote:

> I recently compiled a new kernel 2.4.16.
> I amended the lilo.conf file and attemped to run lilo.
> I got the message: Warning: device 0x0306 exceeds 1024 
> cylinder limit.  geo_comp_addr: cylinder number is too 
> big (2751>1023)
> I think it means that linux is limited to 1024 cyl but I
> know it has been updated and this same lilo was booting 
> a system on this same HD.  I don't under stand why it has
> decided to reject this new conf.
> Can you tell me how to fix it?   My lilo ver. is 21
> I am presently running caldera 2.4 with kernel 2.2.14. and 
> I want to run 2.4.16.    Do I really have to note the 
> HD geometry now.   Why didn't I have to before?
> Will that fix it.
> garion
>