Yet another LILO boot problem with LI on screen

Yet another LILO boot problem with LI on screen

Post by Tim William » Sun, 31 Dec 1899 09:00:00



I have a problem, could anyone help me?

This is a fresh install of Redhat 6.1.  I presume that since it's displaying
LI that lilo has been run.  That leaves drive geometry, right?  I can't boot
the OS I just installed but I am able to boot using a rescue floppy I got
from the internet.  It is based on the 1.3.84.  Using this, I can boot and
get at the install I just made, but I think I'm still using the rescue
kernel.  I have tried to make another boot floppy using the Redhat 6.1
kernel, but I can't get it to work.

After booting with the rescue floppy and telling it to use the hard drive,
the kernel reports itself as 1.3.84, so even though it's trying to boot from
the harddrive, I'm somehow still using the rescue kernel.

What I want to accomplish either to fix the LILO on my harddrive, or to get
the one on the floppy to get the correct kernel.  I believe that the kernel
that's on the hard drive is 2.2.12-20

Here is a bunch of info about my setup.

Drives:
Harddrive: Master on first IDE
8455 Mb
cylinders                         16383
Heads                             16
Sectors/Track                 63
Multi-Sector transfers    16 Sectors
LBA mode control          Enabled
32 Bit I/O                         Enabled (I can change this to Disabled)
Transfer mode                Fast PIO

CD is Master on second IDE, it is bootable and is where I installed Linux
from.

Also, general hard drive setting is
Translation method        Extended (I can change this to Standard)(I don't
really know what this does)

Partition information
    Device    Boot       Start         End             Blocks        Id
System
/dev/hda1    *                 64         33264         16600+     83
Linux                                (mounted as /boot)
/dev/hda2                33265  16992864     8479800         5    Extended
( I have no clue what this is)
/dev/hda5                33328  16860816     8413744+    83     Linux
(mounted as /)
/dev/hda6         16860880  16992864         65992+     82     Linux swap
(should be my swap space)

lilo.conf I used on the rescue disk

boot = /dev/fd0
prompt
message=/boot/txt
vga = normal

image = /boot/vmlinuz
    root = /dev/hda5
    label = l
    read-only

image = /boot/vmlinuz
    root = /dev/fd0
    label = r
    append="load_ramdisk=1 prompt_ramdisk=0 ramdisk_start=450"
     read-only

 
 
 

Yet another LILO boot problem with LI on screen

Post by Tim William » Sun, 31 Dec 1899 09:00:00


Forgot one thing.  Added info about disk geometry reported by fdisk below:


Quote:> I have a problem, could anyone help me?

> This is a fresh install of Redhat 6.1.  I presume that since it's
displaying
> LI that lilo has been run.  That leaves drive geometry, right?  I can't
boot
> the OS I just installed but I am able to boot using a rescue floppy I got
> from the internet.  It is based on the 1.3.84.  Using this, I can boot and
> get at the install I just made, but I think I'm still using the rescue
> kernel.  I have tried to make another boot floppy using the Redhat 6.1
> kernel, but I can't get it to work.

> After booting with the rescue floppy and telling it to use the hard drive,
> the kernel reports itself as 1.3.84, so even though it's trying to boot
from
> the harddrive, I'm somehow still using the rescue kernel.

> What I want to accomplish either to fix the LILO on my harddrive, or to
get
> the one on the floppy to get the correct kernel.  I believe that the
kernel
> that's on the hard drive is 2.2.12-20

> Here is a bunch of info about my setup.

> Drives:
> Harddrive: Master on first IDE
> 8455 Mb
> cylinders                         16383
> Heads                             16
> Sectors/Track                 63
> Multi-Sector transfers    16 Sectors
> LBA mode control          Enabled
> 32 Bit I/O                         Enabled (I can change this to Disabled)
> Transfer mode                Fast PIO

> CD is Master on second IDE, it is bootable and is where I installed Linux
> from.

