From owner-freebsd-questions Wed Aug 16 12:32:06 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id MAA24090 for questions-outgoing; Wed, 16 Aug 1995 12:32:06 -0700 Received: from sage.cc.purdue.edu (sage.cc.purdue.edu [128.210.10.6]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id MAA24063 for ; Wed, 16 Aug 1995 12:31:58 -0700 Received: from cfs.purdue.edu (cfs.cfs.purdue.edu [128.210.80.11]) by sage.cc.purdue.edu (8.6.10/8.6.12) with ESMTP id OAA19324 for ; Wed, 16 Aug 1995 14:31:25 -0500 Received: from CFS/MERCURY_MAIL by cfs.purdue.edu (Mercury 1.21); 16 Aug 95 14:32:44 Received: from MERCURY_MAIL by CFS (Mercury 1.21); 16 Aug 95 14:32:40 From: "W. Jeremy Nauck" Organization: CFS at Purdue University To: questions@FreeBSD.org Date: Wed, 16 Aug 1995 14:32:33 EST Subject: P5 w/ Adaptec AHA-2940W SCSI card Reply-to: Jeremy@cfs.purdue.edu X-Confirm-Reading-To: Jeremy@cfs.purdue.edu X-pmrqc: 1 Priority: normal X-mailer: Pegasus Mail for Windows (v2.0-WB3) Message-ID: <9F9A220B3A@cfs.purdue.edu> Sender: questions-owner@FreeBSD.org Precedence: bulk Greetings friends! Here's an interesting phenom that you may not have seen yet! During the initial boot from floppy before installation (2.0 and 2.0.5) everything begins to boot alright, but immediately after the phase the system panics with RAM parity error. Probable hardware problem. I isolated the error to our Adaptec AHA-2940W SCSI card (PCI) by removing it and booting with only a 1.44 3.5" floppy installed. The install process then begins normally. The AHC0 device is not even probed which I find odd since I was under the impression that it was included in the generic kernal distribution. Any hints/suggestions you may provide would be very helpful! Thanks in advance! -Jeremy ---------------------------------------------------------- Diclaimer goes here....etc...