From owner-freebsd-questions Wed Mar 13 06:21:45 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA00819 for questions-outgoing; Wed, 13 Mar 1996 06:21:45 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA00813 for ; Wed, 13 Mar 1996 06:21:41 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id BAA03121; Thu, 14 Mar 1996 01:02:05 +1030 From: Michael Smith Message-Id: <199603131432.BAA03121@genesis.atrad.adelaide.edu.au> Subject: Re: DDS DAT Drive and 2.1.0-R ? To: avalon@coombs.anu.edu.au (Darren Reed) Date: Thu, 14 Mar 1996 01:02:05 +1030 (CST) Cc: freebsd-questions@freebsd.org In-Reply-To: <199603131344.FAA29026@freefall.freebsd.org> from "Darren Reed" at Mar 14, 96 00:45:49 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Darren Reed stands accused of saying: > > Please, no comments about use better hardware, unless there is no other > way.... Well, I wouldn't be putting the hardware the 'nca' driver talks to at the top of my shopping list... > Does anyone have the blocking/density and size parameters for dump(1) > for use with DDS DAT drives ? Your settings are fine. You're looking at either a driver bug/shortcoming or hardware limitation. > 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 What does the driver mean? Have you looked at the source? > # mt -f /dev/nrst0 status > Present Mode: Density = X3B5/88-185A Blocksize variable This is fine, AFAIK. The DAT at work says the same thing, FWIW, and it works fine. > 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 ? That's because the systax is all wrong? Whay makes you think that's the way to do it? Look at GENERIC : controller scbus0 device sd0 device od0 device st0 device cd0 This supports any number of SCSI busses, and any number of any of the devices... > Also, on the wish list, what about lsdev returning irq's, etc ? 'lsdev -c' > darren -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[