You are not logged in.
Pages: 1
I upgraded the kernel and now sensors isn't displaying my core temp correct for my core2 duo. Help?
Edit: It looks like it's raised the temps 15C.

Interesting, Crit used to be 85...
Edit again: Oh and I booted into windows to check against Speedfan...which says that it's acting like normal. Sensors has gone mad!!!11
Last edited by Gauvenator (2008-05-27 22:16:40)
Offline
Maybe the modules changed since the last kernel. Try
modprobe coretempand try again.
Use
sensors-detectto see what module you need.
For lack of better words: chair, never, toothbrush, really. Ohw, and fish!
Offline
Maybe the modules changed since the last kernel. Try
modprobe coretempand try again.
Usesensors-detectto see what module you need.
Thx.
Tried it and it's still acting up....hmm.
Offline
hmm, these seem normal values for a C2D. The crit temp I think can be changed in either bios or sensors's config. Is your problem solved? Or do you think the temps reported by sensors are wrong?
For lack of better words: chair, never, toothbrush, really. Ohw, and fish!
Offline
hmm, these seem normal values for a C2D. The crit temp I think can be changed in either bios or sensors's config. Is your problem solved? Or do you think the temps reported by sensors are wrong?
On my watercooling this is not normal. Usually I max out around 45C (43-44 folding) and idle high 20's. Them temps are wrong by sensors, but it is odd that it would be by 15C, which is also the difference that the new crit is (85 before 100 now...)
At least it is a linear difference and not just completely random
Maybe there's a way to change the crit temp?
Offline
I think you can change the crit temp in /etc/sensors3.conf, but I'm not 100% on that. Also, on my PC I'm able to set a crit temp in my bios. Coincidentally, this is the same crit temp sensors uses, but I did not bother to check if I can really set this from my bios.
It would be strange if your reported temp would change if you changed the crit temp though... hmm...
For lack of better words: chair, never, toothbrush, really. Ohw, and fish!
Offline
Same problem here, i'll check that sensors3.conf soon and in the bios for crit temp. http://bbs.archlinux.org/viewtopic.php? … 91#p376291
ARCH64 | XMonad | Configs | myAURpkgs | ArchWiki Contribs | Screenies
Offline
Intel calibrated the sensors to be most accurate near the critical temperature, so they report the difference between the the crit. and current temp.
Programs like coretemp have to substract the value the cpu reports from the crit. one. That means for example: current = 100C - sensorvalue.
But the problem is that Intel releases these ciritcal temperatures only for their mobile processors, so if you have a desktop cpu, coretemp will set a crit. temp which it think _could_ fit. The older C2D should be right with 100C, while the newer 45nm E8x00 Wolfdales should be at 95C.
Last edited by MONVMENTVM (2008-06-04 11:00:19)
Offline
Pages: 1