From owner-freebsd-questions Thu Jun 6 19:30:23 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA12682 for questions-outgoing; Thu, 6 Jun 1996 19:30:23 -0700 (PDT) Received: from croute.com (ishm2.croute.com [199.97.106.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id TAA12623 for ; Thu, 6 Jun 1996 19:30:06 -0700 (PDT) Received: from bldg1.croute.com by croute.com (4.1/SMI-4.1) id AA16270; Thu, 6 Jun 96 21:28:58 CDT Received: from COMPUROUTE/SpoolDir by bldg1.croute.com (Mercury 1.13); Thu, 6 Jun 96 21:28:27 +600 Received: from SpoolDir by COMPUROUTE (Mercury 1.13); Thu, 6 Jun 96 21:28:18 +600 From: "Larry Dolinar" Organization: CompuRoute, Inc. To: novell@listserv.syr.edu, questions@freebsd.org Date: Thu, 6 Jun 1996 21:28:11 +600 CDT Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Subject: Seagate ST32151N/Adaptec 2940 on Asus P55TP4N and PVI486SP3 X-Confirm-Reading-To: "Larry Dolinar" X-Pmrqc: 1 Priority: normal X-Mailer: Pegasus Mail v3.22 Message-Id: <45DBD3E4266@bldg1.croute.com> Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Apologies for the cross-posting... There IS something going on with this combination: Adaptec's boot sequence consistently times out on these drives, regardless of what else is in the system. An ST31200N at id 0 shows fine, the ST32151N eventually comes back as variations on "device not ready". NCR-based controllers (Asus SC-200 and Symbios 8150S) and Tekram 390 do NOT exhibit this behavior. Doesn't matter what id the ST32151N is at, or if it's the only drive. Smells like firmware, but whose? Adaptec BIOS is EC00, very close to latest. Insights welcomed -- waiting on answers from Seagate and Adaptec.