2008/2/4, Beso <givemesugarr@gmail.com>:


2008/2/4, ionut cucu <cuciferus@gmail.com>:
On Sun, 3 Feb 2008 15:49:47 +0000
Beso <givemesugarr@gmail.com> wrote:

> 2008/2/3, ionut cucu <cuciferus@gmail.com>:
> >
> > On Sun, 3 Feb 2008 13:55:56 +0000
> > Beso <givemesugarr@gmail.com> wrote:
> >
> > > 2008/2/3, ionut cucu <cuciferus@gmail.com>:
> > > >
> > > > Hi List,
> > > > I've just bought a new laptop Acer 5715Z and I've have the
> > > > following issue the processor overheats until the laptop
> > > > closes(100 degrees Celsius). This happened when I had two
> > > > parallel emerges. So I went to the shop and changed it with
> > > > another one, same model. This one can hold up to 3 parallel
> > > > emerges but it overheats when I'm watching a movie, again it
> > > > reaches the 100 degrees limit. I'm I doing something wrong
> > > > here? I'm I missing something (this is the first laptop I
> > > > have) ?. Or just by coincidence this one is broken too. I've
> > > > looked on the Internet but I hadn't found any similar issues.
> > > > Thanks! -- gentoo-amd64@lists.gentoo.org mailing list
> > > >
> > > > first: maybe the thermal isn't set right.
> > > what does cat /proc/acpi/thermal_zone/THRM/trip_points says?!
> > > mine is something like this:
> > >
> > > critical (S5):           105 C
> > > passive:                 76 C: tc1=3 tc2=1 tsp=150 devices=CPU0
> > > active[0]:               67 C: devices= FN1
> > > active[1]:               57 C: devices= FN2
> > >
> > > you might have different values but at least you should have one
> > > active and one passive.
> > I have only the critical level set
> > > second: don't do parallel emerge if you're not sure that the
> > > packages from one emerge don't collide with the ones from the
> > > other. for example, knetworkmanager needs networkmanager which
> > > needs dhcdb which needs dhclient. if you emerge something that
> > > would emerge dhclient then you'd emerge 2 times dhclient or you
> > > might risk one of the 2 emerges to fail because a dep hasn't yet
> > > been installed. you could push up the number of processes to be
> > > build together by increasing the makeopts for example to -j6 or
> > > more. increase the number and see your processors loads. the best
> > > number is the one that puts your processors to about 80% of cpu
> > > so that you'd still have 20% of cpu power to do other things.
> > > also add the niceness option so that you don't see slowdowns when
> > > you compile and use some other program.
> > Well the parallel emerges are done just to load the cpu, after the
> > main installation process, but thanks for the j6 idea
> > > third: have you installed acpi and acer-acpi?! i presume that
> > > you've done it and you're starting both acpi and acer-acpi at
> > > boot. anyway, the important thing is are the trip_points. if you
> > > don't have them then you might need to make a script to get the
> > > thermal temperature and to slowdown manually the processor when
> > > it pushes too much up the temperature.
> > acer_acpi refuses to compile with some file missing error...will
> > search the bugs later, but is it really necessary? if so could you
> > please elaborate a little because I was under the impression that
> > the fans were hardware controlled by default
> > --
> > gentoo-amd64@lists.gentoo.org mailing list
>
>
> acer-acpi is usually necessary for acer notebooks to work well. it is
> mandatory for hotkeys and other stuff and is necessary to correct some
> acer's modifications in the acpi. so for what i know acer-acpi is
> manadatory for acer notebooks as it is asus-acpi on asus notebooks.
> try to see if everything fixes after you install it (try unmasking
> newer versions if you cannot install stable ones).
> the fans are ususally board controlled as it is the passive mode that
> reduces the cpu speed, but they can be forced via scripts.
>
>
>
>
Unfortunately asus_acpi doesn't compile
(http://bugs.gentoo.org/show_bug.cgi?id=208577). So I'm just asking for
the cooling process is it mandatory. The issue here is not some hotkeys
but the temperature...I wish to know weather this one is broken to or
not. From what I've read on the http://code.google.com/p/aceracpi/ this
program/driver is mostly for the lcd, battery lifetime  etc. But being
the second laptop with the same issue makes me wonder...I wish i could
compile this....
--
gentoo-amd64@lists.gentoo.org mailing list

well, we have a little problem about trip points, since the only indicated there is the critical one and you don't have passive ones.
well, we'll need to do a little work on the manual scripts to have the fan work and to be sure that the thermal won't reach critical trip point where it would shutdown.
i'll take a look and post some scripts that should help. you'll have to be sure that you have installed lm_sensors and cpufrequtils and that you have compiled the cpufreq modules into the kernel or as modules and you'll have them loaded at boot. we'll have to make the processor slow down when the thermal goes too high. also i'd like to know what are the capabilities of your processors:
a cat on the /proc/cpuinfo and then on cat /proc/acpi/processor/CPU(x)/info where (x) is the number of the core to know what sort of management it can support. you should have cpu0 and cpu1 if you have a dualcore.


--
dott. ing. beso
i forgot to mention the other files in the cpu and thermal directory. they would help setting up the scripts. also you'll need /dev/cpu/microcode, /dev/cpu/cpuid, /dev/cpu/msr, Intel MCE features, Intel core2/ newer xeon compiled directly into the kernel and not as modules. they're in the processor types and features of the kernel. also you'll need the following from the power management options:
- acpi support
---> everything compiled into the kernel and not as modules with the exception of dock, asus extras, toshiba extras, acpi container, smart battery system which are not mandatory.
- cpu frequency scaling
                                       [*] CPU Frequency scaling                                                                                  
                                       [*]   Enable CPUfreq debugging                                                                             
                                       <*>   CPU frequency translation statistics                                                                 
                                       [*]     CPU frequency translation statistics details                                                       
                                             Default CPUFreq governor (userspace)  --->                                                           
                                       <M>   'performance' governor                                                                               
                                       <M>   'powersave' governor                                                                                 
                                       ---   'userspace' governor for userspace frequency scaling                                                 
                                       <M>   'ondemand' cpufreq policy governor                                                                   
                                       <M>   'conservative' cpufreq governor                                                                      
                                       ---   CPUFreq processor drivers                                                                            
                                       < >   AMD Opteron/Athlon64 PowerNow!                                                                       
                                       <*>   Intel Enhanced SpeedStep (deprecated)                                                                
                                       <*>   ACPI Processor P-States driver                                                                       
                                       ---   shared options                                                                                       
                                       [*]   /proc/acpi/processor/../performance interface (deprecated)

after controlling this and recompiling if necessary reboot (if you've recompiled) and do another cat on the thermal trip points to see if it shows also other states. if it doesn't we will really have to impose the throttling manually when the temperature goes too high. we'll use the cpufreq governor to impose the speed when needed and then we'll impose throttling (processor suspension) when the thermal temp goes too high with it. if your pc supports limits and other speq steps we could have it lower the current state to a lower one to cool off a bit. but for this there's the need to know what your processor can do.
--
dott. ing. beso