How hot is your your Pentium M ?

dr_zayus69 · 06-16-2006, 09:41 PM

i have a Toshiba Satellite 1905-S303 with a Pentium M and it runs 55-60 usually but it heats up pretty quick. If it gets over 70 C for more then a second it automatically shuts off. Im looking into laptop coolers to prevent that. I had to install the omnibook module and i can use that to monitor the heat and control the fan. Could your choice of distro possible make it hotter? Like if you have a big distro with kde? I have Suse 10 on here right now but thinking of trying slackware with fluxbox. Also i was thinking of trying to undervolt it and see if that helped any.

-=Graz=- · 06-16-2006, 10:31 PM

DIstribution would not make any difference at all unforuntately (unless of coarse it has detected an incorect CPU or has set bad trip points for the fan to kick off)..

Is the fan on your machine running once it gets to say 55 degrees?? If the fan is going full speed and the machine still heats all the way to shutdown then it could in fact be a hardware problem.. Or it could be that the sensors are infact reporting the wrong temp.

undervolting may help but i have not done this on a laptop ever before. could be dangerous. I really dont think distibution or desktop enviroment should make to much difference at all though.

dr_zayus69 · 06-16-2006, 11:04 PM

here is the fan policy that omnibook has set by default:

Code:

jeff@linux:/proc/omnibook> cat fan_policy
Fan off temperature:        40 C
Fan on temperature:         50 C
Fan level 2 temperature:    55 C
Fan level 3 temperature:    60 C
Fan level 4 temperature:    61 C
Fan level 5 temperature:    68 C
Fan level 6 temperature:    71 C
Fan level 7 temperature:    71 C
Minimal temperature to set: 25 C
Maximal temperature to set: 95 C

i think it is a hardware issue because i don't think my battery is detected right because the little light says the battery is fully charged and it should be because i always use it plugged in but if i try to start it up not plugged in, in other words with the battery, it shuts off before even getting to log in. Also i know it is a much faster burner but when i tried to burn a cd with the burner it was topping out at 4X so it took forever. I don't use my laptop often so i hadn't taken the time to sort all that stuff out but my desktop pretty much died on me so i guess i will have to now so i can use my laptop till i get a new box.

-=Graz=- · 06-17-2006, 01:48 AM

Hmmm interesting. I know on my old laptop the battery indicates that it is fully charged and it wont start of the battery. the battery would be dead though as it is some 4 years old or so now. sometimes they just stop working.
I would not think that you would have problems with suse or fedora but you could try Ubuntu ? It seems to offer great support for laptop straight out the box..
My machine is running extremely well at the moment (with both Slackware and Ubuntu)..

davidsrsb · 06-17-2006, 04:13 AM

Temperature is going to vary a lot between brands/models because of variation in heatsink performance, airflow and bios decisions.

BSlack · 06-20-2006, 03:12 AM

Quote:

# Set the trip point temperatures (in Celsius)
echo -n "100:0:90:80:58" > /proc/acpi/thermal_zone/THRM/trip_points

...it reverts to default values after few minutes.
Can anybody explain me why?
How can i set the trip points permanently?

-=Graz=- · 06-21-2006, 04:54 AM

Quote:

Originally Posted by BSlack

...it reverts to default values after few minutes.
Can anybody explain me why?
How can i set the trip points permanently?

It will revert back to normal trip point values after a reboot. Im sure there is a conf file that specifies this setting (it could b listed in this thread somewhere)... If not, a somewhat dirty approach could be to add the setting into /etc/rc.d/rc.local
This will apply the setting as root each boot...

BSlack · 06-21-2006, 07:59 AM

Quote:

Originally Posted by -=Graz=-

a somewhat dirty approach could be to add the setting into /etc/rc.d/rc.local
This will apply the setting as root each boot...

Ok, this is my approach, but after a few minutes
the trip point temperatures are reversed to default
values.

The following are the default values at boot:

Code:

[root@SlackTop: TZ1]# pwd
/proc/acpi/thermal_zone/TZ1

[root@SlackTop: TZ1]# cat *
<setting not supported>
cooling mode:   active
polling frequency:       10 seconds
state:                   active[2]
temperature:             54 C
critical (S5):           94 C
passive:                 92 C: tc1=1 tc2=2 tsp=100 devices=0xdffcefa0 
active[0]:               84 C: devices=0xc14e1ea0 
active[1]:               65 C: devices=0xc14e1e00 
active[2]:               16 C: devices=0xc14e1d80

... and what happen while i'm working:

Code:

[root@SlackTop: TZ1]# date
Wed Jun 21 13:39:54 CEST 2006

[root@SlackTop: TZ1]# echo -n "90:85:60:45:16" > trip_points

[root@SlackTop: TZ1]# cat *
<setting not supported>
cooling mode:   active
polling frequency:       10 seconds
state:                   active[1]
temperature:             54 C
critical (S5):           90 C
passive:                 85 C: tc1=1 tc2=2 tsp=100 devices=0xdffcefa0 
active[0]:               60 C: devices=0xc14e1ea0 
active[1]:               45 C: devices=0xc14e1e00 
active[2]:               16 C: devices=0xc14e1d80

 ...
 ...
 ...

[root@SlackTop: TZ1]# date
Wed Jun 21 14:03:07 CEST 2006

