Tom Brinkman grabbed a keyboard and wrote:
>
> On Thursday 21 March 2002 02:09 pm, David Guntner wrote:
> >
> > It may well have. But after what I've read about the program,
> > there's no way in hell I was going to run it without a way to
> > actively monitor my CPU temp while it was running. :-) Running
> > "sensors" now shows temp1 as 27 degrees C, and temp2 & temp3 as 32
> > degrees C. (Am I correct in assuming that temp1 is the motherboard
> > temp?)
>
> IIRC, you can run 'sensors-detect' again and it might indicate for
> sure which temp is which when temp1, temp2, temp3 is given. But yes,
> it's a pretty safe bet that temp1 is the chipset on the motherboard
> (again not a core temp), and temp2 is the cpu. temp3 might just be
> your video card. When I had a Voodoo3, it was reported as temp3. My
> current nVidia card lacks this hardware capability (Geforce2).
I do have a Voodoo3 in the machine, so that must be it.
> I'd guess that since you're seein an idle to low load cpu temp of
> 32C, that when you run cpuburn's 'burnK6', don't let the cpu temp go
> over 50C, 45C would be better.
I'll keep that in mind then, for when I finally get around to trying it
out.
> There was a discussion of this recently on the cooker mailing
> list. Some said to put the modules that 'sensors-detect' specified
> in /etc/modules rather than /etc/modules.conf. I found that simply
> leaving the modules in modules.conf, but also adding 'i2c-proc' to
> etc/modules made the boot error mesg go away.
It's probably one of those "either-or" situations. Either way probably
works, it's just a matter of asthetics. :-)
> Anyhow, I'm glad you seem to have found your problem,
So far, so good. It's been running straight for 1 day, 6 hours as of my
writing this. I'm going to give it another two days, and if it is still
holding up, I'm putting the 550MHz CPU back in and let it run a week. If
it continues to run, I'm going to formally declare "problem solved," and
then go out and buy another memory DIMM to replace the bad one. I much
prefer running 256M instead of 192M. :-)
> still surprised memtest86 didn't find it.
That makes two of us. :-)
> Makes an additional case for runnin cpuburn. It's an old overclockers
> tool to verify stability, but IMO, should be run on any decent system.
> If a desktop can run cpuburn for an hour, it should be bulletproof to
> run 24/7 till the cows come home ;) If it can't run cpuburn... it
> ain't decent.
Gives new meaning to "smoke test," eh? :-)
FWIW, I've been running my Linux box one a 24/7 basis for many months
(probably close to a year) with no power-offs except for when I've had to
play with something inside. Er, barring the occasional memory problem,
that is.... :-)
Thanks again for all the help!
--Dave
--
David Guntner GEnie: Just say NO!
http://www.akaMail.com/pgpkey/davidg or key server
for PGP Public key
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