> Also, general hard drive setting is
> Translation method        Extended (I can change this to Standard)(I don't
> really know what this does)

Partion info reported from running:
fdisk -u -l /dev/hda

You must set heads.
You can do this from the extra functions menu.

Disk /dev/hda: 0 heads, 63 sectors, 1023 cylinders
Units = sectors of 1 * 512 bytes

    Device    Boot       Start         End             Blocks        Id
System
/dev/hda1    *                 64         33264         16600+     83
Linux            (mounted as /boot)
/dev/hda2                33265  16992864     8479800         5    Extended
( I have no clue what this is)
/dev/hda5                33328  16860816     8413744+    83     Linux
(mounted as /)
/dev/hda6         16860880  16992864         65992+     82     Linux swap
(should be my swap space)

- Show quoted text -

Quote:

> lilo.conf I used on the rescue disk

> boot = /dev/fd0
> prompt
> message=/boot/txt
> vga = normal

> image = /boot/vmlinuz
>     root = /dev/hda5
>     label = l
>     read-only

> image = /boot/vmlinuz
>     root = /dev/fd0
>     label = r
>     append="load_ramdisk=1 prompt_ramdisk=0 ramdisk_start=450"
>      read-only


 
 
 

Yet another LILO boot problem with LI on screen

Post by root » Sun, 31 Dec 1899 09:00:00


According to  a comprehensive review of LILO

LI means that the first stage boot loader was able to load the
second stage boot loader, but has failed to execute it.
This can either be caused by a geometry mismatch or by moving
/boot/boot.b without running the map installer.
I got this document via web search.

> I have a problem, could anyone help me?

> This is a fresh install of Redhat 6.1.  I presume that since it's displaying
> LI that lilo has been run.  That leaves drive geometry, right?  I can't boot
> the OS I just installed but I am able to boot using a rescue floppy I got
> from the internet.  It is based on the 1.3.84.  Using this, I can boot and
> get at the install I just made, but I think I'm still using the rescue
> kernel.  I have tried to make another boot floppy using the Redhat 6.1
> kernel, but I can't get it to work.

> After booting with the rescue floppy and telling it to use the hard drive,
> the kernel reports itself as 1.3.84, so even though it's trying to boot from
> the harddrive, I'm somehow still using the rescue kernel.

> What I want to accomplish either to fix the LILO on my harddrive, or to get
> the one on the floppy to get the correct kernel.  I believe that the kernel
> that's on the hard drive is 2.2.12-20

> Here is a bunch of info about my setup.

> Drives:
> Harddrive: Master on first IDE
> 8455 Mb
> cylinders                         16383
> Heads                             16
> Sectors/Track                 63
> Multi-Sector transfers    16 Sectors
> LBA mode control          Enabled
> 32 Bit I/O                         Enabled (I can change this to Disabled)
> Transfer mode                Fast PIO

> CD is Master on second IDE, it is bootable and is where I installed Linux
> from.

> Also, general hard drive setting is
> Translation method        Extended (I can change this to Standard)(I don't
> really know what this does)

> Partition information
>     Device    Boot       Start         End             Blocks        Id
> System
> /dev/hda1    *                 64         33264         16600+     83
> Linux                                (mounted as /boot)
> /dev/hda2                33265  16992864     8479800         5    Extended
> ( I have no clue what this is)
> /dev/hda5                33328  16860816     8413744+    83     Linux
> (mounted as /)
> /dev/hda6         16860880  16992864         65992+     82     Linux swap
> (should be my swap space)

> lilo.conf I used on the rescue disk

> boot = /dev/fd0
> prompt
> message=/boot/txt
> vga = normal

> image = /boot/vmlinuz
>     root = /dev/hda5
>     label = l
>     read-only

> image = /boot/vmlinuz
>     root = /dev/fd0
>     label = r
>     append="load_ramdisk=1 prompt_ramdisk=0 ramdisk_start=450"
>      read-only

 
 
 

