>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 5/22/00, 9:21:47 AM, <[EMAIL PROTECTED]> wrote regarding Re: LILO
question:
>
> LILO doesn't use the BIOS boot sequence. The BIOS calls LILO.
> The boot sequence in the CMOS, tells the BIOS where to find LILO.
> By the time LILO starts, the boot sequence has already been done.
But when doing a LILO update (or installing LILO) to the MBR I believe
it does indeed look at
[EMAIL PROTECTED] (Benjamin Scott) writes:
> On Wed, 17 May 2000, Randy Edwards wrote:
> > Running LILO now I get an error message about /dev/sda not being the
first
> > drive (I'm not home so I don't have access to the text). Tell me, does
> > LILO read the BIOS to determine the boot sequenc
> Is there a Linux filesystem on the SCSI disk? Set the boot order to "A, C,
> SCSI" and disable the IDE controller. That will make the SCSI drive the first
> (only) BIOS drive, allowing you to boot from floppy and then run LILO.
Whoops, I forgot to update my saga after writing that last mes
On Wed, 17 May 2000, Randy Edwards wrote:
> Running LILO now I get an error message about /dev/sda not being the first
> drive (I'm not home so I don't have access to the text). Tell me, does
> LILO read the BIOS to determine the boot sequence of hard drives?
I don't think it accesses the BIOS
On Thu, May 18, 2000 at 08:54:24AM -0400, Bruce McCulley <[EMAIL PROTECTED]>
wrote:
> In the process I found some references to GRUB which suggested that it was
> becoming the boot loader of choice, at least for Caldera, partly because it
> circumvents that nasty BIOS cylinder number limitation.
I haven't really played with GRUB, but I recently muddled through some boot
problems after I installed Caldera (first mistake) and used COAS to change the
boot details (second mistake). The result was exactly the LILO behavior you
observed, LI then wipeout. I found an explanation that said the L
Well, I've been having a really good time playing with LILO and GRUB and
I've gotten *really* good at smacking ESC because I'm tired of watching the
memory count for the umpteenth time during a reboot. Here's a summary of my
boot adventures:
Box: 3 IDE HDs (hda, hdb, and hdc) and one SCSI
> Have you tried putting the "linear" or "lba32" options in your
> /etc/lilo.conf file?
Yup, my first impulse was to use linear, but also tried lba32. No
luck. Running LILO now I get an error message about /dev/sda not being the
first drive (I'm not home so I don't have access to the text)
Sounds like a job for "linear".
Check the lilo.conf man page for more info.
ccb
--
Charles C. Bennett, Jr. VA Linux Systems
Systems Engineer, 25 Burlington Mall Rd., Suite 300
US Northeast Region Burlington, MA 01803-4145
+1 617 543-65
On Tue, 16 May 2000, Randy Edwards wrote:
> I installed LILO (version 21.4-2) on /dev/sda (a 9GB SCSI drive) and it
> looked like it went fine. /dev/sda1 is a tiny 60-70 MB boot partition at
> the beginning of the drive. However, when I try to boot from it I get the
> "LI" and nothing else.
H
I'm playing "reorganize drives and partitions" in a box and am converting
over from booting off from /dev/hda1 to /dev/sda1. Moving things around
went fine (God what a blessing that is compared to doing something similar
with Windows!), but I'm having problems booting off from the
SCSI partition
12 matches
Mail list logo
