Today I created a PHC patch for the brand new stable kernel 2.6.26:
Undervolt your CPU with Linux PHC and kernel 2.6.26
Andreas
Today I created a PHC patch for the brand new stable kernel 2.6.26:
Undervolt your CPU with Linux PHC and kernel 2.6.26
Andreas
~ Sanity is the sign of an unused mind.
~ I poked a badger with a spoon!
The only thing the script does (when it works) is that it tells you which vid's you can use safely. Even if the script misbehaves, you can still follow the rest of the instructions in the howto, but you'll have to test your vid's manually.
If your default vid's are as from your post a few pages back:
Then, to set all vid's temporarily to 19, you can use these commands:
(the second "echo" command is only if you have a dual core cpu...)Code:sudo bash echo "9:19 6:19" > /sys/devices/system/cpu/cpu0/cpufreq/phc_controls echo "9:19 6:19" > /sys/devices/system/cpu/cpu1/cpufreq/phc_controls exit
And to really stress the cpu run "burnMMX" in a terminal (or in two terminals to stress both cores of a dual core cpu). Let it run for a while, and if it doesn't freeze the computer within a minute or so, it's probably going to be stable.
If it seems stable, make it automatically load on boot:
And add these lines:Code:gksudo gedit /etc/rc.local
(again, the second line is only if you have a dual core cpu...)Code:echo "9:19 6:19" > /sys/devices/system/cpu/cpu0/cpufreq/phc_controls echo "9:19 6:19" > /sys/devices/system/cpu/cpu1/cpufreq/phc_controls
Last edited by jocko; July 14th, 2008 at 11:53 PM.
It didn't freeze the computer when set to 19, but when I tried to run a virtual machine which would've consumed 512 MB of ram, it virtual machine (VirtualBox) aborted. Would this be caused by the low VID or is this a separate problem?
~ Sanity is the sign of an unused mind.
~ I poked a badger with a spoon!
I would blame it on something else. This would be an all or nothing. Either everything freezes or it all works fine.
Thank you!!!
For me, the originals VID's were 10:43 8:31 6:19 and running the script wouldn't crash the system; I set the VIDs all to 1, and then found, using PHCtool, that it wouldn't run any lower than 19 (probably already discussed, didn't read the whole thread).
So now I've set all VIDs to 19 and the system seems perfectly stable and so on, hasn't crashed. A very good thing is that I believe that now the system consumes the same power running with the cpu in performance mode or powersave, is that true?
Sad thing: the battery life won't increase, since the VID was already the lowest possible when running at 1GHz (lowest speed for my proc).
One more question: whenever I suspend or hibernate, when coming back, phctool won't work. If run in terminal, the message it outputs is this one:
any ideas? anyone getting the same problem?Code:Traceback (most recent call last): File "./phctool.py", line 467, in <module> app=appgui() File "./phctool.py", line 103, in __init__ self.ShowThrottlingControl() ##display trottling Controls File "./phctool.py", line 258, in ShowThrottlingControl getattr(self, 'label_TState'+str(cpu)).set_text(self.throttling.data[cpu]['states']['T'+str(tid)]+"%") KeyError: 'T8'
I'm not getting any problems running phctool after hibernate
I was wondering if this may've messed up some of my start-up things. The startup music bit plays before I log in, but the music that normally plays after I log in doesn't play anymore. Also, it takes a minute or so longer than usual to log in. These alone aren't really that big of problems. However, my Firefox is also messed up. When I try to start Firefox, it fails the first few times and then finally seems stable. Then, when I try to play a game, it fails as soon as the java starts loading.
This has only happened since I made the changes to the "/etc/rc.local" script and i was wondering if I added the lines incorrectly somehow:
Does anything look wrong?#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
echo "9:19 6:19" > /sys/devices/system/cpu/cpu0/cpufreq/phc_controls
echo "9:19 6:19" > /sys/devices/system/cpu/cpu1/cpufreq/phc_controls
exit 0
~ Sanity is the sign of an unused mind.
~ I poked a badger with a spoon!
Bookmarks