Yet another LILO boot problem with LI on screen

Post by Armand Wels » Sun, 31 Dec 1899 09:00:00


What does your lilo.conf on your hard drive look like?  Also, are you using
linear mode?  you might need to do this.


> Forgot one thing.  Added info about disk geometry reported by fdisk below:



> > I have a problem, could anyone help me?

> > This is a fresh install of Redhat 6.1.  I presume that since it's
> displaying
> > LI that lilo has been run.  That leaves drive geometry, right?  I can't
> boot
> > the OS I just installed but I am able to boot using a rescue floppy I
got
> > from the internet.  It is based on the 1.3.84.  Using this, I can boot
and
> > get at the install I just made, but I think I'm still using the rescue
> > kernel.  I have tried to make another boot floppy using the Redhat 6.1
> > kernel, but I can't get it to work.

> > After booting with the rescue floppy and telling it to use the hard
drive,
> > the kernel reports itself as 1.3.84, so even though it's trying to boot
> from
> > the harddrive, I'm somehow still using the rescue kernel.

> > What I want to accomplish either to fix the LILO on my harddrive, or to
> get
> > the one on the floppy to get the correct kernel.  I believe that the
> kernel
> > that's on the hard drive is 2.2.12-20

> > Here is a bunch of info about my setup.

> > Drives:
> > Harddrive: Master on first IDE
> > 8455 Mb
> > cylinders                         16383
> > Heads                             16
> > Sectors/Track                 63
> > Multi-Sector transfers    16 Sectors
> > LBA mode control          Enabled
> > 32 Bit I/O                         Enabled (I can change this to
Disabled)
> > Transfer mode                Fast PIO

> > CD is Master on second IDE, it is bootable and is where I installed
Linux
> > from.

> > Also, general hard drive setting is
> > Translation method        Extended (I can change this to Standard)(I
don't
> > really know what this does)

> Partion info reported from running:
> fdisk -u -l /dev/hda

> You must set heads.
> You can do this from the extra functions menu.

> Disk /dev/hda: 0 heads, 63 sectors, 1023 cylinders
> Units = sectors of 1 * 512 bytes

>     Device    Boot       Start         End             Blocks        Id
> System
> /dev/hda1    *                 64         33264         16600+     83
> Linux            (mounted as /boot)
> /dev/hda2                33265  16992864     8479800         5    Extended
> ( I have no clue what this is)
> /dev/hda5                33328  16860816     8413744+    83     Linux
> (mounted as /)
> /dev/hda6         16860880  16992864         65992+     82     Linux swap
> (should be my swap space)

> > lilo.conf I used on the rescue disk

> > boot = /dev/fd0
> > prompt
> > message=/boot/txt
> > vga = normal

> > image = /boot/vmlinuz
> >     root = /dev/hda5
> >     label = l
> >     read-only

> > image = /boot/vmlinuz
> >     root = /dev/fd0
> >     label = r
> >     append="load_ramdisk=1 prompt_ramdisk=0 ramdisk_start=450"
> >      read-only

 
 
 

Yet another LILO boot problem with LI on screen

Post by Tim William » Sun, 31 Dec 1899 09:00:00


Yes, I knew this.  Since I've never moved boot.b, I don't think it's that.
It seems likely to be a geometry mismatch.  However, I don't know what to do
about it.


> According to  a comprehensive review of LILO

> LI means that the first stage boot loader was able to load the
> second stage boot loader, but has failed to execute it.
> This can either be caused by a geometry mismatch or by moving
> /boot/boot.b without running the map installer.
> I got this document via web search.


> > I have a problem, could anyone help me?

> > This is a fresh install of Redhat 6.1.  I presume that since it's
displaying
> > LI that lilo has been run.  That leaves drive geometry, right?  I can't
boot
> > the OS I just installed but I am able to boot using a rescue floppy I
got
> > from the internet.  It is based on the 1.3.84.  Using this, I can boot
and
> > get at the install I just made, but I think I'm still using the rescue
> > kernel.  I have tried to make another boot floppy using the Redhat 6.1
> > kernel, but I can't get it to work.

