Open GoogleCodeExporter opened 8 years ago
GoogleCodeExporter
commented
8 years ago Hi Piotr,
I can't see, why it shouldn't work right now, but I might help with a work
around.
Please tell me, what you want to achieve by disabling turbo.
Do you want to run the system faster or do you want to run slower for better
battery life and a cooler laptop?
-SvenOriginal comment by sven.wit...@gmail.com on 12 Dec 2011 at 7:55
GoogleCodeExporter
commented
8 years ago Sorry for my english, I'm from Russia.
I have the same problem. I Disable Hardware Turbo, apply and restart, after
that Turbo was again checked and worked.
I have acer aspire 5560 with A4-3300M.
Thanks for your programm! Original comment by dik...@gmail.com on 26 Jan 2012 at 1:29
GoogleCodeExporter
commented
8 years ago Original comment by sven.wit...@gmail.com on 7 Mar 2013 at 10:05
GoogleCodeExporter
commented
8 years ago Hi, this is actually quite problematic.
I think i might've mistakenly ticked(enabled) Hardware Turbo, and after the
restart I noticed that it was ticked and apparently it remains ticked after
restart/shutdown, it's almost as if the code to untick it is not present and
this is something that sticks. Maybe the p-states settings stick too ? but
since there's some AMD driver, it is setting them to default at windows
startup, because even after uninstalling fusiontweaker, the Hardware Turbo is
still enabled after restart, and thus the only two states the CPU goes into are
P0 and P1 which by default is 2.3GHz and 1.4Ghz which is kinda scary :D (i'm
aiming for undervolting, and 2.3GHz is 1.3+ volts)
Anyway, I tried with the .exe from the downloads section but it's the same
thing.
Also, after unticking it, it gets stuck at P1 state (so not fluctuating from P0
to P1 as it does after any restart now) ...
Not really sure what else to say here... but i am currently in linux and it's
800Mhz, so whatever it is, it's either affecting windows only, or linux just
overrode it.
Please fix.
Peace.Original comment by emanueLc...@gmail.com on 9 Feb 2014 at 11:41
GoogleCodeExporter
commented
8 years ago Hi, let me try to describe my view here.
The turbo capability is something, which is internally programmed into the APU
and is read everytime the processor starts up (switch off completely, not a
restart). If the service hasn't been started yet (Set permanent) and
FusionTweaker GUI is not running, there should be no turbo enabled. How did you
check, that the turbo is on? Maybe we can figure out, whats going on.
For sure, FusionTweaker has bugs, since I really never had the chance to test
it personally for a longer time. So please excuse me ;)
I know, sometimes CCC and Windows PowerManagement is fighting against
FusionTweaker, since there are some things, which can be controlled there too.
Best regards,
Sven Original comment by sven.wit...@gmail.com on 9 Feb 2014 at 3:42
GoogleCodeExporter
commented
8 years ago Hey it's not problem, it's understandable. I'd love for us to figure this one
out though.
I basically, restarted at one point, noticed that processor was in P0 and P1
states only (with coretemp program) then opened fusiontweaker, opened the
(forgot which button it is right now) window with the service, unticked the
service and the turbo, closed window (by the x) then notice that main window
was showing cpu stuck at P1 state, then actually opening the service window and
just closing it a couple of times (if i remember correctly) restored the cpu
using p0 to p7 states instead of just stuck at p1 state. Then went ahead and
exited and uninstalled fusiontweaker while making sure with coretemp that it
was ideed still working with p0 to p7 states no problem. After this uninstall,
i checked if there were any services left from fusiontweaker and i couldn't
find any (great). Then restarted windows, upon start i noticed with coretemp
that cpu was in p0 and p1 states again with the default values for all the
states basically(this part is to be exactly as expected, from my interactions
with k10stat from before i noticed indeed the pstate values changed by it do
not stick after restart) however it was still stuck between p0 and p1
exclusively, so i started k10stat and set all p0 thru p7 states to 800mhz,
worked. Restarted again, noticed it was stuck at p0 and p1 again, did the
k10stat again to 800mhz, shut down windows which powered off the laptop (waited
like 10 sec while off, but did not remove battery or ac adapter from laptop)
then started up laptop, booted windows, noticed the same p0-p1 stuckness... did
the k10stat again and that's about it before i chose to boot linux and so far I
didn't boot back since.
Maybe some other program (CCC ?) saved this turbo state somehow, and it's
keeping/restoring it upon boot... but before, i was thinking that this turbo
bit on/off is somewhere written in some kind of flash or cmos even , i don't
know really :)
I can imagine CCC/windows powermanagement fighting is about the min/max limits
... that sort of cpu throttling that can be set (min cpu %, and max cpu %, or
in CCC is about the Mhz but same concept)
When you say this; "The turbo capability is something, which is internally
programmed into the APU and is read everytime the processor starts up (switch
off completely, not a restart)."
Did you mean that it's programmed as in an eeprom kinda way? that it sticks
even when you "switch off completely" ? or i am misreading that; because if
this is true, maybe then, the code for removing the turbo (switching turbo off)
might not be doing it at all (just guessing, but this is how it seems to me to
be acting thus far)
Thank you Sven.Original comment by emanueLc...@gmail.com on 9 Feb 2014 at 8:43
GoogleCodeExporter
commented
8 years ago not=no*
btw, I was a little amazed to see turbo being ticked at all, because I remember
never ticking it before clicking apply, ever. Unless, when ticking the `make
those P-states Permanent` it ALSO ticked the `turbo` automatically (can't
remember if it does that), then i could've not noticed that turbo was on before
applying and closing window.
Original comment by emanueLc...@gmail.com on 9 Feb 2014 at 8:46
GoogleCodeExporter
commented
8 years ago is turbo the only thing that is programmed into apu ? (if i understood that
right)
i'm assuming the p-states are not, i mean, they only stick until the next cpu
reset(windows restart)
meanwhile i found this quote:
"
note: AMD 12.3 is Buggy if OCing CPU. PC Hangs on Shutdown when K10stat or
fusion tweaker is used and turbo boost (B0) is on.
This may be a bug in later AMD drivers. This occurs regardless of using new
Bios Mod for selecting Fixed dgpu mode or not.
WORKAROUND = Turn Off Turbo Boost (B0) in K10stat when powering off PC or don't
use K10stat at all for OCing CPU
Discovered by LINK626, thanks!>>>
http://forum.notebookreview.com/asus/601808-k53ta-best-deal-ever-could-290.html#
post8425114
"
not entirely sure how much it relates to this
(amd 12.3 is ccc version)
I will go back into windows and see if i can do something about it, maybe by
uninstalling ccc although that seems messy ... i'll try something:)
Original comment by emanueLc...@gmail.com on 9 Feb 2014 at 9:01
GoogleCodeExporter
commented
8 years ago omg you are not going to believe this! (ok you will, but i won't :D)
windows is starting up in 15 sec and i can see coretemp (ran automatically)
the P0-P1 states are exclusively what the cpu is in until 1 minute 30 seconds
of (windows)uptime passes (taskmanager shows this counter) and then it's all
back to normal, switches to 800Mhz since it's THAT idle after like 20 sec of
uptime anyway
In other words, something (other than fusiontweaker, 'cause i had its service
on disabled and it's thus not started) is keeping the cpu at P0-P1 states for 1
minute 30 sec arguably to speedup loading windows ... guessing this is CCC or
whatever amd cpu drivers it installed (no idea)
But the point is, it's not fusiontweaker, even though, entering it, looking at
the service window, it does show Turbo is ticked(enabled) - but the service was
manually disabled by me btw (though this should be irrelevant to the turbo
state, + `the keep P-states permanent option` was disabled from before so I had
no reason to keep the service running)
I should probably check if turbo is enabled after 1 min 30 sec ... 'cause I am
not sure if i checked it before or after... but possibly this one remains
checked for other reasons (is it reading turbo state from the APU ? maybe turbo
state is temporarily enabled by CCC for 1 min 30 sec but then disabled ? but
if so, fusiontweaker should show it unticked after 1 min 30sec, i'll check)
Original comment by emanueLc...@gmail.com on 9 Feb 2014 at 9:28
GoogleCodeExporter
commented
8 years ago Hi,
for the Turbo part: The setting, if turbo is enabled and how many pstates are
boosted, is read out on every startup. This will always be the same. The
registers can be changed by software later on after booting, but the APU always
starts the same as you already figured for the pstates.
So, if your pstates stuck in p0 and p1, and you are really sure, that
fusiontweaker AND the fusiontweaker service are not running anymore, another
program is doing something weird here (Windows Power Management is able to do
this intentionally).
Try the following, start fusiontweaker and go to the status tab. Hit "Log now"
and send me the log file. Maybe I can tell from there, what the problem could
be. There is one register, which holds the value for "maxPstate". This could be
one root cause, if it sits at 1 (-> highest pstate P1), instead of letting the
CPU part go to P7.
Best regards,
Sven Original comment by sven.wit...@gmail.com on 9 Feb 2014 at 9:29
GoogleCodeExporter
commented
8 years ago Hi,
if I read it right, you have an A6-3400m, which should have turbo by default.
That means, that one pstate (P0) is the turbo (or so called boosted) pstate.
This one sould show 2.3GHz, right? P1 should be the fastest pstate running all
cores together. If you see, that it stucks in p0 and p1, it is apparent, that
some software is letting the CPU not throttle at all, because P1 is the fastest
pstate, which can be controlled by software. Going into p0, can only be
controlled by hardware, depending on current temperature and load. Hope, that
helps for a better understanding.
Best regards,
SvenOriginal comment by sven.wit...@gmail.com on 9 Feb 2014 at 9:42
GoogleCodeExporter
commented
8 years ago I can now confirm without a shadow of a doubt that turbo works exactly as it
should be in fusiontweaker (just tested) and i realized that k10stat's Boost is
the same as fusiontweaker's Turbo, AND that it's the P0 state(which i knew from
k10stat, but didn't know what Boost option was in k10stat) ... but i previously
wrongly though that this turbo state is the stuckness between P0-P1 which seems
to survive restart&shutdown. And now I can read your newest post which tells me
the same thing(about that turbo really is)
You are right indeed. Also I apologize for blaming fusiontweaker for this,
definitely some other program is doing this for 1min 30 sec.
Also I wrongly "knew" that this turbo state meant only one core would be
boosted at a time, but nope: all 4 could be on at the same time, even when load
is 2%
Thank you Sven for making me understand this and realizing what Turbo is and
most importantly that it's not fusiontweaker's fault at all.
The logs also confirm.Original comment by emanueLc...@gmail.com on 9 Feb 2014 at 9:57
Attachments:
GoogleCodeExporter
commented
8 years ago 
Hi,
very good. "BoostEnAllCore" is set to 1, which means, that if current
temperature allows, all cores can be boosted (or turbo). As I wrote, this can
not be controlled by software. It's basically a safety thing of the CPU not to
overheat, but be careful with changing P1, since this can be set to the same
frequency as P0! In the end, disabling turbo, was meant to get rid of all
hardware controlled (boosted) states and get all controllable through software.
Since there are enough pstates left for playing (P1..P7 in your case) there is
no big value in disabling turbo.
Best regards,
Sven Original comment by sven.wit...@gmail.com on 9 Feb 2014 at 10:12
GoogleCodeExporter
commented
8 years ago Nicely explained. Thanks!
I'm definitely going to undervolt this from the defaults(while at the same time
overclock it a bit), so even if I were to set P1 to P0, both will have
considerably less than that 1.3V ... so I wouldn't worry much about decreasing
cpu life(which was the reason i was distressed about it being P0-P1 in the
first place, i thought it was going to remain so full time)
and P7 will be 400Mhz 0.6125V - works for me and P6 800Mhz 0.850V ... one more
i tested was 1800Mhz 0.9875V which I read would be stable at same voltage for
2000Mhz too.
Anyway, it's great to know to look at other programs for doing the evil "boost"
for 1min 30sec
there's a guide here(for my system, but using k10stat):
http://slappablog.com/2011/12/08/laptop-llano-sabine-overclocking-guide-a4-3300m
-a6-3400m-a8-3500m/
The best part about fusiontweaker is that it can change the NB states values
too, which k10stat cannot(for me). I might be interested in undervolting those
too and doing some stresstests afterwards to see they are stable.
One thing I'd wish fusiontweaker would have is profiles; in k10stat I would
change all states to same value in a profile and test it, and have the ability
to quickly switch to other profiles. With fusiontweaker however the only way to
keep the values is to make sure they are saved in the service(even if it's
unticked) that way I can restore them without having to input them again (or
have the service restore them for me automatically - but still it's only one
profile basically)
Peace out.Original comment by emanueLc...@gmail.com on 9 Feb 2014 at 10:33
GoogleCodeExporter
commented
8 years ago Actually I had discussions with other users already about profiles on
BrazosTweaker. I don't really see the value. The only thing, I can think of to
add, would be a tick to enable or disable certain pstates in the GUI.
Best regards,
Sven Original comment by sven.wit...@gmail.com on 9 Feb 2014 at 10:40
Original issue reported on code.google.com by
piotr.go...@gmail.comon 8 Dec 2011 at 2:03