From owner-freebsd-scsi  Sat Aug 17 11:25:54 1996
Return-Path: owner-freebsd-scsi
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA07212
          for freebsd-scsi-outgoing; Sat, 17 Aug 1996 11:25:54 -0700 (PDT)
Received: from ns.stercomm.com (ns.stercomm.com [199.3.19.2])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA07206
          for <scsi@freebsd.org>; Sat, 17 Aug 1996 11:25:51 -0700 (PDT)
Received: from smtplink.stercomm.com by ns.stercomm.com 
	id AA06244; Sat, 17 Aug 1996 14:22:58 -0400
Received: from ccMail by smtplink.stercomm.com
  (IMA Internet Exchange 2.01 Enterprise) id 2160F420; Sat, 17 Aug 96 14:28:18 -0400
Mime-Version: 1.0
Date: Sat, 17 Aug 1996 14:22:27 -0400
Message-Id: <2160F420.1733@smtplink.stercomm.com>
From: Dale_Moberg@stercomm.com
Subject: nca scsi driver error messages during boot.
To: scsi@freebsd.org
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Description: cc:Mail note part
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

     

Resent to scsi list after no response in questions.

______________________________ Forward Header __________________________________
Subject: nca scsi driver error messages during boot.


     
     
     Hi,
     
     I am trying to get to the point of using disklabel on a scsi drive 
     but disklabel times out when asked to write a label to the disk.
     
     dmesg shows that during boot the nca scsi driver finds the controller 
     card (a NCR-53C400 based Trantor board model 160B). It also probes 
     the bus and finds sd0(nca1:0:0) which responds with
     HP 1.050 GB 3rd 0582 type 0 fixec scsi2
     Direct Access 1001 MB (2051460 512 byte sectors)
     
     But I also see the following error messages:
     
     nca1/0/0 unknown message: 0x1
     nca1/0/0 unknown message: 0x1
     nca1/0/0 unknown message: 0x19
     nca1/0/0 unknown message: 0xf
     
     
     The HP drive is a fast scsi 2 drive whose documentation says to supply 
     termpwr and to terminate using a cable with active termination. This I 
     have done. Unfortunately the controller card documentation (from 
     Adaptec) does not say how its termination can be modified or whether 
     it is active. The controller card has both an internal 50 pin 
     connector for ribbon cable and a DB25 for external devices. I do not 
     know how the card figures out whether it is in the middle or at the 
     end. 
     
     My question is whether the unknown messages that are found during boot 
     give any clues about what the real problem is and how it might be 
     fixed? If not, is there a controller card that can supply active 
     termination and is configurable (jumpers preferably) and that is known 
     to work with fast scsi 2 drives (and of course freebsd!!!)
     
     Thanks for any assistance.