From owner-freebsd-scsi Sat Aug 17 16:32:30 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA28239 for freebsd-scsi-outgoing; Sat, 17 Aug 1996 16:32:30 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA28230; Sat, 17 Aug 1996 16:32:29 -0700 (PDT) Message-Id: <199608172332.QAA28230@freefall.freebsd.org> To: Dale_Moberg@stercomm.com cc: scsi@freebsd.org Subject: Re: nca scsi driver error messages during boot. In-reply-to: Your message of "Sat, 17 Aug 1996 14:22:27 EDT." <2160F420.1733@smtplink.stercomm.com> Date: Sat, 17 Aug 1996 16:32:28 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Resent to scsi list after no response in questions. Many of us are not on that list. > 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 drive is attempting to negotiate Synchronous transfers with the nca driver, but I guess they are not supported. The NCA driver should send a message reject in response to any messages it doesn't understand which should solve this problem until synchronous transfer support can be added (assuming the hardware supports it). Unfortunately, I'm not very familiar with the nca driver, so perhaps someone else can look into this? I think pkh did some work on it the last time around. If no one else pipes up, I'll have a look-see and try to give you a work around. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================