Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-laptop
Navigation:
Lists: gentoo-laptop: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-laptop@g.o
From: Beso <givemesugarr@...>
Subject: Re: Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
Date: Wed, 10 Oct 2007 21:17:34 +0200
<br><br><div><span class="gmail_quote">2007/10/10, Marco Calviani &lt;<a href="mailto:marco.calviani@...">marco.calviani@...</a>&gt;:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Beso,<br>&nbsp;&nbsp;sorry i misunderstood your suggestion. I did what you suggest and<br>this is the result of the trip_points:<br><br>critical (S5):&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;100C</blockquote><div><br>wow.... you don&#39;t have  anything that says to the cpu to slow down when it reaches some point....
<br>now, to add some other trip points you have to copy these in a konsole with root priviledges:<br>echo &quot;passive:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 78 C: tc1=3 tc2=1 tsp=150 devices=CPU0 \<br>active[0]:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 68 C: devices= FN1 \
<br>active[1]:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 58 C: devices= FN2&quot; &gt;&gt; /proc/acpi/thermal_zone/TZ01/trip_points<br><br>then do a cat on the thermal_zone/TZ0/trip_points to see if you&#39;ve added the lines for passive and active&nbsp; lines.
<br>that means that when your thermal reaches 78 degrees it will slow down the processor. from 58 to 68 it will turn on the fan but don&#39;t turn down the speed of the processor, below 58 it will turn off the fan.<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"></blockquote></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
which i suppose is the reason why at that temperature the laptop switch off.<br>So, nothing except for the critical state. Should i have to add there something?</blockquote><div><br>if the pc turns down then it can read from somewhere the actual thermal point. you try to see after actually setting the things i&#39;ve just said, if your pc is behaving as it should. remember to also turn on the polling frequency. without it it will not look for thermal changes. and remember to actually compile the mce and speedstep features in the kernel and not as module and reboot and then set the things i&#39;ve mentioned. after that type acpitool (it should be installed by default with the acpi package) and see what it says. it should give something like this:
<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">&nbsp; Battery #1&nbsp;&nbsp;&nbsp;&nbsp; : charging, 46.00%, 01:17:04<br>&nbsp; AC adapter&nbsp;&nbsp;&nbsp;&nbsp; : on-line<br>&nbsp; Thermal zone 1 : activ, 58 C
</blockquote><div><br>it indicates, as you can see not only the battery and ac status but also the current processor mode (active) and the current thermal temperature.... if you don&#39;t have acpitool try acpi -t (you&#39;ll surely have either one or the other) and it should indicate the thermal state and temperature. if this command don&#39;t give you these infos then you&#39;ll have to be very careful using your pc since acpi probably don&#39;t support santarosa well. you should then unmask newer acpi in portage (adding acpi in /etc/package.keywords) and try with the new acpi (
1.0.6).<br>you may need some additional acpi modules, like ibm_acpi for example, but that depends on your&#39;s pc brand. i&#39;m looking around to see if there were someone that had problems with santarosa and linux acpi, but for the moment i couldn&#39;t find something useful. try what i&#39;ve said and see if the things work. if they work then append the tweak in some script that starts at boot like the top of xdm script and you&#39;ll have a functional system. let me know if you were succesful on that.
<br></div><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">An additional problem is this:<br>doing a<br>$ cat /proc/acpi/thermal_zone/TZ01/temperature
<br>it gives only a:<br><br>temperature:&nbsp;&nbsp;&nbsp;&nbsp; 0C<br><br>My question is:<br>even if i change the polling frequency, how the fan can start if the<br>temperature gives 0??<br>Do you know if it&#39;s possible to link the fan start with the core
<br>temperature instead of the ACPI thermal zone?</blockquote><div><br>probably the fan don&#39;t start since&nbsp; you have it as a module. i&#39;ve curently had the same problem which solved by compiling it integrated in the kernel. the fan in your case should always be on, not always be off.... 
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Regards,<br>m<br><br>&gt;<br>&gt; thats why i told you to do this commanda:<br>
&gt; &gt; echo &quot;2 seconds&quot; &gt;<br>&gt; /proc/acpi/thermal_zone/TZ01/polling:frequency<br>&gt; &gt;<br>&gt;&nbsp;&nbsp;this enables the polling of your thermal every 2 seconds. this should be<br>&gt; enough.<br>&gt; do you have the other file that i mentioned:
<br>&gt; &gt; /proc/acpi/thermal_zone/TZ01/trip_points ?!<br>&gt; this sets the trip points for your processor. whitout it you governor cannot<br>&gt; understand what to do even if it polls right.<br>&gt;<br>&gt; as for the kernel thigs, set these options:
<br>&gt; select processor type: intel core2 instead of normal x86<br>&gt; CONFIG_X86_SPEEDSTEP_CENTRINO=y instead of m<br>&gt; CONFIG_ACPI_FAN=y instead of m<br>&gt; CONFIG_MICROCODE=y instead of m (for what i know cpu micocode is needed on
<br>&gt; intels)<br>&gt; CONFIG_K8_NUMA=n instead of y (this should be the amdk8 numa, that you<br>&gt; should not need. if it&#39;s not then let him be)<br>&gt; CONFIG_X86_MCE_AMD=n instead of y (you don&#39;t need amd mce features since
<br>&gt; they are not included into intel cpus)<br>&gt; CONFIG_NR_CPUS=32 &lt;-- this leaves me a little dazzled: do you really have 32<br>&gt; cpus in your core?! for what i know this sets the real number of cpus inside<br>
&gt; the kernel, but i might be wrong. so if this is really what i think it is,<br>&gt; ie the real nr of cpus (not virtual ones) set this to 2 or 4 based on your<br>&gt; cpu cores.<br>&gt; CONFIG_HOTPLUG_CPU=n instead of y (i don&#39;t really think that you&#39;ll unplug
<br>&gt; your cpu from your laptop when the laptop is still running considering that<br>&gt; you don&#39;t use multi cpus but a single multicore cpu. the same goes for<br>&gt; memory hotplug: i don&#39;t think that your laptop supports it, so just disable
<br>&gt; it.)<br>&gt; for what i have seen the acpi problems may be due to a failure in loading<br>&gt; the intel speedstep module. if you look into the modules loaded (lsmod) you<br>&gt; should not see it. so it&#39;s better to insert it directly in the kernel, since
<br>&gt; it is one of the first modules called (if you use it as a module you should<br>&gt; be loading it with initramdisk before loading acpi to have a full acpi<br>&gt; configuration).<br>&gt; try setting these options and recompile and install the new kernel and
<br>&gt; modules and reboot (kexec is not working on my amd turion with 64bit enabled<br>&gt; and so may also be for your core2duo).<br>&gt;<br>&gt;&nbsp;&nbsp;2007/10/10, Marco Calviani &lt;<a href="mailto:marco.calviani@...">
marco.calviani@...</a>&gt;:<br>&gt; &gt; Sorry i missed the attachment.<br>&gt; &gt;<br>&gt; &gt; regards,<br>&gt; &gt; m<br>&gt; &gt;<br>&gt; &gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt; --<br>&gt; dott. ing. beso<br>--<br>
<a href="mailto:gentoo-laptop@g.o">gentoo-laptop@g.o</a> mailing list<br><br></blockquote></div><br><br clear="all"><br>-- <br>dott. ing. beso
Replies:
Re: Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
-- Marco Calviani
References:
Problem with CPU temperature (Santa Rosa CPU)
-- Marco Calviani
Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
-- Marco Calviani
Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
-- Marco Calviani
Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
-- Marco Calviani
Re: Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
-- Beso
Re: Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
-- Marco Calviani
Navigation:
Lists: gentoo-laptop: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
Next by thread:
Re: Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
Previous by date:
Re: Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
Next by date:
Re: Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)


Updated Jun 17, 2009

Summary: Archive of the gentoo-laptop mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.