Reading CPU Core Temp

Adam

Hi again, everybody, and I hope you got whatever gifts you wanted. I
solved my hardware problems of the past few months by buying a new
system, a bottom-of-the-line Compaq (aka HP) desktop with a Celeron 420
CPU, and installing Mandriva 2008.0, kernel 2.6.22.12-desktop-1mdv .
What I can't figure out is how to read the temperature of the CPU core,
which can somehow be read directly from some CPU registers. I gather
that the module 'coretemp' can do just that and has reportedly been
included with the kernel since 2.6.22, but it doesn't seem to be
included in my system, or at least isn't included correctly:

[adam@eris coretemp]$ sudo modprobe coretemp
FATAL: Error inserting coretemp
(/lib/modules/2.6.22.12-desktop-1mdv/kernel/drivers/hwmon/coretemp.ko):
Invalid module format

Could somebody point me in the right direction? I don't really care
whether I use the 'coretemp' module or not, I just want to be able to
read the CPU core temp somehow. Through Google I learned that the raw
value is stored as a difference from some fixed maximum (85C or 100C)
but couldn't find out how to get that value. It must be possible,
because there are Win programs that can do this on my system. Thanks in
advance for any guidance on this!

Adam
--
Email: adam seven zero seven at verizon dot net

Adam

David W. Hodgins wrote:
>> What I can't figure out is how to read the temperature of the CPU core,
>
> shows that within the Celeron
> family, only Celeron-M 400 series, and Celeron E1000 series. Is your cpu
> a mobile, Celeron-M, or just a plain desktop Celeron?

[adam@eris ~]$ uname -p
Intel(R) Celeron(R) CPU 420 @ 1.60GHz

Plain desktop Celeron 420, apparently.

> Trying modprobe -v coretemp fails here with "No such device". I suspect
> we're both stuck with lm_sensors.

