From owner-freebsd-hackers  Mon Nov  4 21:13:55 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA04244
          for hackers-outgoing; Mon, 4 Nov 1996 21:13:55 -0800 (PST)
Received: from netrover.com (ottawa23.netrover.com [205.209.19.32])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA04230
          for <freebsd-hackers@FreeBSD.org>; Mon, 4 Nov 1996 21:13:48 -0800 (PST)
Received: (from brianc@localhost) by netrover.com (8.7.6/8.7.3) id AAA00885; Tue, 5 Nov 1996 00:12:21 -0500 (EST)
Message-Id: <199611050512.AAA00885@netrover.com>
Date: Tue, 5 Nov 1996 00:12:20 -0500
From: brianc@netrover.com (Brian Campbell)
To: freebsd-hackers@FreeBSD.org
Subject: Re: atapi errors
References: <199611040304.WAA00778@netrover.com> <Pine.BSF.3.91.961104213652.367A-100000@wong.rogerswave.ca>
X-Mailer: Mutt 0.48.1
Mime-Version: 1.0
Reply-to: freebsd-hackers@FreeBSD.org
In-Reply-To: <Pine.BSF.3.91.961104213652.367A-100000@wong.rogerswave.ca>; from Ken Wong on Nov 4, 1996 21:41:07 -0500
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Ken Wong writes:
> My config seems to work fine. I see the difference is cdrom rev. 3.05
> as compare to 3.04 in yours.
> 
> wdc1 at 0x170-0x177 irq 15 on isa
> wdc1: unit 0 (atapi): <NEC                 CD-ROM DRIVE:282/3.05>, removable, dma, iordy
> wcd0: 1376Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray
> wcd0: medium type unknown, unlocked
> 
> > With the 1014 snap and an 8x NEC IDE CD-ROM, I'm getting:
> > 
> > wdc1 at 0x170-0x177 irq 15 flags 0x80ff on isa
> > wdc1: unit 0 (atapi): <NEC                 CD-ROM DRIVE:282/3.04>, removable, dma, iordy
> > wcd0: 1376Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray
> > wcd0: medium type unknown, unlocked
> > atapi1.0: invalid command phase, ireason=0xd0, status=d0<busy,ready,opdone>, error=d0
> > atapi1.0: invalid command phase, ireason=0xd8, status=d8<busy,ready,opdone,drq>, error=d8<mchg>
> > atapi1.0: controller not ready for cmd
> > atapi1.0: controller not ready for cmd

Hmmm ... it'd be nice to blame it on the hardware, but I don't think I
can this time.  Booting the same machine into windows 95 or qnx enables
the CD to be read without any problems.

I was hoping someone would say "oh, that's been fixed in -current, grab
atapi.c" or "oh, looks like it timed out too soon, adjust flarg to plib"