On Mon, Dec 10, 2007 at 07:42:38PM -0800, Jesse Peterson wrote:
> On Tue,  4 Dec 2007 08:40:02 +0000 (UTC)
> Manuel Bouyer <bouyer@antioche.eu.org> wrote:
> 
> >  On Mon, Dec 03, 2007 at 11:19:05PM -0800, Jesse Peterson wrote:
> >  > Can you expound on what is needed and this "code" is or point me to more information? I'd be interesting in finding a solution to this. I'm not sure what the "parameter list" is with regard to ASC/ASCQ and where in the source things related to this might be. I tried to turn on SCSIPI debugging unsuccessfully.
> >  
> >  
> >  Look at src/sys/dev/scsipi/st_atapi.c, all should be there. The problem is
> >  that your enclosure presents to the host a scsibus, not an atapibus.
> 
> I'm not sure why this is a problem? Is the problem that NetBSD inherently can't support ATAPI devices on pseudo-SCSI buses or is it that this particular enclosure doesn't work? The drive was sold as it is (ie, it's not an aftermarket enclosure) in this enclosure and it does work on other OSs.

The problem is that the driver has no ways to know that this is an ATAPI
device and not a SCSI one (the enclosure announce itself as SCSI). Maybe
other OSes have specific drivers for this device, or a quirk list.

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
     NetBSD: 26 ans d'experience feront toujours la difference
--