[adam@eris ~]$ sudo modprobe -v coretemp
insmod
/lib/modules/2.6.22.15-desktop-1.uc1mdv/kernel/drivers/hwmon/coretemp.ko
FATAL: Error inserting coretemp
(/lib/modules/2.6.22.15-desktop-1.uc1mdv/kernel/drivers/hwmon/coretemp.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

When I hacked the 'sensors-detect' script to always report that core
temperature was available, that didn't get me anywhere because that
forced use of the 'coretemp' module which as you can see is somehow
screwed up on my system.

>> because there are Win programs that can do this on my system.
>
> Are you sure the win programs are reading the core temp, and not a sensor
> value?

"Hardware sensors monitor 4.3" showed "Mainboard xx.x C, CPU1 34.0 C,
Temp3 26.0 C, CPU0 Core 55.0 C", and the 34 and 26 are in line with what
lm_sensors reports. (They don't sound right, but they're consistent.)
"Core Temp 0.96" only shows a core temp, but it's also around 50 C.

I found C source for one version of the coretemp module, but couldn't
understand it. Fortunately I see absolutely no signs of overheating;
I'm just curious. Thanks for your suggestions!

Adam

Adam

Peter D. wrote:
>> What I can't figure out is how to read the temperature of the CPU core,
>
> Have you installed "lmsensors"?

Thanks for the suggestion, Peter. Yep, lm_sensors is installed, but
that only reads the outputs of the sensor chip. (I've figured out what
most of those values indicate on my system, but that's another topic.)
There's some registers in the CPU that measure the actual core temp.

I'm still running lm_sensors version 2.10.4, because version 3 won't
compile correctly on my system. Both use module 'coretemp' to get the
value I'm looking for. I found C source for some version of module
'coretemp' (also won't compile correctly on my system) and will be
looking over it later today. Any suggestions, anybody, on what to do
next? Thanks!

Adam

Darklight

Adam wrote:

> Peter D. wrote:
>>> What I can't figure out is how to read the temperature of the CPU core,
>>
>> Have you installed "lmsensors"?
>
> Thanks for the suggestion, Peter. Yep, lm_sensors is installed, but
> that only reads the outputs of the sensor chip. (I've figured out what
> most of those values indicate on my system, but that's another topic.)
> There's some registers in the CPU that measure the actual core temp.
>
> I'm still running lm_sensors version 2.10.4, because version 3 won't
> compile correctly on my system. Both use module 'coretemp' to get the
> value I'm looking for. I found C source for some version of module
> 'coretemp' (also won't compile correctly on my system) and will be
> looking over it later today. Any suggestions, anybody, on what to do
> next? Thanks!
>
> Adam

i think you might need the k8temp module as i need this to read the
core temperatures of my dual core cpu

Adam

David W. Hodgins wrote:
>> What I can't figure out is how to read the temperature of the CPU core,
>
> shows that within the Celeron
> family, only Celeron-M 400 series, and Celeron E1000 series. Is your cpu
> a mobile, Celeron-M, or just a plain desktop Celeron?

[adam@eris ~]$ uname -p
Intel(R) Celeron(R) CPU 420 @ 1.60GHz

Plain desktop Celeron 420, apparently.

> Trying modprobe -v coretemp fails here with "No such device". I suspect
> we're both stuck with lm_sensors.

[adam@eris ~]$ sudo modprobe -v coretemp
insmod
/lib/modules/2.6.22.15-desktop-1.uc1mdv/kernel/drivers/hwmon/coretemp.ko
FATAL: Error inserting coretemp
(/lib/modules/2.6.22.15-desktop-1.uc1mdv/kernel/drivers/hwmon/coretemp.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

When I hacked the 'sensors-detect' script to always report that core
temperature was available, that didn't get me anywhere because that
forced use of the 'coretemp' module which as you can see is somehow
screwed up on my system.

>> because there are Win programs that can do this on my system.
>
> Are you sure the win programs are reading the core temp, and not a sensor
> value?

"Hardware sensors monitor 4.3" showed "Mainboard xx.x C, CPU1 34.0 C,
Temp3 26.0 C, CPU0 Core 55.0 C", and the 34 and 26 are in line with what
lm_sensors reports. (They don't sound right, but they're consistent.)
"Core Temp 0.96" only shows a core temp, but it's also around 50 C.

I found C source for one version of the coretemp module, but couldn't
understand it. Fortunately I see absolutely no signs of overheating;
I'm just curious. Thanks for your suggestions!

Adam

David W. Hodgins

On Fri, 04 Jan 2008 18:44:24 -0500, Adam <.address> wrote:

> system, a bottom-of-the-line Compaq (aka HP) desktop with a Celeron 420
> CPU, and installing Mandriva 2008.0, kernel 2.6.22.12-desktop-1mdv .
> What I can't figure out is how to read the temperature of the CPU core,

shows that within the Celeron
family, only Celeron-M 400 series, and Celeron E1000 series. Is your cpu
a mobile, Celeron-M, or just a plain desktop Celeron?

Mine has Intel(R) Celeron(R) CPU 2.40GHz,
Family, model, stepping 15, 3, 4 (Pentium 4).

Trying modprobe -v coretemp fails here with "No such device". I suspect
we're both stuck with lm_sensors.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

Adam

David W. Hodgins wrote:
>> What I can't figure out is how to read the temperature of the CPU core,
>
> shows that within the Celeron
> family, only Celeron-M 400 series, and Celeron E1000 series. Is your cpu
> a mobile, Celeron-M, or just a plain desktop Celeron?

[adam@eris ~]$ uname -p
Intel(R) Celeron(R) CPU 420 @ 1.60GHz

Plain desktop Celeron 420, apparently.

> Trying modprobe -v coretemp fails here with "No such device". I suspect
> we're both stuck with lm_sensors.

[adam@eris ~]$ sudo modprobe -v coretemp
insmod
/lib/modules/2.6.22.15-desktop-1.uc1mdv/kernel/drivers/hwmon/coretemp.ko
FATAL: Error inserting coretemp
(/lib/modules/2.6.22.15-desktop-1.uc1mdv/kernel/drivers/hwmon/coretemp.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

When I hacked the 'sensors-detect' script to always report that core
temperature was available, that didn't get me anywhere because that
forced use of the 'coretemp' module which as you can see is somehow
screwed up on my system.

>> because there are Win programs that can do this on my system.
>
> Are you sure the win programs are reading the core temp, and not a sensor
> value?

"Hardware sensors monitor 4.3" showed "Mainboard xx.x C, CPU1 34.0 C,
Temp3 26.0 C, CPU0 Core 55.0 C", and the 34 and 26 are in line with what
lm_sensors reports. (They don't sound right, but they're consistent.)
"Core Temp 0.96" only shows a core temp, but it's also around 50 C.

I found C source for one version of the coretemp module, but couldn't
understand it. Fortunately I see absolutely no signs of overheating;
I'm just curious. Thanks for your suggestions!

Adam

David W. Hodgins

On Fri, 04 Jan 2008 18:44:24 -0500, Adam <.address> wrote:

> system, a bottom-of-the-line Compaq (aka HP) desktop with a Celeron 420
> CPU, and installing Mandriva 2008.0, kernel 2.6.22.12-desktop-1mdv .
> What I can't figure out is how to read the temperature of the CPU core,

shows that within the Celeron
family, only Celeron-M 400 series, and Celeron E1000 series. Is your cpu
a mobile, Celeron-M, or just a plain desktop Celeron?

Mine has Intel(R) Celeron(R) CPU 2.40GHz,
Family, model, stepping 15, 3, 4 (Pentium 4).

Trying modprobe -v coretemp fails here with "No such device". I suspect
we're both stuck with lm_sensors.

> because there are Win programs that can do this on my system.

Are you sure the win programs are reading the core temp, and not a sensor
value?

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

Adam

David W. Hodgins wrote:
>> What I can't figure out is how to read the temperature of the CPU core,
>
> shows that within the Celeron
> family, only Celeron-M 400 series, and Celeron E1000 series. Is your cpu
> a mobile, Celeron-M, or just a plain desktop Celeron?

[adam@eris ~]$ uname -p
Intel(R) Celeron(R) CPU 420 @ 1.60GHz

Plain desktop Celeron 420, apparently.

> Trying modprobe -v coretemp fails here with "No such device". I suspect
> we're both stuck with lm_sensors.

[adam@eris ~]$ sudo modprobe -v coretemp
insmod
/lib/modules/2.6.22.15-desktop-1.uc1mdv/kernel/drivers/hwmon/coretemp.ko
FATAL: Error inserting coretemp
(/lib/modules/2.6.22.15-desktop-1.uc1mdv/kernel/drivers/hwmon/coretemp.ko):
Unknown symbol in module, or unknown parameter (see dmesg)

When I hacked the 'sensors-detect' script to always report that core
temperature was available, that didn't get me anywhere because that
forced use of the 'coretemp' module which as you can see is somehow
screwed up on my system.

>> because there are Win programs that can do this on my system.
>
> Are you sure the win programs are reading the core temp, and not a sensor
> value?

"Hardware sensors monitor 4.3" showed "Mainboard xx.x C, CPU1 34.0 C,
Temp3 26.0 C, CPU0 Core 55.0 C", and the 34 and 26 are in line with what
lm_sensors reports. (They don't sound right, but they're consistent.)
"Core Temp 0.96" only shows a core temp, but it's also around 50 C.

I found C source for one version of the coretemp module, but couldn't
understand it. Fortunately I see absolutely no signs of overheating;
I'm just curious. Thanks for your suggestions!

Adam

Darklight

Adam wrote:

> Peter D. wrote:
>>> What I can't figure out is how to read the temperature of the CPU core,
>>
>> Have you installed "lmsensors"?
>
> Thanks for the suggestion, Peter. Yep, lm_sensors is installed, but
> that only reads the outputs of the sensor chip. (I've figured out what
> most of those values indicate on my system, but that's another topic.)
> There's some registers in the CPU that measure the actual core temp.
>
> I'm still running lm_sensors version 2.10.4, because version 3 won't
> compile correctly on my system. Both use module 'coretemp' to get the
> value I'm looking for. I found C source for some version of module
> 'coretemp' (also won't compile correctly on my system) and will be
> looking over it later today. Any suggestions, anybody, on what to do
> next? Thanks!
>
> Adam

i think you might need the k8temp module as i need this to read the
core temperatures of my dual core cpu