From owner-freebsd-questions  Thu Nov 30 17:46:10 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id RAA12279
          for questions-outgoing; Thu, 30 Nov 1995 17:46:10 -0800
Received: from quip.eecs.umich.edu (dmuntz@quip.eecs.umich.edu [141.212.99.8])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA12269
          for <questions@freebsd.org>; Thu, 30 Nov 1995 17:46:05 -0800
Received: (from dmuntz@localhost) by quip.eecs.umich.edu (8.7.2/8.7.2) id UAA09106 for questions@freebsd.org; Thu, 30 Nov 1995 20:46:01 -0500 (EST)
Date: Thu, 30 Nov 1995 20:46:01 -0500 (EST)
From: Dan Muntz <dmuntz@eecs.umich.edu>
Message-Id: <199512010146.UAA09106@quip.eecs.umich.edu>
To: questions@freebsd.org
Subject: Re:  Intel Endeavor MB cache problem
Sender: owner-questions@freebsd.org
Precedence: bulk

eyfarris@gdwest.gd.com wrote:
> I am running the same motherboard without any problems,
> but - not at 133MHz, yet.

Well, with your data point, and the fact that I was able to reproduce the
problem on a separate 133MHz system, I've got a pretty good idea about what's
wrong.  I set my clock to 120MHz and everything was fine.  I ran a memory
test under DOS at 133MHz and it failed.  Looks like the external cache
on the Endeavor doesn't work at 133MHz.  The documentation that came with
the MB is pretty poor and I can't see any obvious jumpers, switches, or
BIOS options that might make it work.  If anyone has any ideas at this
point, let me know.  (yeah, I know, buy ASUS)

  -Dan