From owner-freebsd-questions  Wed May 24 17:33:42 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id RAA28735
          for questions-outgoing; Wed, 24 May 1995 17:33:42 -0700
Received: from test.dad.home (benhome.tbcnet.com [205.199.1.108])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA28729
          for <questions@freeBSD.org>; Wed, 24 May 1995 17:33:37 -0700
Received: (from ben@localhost) by test.dad.home (8.6.9/8.6.9) id TAA00275; Wed, 24 May 1995 19:27:35 GMT
Date: Wed, 24 May 1995 19:27:34 +0000 ()
From: Ben Schmidtke <ben@benhome.tbcnet.com>
X-Sender: ben@test.dad.home
To: questions@FreeBSD.org
Subject: CDROM and wt Tape driver
Message-ID: <Pine.BSF.3.91.950524191739.254A-100000@test.dad.home>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: questions-owner@FreeBSD.org
Precedence: bulk

 I am currently running FreeBSD 2.0 Release #2 (Jan '94), and am having
trouble with the mcd0a driver dropping out with a media change error. This
occurrs during "heavy" activity such as package installation. The CDROM is
a Mitsumi single speed drive with a 16 bit controller card. Is there a 
bug fix that I should be aware of?

 I also have an ancient Wantek tape drive in this system. If I configure 
the kernel so that it knows the hardware parameters for the controller, 
when the system boots up, very strange things happen. One example is that 
at the login prompt, the block cursor is nailed in the leftmost column on 
the screen, but characters echoed to the screen appear in the expected 
place (after the prompt). It's all down hill from there.

 Both of these devices worked correctly in FreeBSD 1.1. Any ideas?