Gentoo Archives: gentoo-laptop

From: Marco Calviani <marco.calviani@×××××.com>
To: gentoo-laptop@l.g.o
Cc: gentoo-user@l.g.o
Subject: Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU)
Date: Sat, 13 Oct 2007 17:01:57
Message-Id: da5cd1900710130949k11e9ad30r28318dd892ab325@mail.gmail.com
In Reply to: Re: [gentoo-laptop] Re: [gentoo-user] Problem with CPU temperature (Santa Rosa CPU) by Beso
1 Just to give a short update:
2 1) no luck with the acer_acpi module: it does not load in the system,
3 as the developer is having a look at it. However he told me that the
4 module can do practically nothing on the thermal zone since this last
5 point is controlled fully by ACPI
6 2) i've tried to modify the DSDT table: it had errors, but also after
7 correction the system behave in practically the same way. I've mailed
8 to the acpi-linux mailing list, hoping that the acpi gurus can try to
9 solve the issue.
10 As far as i understand now it is just a matter of ACPI implementation.
11
12 Regards,
13 m
14
15 On 10/11/07, Beso <givemesugarr@×××××.com> wrote:
16 > normally all acer have dsdt problems and don't work unless you load
17 > acer_acpi.
18 > now, in the portage tree there's only the 0.8.2 version, so you have to go
19 > here:
20 >
21 > http://code.google.com/p/aceracpi/
22 >
23 > download the latest version and install it. there's a 5720 product listed
24 > (under travelmate and not aspire, but it may have been an error). simply
25 > search for acer_acpi in the /lib/modules/2.6.22-gentoo-r8 and delete it then
26 > do a depmod -a and update the modules installed and retry loading the newly
27 > compiled driver. if you manage to get it working in this way ok, if not try
28 > contacting the guy maintaing the aceracpi module and tell him about you
29 > problems. he may be of help.
30 >
31 >
32 > 2007/10/11, Marco Calviani <marco.calviani@×××××.com>:
33 > > Hi Beso,
34 > > i have an Acer Aspire 5720. I've tried with the acer_acpi, it
35 > > compiles well but when it comes to loading it fails, saying
36 > > "No or unsupported WMI interface, unable to load".
37 > >
38 > > However as far as i can understood, this module deals with issues of
39 > > buttons and hotkey not with ACPI issues.
40 > >
41 > > Yes, my DSDT failed during recompiling, but i have managed to solve
42 > > the issues, and now it compiled well (with warning but i'm not
43 > > caring). I'll try to recompile the new DSDT in the kernel, maybe it
44 > > could help (but i'm not sure).
45 > >
46 > > Regards,
47 > > m
48 > >
49 > > On 10/11/07, Beso <givemesugarr@×××××.com> wrote:
50 > > > yep you're right.... i cannot modify my trippoints so this file cannot
51 > be
52 > > > modified....
53 > > > i don't think that it's random, since it is 40 c.... try doing some
54 > > > compiling or so and see if it goes up and then stop compiling and do
55 > nothing
56 > > > and see if it goes down.... this will tell you if thermal is working....
57 > > > for dsdt problem you have follow this guide:
58 > > > http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems
59 > > > if it gives you errors when recompiling dsdt then it may be a dsdt
60 > problem,
61 > > > but if it gives you no problem recompiling it then it may be that you
62 > need
63 > > > some additional modules like asus_acpi or ibm or toshiba ones based on
64 > your
65 > > > pc model. i don't know what you're using (i've managed to see some
66 > lenovo,
67 > > > asus toshiba and acer models around and for what i know every one of
68 > then
69 > > > needs an additional acpi module to have it work correctly). that was why
70 > > > i've asked you for your brand and model name.
71 > > >
72 > > > 2007/10/11, Marco Calviani <marco.calviani@×××××.com>:
73 > > > > Hi Beso,
74 > > > > i've tried with your trip_points modification but it gives this
75 > error:
76 > > > >
77 > > > > bash: echo: write error: Invalid argument
78 > > > >
79 > > > > like i'm not able to write on that file.
80 > > > >
81 > > > > And of course acpitool gives me a random ACPI temperature:
82 > > > >
83 > > > > Battery #1 : charged
84 > > > > AC adapter : on-line
85 > > > > Thermal zone 1 : ok, 40 C
86 > > > >
87 > > > > PS: i followed all your suggestions concerning the microcode and fan
88 > > > > option in the kernel.
89 > > > > Could this be a problem of DSDT?
90 > > > >
91 > > > > regards,
92 > > > > m
93 > > > >
94 > > > > On 10/10/07, Beso <givemesugarr@×××××.com > wrote:
95 > > > > >
96 > > > > >
97 > > > > > 2007/10/10, Marco Calviani < marco.calviani@×××××.com>:
98 > > > > > > Hi Beso,
99 > > > > > > sorry i misunderstood your suggestion. I did what you suggest
100 > and
101 > > > > > > this is the result of the trip_points:
102 > > > > > >
103 > > > > > > critical (S5): 100C
104 > > > > >
105 > > > > > wow.... you don't have anything that says to the cpu to slow down
106 > when
107 > > > it
108 > > > > > reaches some point....
109 > > > > > now, to add some other trip points you have to copy these in a
110 > konsole
111 > > > with
112 > > > > > root priviledges:
113 > > > > > echo "passive: 78 C: tc1=3 tc2=1 tsp=150
114 > devices=CPU0 \
115 > > > > > active[0]: 68 C: devices= FN1 \
116 > > > > > active[1]: 58 C: devices= FN2" >>
117 > > > > > /proc/acpi/thermal_zone/TZ01/trip_points
118 > > > > >
119 > > > > > then do a cat on the thermal_zone/TZ0/trip_points to see if you've
120 > added
121 > > > the
122 > > > > > lines for passive and active lines.
123 > > > > > that means that when your thermal reaches 78 degrees it will slow
124 > down
125 > > > the
126 > > > > > processor. from 58 to 68 it will turn on the fan but don't turn down
127 > the
128 > > > > > speed of the processor, below 58 it will turn off the fan.
129 > > > > > >
130 > > > > > >
131 > > > > >
132 > > > > > > which i suppose is the reason why at that temperature the laptop
133 > > > switch
134 > > > > > off.
135 > > > > > > So, nothing except for the critical state. Should i have to add
136 > there
137 > > > > > something?
138 > > > > >
139 > > > > > if the pc turns down then it can read from somewhere the actual
140 > thermal
141 > > > > > point. you try to see after actually setting the things i've just
142 > said,
143 > > > if
144 > > > > > your pc is behaving as it should. remember to also turn on the
145 > polling
146 > > > > > frequency. without it it will not look for thermal changes. and
147 > remember
148 > > > to
149 > > > > > actually compile the mce and speedstep features in the kernel and
150 > not as
151 > > > > > module and reboot and then set the things i've mentioned. after that
152 > > > type
153 > > > > > acpitool (it should be installed by default with the acpi package)
154 > and
155 > > > see
156 > > > > > what it says. it should give something like this:
157 > > > > >
158 > > > > > > Battery #1 : charging, 46.00%, 01:17:04
159 > > > > > > AC adapter : on-line
160 > > > > > > Thermal zone 1 : activ, 58 C
161 > > > > >
162 > > > > > it indicates, as you can see not only the battery and ac status but
163 > also
164 > > > the
165 > > > > > current processor mode (active) and the current thermal
166 > temperature....
167 > > > if
168 > > > > > you don't have acpitool try acpi -t (you'll surely have either one
169 > or
170 > > > the
171 > > > > > other) and it should indicate the thermal state and temperature. if
172 > this
173 > > > > > command don't give you these infos then you'll have to be very
174 > careful
175 > > > using
176 > > > > > your pc since acpi probably don't support santarosa well. you should
177 > > > then
178 > > > > > unmask newer acpi in portage (adding acpi in /etc/package.keywords)
179 > and
180 > > > try
181 > > > > > with the new acpi ( 1.0.6).
182 > > > > > you may need some additional acpi modules, like ibm_acpi for
183 > example,
184 > > > but
185 > > > > > that depends on your's pc brand. i'm looking around to see if there
186 > were
187 > > > > > someone that had problems with santarosa and linux acpi, but for the
188 > > > moment
189 > > > > > i couldn't find something useful. try what i've said and see if the
190 > > > things
191 > > > > > work. if they work then append the tweak in some script that starts
192 > at
193 > > > boot
194 > > > > > like the top of xdm script and you'll have a functional system. let
195 > me
196 > > > know
197 > > > > > if you were succesful on that.
198 > > > > >
199 > > > > >
200 > > > > > > An additional problem is this:
201 > > > > > > doing a
202 > > > > > > $ cat /proc/acpi/thermal_zone/TZ01/temperature
203 > > > > > > it gives only a:
204 > > > > > >
205 > > > > > > temperature: 0C
206 > > > > > >
207 > > > > > > My question is:
208 > > > > > > even if i change the polling frequency, how the fan can start if
209 > the
210 > > > > > > temperature gives 0??
211 > > > > > > Do you know if it's possible to link the fan start with the core
212 > > > > > > temperature instead of the ACPI thermal zone?
213 > > > > >
214 > > > > > probably the fan don't start since you have it as a module. i've
215 > > > curently
216 > > > > > had the same problem which solved by compiling it integrated in the
217 > > > kernel.
218 > > > > > the fan in your case should always be on, not always be off....
219 > > > > >
220 > > > > > >
221 > > > > > > Regards,
222 > > > > > > m
223 > > > > > >
224 > > > > > > >
225 > > > > > > > thats why i told you to do this commanda:
226 > > > > > > > > echo "2 seconds" >
227 > > > > > > > /proc/acpi/thermal_zone/TZ01/polling:frequency
228 > > > > > > > >
229 > > > > > > > this enables the polling of your thermal every 2 seconds. this
230 > > > should
231 > > > > > be
232 > > > > > > > enough.
233 > > > > > > > do you have the other file that i mentioned:
234 > > > > > > > > /proc/acpi/thermal_zone/TZ01/trip_points ?!
235 > > > > > > > this sets the trip points for your processor. whitout it you
236 > > > governor
237 > > > > > cannot
238 > > > > > > > understand what to do even if it polls right.
239 > > > > > > >
240 > > > > > > > as for the kernel thigs, set these options:
241 > > > > > > > select processor type: intel core2 instead of normal x86
242 > > > > > > > CONFIG_X86_SPEEDSTEP_CENTRINO=y instead of m
243 > > > > > > > CONFIG_ACPI_FAN=y instead of m
244 > > > > > > > CONFIG_MICROCODE=y instead of m (for what i know cpu micocode is
245 > > > needed
246 > > > > > on
247 > > > > > > > intels)
248 > > > > > > > CONFIG_K8_NUMA=n instead of y (this should be the amdk8 numa,
249 > that
250 > > > you
251 > > > > > > > should not need. if it's not then let him be)
252 > > > > > > > CONFIG_X86_MCE_AMD=n instead of y (you don't need amd mce
253 > features
254 > > > since
255 > > > > > > > they are not included into intel cpus)
256 > > > > > > > CONFIG_NR_CPUS=32 <-- this leaves me a little dazzled: do you
257 > really
258 > > > > > have 32
259 > > > > > > > cpus in your core?! for what i know this sets the real number of
260 > > > cpus
261 > > > > > inside
262 > > > > > > > the kernel, but i might be wrong. so if this is really what i
263 > think
264 > > > it
265 > > > > > is,
266 > > > > > > > ie the real nr of cpus (not virtual ones) set this to 2 or 4
267 > based
268 > > > on
269 > > > > > your
270 > > > > > > > cpu cores.
271 > > > > > > > CONFIG_HOTPLUG_CPU=n instead of y (i don't really think that
272 > you'll
273 > > > > > unplug
274 > > > > > > > your cpu from your laptop when the laptop is still running
275 > > > considering
276 > > > > > that
277 > > > > > > > you don't use multi cpus but a single multicore cpu. the same
278 > goes
279 > > > for
280 > > > > > > > memory hotplug: i don't think that your laptop supports it, so
281 > just
282 > > > > > disable
283 > > > > > > > it.)
284 > > > > > > > for what i have seen the acpi problems may be due to a failure
285 > in
286 > > > > > loading
287 > > > > > > > the intel speedstep module. if you look into the modules loaded
288 > > > (lsmod)
289 > > > > > you
290 > > > > > > > should not see it. so it's better to insert it directly in the
291 > > > kernel,
292 > > > > > since
293 > > > > > > > it is one of the first modules called (if you use it as a module
294 > you
295 > > > > > should
296 > > > > > > > be loading it with initramdisk before loading acpi to have a
297 > full
298 > > > acpi
299 > > > > > > > configuration).
300 > > > > > > > try setting these options and recompile and install the new
301 > kernel
302 > > > and
303 > > > > > > > modules and reboot (kexec is not working on my amd turion with
304 > 64bit
305 > > > > > enabled
306 > > > > > > > and so may also be for your core2duo).
307 > > > > > > >
308 > > > > > > > 2007/10/10, Marco Calviani < marco.calviani@×××××.com>:
309 > > > > > > > > Sorry i missed the attachment.
310 > > > > > > > >
311 > > > > > > > > regards,
312 > > > > > > > > m
313 > > > > > > > >
314 > > > > > > > >
315 > > > > > > >
316 > > > > > > >
317 > > > > > > >
318 > > > > > > > --
319 > > > > > > > dott. ing. beso
320 > > > > > > --
321 > > > > > > gentoo-laptop@g.o mailing list
322 > > > > > >
323 > > > > > >
324 > > > > >
325 > > > > >
326 > > > > >
327 > > > > > --
328 > > > > > dott. ing. beso
329 > > > > --
330 > > > > gentoo-laptop@g.o mailing list
331 > > > >
332 > > > >
333 > > >
334 > > >
335 > > >
336 > > > --
337 > > > dott. ing. beso
338 > > --
339 > > gentoo-laptop@g.o mailing list
340 > >
341 > >
342 >
343 >
344 >
345 > --
346 > dott. ing. beso
347 --
348 gentoo-laptop@g.o mailing list

Replies