From owner-freebsd-hardware Tue Nov 12 08:37:08 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA04103 for hardware-outgoing; Tue, 12 Nov 1996 08:37:08 -0800 (PST) Received: from persprog.com (persprog.com [204.215.255.203]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA04080 for ; Tue, 12 Nov 1996 08:36:44 -0800 (PST) Received: by persprog.com (8.7.5/4.10) id LAA18001; Tue, 12 Nov 1996 11:17:40 -0500 Received: from dasa(192.2.2.199) by cerberus.ppi.com via smap (V1.3) id sma017999; Tue Nov 12 11:17:34 1996 Received: from DASA/SpoolDir by dasa.ppi.com (Mercury 1.21); 12 Nov 96 11:17:37 +0500 Received: from SpoolDir by DASA (Mercury 1.30); 12 Nov 96 11:17:29 +0500 From: "David Alderman" Organization: Personalized Programming, Inc To: "Michael L. VanLoon -- HeadCandy.com" , Harlan Stenn , rschof@mccomm.nl, freebsd-hardware@freebsd.org Date: Tue, 12 Nov 1996 11:17:25 +0500 Subject: Re: After changing to an AHA2940 I can't boot the kernel. Priority: normal X-mailer: Pegasus Mail for Windows (v2.42a) Message-ID: <229687605AD@dasa.ppi.com> Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From: "Michael L. VanLoon -- HeadCandy.com" > > >Most likely problem: the sector mapping on one controller is different from > >that on the other. > > This is theoretically possible. But in the Real World, I have never > seen this happen, juggling drives between a BusLogic BT747s, a BT956c, > an Adaptec 2940UW, and an NCR 53c810. I think I mixed a 1542 in there > a few times, too, but I'm not positive. > You must have never used Future Domain, have you? ;-) All of the controllers you mentioned forutnately use the same geometry scheme AFAIK. There are controllers out there that use different mapping schemes that can cause failure - particularly older models. Also DOS>1G support can cause boot loader problems, although I don't remember the boot loader failure in the place mentioned. Actually I have encountered what appears to be a geometry problem involving the same controller in two different motherbards. Going from a ASUS P55TP4N to an ASUS P55T2P4 with a hard disk and controller results in a failure to load the boot loader. Of course, this was under SCO (and who knows what atrocities they are committing in their boot loader) but it's still quite a mystery. ====================================== When philosophy conflicts with reality, choose reality. Dave Alderman -- dave@persprog.com ======================================