On 02/25/00, at 03:58 PM, [EMAIL PROTECTED] said:
>lilo does not report unspecified errors.
I'm sure it doesn't, so let me be more precise. That portion of the Redhat
installer that installs lilo quit, saying nothing more than "there was an error
installing lilo." or words to that effect. Not at all helpful.
>> Redhat support passed the buck, naturally, since I mentioned OS/2:
>>
>> "The resolution of your problem is:
>> Unfortunately, working with the OS/2 boot manager is not supported."
>Twaddle.
My sentiments exactly.
>Install lilo into the partition boot record (boot =
>/dev/sda8). Your kernel image should already be there; if it isn't, put
>it there. you should also have /boot/boot.b. If lilo was installed,
>there will also be /boot/map and /boot/boot.0808 (a copy of what was on
>the partition boot record before lilo.)
The kernel image was there, as was /boot/boot.b. However, /boot/map and
/boot/boot.0808 were *not* there, indicating that lilo had not been installed.
I ran /sbin/lilo -v, it ended with an error, something about a partition, which
didn't look right at all. I then checked /etc/lilo.conf, and was quite
surprised to find sda1 and sda5 listed there. I did *not* select them for
booting from lilo during the installation, since they will be booted from Boot
Manager, but there they were. So I deleted them from the list, and reran
/sbin/lilo -v, which then finished cleanly. A reboot confirmed it: Problem
solved.
>Oh, yes, this is redhat with a scsi /, so in /boot should also be an
>initrd...
That was all there, but I can't help but wonder if that had something to do
with it. This system is all SCSI, the others I've worked with were all IDE. So
there's a possibility... I hadn't even thought about it until you mentioned it.
Doh!
The only other thing I can think of is that it might have something to do with
the partition table. When doing one of these systems, it is vitally important
to use OS/2 fdisk or Partition Magic under OS/2 to create the partitions. If
you use Linux fdisk, OS/2 may not recognize the partition boundaries, and the
results of that are unpredictable at best, to put it mildly. So obviously there
is some kind of discrepancy there. Whether whatever this is could cause the
Redhat installer to get flaky, who knows? If there's a problem reading it one
way, there could very well be a problem reading it the other way.
--
-----------------------------------------------------------
Carl Brown [EMAIL PROTECTED]
-----------------------------------------------------------
Experience is something you don't get until just after you need it.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
