From owner-freebsd-questions Fri Dec 1 12:20:16 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA22285 for questions-outgoing; Fri, 1 Dec 1995 12:20:16 -0800 Received: from gdwest.gd.com (gdwest.gd.com [134.120.3.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA22275 for ; Fri, 1 Dec 1995 12:20:11 -0800 Received: (from eyfarris@localhost) by gdwest.gd.com (8.6.10/8.6.10) id MAA12976; Fri, 1 Dec 1995 12:20:09 -0800 Date: Fri, 1 Dec 1995 12:20:09 -0800 From: Eblan Y Farris Message-Id: <199512012020.MAA12976@gdwest.gd.com> To: dmuntz@eecs.umich.edu, questions@freebsd.org Subject: Re: Intel Endeavor MB cache problem Sender: owner-questions@freebsd.org Precedence: bulk Dan Check your switch setting and make sure that sw's 1,6,7,8 are on. Also, where did you get the board and/or cache module? What type of cache module is it, including timing. What type of SIMMs do you have? I will be checking this board at 133MHz this weekend and will let you know. efarris@surfusa.com ----------------------------------include--------------------------------- > 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 -------------------------------------------------------------------------