From owner-freebsd-current Wed Jul 29 11:03:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16393 for freebsd-current-outgoing; Wed, 29 Jul 1998 11:03:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from att.com (kcgw1.att.com [192.128.133.151]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA16374 for ; Wed, 29 Jul 1998 11:03:42 -0700 (PDT) (envelope-from jwb@homer.att.com) Received: from kcig1.att.att.com by kcgw1.att.com (AT&T/UPAS) for freebsd.org!freebsd-current sender homer.att.com!jwb (homer.att.com!jwb); Wed Jul 29 13:03 CDT 1998 Received: from ulysses.homer.att.com (ulysses.homer.att.com [135.205.212.4]) by kcig1.att.att.com (AT&T/GW-1.0) with ESMTP id NAA22197 for ; Wed, 29 Jul 1998 13:02:56 -0500 (CDT) Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.213.77]) by ulysses.homer.att.com (8.8.8/8.8.8) with SMTP id OAA02773 for ; Wed, 29 Jul 1998 14:02:54 -0400 (EDT) Received: by akiva.homer.att.com (4.1) id AA12382; Wed, 29 Jul 98 14:02:55 EDT Message-Id: <9807291802.AA12382@akiva.homer.att.com> Received: from localhost.homer.att.com [127.0.0.1] by akiva; Wed Jul 29 14:02:55 EDT 1998 X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: install with adaptec aic-78xx PCI Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 29 Jul 1998 14:02:54 -0400 From: "J. W. Ballantine" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have an AT&T Globalyst 630 with a adaptec aic-78xx PCI that is running NT and had current on it. Due to several things, I had to reload FBSD. When I tried to load from the 3.0-YYMMDD-SNAP boot(980426 or 980520), it would not consisently install, in fact it generally locked up the SD0 drive at either prior to the install menu being displayed or when it when to update the SD0 label. Yet when I loaded from 2.2.6(or7)-RELEASE boot floppy I had no problem with it. Has the driver for the adaptec aic-78xx PCI SCSI controller changed to cause this problem or is it something else?? (At one point Doug White thought it might be memory problems, but it doesn't appear to be the problem.) Jim Ballantine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message