From owner-freebsd-smp Sun Nov 19 17:33:24 2000 Delivered-To: freebsd-smp@freebsd.org Received: from gtei2.bellatlantic.net (gtei2.bellatlantic.net [199.45.39.161]) by hub.freebsd.org (Postfix) with ESMTP id 1B09837B479 for ; Sun, 19 Nov 2000 17:33:22 -0800 (PST) Received: from seth-f1pgytg8r3 (client-64-223-145-91.bellatlantic.net [64.223.145.91]) by gtei2.bellatlantic.net (8.9.1/8.9.1) with SMTP id UAA15497; Sun, 19 Nov 2000 20:33:06 -0500 (EST) Message-Id: <3.0.6.32.20001119203634.00c689f8@hobbiton.shire.net> X-Sender: seth-pc@hobbiton.shire.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 19 Nov 2000 20:36:34 -0800 To: Ernie Elu From: Seth Leigh Subject: Re: Abit BP6 failures Cc: freebsd-smp@FreeBSD.ORG In-Reply-To: <200011192209.eAJM9Vq01712@spooky.eis.net.au> References: <3.0.6.32.20001119100352.00c41248@hobbiton.shire.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yeah, in fact I think it may have something to do with the chipset, since it didn't do it when it was new, but it sometimes does it now. I have been overclocking this machine since day 1, and I have noticed a bit of a degradation in its ability to be overclocked. For a long time I ran the Celeron 400s at 552 MHz, but now it isn't stable at 552, and I have to run it at 480 MHz, where it is rock solid. Why won't it run at 552 anymore? I believe it is actual degradation of either one or both of the CPUs, or else the chipset. I am going to pull the motherboard out, remove the heatsink from the BX chip on the motherboard, and put some heatsink compound underneath it, and mount a fan onto the heatsink. I will then try going back up to 552 MHz. The motherboard is a year and a half old as it is, so I don't really care if I risk frying it, since if I fry it I will just replace it with an 850 MHz or 900 MHz Athlon. If I don't fry it I will hold onto it for another 6 or 8 months and replace it with a dual Athlon, which I assume will be shipping by then. Seth At 08:09 AM 11/20/2000 +1000, you wrote: >> Actually yes, I have had this problem with my BP6. It isn't running >> FreeBSD though, this machine is running just Win2K and Solaris 2.8. >> >> What will happen is that sometimes, after shutting it down, is that when I >> go to reboot it it will just do *nothing* after I power it on, no display >> on the screen or anything. When that happens (which isn't all the time) I >> will just cycle the switch on the back of the case (the switch that >> directly turns off the power supply), and then cycle it back on and hit the >> On button on the front panel of my machine again. When this problem occurs >> it usually takes between 1 and 4 such cyclings to get it to boot up. >> >> I thought I was the only one with this problem. Oh well. >> >> The nice thing is that I hardly ever shut this machine down. It runs >> either Win2K or Solaris 24/7, so the problem isn't too annoying. Also, it >> doesn't always fail to boot up when I have shut it down, perhaps it does it >> a third of the time. >> >> Other than that, I have had zero problems with my BP6 under those two OSes. >> I love it, it is a year and a half old and has been running 2 Celeron 400s >> at either 552 MHz or 480 MHz ever since I built it. >> >> Oh yeah, I water cooled the CPUs. :-) >> >> (www.2coolcomputer.com is where I got the water blocks to do this) >> >> Seth Leigh >> > >Oh well it's good to see I am not the only one with the problem, looks like >a design fault in the BP6, I noticed that the problem almost goes away if >you only have a single CPU fitted. I wonder if that means the BX chip has >cooked itself over time. > >- Ernie. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message