> > After booting with the rescue floppy and telling it to use the hard
drive,
> > the kernel reports itself as 1.3.84, so even though it's trying to boot
from
> > the harddrive, I'm somehow still using the rescue kernel.

> > What I want to accomplish either to fix the LILO on my harddrive, or to
get
> > the one on the floppy to get the correct kernel.  I believe that the
kernel
> > that's on the hard drive is 2.2.12-20

> > Here is a bunch of info about my setup.

> > Drives:
> > Harddrive: Master on first IDE
> > 8455 Mb
> > cylinders                         16383
> > Heads                             16
> > Sectors/Track                 63
> > Multi-Sector transfers    16 Sectors
> > LBA mode control          Enabled
> > 32 Bit I/O                         Enabled (I can change this to
Disabled)
> > Transfer mode                Fast PIO

> > CD is Master on second IDE, it is bootable and is where I installed
Linux
> > from.

> > Also, general hard drive setting is
> > Translation method        Extended (I can change this to Standard)(I
don't
> > really know what this does)

> > Partition information
> >     Device    Boot       Start         End             Blocks        Id
> > System
> > /dev/hda1    *                 64         33264         16600+     83
> > Linux                                (mounted as /boot)
> > /dev/hda2                33265  16992864     8479800         5
Extended
> > ( I have no clue what this is)
> > /dev/hda5                33328  16860816     8413744+    83     Linux
> > (mounted as /)
> > /dev/hda6         16860880  16992864         65992+     82     Linux
swap
> > (should be my swap space)

> > lilo.conf I used on the rescue disk

> > boot = /dev/fd0
> > prompt
> > message=/boot/txt
> > vga = normal

> > image = /boot/vmlinuz
> >     root = /dev/hda5
> >     label = l
> >     read-only

> > image = /boot/vmlinuz
> >     root = /dev/fd0
> >     label = r
> >     append="load_ramdisk=1 prompt_ramdisk=0 ramdisk_start=450"
> >      read-only

 
 
 

Yet another LILO boot problem with LI on screen

Post by Tim William » Sun, 31 Dec 1899 09:00:00


From /etc/lilo.conf on hda5
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
default=linux

image=/goot/vmlinuz-2.2.12-20
    label=linux
    initrd=/boot/initrd-2.2.12-20.img
    read-only
    root=/dev/hda5

So, I'm not using linear mode.

Attempts to use use lilo on that file result in an error:


Device 0x0301: Got bad geometry 63/0/1023

The same thing happens if I add a line that says "linear" before the
"prompt" line.

I've also tried to use the extended menu of fdisk to set the number of heads
to 16.  The write claims to succeed, but I get

Calling ioctl() to re-read partition tab le.
Syncing disks.
Re-read table failed with error 16: Device or resource busy.
Reboot your system to ensure the partition table is updated.

After reboot, fdisk still reports 0 heads and wants me to set the number of
heads.


> What does your lilo.conf on your hard drive look like?  Also, are you
using
> linear mode?  you might need to do this.



> > Forgot one thing.  Added info about disk geometry reported by fdisk
below:



> > > I have a problem, could anyone help me?

> > > This is a fresh install of Redhat 6.1.  I presume that since it's
> > displaying
> > > LI that lilo has been run.  That leaves drive geometry, right?  I
can't
> > boot
> > > the OS I just installed but I am able to boot using a rescue floppy I
> got
> > > from the internet.  It is based on the 1.3.84.  Using this, I can boot
> and
> > > get at the install I just made, but I think I'm still using the rescue
> > > kernel.  I have tried to make another boot floppy using the Redhat 6.1
> > > kernel, but I can't get it to work.

