From owner-freebsd-hardware@FreeBSD.ORG Tue Apr 18 08:43:35 2006 Return-Path: X-Original-To: freebsd-hardware@FreeBSD.ORG 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 5912C16A406 for ; Tue, 18 Apr 2006 08:43:35 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id A090443D73 for ; Tue, 18 Apr 2006 08:43:25 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (idqfmh@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k3I8hIKN049637 for ; Tue, 18 Apr 2006 10:43:23 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k3I8hI6E049636; Tue, 18 Apr 2006 10:43:18 +0200 (CEST) (envelope-from olli) Date: Tue, 18 Apr 2006 10:43:18 +0200 (CEST) Message-Id: <200604180843.k3I8hI6E049636@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hardware@FreeBSD.ORG In-Reply-To: <20060415153418.M52372@bmyster.com> X-Newsgroups: list.freebsd-hardware User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 18 Apr 2006 10:43:23 +0200 (CEST) Cc: Subject: Re: IDE tape drive stt3401a X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hardware@FreeBSD.ORG List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Apr 2006 08:43:35 -0000 Carl Foote wrote: > I just converted a windows server over to Freebsd 5.4 stable. The stt3401a > tape drive that was in server was working fine. The tape drive posts in the > BIOS but when freebsd boots up, it will not detect the drive. You haven't removed the ast(4) driver from your kernel, have you? > Documentation > for the drive does state it cannot be on the same controller as a hard drive, > which I verified. It can be on the same controller, but not on the same channel. As far as I know, it works when configured as slave device (even though this isn't really a legal ATA configuration): atapci0: port 0xf000-0xf00f,0-0x3,0-0x7,0-0x3,0-0x7 irq 9 at device 31.1 on pci0 ata1: at 0x170 irq 15 on atapci0 ast0: TAPE at ata1-slave PIO3 > So, on its own controller (secondary) as master Try to configure it as slave device. > I know freebsd is doing /dev differently than in the past. It loads /dev > dynamically on boot, so it is not loaded with all the device files, just the > ones it detects. Is there a way to force the dev file to load. There is no way, and it wouldn't be useful anyway. If no driver attaches to the device, a device node in /dev wouldn't buy you anything. > ANY suggestions would be appreciated. You're not giving much information ... It would be helpful to know what kind of controller you have. An appropriate excerpt from a verbose boot might contain useful information (/var/run/dmesg.boot). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "I started using PostgreSQL around a month ago, and the feeling is similar to the switch from Linux to FreeBSD in '96 -- 'wow!'." -- Oddbjorn Steffensen