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