[root@SlackTop: TZ1]# cat *
<setting not supported>
cooling mode:   active
polling frequency:       10 seconds
state:                   active[2]
temperature:             54 C
critical (S5):           94 C
passive:                 92 C: tc1=1 tc2=2 tsp=100 devices=0xdffcefa0 
active[0]:               84 C: devices=0xc14e1ea0 
active[1]:               65 C: devices=0xc14e1e00 
active[2]:               16 C: devices=0xc14e1d80

Any idea about that?
I'd like to set the temperatures once, at boot time,
but it seems that I'm not doing it in the right way.

Fluxx · 06-21-2006, 12:20 PM

I use a Centrino M (Siemens Fujitsu Amilo) with acpi kernel modules (2.6.16.20 Slackware-current) and speedstep-centrino kernel module with cpuspeed running as daemon.

Even with overclocked ATI Radeon X600SE the temperature in normal usage is about 47 ° C, the fan is not running. If the temperature is over 50° C the fan is in state 1. If I play a 3D-game (torcs in fullscreen-mode) or rip a dvd with mencoder (so that the cpu is running permanently with 100 %) the temperature is about 65 ° C and the fan is running in state 3 (I can hear it, that there are 3 states).

My system has no cooling_mode enabled, the critical temperature is 100 ° C.

Here the output of "cat /proc/acpi/thermal_zone/THRM/*"

Code:

<setting not supported>
cooling mode:	critical
polling frequency:       <setting not supported>
state:                   ok
temperature:             47 C
critical (S5):           100 C

Fluxx.

johnson_steve · 06-21-2006, 12:44 PM

If it makes you intel guys feel any better the fan on my powerbook G3 doesn't even turn on until it hits 75C and is usually around 60C if it's been running for a while. I checked it out and yes thats how hot it's supposed to run. the bottom of the case is a heat spreader; so the whole bottom gets quite hot. so if you think your lap is hot borrow a mac.

the_real_absinthe · 06-21-2006, 01:59 PM

here's my pentium M on an acer aspire 1692 (pentium M 740) inside a small room with around 27 °C: its running from 14:00 at full speed training a neural net (now it's 21:00 so it is running from 7 hours constantly at top speed)

Code:

utente@laptop:/proc/acpi/thermal_zone/THRM$ cat *
<setting not supported>
cooling mode:   passive
<polling disabled>
state:                   ok
temperature:             66 C
critical (S5):           97 C
passive:                 93 C: tc1=2 tc2=3 tsp=40 devices=0xdfe014a0

the fan is active at low speed.

-=Graz=- · 06-22-2006, 03:01 AM

BSlack, this is interesting - your right!

Um.... One thing i have noticed is that in /proc/acpi/thermal_zone$ there are two directories on my machine.
THRC and THRS - im unsure of what the difference between the two are but they both seem to have the same conf files inside/
maybe worth applying the setting to the one that your not currently.

BSlack · 06-22-2006, 04:23 AM

Quote:

Originally Posted by -=Graz=-

One thing i have noticed is that in /proc/acpi/thermal_zone$ there are two directories on my machine

There are 3 directories in my /proc/acpi/thermal_zone :
C1FA, C1FB and TZ1; all with the same files.
I think the first 2 are for some sensors on the main board,
indeed their temperature never changes.
I'm quite sure that TZ1 is for the CPU because
the fan runs in agreement with the trip point temperatures.

I'm wondering who resets the trip point temperatures
whenever I modify them... the kernel? acpid?
I tried to look for some hints in the kernel documentation
without success. Is there any config file somewhere?

----

My laptop is a COMPAQ Evo N610c.
/proc/cpuinfo says it's a
Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz.
I run Slackware (updated to current) with the official
kernel 2.6.16.20 from the slackware-current/testing.
Usually the temperature is ~ 50 °C and it raises up to 70 °C
and more when I run intensive jobs (compiling, audio encoding...).
At usual system loads the heat comes from the HD to a large extent.

-=Graz=- · 06-22-2006, 05:50 AM

i have not actually seen any of those 3 x directories you listed for some reason. Other folk earlier in this thread also noted the ones that i have listed..

The newest kernel i have used is 2.6.15.x not .16 , maybe something has changed..

Ill look into this a bit more tomorrow when i have more time - good luck though

BSlack · 06-22-2006, 08:12 AM

Quote:

Originally Posted by -=Graz=-

i have not actually seen any of those 3 x directories you listed for some reason. Other folk earlier in this thread also noted the ones that i have listed..

The number of directories and their names depends
on the hardware (chipsets, cpu, ...) and on BIOS.

Anyway, it seems I finally found the answer

:
http://acpi.sourceforge.net/index.html

(at a very first sight) it seems that the kernel receives
the trip points (and all the other info) from the BIOS,
so I guess this is the reason why they are restored.
In fact when you make a change to /proc/acpi/thermal_zone/XYZ/trip_points
you modify the values in the kernel memory not in the BIOS!
At some point the kernel restores the BIOS values,
I don't know why or what event drives this behaviour.
If I have understood well, you can modify the trip points
for the session by means of a _complicated_
kernel patch (check the link above and you will
understand why it's _complicated_

).

A somewhat dirty approach could be to put
echo -n "X:Y:Z:T:W" > /proc/acpi/thermal_zone/XYZ/trip_points
in crontab...