I'm sure that Tom will explain his reasoning on the bios temp thing, but as he's probably asleep right now, let me butt in. I suspect that the difference between using sensors and rebooting then looking at the bios is just timing. i.e. Using sensors you can see the temp while the cpu is under load. By the time you've shut down and brought up bios screens, the load is long gone and the temp not indicative.
Brian On Thu, 2002-03-21 at 06:32, David Guntner wrote: > Tom Brinkman grabbed a keyboard and wrote: > > > > Type 'sensors' in a term. You should see somethin like > > SYS Temp: +28.8�C (limit = +60�C, hysteresis = +50�C) > > CPU Temp: +44.0�C (limit = +60�C, hysteresis = +50�C) > > SBr Temp: +23.2�C (limit = +60�C, hysteresis = +50�C) > > There maybe numbers associated, eg, temp 1, temp2, etc. In my > > example cpu temp is number 2. > > I think whatever this program needs is not available with the motherboard > that I'm using. I typed "sensors," and then when I ran it a second time > after I did a "modprobe i2c-proc" in response to the first attempt's > complaining about it (oops :), it reported "No sensors found!" So, > whatever it's expecting to be on my motherboard for that program to > interface with, doesn't seem to be there. > > > In Gkrellm's configuration, under > > Builtins | Sensors, you would type 'cpu' (w/o the quotes) in the > > second line under 'Sensor Label'. Cpu temp should then be reported. > > Gkrellm can be configured to show temps in C or F, but sensors and > > most everybody else uses Celsius. > > Unfortunately, gkrellm's configuration on my machine has no "sensors" under > Builtins. I'm guessing that's due to whatever caused the "sensors" program > to report that there aren't any. > > > > At least when I reboot to look at it in the BIOS, it's well below > > > that. > > > > Should be about 30C lower. Just to repeat what I said before. > > The bios temp is all but useless. Also, for AMD cpu's, the temp is > > from an external probe in contact with the cpu die, or measured from > > a pin. It is always 10 to 20C less than the actual core temp, could > > be as much as 30C less. > > I accept what you're saying about BIOS temps, but it seems to be the only > thing I have available to me with this motherboard. FWIW, my Linux system > has been running all night, and I just did some things with it (which would > bring the load up a little bit), and then rebooted to get into the BIOS > setup to look at the reading. It's currently showing 39 degrees C (102 F), > which is 30 degrees below the number(s) you reported previously. So I > don't think it's a CPU temp issue. Also (in case you missed in in one of > my earlier messages), when this problem started, I took out the 550MHz CPU > I had in there at the time and fell back to my old 350MHz CPU, to see if it > *was* the CPU. The problem continued even after swapping out CPUs. > > BTW, you make a big deal out of the BIOS reported temprature not being > worth much (which I accept), but then go on to recommend these sensor > programs (which apparently don't work with my motherboard :). Aren't > *they* just pulling numbers from the BIOS? I'm just asking because I've > gotten the impression that you think those are more accurate, and if that's > the case, I'm curious as to how since it seems like they'd still be getting > the same bad numbers that the BIOS setup page would be reporting.... > > One (new) thing of note: Last night when I got home from work, I shut down > the machine and reseated all three DIMM modules. After doing that, my > machine refused to start at all. Well, one time it started to boot and > then just hung in the middle of the boot - after that, I couldn't get the > machine to do *anything* when powered on (or just the reset button pushed). > I started pulling DIMMs one at a time and found that when one particular > DIMM is in the system, it won't start. When it's out, the machine will > come up fine. (And yes, I moved one of the other modules to the slot that > the troublemaker was in, to make sure it wasn't the slot. :) So, either I > managed to fry that DIMM when I was reseating it, or that module was doing > a slow die on me and it finally just gave up the ghost. A few days of > running the machine should give me an idea - this last week I haven't been > able to get the machine to stay up for more than 48 hours without locking > up. If it runs for a week, I'm going to chalk it up to "problem solved" > and go buy another DIMM to replace it. Well, actually, if it stays up a > week, I'm putting the 550MHz chip back in first and then run it for another > week. :-) > > Again, thanks for all the information. It has been most interesting. > > --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
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
