Linear and LBA32 are mutually exclusive; you'll need
to take the Linear out of your /etc/lilo.conf file.
That will get rid of the error that you are seeing, and
should fix everything right up. Luckily, systems that
require linear don't require LBA32, and vice versa.
You can (although I don't recommend it) remove BOTH
Linear and LBA32 from /etc/lilo.conf, and simply run
lilo as
/sbin/lilo -L -v
which would also work, as you can specify any of the switches
to Lilo through the commandline when run; the problem is
that you then have to always remember them, every time you
upgrade your kernal or do anything that would require you
to need to rerun lilo (which includes the near constant
refresh of Win98 (i.e., Reinstalling it)). That's why I
recommend that you put it in /etc/lilo.conf, but Linux is
Unix, and Unix is about choices on how to do things...
Bill Ward
-----Original Message-----
From: K Old [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 07, 2001 7:29 PM
To: [EMAIL PROTECTED]
Subject: [With More Info] RE: Reinstall LILO manually?
Ok, I have done some investigating.
The original response I got from doing a /sbin/lilo -v is
LILO version 21.4-4, Copyright (C) 1992-1998 Werner Almesberger
'lba32' extensions Copyright (C) 1999,2000 John Coffman
Reading boot sector from /dev/hda
Merging with /boot/boot.b
Fatal: 'linear' and 'lba32' (-l and -L) are mutually exclusive.
My lilo.conf file looked like this:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=linux
image=/boot/vmlinuz-2.2.16-22
label=linux
read-only
root=/dev/hda5
other=/dev/hda1
label=dos
I modified it (based on the email below) to look like this:
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
lba32
timeout=50
message=/boot/message
linear
default=Linux
image=/boot/vmlinuz-2.2.16-22
label=Linux
initrd=/boot/initrd-2.2.16-22.img
read-only
root=/dev/hda5
image=/dev/hda1
label=Win98
After I do a /sbin/lilo -v it returns the same error message from above.
Any ideas what I should do?
Thanks,
Kevin
[EMAIL PROTECTED]
>From: Ward William E DLDN Reply-To: [EMAIL PROTECTED] To:
>"'[EMAIL PROTECTED]'" Subject: RE: Reinstall LILO manually? Date: Wed,
>7 Mar 2001 16:25:14 -0500
>
>The answer to your question is YES, you can reinstall LILO manually; the
>other part of your question (which you didn't ask) is how to get LILO
>working properly as it currently exists (which is the more important,
>potentially, question!).
>
>Have you tried running adding LBA32 to your /etc/lilo.conf and rerunning
>lilo? If you have a large partition (>8 GB) it won't boot from LILO without
>it. I would suggest that you try to find WHY LILO isn't working... RH7.0
>came with the LBA32 optionable LILO, no upgrade required.
>
>Put it in after prompt and before timeout, e.g.
>
>prompt lba32 timeout=50
>
>You may also need to remove the word linear. As in all changes to system
>files MAKE A COPY FIRST!
>
>Then run lilo:
>
>/sbin/lilo -v
>
>and you should be fixed. You should also double check (first!) that you
>have specified the Win98 partition. This may look like this, although you
>should correct it for your system:
>
>image=/dev/hda label=Win98
>
>Which needs to be added to the /etc/lilo.conf. So, in total, you need a
>lilo.conf something like this, minimum:
>
>boot=/dev/hda map=/boot/map install=/boot/boot.b prompt lba32 timeout=50
>default=Linux image=/boot/vmlinuz-2.2.16-22 label=Linux
>initrd=/boot/initrd-2.2.16-22.img read-only root=/dev/hda2 image=/dev/hda1
>label=Win98
>
>Then run /sbin/lilo -v and that should do it, I think (though I'm sure that
>someone will correct me if I've made a mistake; I'm doing this off the top
>of my head, and haven't had to do this in 5 months, so I could use a jog in
>the elbow if I've messed something up!)
>
>Bill Ward -----Original Message----- From: K Old
>[mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 07, 2001 3:51 PM To:
>[EMAIL PROTECTED] Subject: Reinstall LILO manually?
>
>
>Hello all,
>
>I was wondering if I could reinstall LILO manually without having to go
>through the reinstall process for RH 7.0. For some reason LILO did not take
>
>control of my MBR and the only way I can get into RH7 is to boot from a
>floppy. I almost lost the floppy the other day, but was lucky and found it.
>
>So to keep from being dependent upon a floppy I've decided to get to the
>bottom of this problem. I have edited the lilo.conf file and tried to test
>it by starting lilo, but I get an error message....something to do with
>memory...if I need the specific error message I can provide it. Should I
>use another boot loader? If so, are they easy to configure. I basically
>want the option to be able to boot into either Win98 or RH.
>
>Thanks, Kevin [EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
