Date: Tue, 5 Nov 1996 00:12:20 -0500 From: brianc@netrover.com (Brian Campbell) To: freebsd-hackers@FreeBSD.org Subject: Re: atapi errors Message-ID: <199611050512.AAA00885@netrover.com> In-Reply-To: <Pine.BSF.3.91.961104213652.367A-100000@wong.rogerswave.ca>; from Ken Wong on Nov 4, 1996 21:41:07 -0500 References: <199611040304.WAA00778@netrover.com> <Pine.BSF.3.91.961104213652.367A-100000@wong.rogerswave.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611050512.AAA00885>