> > > After booting with the rescue floppy and telling it to use the hard
> drive,
> > > the kernel reports itself as 1.3.84, so even though it's trying to
boot
> > from
> > > the harddrive, I'm somehow still using the rescue kernel.

> > > What I want to accomplish either to fix the LILO on my harddrive, or
to
> > get
> > > the one on the floppy to get the correct kernel.  I believe that the
> > kernel
> > > that's on the hard drive is 2.2.12-20

> > > Here is a bunch of info about my setup.

> > > Drives:
> > > Harddrive: Master on first IDE
> > > 8455 Mb
> > > cylinders                         16383
> > > Heads                             16
> > > Sectors/Track                 63
> > > Multi-Sector transfers    16 Sectors
> > > LBA mode control          Enabled
> > > 32 Bit I/O                         Enabled (I can change this to
> Disabled)
> > > Transfer mode                Fast PIO

> > > CD is Master on second IDE, it is bootable and is where I installed
> Linux
> > > from.

> > > Also, general hard drive setting is
> > > Translation method        Extended (I can change this to Standard)(I
> don't
> > > really know what this does)

> > Partion info reported from running:
> > fdisk -u -l /dev/hda

> > You must set heads.
> > You can do this from the extra functions menu.

> > Disk /dev/hda: 0 heads, 63 sectors, 1023 cylinders
> > Units = sectors of 1 * 512 bytes

> >     Device    Boot       Start         End             Blocks        Id
> > System
> > /dev/hda1    *                 64         33264         16600+     83
> > Linux            (mounted as /boot)
> > /dev/hda2                33265  16992864     8479800         5
Extended
> > ( I have no clue what this is)
> > /dev/hda5                33328  16860816     8413744+    83     Linux
> > (mounted as /)
> > /dev/hda6         16860880  16992864         65992+     82     Linux
swap
> > (should be my swap space)

> > > lilo.conf I used on the rescue disk

> > > boot = /dev/fd0
> > > prompt
> > > message=/boot/txt
> > > vga = normal

> > > image = /boot/vmlinuz
> > >     root = /dev/hda5
> > >     label = l
> > >     read-only

> > > image = /boot/vmlinuz
> > >     root = /dev/fd0
> > >     label = r
> > >     append="load_ramdisk=1 prompt_ramdisk=0 ramdisk_start=450"
> > >      read-only

 
 
 

Yet another LILO boot problem with LI on screen

Post by Tim William » Sun, 31 Dec 1899 09:00:00


I meant boot, not goot.  I was typing this, not cut/paste.

> From /etc/lilo.conf on hda5
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> default=linux

> image=/goot/vmlinuz-2.2.12-20
>     label=linux
>     initrd=/boot/initrd-2.2.12-20.img
>     read-only
>     root=/dev/hda5

> So, I'm not using linear mode.

> Attempts to use use lilo on that file result in an error:


> Device 0x0301: Got bad geometry 63/0/1023

> The same thing happens if I add a line that says "linear" before the
> "prompt" line.

> I've also tried to use the extended menu of fdisk to set the number of
heads
> to 16.  The write claims to succeed, but I get

> Calling ioctl() to re-read partition tab le.
> Syncing disks.
> Re-read table failed with error 16: Device or resource busy.
> Reboot your system to ensure the partition table is updated.

> After reboot, fdisk still reports 0 heads and wants me to set the number
of
> heads.



> > What does your lilo.conf on your hard drive look like?  Also, are you
> using
> > linear mode?  you might need to do this.



> > > Forgot one thing.  Added info about disk geometry reported by fdisk
> below:



> > > > I have a problem, could anyone help me?

> > > > This is a fresh install of Redhat 6.1.  I presume that since it's
> > > displaying
> > > > LI that lilo has been run.  That leaves drive geometry, right?  I
> can't
> > > boot
> > > > the OS I just installed but I am able to boot using a rescue floppy
I
> > got
> > > > from the internet.  It is based on the 1.3.84.  Using this, I can
boot
> > and
> > > > get at the install I just made, but I think I'm still using the
rescue
> > > > kernel.  I have tried to make another boot floppy using the Redhat
6.1
> > > > kernel, but I can't get it to work.

