RE: sysutils/cpuburn lives up to its name

2002-11-12 Thread David Daugherty
 [mailto:owner-freebsd-questions;FreeBSD.ORG] On Behalf Of Ray Kohler
 The subject explains it pretty well -- last night
 I ran burnK7 from the cpuburn port and my system is
 toast. Now I'm trying to figure out just what it
 was I killed so I can replace it.
 About 40 seconds into the run, the system switched
 the power off. Now it won't switch back on again.
 ACPI was disabled (relevant, since this was -current)
 but APM was on. I know the power supply is good
 since the on-board NIC shows a link on the Linksys
 it's attached to, and that only happens when it has
 power. The system just does nothing when I push the
 power switch.
 So what needs replaced? The Motherboard? The CPU?
 Something else?
Generally, when this happens it's best to remove everything from the box
except for things necessary. Remove it all except the video card, then
try to boot and see if you can get the video's BIOS to pop up. Then put
the memory back and try booting again. Then put the hard drive back in
and try booting again. You should get the idea from here on out ;-)

---
| /\ \/ @

[EMAIL PROTECTED]
DataSphere - Databases, back end web programming and networking
360.656.6226
ICQ: 21106703 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: sysutils/cpuburn lives up to its name

2002-11-11 Thread Gary W. Swearingen
Ray Kohler [EMAIL PROTECTED] writes:

 power. The system just does nothing when I push the
 power switch.
 So what needs replaced? The Motherboard? The CPU?
 Something else?

I don't know ACPI/APM, so can't help much.  I did read recently a
comment that a good motherboard's Power-On Self Test will beep a certain
code if it is booted with its CPU (or maybe other parts?) missing,
giving a clue as to whether the problem is the CPU or not.  I'm guessing
that if it does nothing with the CPU and beeps without the CPU, then you
suspect the CPU first, but if it does nothing without the CPU, you
suspect other things first.  But what you suspect first depends on how
easy it is for you to get a temporary or permanent replacement for it.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message