From owner-freebsd-questions Wed Mar 13 05:44:04 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA29071 for questions-outgoing; Wed, 13 Mar 1996 05:44:04 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id FAA29026 for ; Wed, 13 Mar 1996 05:44:00 -0800 (PST) Message-Id: <199603131344.FAA29026@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA109594749; Thu, 14 Mar 1996 00:45:49 +1100 From: Darren Reed Subject: DDS DAT Drive and 2.1.0-R ? To: freebsd-questions@freebsd.org Date: Thu, 14 Mar 1996 00:45:49 +1100 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Please, no comments about use better hardware, unless there is no other way.... Does anyone have the blocking/density and size parameters for dump(1) for use with DDS DAT drives ? Currently, I keep seeing these errors: Mar 14 00:38:56 freebsd /kernel.scsi: data length underflow Mar 14 00:38:56 freebsd /kernel.scsi: nca0/4/0 data length underflow Mar 14 00:38:56 freebsd last message repeated 130 times Mar 14 00:40:42 freebsd /kernel.scsi: nca0/4/0 (st0) timed out # mt -f /dev/nrst0 status Present Mode: Density = X3B5/88-185A Blocksize variable ---------available modes--------- Mode 0: Density = 0x00 Blocksize variable Mode 1: Density = 0x00 Blocksize variable Mode 2: Density = 0x00 Blocksize variable Mode 3: Density = 0x00 Blocksize variable Also, when I tried a kernel config with the following, st0 didn't work: controller scbus0 at nca0 disk sd? at scbus? target ? disk sd? at scbus? target ? tape st? at scbus? target ? device cd? at scbus? target ? kernel would find and allocate it, when booting as st0, but obviosuly the device in /dev was wrong or something. Also, on the wish list, what about lsdev returning irq's, etc ? darren