> > > > After booting with the rescue floppy and telling it to use the hard
> > drive,
> > > > the kernel reports itself as 1.3.84, so even though it's trying to
> boot
> > > from
> > > > the harddrive, I'm somehow still using the rescue kernel.

> > > > What I want to accomplish either to fix the LILO on my harddrive, or
> to
> > > get
> > > > the one on the floppy to get the correct kernel.  I believe that the
> > > kernel
> > > > that's on the hard drive is 2.2.12-20

> > > > Here is a bunch of info about my setup.

> > > > Drives:
> > > > Harddrive: Master on first IDE
> > > > 8455 Mb
> > > > cylinders                         16383
> > > > Heads                             16
> > > > Sectors/Track                 63
> > > > Multi-Sector transfers    16 Sectors
> > > > LBA mode control          Enabled
> > > > 32 Bit I/O                         Enabled (I can change this to
> > Disabled)
> > > > Transfer mode                Fast PIO

> > > > CD is Master on second IDE, it is bootable and is where I installed
> > Linux
> > > > from.

> > > > Also, general hard drive setting is
> > > > Translation method        Extended (I can change this to Standard)(I
> > don't
> > > > really know what this does)

> > > Partion info reported from running:
> > > fdisk -u -l /dev/hda

> > > You must set heads.
> > > You can do this from the extra functions menu.

> > > Disk /dev/hda: 0 heads, 63 sectors, 1023 cylinders
> > > Units = sectors of 1 * 512 bytes

> > >     Device    Boot       Start         End             Blocks
Id
> > > System
> > > /dev/hda1    *                 64         33264         16600+     83
> > > Linux            (mounted as /boot)
> > > /dev/hda2                33265  16992864     8479800         5
> Extended
> > > ( I have no clue what this is)
> > > /dev/hda5                33328  16860816     8413744+    83     Linux
> > > (mounted as /)
> > > /dev/hda6         16860880  16992864         65992+     82     Linux
> swap
> > > (should be my swap space)

> > > > lilo.conf I used on the rescue disk

> > > > boot = /dev/fd0
> > > > prompt
> > > > message=/boot/txt
> > > > vga = normal

> > > > image = /boot/vmlinuz
> > > >     root = /dev/hda5
> > > >     label = l
> > > >     read-only

> > > > image = /boot/vmlinuz
> > > >     root = /dev/fd0
> > > >     label = r
> > > >     append="load_ramdisk=1 prompt_ramdisk=0 ramdisk_start=450"
> > > >      read-only

 
 
 

Yet another LILO boot problem with LI on screen

Post by MANSOOR DING » Sun, 31 Dec 1899 09:00:00


First check to see if your non-DOS partition is active. If not make it
active and if its already active than do this:

I had the same problem. I was trying to install Linux and win95 in dual
boot. This is what I did.
!) Define your hard drive in LBA mode in CMOS setup.
2) Define the primary partitions for windows95 as big as you want but not
the whole hard drive. You can select FAT32 or FAT16 file system for windows.
I selected FAT32.
3) Make the primary partition as active using FDISK (DOS/WINDOWS95).
4)Install windows 95 on your primary partition.
5)Install Linux on the non-DOS partition. During the installation makesure
LILO should go in MBR and LINUX is your active boot partition.
Good Luck!


Quote:> I have a problem, could anyone help me?

> This is a fresh install of Redhat 6.1.  I presume that since it's
displaying
> LI that lilo has been run.  That leaves drive geometry, right?  I can't
boot
> the OS I just installed but I am able to boot using a rescue floppy I got
> from the internet.  It is based on the 1.3.84.  Using this, I can boot and
> get at the install I just made, but I think I'm still using the rescue
> kernel.  I have tried to make another boot floppy using the Redhat 6.1
> kernel, but I can't get it to work.

