From owner-freebsd-hackers Wed Jan 21 09:10:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12208 for hackers-outgoing; Wed, 21 Jan 1998 09:10:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from word.smith.net.au (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12178 for ; Wed, 21 Jan 1998 09:10:33 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id DAA00982; Thu, 22 Jan 1998 03:33:36 +1030 (CST) Message-Id: <199801211703.DAA00982@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Pedro A M Vazquez cc: hackers@FreeBSD.ORG Subject: Re: wfd/zip ATAPI In-reply-to: Your message of "Mon, 19 Jan 1998 14:11:30 -0200." <199801191611.OAA11884@kalypso.iqm.unicamp.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Jan 1998 03:33:36 +1030 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > Mike > This is the output from a verbose boot/probe: > atapi0.1 at 0x1f0: attach called > wdc0: unit 1 (atapi): , removable, intr, iordis Looks basically the same as the one I have, yup. It probes OK. > it seems to follow most atapi commands, doesn't it? It certainly understands MODE_SENSE. > When it hangs it stops to work just after this: > > atapi0.1: start > atapi0.1: intr ireason=0x1, len=64000, status=58, error=0 > atapi0.1: send cmd WRITE_BIG 2a-0-0-0-0-10-0-0-3-0-0-0-0-0-0-0 > atapi0.1: intr ireason=0x0, len=1536, status=58, error=0 > atapi0.1: intr ireason=0x3, len=1536, status=50, error=0 > atapi0.1: req cb 28-0-0-0-0-30-0-0-8-0-0-0-0-0-0-0 len=4096 > atapi0.1: start > atapi0.1: intr ireason=0x1, len=4096, status=58, error=0 > > I've no logs after this point but on the console it goes to > a series of req cb with size 64 and then stops. This is very similar to what I see. I found I got better error messages by turning off multi-sector etc. modes. The drive appears to wedge up; I get one error register value with a sense code of 0xd (which is undefined), and then it stops taking commands. Is it possible that the drive doesn't handle the WRITE-10 command well? I don't know why it's called WRITE_BIG, given the alternative is WRITE-12. The SFF-8020i document implies that READ-10 is obsolete and that READ-12 should be used... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\