From owner-freebsd-chat  Wed Jan  7 09:56:05 1998
Return-Path: <owner-freebsd-chat@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA21860
          for chat-outgoing; Wed, 7 Jan 1998 09:56:05 -0800 (PST)
          (envelope-from owner-freebsd-chat@FreeBSD.ORG)
Received: from kalypso.cybercom.net (kalypso.cybercom.net [209.21.136.5])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21836
          for <freebsd-chat@freebsd.org>; Wed, 7 Jan 1998 09:55:50 -0800 (PST)
          (envelope-from ksmm@kalypso.cybercom.net)
Received: from localhost (ksmm@localhost) by kalypso.cybercom.net (8.8.7/8.8.7) with SMTP id MAA24915 for <freebsd-chat@freebsd.org>; Wed, 7 Jan 1998 12:54:44 -0500 (EST)
Date: Wed, 7 Jan 1998 12:54:40 -0500 (EST)
From: The Classiest Man Alive <ksmm@cybercom.net>
To: freebsd-chat@FreeBSD.ORG
Subject: More than 64 MB of RAM
Message-ID: <Pine.BSI.3.95.980107123002.18455B-100000@kalypso.cybercom.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-chat@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I recently bought an ASUS P2L97 Pentium II motherboard and put 128 MB of
RAM on it, but FreeBSD didn't like that.  (Neither did Linux, Windows 95
or NT.)  It worked smashingly when I removed 64 MB of that RAM.  Is there
anything special that I need to do with this motherboard (e.g., BIOS
setting, ritual sacrifices) to get it to work with protected memory
access?

Thanks, peoples.
K.S.