[Repo Core]
Post here all issues you have with our core repository
FS#299 - CPU is hot
Attached to Project:
[Repo Core]
Opened by Nicola (souledge) - Sunday, 19 June 2011, 20:56 GMT
Last edited by Anke Boersma (abveritas) - Tuesday, 31 July 2012, 11:54 GMT
Opened by Nicola (souledge) - Sunday, 19 June 2011, 20:56 GMT
Last edited by Anke Boersma (abveritas) - Tuesday, 31 July 2012, 11:54 GMT
|
DetailsCPU temp increase a lot, even in idle.
I think that it should be a problem of cpufreq that isn't set automatically from the system like in other distro. In fact kernel modules of cpufreq seems not be loaded. Idle temp about 56°, normally it is 42/43. |
This task depends upon
So, it is like i said last time: acpi-cpufreq isn't loaded at the startup, so CPU go at maximum speed.
After I loaded that module, CPU went always at maximum speed but, with
cpufreq-set -g powersave
it seems that CPU temperature go down quickly.
After this, I used also
cpufreq-set -f 800000 -c 0
cpufreq-set -f 800000 -c 1
(one command for each processor)
to set the current cpu speed at the minimum said by "cpufreq-info" command,
and temperature went down enough, about 44/45°C, my "normal" temperature.
How can we have the same result but automatically?
In laptops expecially high temperatures are easy to note.
It seems, anyway, that other distro have automatically cpu scaling when Linux doesn't require high computation power.
I hope that this time I'm been useful ;)
https://gitorious.org/chakra-packages/platform/blobs/testing/chakra-hardware-detection/opt/chakra/hooks/hwdetect_4_power
Then tribe should pick it up and add it to rc.conf (line 175):
https://gitorious.org/chakra/tribe/blobs/master/scripts/postinstall-functions/job-setup-hardware
This code is old and maybe need to be reworked ...
ls /lib/modules/2.6.38-CHAKRA/kernel/arch/x86/kernel/cpu/cpufreq
acpi-cpufreq.ko.gz gx-suspmod.ko.gz mperf.ko.gz powernow-k6.ko.gz speedstep-ich.ko.gz
cpufreq-nforce2.ko.gz longhaul.ko.gz p4-clockmod.ko.gz powernow-k7.ko.gz speedstep-lib.ko.gz
e_powersaver.ko.gz longrun.ko.gz pcc-cpufreq.ko.gz powernow-k8.ko.gz speedstep-smi.ko.gz
I was only searching for *.ko instead of *.ko* - should be fixed in a new chakra-hardware-detection.
# watch grep \"cpu MHz\" /proc/cpuinfo
Every 2.0s: grep "cpu MHz" /proc/cpuinfo Mon Jul 4 01:45:54 2011
cpu MHz : 1000.000
cpu MHz : 2000.000
1. Tribe adds to the MODULES line of rc.conf every known module for the system, as if the kernel couldn't load them by itself.
2. Despite the fact Tribe does this, it doesn't add the proper power throttling modules to rc.conf, and it doesn't configure the system to use ACPI. Tribe is hard on you, sucks power, and you need to customize rc.conf to get good results. These are my rc.conf MODULES lines, for posterity.
#MODULES=( nvidia battery button processor thermal video btusb cdrom edac_core edac_mce_amd hid k8temp i2c-nforce2 i2c-core evdev joydev psmouse serio_raw sparse-keymap media uvcvideo v4l2-compat-ioctl32 videodev mmc_core hp-wmi wmi ssb nvidia nv_tco crc16 snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-codec snd-hda-intel soundcore pata_amd scsi_mod sata_nv forcedeth bluetooth rfkill pcmcia pcmcia_core usb-storage usbhid usbcore ehci-hcd ohci-hcd uas sd_mod sr_mod st sg ac long_isnt_it? )
MODULES=( powernow-k8 nvidia )
Of course, the long_isnt_it? module is a bogus one, and the thing doesn't give an error since I commented the line :D. My MODULES line has only two modules: nvidia (I need to load it manually) and powernow-k8 (my power throttling driver, for Intel, this is acpi-cpufreq)
Also, keep in mind that appset-qt is tremendously inefficient while it's idling. In my system it idles at 2% CPU, when it should be 0. That includes periodical updates for the tray icon when it doesn't do anything, and an unbearable, CPU-eating, screen flash when appset-qt is compiling something from CCR.
I used to think it was a Core Due Duo issue but I see that also other cpu are affected.
- Chakra doesn't load the appropiate CPU throttling modules (powernow-k8, acpi-cpufreq) automatically. This is something it shares with Arch Linux.
- Chakra also doesn't enable the relevant energy saving facilities automatically. They must be enabled manually in all cases.
@Nicola: what you state is partially true and partially false. This bug makes impossible to use Chakra OUT OF THE BOX on a laptop. If you tweak the laptop, you can get comparable battery life with other Linux distros.
The problem is all in the CPU scaling, you're right...but this is a important issue I think, especially for new users
http://chakra-linux.org/wiki/index.php/Cpufrequtils
We work hard on Tribe atm to fix known issues. To follow the kernel-development check here:
http://chakra-project.org/bbs/viewtopic.php?id=6534
Most of this report dealt with cpu-frequtils, package is no longer maintained, and will be depreciated in Chakra.