SLUG Mailing List Archives
Re: [SLUG] Lilo problem
- To: Melinda Taylor <melinda@xxxxxxxxxxxxxxxx>
- Subject: Re: [SLUG] Lilo problem
- From: DaZZa <dazza@xxxxxxxxxx>
- Date: Fri Aug 4 09:23:51 2000
- Cc: slug@xxxxxxxxxxx
On Thu, 3 Aug 2000, Melinda Taylor wrote:
> I have a machine that had an existing 2 gig disk that contains win95. I
> then added a 20 gig disk to it and installed Redhat 6.2 linux on it.
> After the install my machine hung after the bios info ie it seems not to
> be able to locate boot info.
This could be caused by a number of situations.
1) Incorrect jumpering of the second drive - you have both drives on the
single bus claiming to be the "master".
2) Bad cabling.
3) The older drive, being the master, cannot "control" the secondary
drive because it's too old.
You really need to give a slightly better description of the problem - how
are the drives jumpered, are they both on the same cable, are they
jumpered for the correct master/slave arrangement etc etc.
> I am unsure what to do. I know that obviously as the disk which
> contains windows currently has the active partition
> and the reason why nothing is happening is cos it cannot find the linux
> boot image (vmlinuz) but I am unsure how to fix it!
Does your machine still boot to Windows? Or does it not even get that far?
> Can I just run fdisk and set the linux partition / to active
> and then lilo will be able to find the /boot directory and
> load? And if I do this will windows still load?
> Also do I then have to make the large linux drive the master or
> is it ok to leave it as slave.
In most cases like this, the large drive either has to be the master, or
on the second IDE bus as the master. Generally speaking, a 2 gig drive
will only be mode 2, or mode 4 - and your new drive will be at least mode
4 - and a mode 2 or 3 drive can't properly control the mode 4 device.