> After booting with the rescue floppy and telling it to use the hard drive,
> the kernel reports itself as 1.3.84, so even though it's trying to boot
from
> the harddrive, I'm somehow still using the rescue kernel.

> What I want to accomplish either to fix the LILO on my harddrive, or to
get
> the one on the floppy to get the correct kernel.  I believe that the
kernel
> that's on the hard drive is 2.2.12-20

> Here is a bunch of info about my setup.

> Drives:
> Harddrive: Master on first IDE
> 8455 Mb
> cylinders                         16383
> Heads                             16
> Sectors/Track                 63
> Multi-Sector transfers    16 Sectors
> LBA mode control          Enabled
> 32 Bit I/O                         Enabled (I can change this to Disabled)
> Transfer mode                Fast PIO

> CD is Master on second IDE, it is bootable and is where I installed Linux
> from.

> Also, general hard drive setting is
> Translation method        Extended (I can change this to Standard)(I don't
> really know what this does)

> Partition information
>     Device    Boot       Start         End             Blocks        Id
> System
> /dev/hda1    *                 64         33264         16600+     83
> Linux                                (mounted as /boot)
> /dev/hda2                33265  16992864     8479800         5    Extended
> ( I have no clue what this is)
> /dev/hda5                33328  16860816     8413744+    83     Linux
> (mounted as /)
> /dev/hda6         16860880  16992864         65992+     82     Linux swap
> (should be my swap space)

> lilo.conf I used on the rescue disk

> boot = /dev/fd0
> prompt
> message=/boot/txt
> vga = normal

> image = /boot/vmlinuz
>     root = /dev/hda5
>     label = l
>     read-only

> image = /boot/vmlinuz
>     root = /dev/fd0
>     label = r
>     append="load_ramdisk=1 prompt_ramdisk=0 ramdisk_start=450"
>      read-only

 
 
 

Yet another LILO boot problem with LI on screen

Post by Tim William » Sun, 31 Dec 1899 09:00:00


Yee Haw!

OK, in order I:
1) changed the BIOS settings to disable 32 bit IO on the hard drive
2) changed the BIOS settings to set translation method to standard
3) Used the floppy to boot again
4) use fdisk to set heads.  Rebooted.
5) Yippee!  This time the number of heads stuck after a reboot
6) ran lilo with the -l flag.  It complained that /boot was read only, so
couldn't creat map~
7) copied /boot/map to /tmp/map
8) ran lilo -C /etc/lilo.conf -l -m /tmp/map
9) rebooted
10) LILO ran from the hard drive!!!!

Thanks for the posts in this newsgroup.  Without the responses to my
question, and even better the responses to other peoples questions, I
wouldn't have been able to fix this.

 
 
 

Yet another LILO boot problem with LI on screen

Post by Armand Wels » Sun, 31 Dec 1899 09:00:00


Quote:> image=/goot/vmlinuz-2.2.12-20
>     label=linux
>     initrd=/boot/initrd-2.2.12-20.img
>     read-only
>     root=/dev/hda5

does it really read image=/goot/vmlinuz-2.2.12-20 or
image=/boot/vmlinuz-2.2.12-20?

if this is all correct, what happens if you "/sbin/lilo" to re-install the
lilo config?

 
 
 

Yet another LILO boot problem with LI on screen

Post by Armand Wels » Sun, 31 Dec 1899 09:00:00


sounds like linear addressing mode would have fixed your problem.  if you
had the drive configured in BIOS to use LBA then linear should have made the
head/cyl/sec issue a irrelavent.

armand


Quote:> Yee Haw!

> OK, in order I:
> 1) changed the BIOS settings to disable 32 bit IO on the hard drive
> 2) changed the BIOS settings to set translation method to standard
> 3) Used the floppy to boot again
> 4) use fdisk to set heads.  Rebooted.
> 5) Yippee!  This time the number of heads stuck after a reboot
> 6) ran lilo with the -l flag.  It complained that /boot was read only, so
> couldn't creat map~
> 7) copied /boot/map to /tmp/map
> 8) ran lilo -C /etc/lilo.conf -l -m /tmp/map
> 9) rebooted
> 10) LILO ran from the hard drive!!!!

