You are not logged in.
I really don't understand why with linux there is a large difference between the processor temperatures than on Windows.
This is the config of my pc:
CPU: Intel Core 2 DUO E6600 Conroe 2400Mhz FSB1066
Mainboard: Asus P5K – P35 LGA775 FSB1333
RAM: 2x Team Group TVDD1024M800 Value DDR2 800 PC6400 1Gb
HD: Segate Barracuda 7200.10 – 500Gb 16Mb SATA-II
Graphic card: Club3D Geforce 8800 GTS 640Mb – 500/1600
Power supply: Corsair HX520W
Cabinet: Aerocool ExtremeEngine 3T Black
DVD-Rom: LG 8164B Black
DVD Recorder: LG GSA-H54L
TV Card: Asus MyCinema-P7131H
Fan: Noctua 120×120 NF-S12
I show you this screen, where there is my arch x86_64 installation with gnome, firefox and other applications like pidgin, skype, gwibber, checkgmail (about 1,5 hours up):
Instead this is the situation under Windows XP Professional 32bit, after ~3,5 hours up with only firefox and some tabs:
Then, on linux, temperatures are really high since i boot it...
Offline
Are you using Cpufrequtils?
Offline
Are you using Cpufrequtils?
I don't know what the hardware sensors monitor applet is using, but I can say that cpufreq-info and lm-sensors are installed.
Offline
Buddy, cpufrequtils allows you to scale your hardware's clock speed. It's a technique that keeps pcs cool, and probably explains the difference, as my linux runs cooler than Windows. Please go to that wiki page and set it up. It doesn't matter if it's installed. Put cpufrequtils to use!
Last edited by Intrepid (2009-06-23 13:28:11)
Intrepid (adj.): Resolutely courageous; fearless.
Offline
I set cpufrequtilis but the temperatures are always the same
cpufreq-info
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 1.60 GHz - 2.39 GHz
available frequency steps: 2.39 GHz, 1.60 GHz
available cpufreq governors: ondemand, powersave, performance
current policy: frequency should be within 1.60 GHz and 2.39 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 2.39 GHz.
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 1
hardware limits: 1.60 GHz - 2.39 GHz
available frequency steps: 2.39 GHz, 1.60 GHz
available cpufreq governors: ondemand, powersave, performance
current policy: frequency should be within 1.60 GHz and 2.39 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency is 2.39 GHz.
So in my /etc/rc.conf i put
MODULES=(acpi-cpufreq cpufreq_powersave cpufreq_ondemand ... )
Then, rebooting, i have always the same screen with the command cpufreq-info, and the same temperatures...
Offline
MODULES=(acpi-cpufreq cpufreq_powersave cpufreq_ondemand ... )
My rc.conf file only contains cpufreq
Offline
In /etc/conf.d/cpufreq, did you set minimum Hz to be 1.6GHz ? Default is 2.5GHz minimum, 3GHz maximum for some reason.
Ok I set the config file like this:
#configuration for cpufreq control
# valid governors:
# ondemand, performance, powersave,
# conservative, userspace
governor="powersave"# valid suffixes: Hz, kHz (default), MHz, GHz, THz
min_freq="1.60GHz"
max_freq="2.39GHz"
Of course I have the relative daemon in the daemons list.
Rebooting I have always the same temperatures and answer by the cpufreq-info command
I don't understand why...
Last edited by Garret (2009-06-23 17:39:33)
Offline
Is your fan functioning as fast in linux as it is in Windows? You might have your fan turned down or off whereas Windows XP typically does not manage fans very well.
What kind of GPU do you use? That would also affect temperature if you do not have gpu heat-management working.
Last edited by Intrepid (2009-06-23 17:42:58)
Intrepid (adj.): Resolutely courageous; fearless.
Offline
Can you check if that works:
cpufreq-set -g ondemand
As root of course.
Offline
Is your fan functioning as fast in linux as it is in Windows? You might have your fan turned down or off whereas Windows XP typically does not manage fans very well.
The fan speed is equal in linux and windows.
What kind of GPU do you use? That would also affect temperature if you do not have gpu heat-management working.
My gpu is a nvdia 8800gts 640mb pci-ex.
Can you check if that works:
cpufreq-set -g ondemand
As root of course.
This is the result:
[garret@desktop ~]$ sudo cpufreq-set -g ondemand
Password:
[garret@desktop ~]$
Offline
Perry3D wrote:Can you check if that works:
cpufreq-set -g ondemand
As root of course.
This is the result:
[garret@desktop ~]$ sudo cpufreq-set -g ondemand Password: [garret@desktop ~]$
No lower temperatures? Now show us cpufreq-info.
I think you are using the performance governor. This command should set the ondemand governor.
Offline
No lower temperatures? Now show us cpufreq-info.
I think you are using the performance governor. This command should set the ondemand governor.
Temperatures are always the same.
cpufreq-info:
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 1.60 GHz - 2.39 GHz
available frequency steps: 2.39 GHz, 1.60 GHz
available cpufreq governors: ondemand, powersave, performance
current policy: frequency should be within 1.60 GHz and 2.39 GHz.
The governor "ondemand" may decide which speed to use within this range.
current CPU frequency is 2.39 GHz.
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 1
hardware limits: 1.60 GHz - 2.39 GHz
available frequency steps: 2.39 GHz, 1.60 GHz
available cpufreq governors: ondemand, powersave, performance
current policy: frequency should be within 1.60 GHz and 2.39 GHz.
The governor "powersave" may decide which speed to use within this range.
current CPU frequency is 2.39 GHz.
Offline
Hmm..very mysterious. The Cores are still running at 2.39Ghz.
You can try editing /etc/conf.d/cpufreq and comment out the two lines:
min_freq="1.60GHz"
max_freq="2.39GHz"
After that restart the cpufreq daemon. It should detect the right frequencies.
Last edited by Perry3D (2009-06-23 18:18:39)
Offline
Hmm..very mysterious. The Cores are still running at 2.39Ghz.
You can try editing /etc/conf.d/cpufreq and comment out the two lines:
min_freq="1.60GHz" max_freq="2.39GHz"
After that restart the cpufreq daemon. It should detect the right frequencies.
No change in temperatures...
[garret@desktop ~]$ sudo /etc/rc.d/cpufreq stop
[garret@desktop ~]$ sudo /etc/rc.d/cpufreq start
:: Setting cpufreq governing rules , cpu 0 1 [DONE]
[garret@desktop ~]$
Offline
Try setting the minimum Hz to something under 1.6, like 1GHz and max to 3GHz, maybe the minimum freq is something like 1.599999GHz You never know. You're running an Intel CPU, right? Have you activated SpeedStep, etc in BIOS? Never hurts to double check
Last edited by Themaister (2009-06-23 21:08:47)
Offline
This got me thinking to try messing with scaling on my laptop. Sadly the initial modprobe fails (No such device). I am guessing Arch's default kernel does not have Via scaling support.
Offline
The fact that it STILL is running faster than 1.60 really shows that it's the lack of CPU scaling causing the temperature difference. Change your line that said governor="powersave" to governor="ondemand" then restart the daemon.
Intrepid (adj.): Resolutely courageous; fearless.
Offline
mybe check first if you have anything cpu intensive running.
Run top, and look for cpu usage.
Offline
No change in temperatures...
Strange, but ...
1. Use Hal to set governor
dbus-send --print-reply --system --dest=org.freedesktop.Hal /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.CPUFreq.SetCPUFreqGovernor string:performance
cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: powersave, ondemand, performance
current policy: frequency should be within 1000 MHz and 1.83 GHz.
The governor "[b]performance[/b]" may decide which speed to use
within this range.
current CPU frequency is [b]1.83[/b] GHz.
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: powersave, ondemand, performance
current policy: frequency should be within 1000 MHz and 1.83 GHz.
The governor "[b]performance[/b]" may decide which speed to use
within this range.
current CPU frequency is [b]1.83[/b] GHz.
Everything seems to be OK. Then ...
2. Use cpufreq-set to set governor
cpufreq-set -g ondemand
cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: powersave, ondemand, performance
current policy: frequency should be within 1000 MHz and 1.83 GHz.
The governor "[b]ondemand[/b]" may decide which speed to use
within this range.
current CPU frequency is [b]1.83[/b] GHz (asserted by call to hardware).
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: powersave, ondemand, performance
current policy: frequency should be within 1000 MHz and 1.83 GHz.
The governor "[b]performance[/b]" may decide which speed to use
within this range.
current CPU frequency is [b]1.83[/b] GHz (asserted by call to hardware).
Ops. Houston, we have a problem. cpufreq-set is unable to set governor properly. Then ...
3. Use Hal to set governor again.
dbus-send --print-reply --system --dest=org.freedesktop.Hal /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.CPUFreq.SetCPUFreqGovernor string:ondemand
cpufreq-info
cpufrequtils 005: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: powersave, ondemand, performance
current policy: frequency should be within 1000 MHz and 1.83 GHz.
The governor "[b]ondemand[/b]" may decide which speed to use
within this range.
current CPU frequency is [b]1000[/b] MHz.
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 1
hardware limits: 1000 MHz - 1.83 GHz
available frequency steps: 1.83 GHz, 1.33 GHz, 1000 MHz
available cpufreq governors: powersave, ondemand, performance
current policy: frequency should be within 1000 MHz and 1.83 GHz.
The governor "[b]ondemand[/b]" may decide which speed to use
within this range.
current CPU frequency is [b]1000[/b] MHz.
Everything seems to be OK again.
Conclusion
pacman -Rscn cpufrequtils
and use Hal or Hal aware software instead.
Last edited by sliponoga (2009-06-24 03:23:19)
Offline
Since my last message I have not changed anything more. I have only just rebooted my pc (inestead before I had just restarted the daemon).
Now I note temperatures are lower than before, but always high for me (and higher than Windows).
and cpufreq-info:
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 1.60 GHz - 2.39 GHz
available frequency steps: 2.39 GHz, 1.60 GHz
available cpufreq governors: powersave, performance
current policy: frequency should be within 1.60 GHz and 2.39 GHz.
The governor "powersave" may decide which speed to use within this range.
current CPU frequency is 1.60 GHz.
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 1
hardware limits: 1.60 GHz - 2.39 GHz
available frequency steps: 2.39 GHz, 1.60 GHz
available cpufreq governors: powersave, performance
current policy: frequency should be within 1.60 GHz and 2.39 GHz.
The governor "powersave" may decide which speed to use within this range.
current CPU frequency is 1.60 GHz.
So it seems the best i can obtain with Linux?
Last edited by Garret (2009-06-24 06:31:53)
Offline
Mind you that a cpu working in 32bit mode (as you have with windows) will generate a bit less heat than one working on 64bit mode (as you have with arch), like many have said the problem must be the governor used and the minimum speed it will set on your cpu.
On windows, when the computer is idling which are the cpu speeds?
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
And i would suggest to change the governor to ondemand instead of powersafe.
Offline
Mind you that a cpu working in 32bit mode (as you have with windows) will generate a bit less heat than one working on 64bit mode (as you have with arch), like many have said the problem must be the governor used and the minimum speed it will set on your cpu.
On windows, when the computer is idling which are the cpu speeds?
How can i know on Windows the cpu speeds?
I make these screenshots with everest ultimate:
Last edited by Garret (2009-06-25 16:09:14)
Offline
With everest I'm not sure. Try with cpu-z, that one I know that shows you the current speed and voltage of your cpu.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline