From owner-freebsd-questions Mon Jun 2 18:11:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA25097 for questions-outgoing; Mon, 2 Jun 1997 18:11:46 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA25092 for ; Mon, 2 Jun 1997 18:11:40 -0700 (PDT) Received: from daisy.snet.net (mail.snet.net [204.60.7.83]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id SAA00673 for ; Mon, 2 Jun 1997 18:11:35 -0700 (PDT) Received: from katya.snet.net (hrfr03-sh9-port21.snet.net [204.60.10.21]) by daisy.snet.net (8.8.5/8.8.5/SNET-1.5) with SMTP id VAA14643 for ; Mon, 2 Jun 1997 21:10:18 -0400 (EDT) Message-ID: <33936E46.167EB0E7@snet.net> Date: Mon, 02 Jun 1997 21:07:18 -0400 From: "Jeffrey M. Metcalf" X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: FreeBSD Questions Subject: Q: Problems with nca0 device Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello All, I am having problems with my Iomega Zip 100 drive connected to my ProAudioStudio SCSI host adapter (device nca0). I get the following message on my console nca0/5/0 data length underflow whenever I attempt to write data to the zip drive. Reading seems OK resulting in the message nca: pseudo-dma timeout I suspect that the second message is more benign that the first. Data that I have written to the drive seem to get truncated or corrupted. This doesn't always occur. I have successfully written some large files to the zip drive, have read them back, and have found them totally uncorrupted. Others have been corrupted. This occurs both with DOS fs and ufs on the ZIP media. Does anyone have any ideas what could be wrong and if there is anything I can do about it? Incidently, the drive seems to work fine under Windows95 with the same host adapter, hence I think it's a FreeBSD driver problem with nca0 rather than a hardware problem. Thank You, JM -- Jeffrey M. Metcalf metcalf@snet.net