> Thanks for the posts in this newsgroup.  Without the responses to my
> question, and even better the responses to other peoples questions, I
> wouldn't have been able to fix this.

 
 
 

Yet another LILO boot problem with LI on screen

Post by Joel Gallu » Sun, 31 Dec 1899 09:00:00



> 6) ran lilo with the -l flag.  It complained that /boot was read only, so
> couldn't creat map~
> 7) copied /boot/map to /tmp/map
> 8) ran lilo -C /etc/lilo.conf -l -m /tmp/map

This will work until the /tmp cleanup job runs from cron and deletes
the map file. As soon as those blocks get reallocated you won't be
able to load the kernel any more.

You need to fix the read-only /boot and rerun lilo.

--
Joel Gallun

http://www.tux.org/~joel

 
 
 

1. Yet another Lilo LI... problem

Hi all,

Thought I knew Linux after five years, but here I am, posting a question
about lilo.

I've just been shifting HD's a bit between machines and I can't get lilo
to work on a 8.6GB Seagate medialist 8420. I get LI on the screen, and
then nothing.
Booting from the bootdisk works, So I've tried rerunning lilo. It
prompts "Added linux" and "Added dos" without trouble, but the system
won't boot.

Here's what fdisk says:
Disk /dev/hda: 255 heads, 63 sectors, 1048 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1       524   4208998+   b  Win95 FAT32
/dev/hda2           525       557    265072+  83  Linux
/dev/hda3           558       753   1574370   83  Linux
/dev/hda4           754      1048   2369587+   5  Extended
/dev/hda5           754       770    136521   82  Linux swap
/dev/hda6           771      1048   2233003+  83  Linux

hda2 is the boot partition, and as you see it's about halfway on the
drive.

As you can see, fdisk reports 1048 cylinders. This is the same as the
Bios reports in LBA mode. However, in NORMAL mode the bios autodetects
16708 cyls, while the HD docs say it has 16383 cyls.
If indeed 1048 cyls is correct, then the boot partition is well within
the 1024 cylinder limit.
I've tried running LILO with and without linear mode, without results.
I've tried enabling/disabling UltraDMA in the bios. I've tried manually
setting PIO modes to 1 and 2 in the bios. All without results.

This is all particularly strange because this setup has worked with no
problems an a different machine with an El Cheapo motherboard and VIA
chipsets, while now I'm running into trouble on an ASUS TXP4 motherboard
with Intel 430TX chips, that, according to the manual, supports drives
larger than 8.4GB

All in all, I'm pretty desperate. Last resort (I'm gonna try now) is
updating the BIOS).

Any suggestions, PLEASE?

Pieter van Beek.

--
KOBAYASHI SOFTWARE                           Gouden Leeuw 836
Phone: +31 20 4165015                        1103KT Amsterdam
PGP Key ID: 0x87339521                        the Netherlands
Fingerprint: 10 B7 E7 6C 2B 5B 93 92  3B 45 0B DD 48 25 04 60

2. rc5des client for solaris x86 ...

3. lilo boot problem: hangs on LI

4. How can I trap the "^z" in sh?

5. Where are there the roll "LI LI ....:" all over the screen?

6. Newbie - How to debug a broken dip ??

7. Sample lilo.conf to solve the LILO stops at LI problem

8. Slooow tar zxvf ...

9. Computer gets stuck at boot up, only "LI" of the LILO prompt shows

10. HD Boot doesn't want to run LILO (I see 'LI')

11. lilo hangs at "LI" while booting from extra HD in Laptop

12. Help!! LILO booting stopping on LI

13. LILO Hangs at boot time: LI then nothing