Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 4 Nov 1996 21:41:07 -0500 (EST)
From:      Ken Wong <wong@wong.rogerswave.ca>
To:        freebsd-hackers@FreeBSD.org
Subject:   Re: atapi errors
Message-ID:  <Pine.BSF.3.91.961104213652.367A-100000@wong.rogerswave.ca>
In-Reply-To: <199611040304.WAA00778@netrover.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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

On Sun, 3 Nov 1996, Brian Campbell wrote:

> 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
> atapi1.0: controller not ready for cmd
> atapi1.0: controller not ready for cmd
> atapi1.0: controller not ready for cmd
> atapi1.0: controller not ready for cmd
> 
> Any ideas on what the problem is, or how to fix?
> 
> 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.961104213652.367A-100000>