From bill@duchess.wagill.com  Thu Mar 27 16:37:06 1997
Received: from duchess.wagill.com (duchess.wagill.com [198.182.208.147])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA07421
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 27 Mar 1997 16:36:59 -0800 (PST)
Received: (from bill@localhost)
	by duchess.wagill.com (8.8.5/8.8.5) id QAA00297;
	Thu, 27 Mar 1997 16:36:48 -0800 (PST)
Message-Id: <199703280036.QAA00297@duchess.wagill.com>
Date: Thu, 27 Mar 1997 16:36:48 -0800 (PST)
From: Bill <bill@duchess.wagill.com>
Reply-To: bill@duchess.wagill.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: Install with mcd0 still broken.
X-Send-Pr-Version: 3.2

>Number:         3126
>Category:       bin
>Synopsis:       Install with mcd0 still broken.
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Mar 27 16:40:03 PST 1997
>Closed-Date:    Sat May 30 10:09:23 PDT 1998
>Last-Modified:  Sat May 30 10:09:56 PDT 1998
>Originator:     Bill
>Release:        FreeBSD 2.1.7-RELEASE i386
>Organization:
>Environment:

	Mitsumi FX001D Internal CDROM drive
	FreeBSD 2.1.7-RELEASE #0: Wed Feb 19 23:08:10  1997
	c/sys/compile/GENERIC  i386

>Description:

	When installing FreeBSD 2.1.7, if one follows the directions and
	thus closes the CDROM drive's gate before starting the installation,
	the install program fails to detect the CDROM drive.

	This is an old problem which is *still* happening.

>How-To-Repeat:

	

>Fix:
	
	Open the CDROM drive's gate; reboot the machine; let the system go through
	its probes; as soon as 'install' is starting, the drive's gate closes (by
	itself); later on install recognizes the CDROM drive (and you may proceed
	with the insrallation).

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->suspended 
State-Changed-By: joerg 
State-Changed-When: Sat Aug 23 15:04:58 MEST 1997 
State-Changed-Why:  

None of the active developers still has such a drive available for 
testing or development work. 

I see only two chances how to finally close this: 

1	One of the people owning such a drive submits a fix, or 
2	We declare the `mcd' driver `unsupported'. 

Before taking route #2, i'd like to wait whether the originator would be 
willing to go #1. 
State-Changed-From-To: suspended->feedback 
State-Changed-By: steve 
State-Changed-When: Mon May 25 14:57:52 PDT 1998 
State-Changed-Why:  
Does this problem still occur in a more recent version. 
2.2.6?  -current? 
State-Changed-From-To: feedback->closed 
State-Changed-By: steve 
State-Changed-When: Sat May 30 10:09:23 PDT 1998 
State-Changed-Why:  
No response to mail ping, so we'll assume the problem has 
been fixed. 
>Unformatted:
