From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 17 00:43:09 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F49B16A4D4 for ; Tue, 17 Feb 2004 00:43:09 -0800 (PST) Received: from 192.168.0.112 (unknown [217.11.112.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id B06EB43D1D for ; Tue, 17 Feb 2004 00:43:08 -0800 (PST) (envelope-from gbautista@odmcomputers.com) Received: from [127.0.0.1] by guillermo (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.3.5)); Tue, 17 Feb 2004 09:42:56 +0100 From: "Guillermo Bautista" To: Date: Tue, 17 Feb 2004 09:42:56 +0100 Message-ID: <004401c3f532$0a3ee5d0$7000a8c0@ODMComputers.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: Do "Freebsd" and "HP StorageWorks DAT 40 Tape Drive" marry?? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2004 08:43:09 -0000 Hello again. I don't know it the list only has traffic a few days during the week, anyway as I finally found the specifications of this Tape drive, I would like to ask you about it: I have a "HP StorageWorks DAT 40 Tape Drive" (Q1553A) in a Proliant ML 350 G3. My FreeBSD 5.1 doesn't recognize the tape, but I doubt if this occurs just because I deactivated in the BIOS the internal Ultra320 SCSI card or it's just because FreeBSD doesn't support this tape. I am not as thumb as it seems (trust me! ;-) ), is just the Proliant now resides at a Data Center which isn't "at hand" right now (it's at a Data Center too many kilometers away from me). I have no more options than going there to check the BIOS and/or recompile the kernel or it wouldn't work even doing so? Guillermo BT gbautista@odmcomputers.com