LILO won't boot old OS... typical newbie woe

LILO won't boot old OS... typical newbie woe

Post by Ralph de Rij » Wed, 16 Sep 1998 04:00:00



Dear all,

I installed Red Hat 5.1 to my second IDE HD (1.6GB); I retained
DOS/Win 3.11 on my first HD (also IDE, 850KB in two partitions, LBA-
addressed). This is a 486DX ISA Cyrix, by the way. Both drives are on
one controller (I don't know which one); the CD-ROM's on the other.

The problem is this: LILO, which I installed on the MBR of /dev/hda
(with the Linear option (for LBA-read drives) on), booted Linux
perfectly but returned 07070707070707070 recurring when asked to boot
DOS/Win.

I have since used DOS fdisk /mbr to restore the MBR and DOS/Win loads
again, but I have to use the boot diskette to fire up Linux (it starts
LILO first). But I want LILO to work! It looks like a great applet.

So, what did I do wrong? And can I reinstall LILO properly with having
to reinstall Linux - from X, say? I've read all the HOWTOs and FAQs I
can find but I haven't a clue - I throw myself on your collective
mercy.

Thanks a million you guys!

Ralph de Rijke
Amsterdam

 
 
 

LILO won't boot old OS... typical newbie woe

Post by Neil Kooze » Wed, 16 Sep 1998 04:00:00


Quote:> The problem is this: LILO, which I installed on the MBR of /dev/hda
> (with the Linear option (for LBA-read drives) on), booted Linux
> perfectly but returned 07070707070707070 recurring when asked to boot
> DOS/Win.

07 is very unusual.  It means "invalid initialization" of the controller
(meaning ... well... hmmm... uh...)

The first thing to sustpect is the dos section of your /etc/lilo.conf file.
 See if it looks something like this:

other = /dev/hda1
   label = dos
   table = /dev/hda

Note the difference between hda and hda1.  If there is nothing wrong there,
then my most definitive answer is: well... hmmm... uh... (Anybody else?)

Neil.

 
 
 

LILO won't boot old OS... typical newbie woe

Post by Andy Lyttl » Wed, 16 Sep 1998 04:00:00


Quote:>I installed Red Hat 5.1 to my second IDE HD (1.6GB); I retained
>DOS/Win 3.11 on my first HD (also IDE, 850KB in two partitions, LBA-
>addressed). This is a 486DX ISA Cyrix, by the way. Both drives are on
>one controller (I don't know which one); the CD-ROM's on the other.

>The problem is this: LILO, which I installed on the MBR of /dev/hda
>(with the Linear option (for LBA-read drives) on), booted Linux
>perfectly but returned 07070707070707070 recurring when asked to boot
>DOS/Win.

>I have since used DOS fdisk /mbr to restore the MBR and DOS/Win loads
>again, but I have to use the boot diskette to fire up Linux (it starts
>LILO first). But I want LILO to work! It looks like a great applet.

I had the exact same problem!  It appears that my copy of LILO is corrupt,
although I don't know why that would be.  I installed Slackware 3.5.0 from
downloaded floppies.  I can use the setup program to make a simple boot disk
that loads Linux from one particular partition (/dev/hdb1 in my case), but
every time I try to install LILO it displays an L followed by two repeated
numbers (I don't remember if it was 07 or something else, like maybe 01, but
it would fill the screen and start scrolling).  Under VirtualPC on a Mac, it
displayed the L and just stopped, without displaying the numbers.

I've tried installing LILO on a couple of hard drives and a floppy or two,
and the same thing always happens.

                              - Andy Lyttle

                                http://www.bigfoot.com/~phroggy/

 
 
 

1. Lilo won't load os/2, os/2 won't load lilo

I'm having some problems getting OS/2 Warp, Dos/Windoze, and Linux to
cohabitate on the same machine.

When I set up lilo with another os (being os/2) I can boot from the drive
where the os/2 boot manager is, and it does indeed load an operating system
that isn't linux, but its not os/2 either.  It loads dos.  The drive
structure is such:

1'st IDE drive: WD 540 meg, formatted ext2fs, linux, lilo on MBR
2'nd IDE drive: WD 540 meg, 1'st partiton 1 meg with os/2 boot manager, 2'nd
                partition is DOS/Windoze, formatted FAT
3'rd IDE drive: WD 340 meg, formatted hpfs, os/2 warp, no boot manager
Linux:          Slackware 2.0, patched kernel to 1.1.38 (where the drives
                actualy work for the first time with no BIOS adjustments!)
Other Problem
causing toys:   Mitsumi CDROM, Colorado 250MB tape (I stopped posting about
                that one long ago :(, 2 floppies, Soundblaster 16 compatible
                sound card, SMC Elite combo ethernet card (8013EC or ~)

So LILO seems to skip right over the partition with os/2's boot manager and
loads up DOS.  Despite the fact that i specified in my lilo.conf for the
os/2_db (spelling) loader to use /dev/hdb1, and that dos is on hdb2.

I've tried putting the other 540 meg drive first, and using OS/2's boot
manager to load everything.  But the fdisk setup program for os/2's boot
manager refuses to believe that there is an operting system on the linux
drive, and it won't let me set up a boot manager option to load it.   :(

I've also tried a utility I picked up from a sunsite cd; setboot.  This is
supposed to pick a boot manager to use on reboot from among different drives
and partition.  It can't seem to find ANY boot managers though, not even the
one that LInux is using!  (damn thing)

On a side note I can't get LInux to read my third drive.  I used the
MAKEDEV script to build the device drivers for the third drive (hd1a)
but Linux just gives that annoying useless drive busy, wrong fs type, or
some other error when I try to access it from anything like mount or fdisk.
This seems to hold true whether the third drive is the DOS drive or the HPFS
one.  DOS/WINDOZE/OS/2 can all see this drive fine though....
Perhaps this is a problem with Enhanced IDE controllers on PCI buses?

Well, I'll stop here.  :)  
If I can get all that to work, I'll be a very happy camper for a few days
until I start tinkering with other stuff.  I seem to enjoy setting up
odd things much more than I do using them anyhow.   ;>

-Steve Rojem

2. update seq_file to support single_open()

3. The Problem -- The new lilo won't overwrite the old boot sector.

4. __eprintf error using apache module

5. LILO won't boot OS/2

6. quot, or other disk accounting

7. *** lilo won't boot win' 95 ***

8. create an account for Sendmail

9. Newbie: CONFIGURE'd boot floppy - won't boot

10. *NEW* boot disk won't, *OLD* boot disk will!

11. old laptop won't boot boot.img

12. LILO fails to boot old OS... advice please!

13. using boot floppy to boot multi OS's (no LILO)