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