Bug#28201: marked as done ([closable?] boot floppies for 2.0 do not make system bootable)
Your message dated 27 May 1999 02:12:47 -0400
with message-id <oa675f11nk.fsf@burrito.fake>
and subject line Bug#28201: boot floppies for 2.0 do not make system bootable
has caused the attached bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Ian Jackson
(administrator, Debian bugs database)
Received: (at submit) by bugs.debian.org; 19 Oct 1998 14:35:09 +0000
Received: (qmail 25703 invoked from network); 19 Oct 1998 14:35:08 -0000
Received: from nis-tradewind.paisley.ac.uk (HELO wpmail.paisley.ac.uk) (146.191.32.5)
by master.debian.org with SMTP; 19 Oct 1998 14:35:08 -0000
Received: from Gate-Message_Server by wpmail.paisley.ac.uk
with Novell_GroupWise; Mon, 19 Oct 1998 15:39:51 +0000
Message-Id: <s62b5d47.054@wpmail.paisley.ac.uk>
X-Mailer: Novell GroupWise 4.1
Date: Mon, 19 Oct 1998 14:39:25 +0000
From: Duncan Thomson <thom-ci0@wpmail.paisley.ac.uk>
To: submit@bugs.debian.org
Subject: boot floppies for 2.0 do not make system bootable
Package: boot-floppies
Version: from the 2.0 release
Severity: important
i have tried to install debian 2.0 on a client's machine, and all goes well until i make the system bootable from the hard disk.
when rebooted, the system print 1FA: and will not proceed further.
the system uses an AHA2940 SCSI controller, and the root partition is the first of the SCSI disk. this partition *has* been made bootable, and i've tried the `linear' option of lilo, to no avail.
since i don't have direct access to the machine, i can't try just any change right away, but i will try the most recent slink boot-floppies on wednesday, and can report back on results.
i hope this problem can be corrected before 2.1 release.
cheers,
-duncan
(Suse linux runs OK, i've heard, so the problem is not `just' a hardware one)
Reply to: