Well it sounds like LILO is trying to boot from the wrong partition. Or,
perhaps the kernel is loading but the "root" device is wrong. I'm guessing
this is the case since I wouldn't expect very elaborate messages such as you
site below from LILO. When you get to where LILO prints hit scroll-lock to get
the prompt and type:

Linux root=/dev/hda1

where 'Linux' is the name of your linux image (if you don't know what the name
of the image is you can hit TAB at the prompt to get a list of images) and
/dev/hda1 is the device path of your root partition. Once you get booted up
look at your /etc/lilo.conf file. There should be a 'root=...' line in it
which is probably incorrect.

As to the BIOS detection, it probably still wants to find two drives. Go into
the BIOS setup and tell it there's no secondary drive and it'll be happy.

Ian Keith Setford wrote:

> Yo-
>
> I recently removed my Windows drive from a machine that runs Debian 95%
> of the time.  The previous arrangement was as follows:
> /dev/hda        Windows         (master primary controller)
> /dev/hdb        Debian          (slave primary controller)
> /dev/hdc        CD-ROM          (master secondary controller)
>
> I removed /dev/hda (Windows) and switched the Debian drive cable and
> set the jumper to master.  I *thought* I was thinking ahead when I
> re-configured LILO to boot from the actual Linux drive instead of from the
> boot sector on the Windows drive.  I ran /sbin/lilo and I also configured
> fstab before I physically removed the drive.
>
> After removal Linux will not boot.  The BIOS detection of the HDD also
> takes about 2 minutes whereas previously it took about 5-10 seconds.
> Debian error says, "DMA reset, irq timeout {SEEK ... SEEK ... }' etc..
>
> I am unsure of what is actually wrong.  I also booted with a rescue disk
> and a boot disk but both will die with error, "Unable to open Initial
> Console."

--
Jens B. Jorgensen
[EMAIL PROTECTED]



--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .

Reply via email to