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