On Thursday 21 March 2002 02:09 pm, David Guntner wrote:
> Tom Brinkman grabbed a keyboard and wrote:
> > but I betcha cpuburn would'a ;)
>
> 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'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.
> My +3.3v display is currently showing 3.55, so that sounds good.
> :-)
Yeah, that's the same as several Soyo boards I've used. I credit
it with my still being able to run very old pc100 at 135mhz, cas2.
Asus is another brand besides Sony, Epox and MSI and a few other good
quality mobo's which provide extra I/O by default. Probly why they're
always on AMD's recommended list ;)
> BTW, when running sensors-detect, it mentioned that you didn't need
> to do certain modprobe commands if those modules were already built
> in to the kernel. Is there an easy way to determine if a given
> module is compiled into the kernel?
> --Dave
Mandrake kernels have had the i2c modules included since
2.2.teens IIRC. A 'locate' will show a sh!+load of 'em in
/usr/src/linux-2<kernel_version>/drivers/ Beginning with the
Christmas Cooker 8.2, I got an error durin boot that 'i2c-proc'
wasn't loaded successfully, but looking later in the boot process the
needed i2c modules were. Even with the boot error mesg, 'sensors'
still worked good as ever.
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.
Anyhow, I'm glad you seem to have found your problem, still
surprised memtest86 didn't find it. 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.
--
Tom Brinkman Corpus Christi, Texas
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
