Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)

[Beso]

2007/10/10, Marco Calviani <marco.calviani@×××××.com>:
>
> Hi Beso,
>   sorry i misunderstood your suggestion. I did what you suggest and
> this is the result of the trip_points:
>
> critical (S5):      100C


wow.... you don't have anything that says to the cpu to slow down when it
reaches some point....
now, to add some other trip points you have to copy these in a konsole with
root priviledges:
echo "passive:                 78 C: tc1=3 tc2=1 tsp=150 devices=CPU0 \
active[0]:               68 C: devices= FN1 \
active[1]:               58 C: devices= FN2" >>
/proc/acpi/thermal_zone/TZ01/trip_points

then do a cat on the thermal_zone/TZ0/trip_points to see if you've added the
lines for passive and active  lines.
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't turn down the
speed of the processor, below 58 it will turn off the fan.

>
which i suppose is the reason why at that temperature the laptop switch off.
> So, nothing except for the critical state. Should i have to add there
> something?


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'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'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:

  Battery #1     : charging, 46.00%, 01:17:04
>   AC adapter     : on-line
>   Thermal zone 1 : activ, 58 C


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't have acpitool try acpi -t (you'll surely have either one or the
other) and it should indicate the thermal state and temperature. if this
command don't give you these infos then you'll have to be very careful using
your pc since acpi probably don'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).
you may need some additional acpi modules, like ibm_acpi for example, but
that depends on your's pc brand. i'm looking around to see if there were
someone that had problems with santarosa and linux acpi, but for the moment
i couldn't find something useful. try what i'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'll have a functional system. let me know
if you were succesful on that.


An additional problem is this:
> doing a
> $ cat /proc/acpi/thermal_zone/TZ01/temperature
> it gives only a:
>
> temperature:     0C
>
> My question is:
> even if i change the polling frequency, how the fan can start if the
> temperature gives 0??
> Do you know if it's possible to link the fan start with the core
> temperature instead of the ACPI thermal zone?


probably the fan don't start since  you have it as a module. i'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....

Regards,
> m
>
> >
> > thats why i told you to do this commanda:
> > > echo "2 seconds" >
> > /proc/acpi/thermal_zone/TZ01/polling:frequency
> > >
> >  this enables the polling of your thermal every 2 seconds. this should
> be
> > enough.
> > do you have the other file that i mentioned:
> > > /proc/acpi/thermal_zone/TZ01/trip_points ?!
> > this sets the trip points for your processor. whitout it you governor
> cannot
> > understand what to do even if it polls right.
> >
> > as for the kernel thigs, set these options:
> > select processor type: intel core2 instead of normal x86
> > CONFIG_X86_SPEEDSTEP_CENTRINO=y instead of m
> > CONFIG_ACPI_FAN=y instead of m
> > CONFIG_MICROCODE=y instead of m (for what i know cpu micocode is needed
> on
> > intels)
> > CONFIG_K8_NUMA=n instead of y (this should be the amdk8 numa, that you
> > should not need. if it's not then let him be)
> > CONFIG_X86_MCE_AMD=n instead of y (you don't need amd mce features since
> > they are not included into intel cpus)
> > CONFIG_NR_CPUS=32 <-- this leaves me a little dazzled: do you really
> have 32
> > cpus in your core?! for what i know this sets the real number of cpus
> inside
> > the kernel, but i might be wrong. so if this is really what i think it
> is,
> > ie the real nr of cpus (not virtual ones) set this to 2 or 4 based on
> your
> > cpu cores.
> > CONFIG_HOTPLUG_CPU=n instead of y (i don't really think that you'll
> unplug
> > your cpu from your laptop when the laptop is still running considering
> that
> > you don't use multi cpus but a single multicore cpu. the same goes for
> > memory hotplug: i don't think that your laptop supports it, so just
> disable
> > it.)
> > for what i have seen the acpi problems may be due to a failure in
> loading
> > the intel speedstep module. if you look into the modules loaded (lsmod)
> you
> > should not see it. so it's better to insert it directly in the kernel,
> since
> > it is one of the first modules called (if you use it as a module you
> should
> > be loading it with initramdisk before loading acpi to have a full acpi
> > configuration).
> > try setting these options and recompile and install the new kernel and
> > modules and reboot (kexec is not working on my amd turion with 64bit
> enabled
> > and so may also be for your core2duo).
> >
> >  2007/10/10, Marco Calviani <marco.calviani@×××××.com>:
> > > Sorry i missed the attachment.
> > >
> > > regards,
> > > m
> > >
> > >
> >
> >
> >
> > --
> > dott. ing. beso
> --
> gentoo-laptop@g.o mailing list
>
>


-- 
dott. ing. beso