Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!news.alpha.net!solaris.cc.vt.edu!insosf1.infonet.net!cynjut.infonet.net!cynjut.infonet.net!not-for-mail
From: burgess@cynjut.infonet.net (Dave Burgess)
Newsgroups: comp.os.386bsd.questions
Subject: Re: Mitsumi CD-ROM install trouble.
Date: 29 Dec 1994 13:29:52 -0600
Organization: Configuration Management Svcs, Inc.
Lines: 33
Message-ID: <3dv2ng$55e@cynjut.infonet.net>
References: <1189@datasync.mv.com> <1994Dec28.171116.7894@fsl.noaa.gov> <3ds9db$gqm@umcc.umcc.umich.edu>
NNTP-Posting-Host: cynjut.infonet.net
In article <3ds9db$gqm@umcc.umcc.umich.edu>,
Bruce Grant <bgrant@umcc.umcc.umich.edu> wrote:
}
}I am seeing this problem too. Correcting the irq and address does not fix
}it. During the boot these messages appear:
}
}mcd0: version information is 0 M 2
}mcd0: Adjusted for newer drive model
}mcd0: type Mitsumi LU005S
}
Isn't 0 M 2 an LU002 drive?
I thought that the LU005 returned a 0 M 4.
If that is the case, then the driver might need a little bit more
tweaking.
(This whole thing might be partly my fault, since I was working on this
chunk opf code for NetBSD and was sharing the work with the FreeBSD
folks. If so, sorry 'bout that.)
If this does turn out to be the case, then the problem is that the LU002
supports a VERY limited subset of the LU005 (and newer) commands.
Because of that, there are several things that could get hosed while
trying to read the drive.
--
TSgt Dave Burgess | Dave Burgess
NCOIC, USSTRATCOM/J6844 | *BSD FAQ Maintainer
Offutt AFB, NE | Burgess@cynjut.infonet.net or ...@s069.infonet...