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