From owner-freebsd-current Tue Apr 9 13:07:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA08501 for current-outgoing; Tue, 9 Apr 1996 13:07:24 -0700 (PDT) Received: from trout.nosc.mil (trout.nosc.mil [128.49.16.7]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA08496 for ; Tue, 9 Apr 1996 13:07:20 -0700 (PDT) Received: from cod.nosc.mil by trout.nosc.mil (4.1/SMI-4.1) id AA27834; Tue, 9 Apr 96 13:07:18 PDT Received: from [128.49.16.48] (aegis.nosc.mil) by cod.nosc.mil (4.1/SMI-4.1) id AA09804; Tue, 9 Apr 96 13:05:22 PDT X-Sender: gshaffer@cod.nosc.mil Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 9 Apr 1996 13:06:40 -0700 To: current@freebsd.org From: gshaffer@nosc.mil (Greg Shaffer) Subject: Adaptec 2940 & Diamond Stealth S3-Trio64 Problem Cc: gshaffer@nosc.mil Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Recently, I upgraded to a new PCI motherboard, UMC chipset (8881/886a), Am586-P75 133MHz CPU, Diamond Stealth 64 (S3-Trio64V+) with 2MB DRAM, and an Adaptec 2940 (Ultra, aic7880) SCSI adapter. At the same time I upgraded the hardware, I also upgraded XFree86 in my FreeBSD 2.1.0 installation to 3.1.2D since it fixed some S3-Trio64 bugs. Right away I started to have problems with the X server (XF86_S3) locking up the computer. When X starts up there is a flurry of disk activity, sometimes the screen will change to my default background color, other times the screen would flicker and then the machine would hang. In all cases I noticed the disk access light on my external hard drive was always on (even thought there was no continued disk activity) and remained on until I reset the machine. This problem originally occured under FreeBSD 2.1.0, upgrading to FreeBSD-stable (current as of src-2.1.0067) did not solve the problem. I also reinstalled my Adaptec 1542CF and the system works fine. Is there anybody else running FreeBSD 2.1.0 or stable with the same or similar setup that has had success? If so what are the BIOS version for your controllers? Does anybody have any suggestions on how to trouble shoot this problem? Thanks Greg Shaffer