From owner-freebsd-questions  Mon Feb 27 08:45:35 1995
Return-Path: questions-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA28574 for questions-outgoing; Mon, 27 Feb 1995 08:45:35 -0800
Received: from halon.sybase.com (halon.sybase.com [192.138.151.33]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id IAA28568 for <questions@freebsd.org>; Mon, 27 Feb 1995 08:45:33 -0800
Received: from sybase.com (sybgate.sybase.com) by halon.sybase.com (5.0/SMI-SVR4/SybFW4.0)
	id AA27166; Mon, 27 Feb 1995 08:49:11 -0800
Received: from cottonwood.sybgate.sybase.com by sybase.com (4.1/SMI-4.1/SybH3.4)
	id AA01944; Mon, 27 Feb 95 08:46:59 PST
Received: by cottonwood.sybgate.sybase.com (4.1/SMI-4.1/SybEC3.2)
	id AA27728; Mon, 27 Feb 95 11:46:56 EST
Date: Mon, 27 Feb 95 11:46:56 EST
From: jeffa@sybase.com (Jeff Anuszczyk)
Message-Id: <9502271646.AA27728@cottonwood.sybgate.sybase.com>
To: questions@FreeBSD.org
Subject: Re: Trying to install FreeBSD V2.0
Cc: jeffa@sybase.com
content-length: 1056
Sender: questions-owner@FreeBSD.org
Precedence: bulk

Hi All,
   Just thought I would give you a status update.  For all PC hackers I'm
sure this won't surprise you... but I finally figured out why I couldn't
install FreeBSD V2.0R on my 486DX2/66.  It turns out when I was originally
installing the system I selected "OPTIMAL" for the BIOS settings (AMI)
assuming that this would be a relatively safe thing to do.  Wrong.
Apparently this sets up some stuff (I'm not exactly sure of what... 
perhaps the cacheing status of 640KB-1MB).  In any case, I finally went
and reset the BIOS to pokey mode (turns the clock to 8MHz, no cacheing
of any type).  I then upped the clock to 33Mhz, enabled the caches.
That's it... left everything else the "default" settings for "pokey" 
mode.  Bingo... everything works fine.  V2.0R installed like a dream.

   So, the moral of the story is... things can appear to be working fine
for MS-DOS/Windows (yea big surprise here) but not be entirely correct.
In my case, these BIOS issues resulted in a kernel panic during 
installation (duplicate alloc).  Really strange.

- Jeff