From owner-freebsd-questions Thu Dec 19 00:35:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA09108 for questions-outgoing; Thu, 19 Dec 1996 00:35:15 -0800 (PST) Received: from gdi.uoregon.edu (cisco-ts9-line3.uoregon.edu [128.223.150.84]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA09097 for ; Thu, 19 Dec 1996 00:35:05 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.2/8.6.12) with SMTP id AAA00452; Thu, 19 Dec 1996 00:34:21 -0800 (PST) Date: Thu, 19 Dec 1996 00:34:20 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Mark Crosland cc: freebsd-questions@freebsd.org Subject: Re: Re: scsi/ncr install, no ncr0 In-Reply-To: <199612132109.NAA03842@redoubt.metapath.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 13 Dec 1996, Mark Crosland wrote: > Thanks for the reply. Turns out a gentleman by the name of Robert Eckardt > (roberte@mep.ruhr-uni-bochum.de) recognized this problem. He thought it was > a combination of BSD ncr driver, ncr controller and HP hard drives. The > BSD ncr driver will only use 'tagged' commands to read/write > data from the drives. I worked on a SCSI-1 driver several years ago, so > I gather that 'tagged' cmds are SCSI-2 cmds. However, the HP > drives don't accept these cmds, and the BSD ncr driver won't 'back off' > and use simpler SCSI cmds. Robert claimed it was fixed in 2.2, and sure > enough I loaded the 2.2 boot floppies from ftp.cdrom.cm and was able to > boot far enough so I could fdisk things. Of course I didn't fdisk > anything because my CDs are 2.1.5 and I would have end up with a 2.1.5 kernel > that wouldn't see my hard drives (most likely !?). So I guess I wait for > 2.2 CDs !? Wierd! > Robert also indicated that the ncr is the only controller that supports > tagged commands (?) So if the driver and disk support tagged cmds I > would get better performance. So, what do you think, I ought to be able > to raise some #$%^& with HP. Are these tagged/overlapped SCSI cmds > standard SCSI-2 ? Seems to me they ought be supported. Odd. I always thought tagged command queueing was a nifty extension, not part of the spec. I don't think my NCR is using it; if I use the fancy driver for DOS, I can crash out my CDROM by copying /kernel.IDE from the CD to the DOS partition :( If I use the lightweight direct-access driver it works OK. It's working fine on 2.2-ALPHA here so I shouldn't worry I guess...? Glad you got it worked out though. Strange... Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major