aplicaxala / brazostweaker

Automatically exported from code.google.com/p/brazostweaker
GNU General Public License v3.0
0 stars 0 forks source link

MSI U270 on E-350 - not stable, settings mess up after sleep/hibernation #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hello,

I recently installed Brazos Tweaker on my MSI U270 with AMD E-350 APU in order 
to undervolt the sytem and gain battery life. I found different settings people 
use, but they are all faulty. They were about:

P0: 1,1500-1,1625
P1: 0,9875-1,0250
P2: 0,8000-0,8375
NB P0: 0,8500
NB P1: 0,8000

Such settings, or settings that are "working for most of the users", don't work 
there. Even now, with setting: P0: 1,2000; P1: 1,1000; P2: 0,9000; NB P0: 
0,9000; NB P1: 0,8500; I receive BSODs and dead freezes when on maximum load.

While I can partly understand that, cause every processor is different and will 
or will not work on some voltage, I get very dissappointed by the application 
itself. When I set everyting up, apply the settings, set them permanent, and 
succesfully restart the computer, everything works fine. My battery life is far 
better, and it goes up from 4 hours to even 6 hours. But after I put the 
computer to sleep (and later it hibernates) all gets messed up. Brazos Tweaker 
still says the settings are active, and the built-in monitoring confirms it, 
the battery indicator shows no more that 3 hours, and percents are going down 
in my eyes. And if I would like to put the settings back to life, and get my 5 
hours back, I have to take out the battery for a few seconds, nothing else 
helps. Yesterday I turned off the hibernation, but still no luck, app reacts 
the same.

Is there any solution to this?

PS. I would like to propose a little change if possible - the settings could be 
pinned to an energy plan. For example the undervolting would be applied to 
Battery Save mode, and if you turn into Normal or Top Performance mode, normal 
voltage settings would apply. That would help browsing and MS Office'ing on 
sligthly lower than should be voltage, and on other energy plans, top 
performancing won't end up with a BSOD or a freeze. At least I think so...

Best Regards,
Mike

Original issue reported on code.google.com by mrsjas...@gmail.com on 19 Oct 2011 at 9:00

GoogleCodeExporter commented 9 years ago
Hi Mike,

in order not to screw up your system, you need to do stress testing for some 
time in each of the PStates. Please use Orthos or Prime95 to do so. Without 
doing this and making the settings permanent you risk the stability of your 
system as you just experienced. First test and then make them permanent!
My own system doesn't work with the above written values either.
I'm running (added some margin to stable values)
P0: 1,225
P1: 1,0375
P2: 0,8375
NB P0: 0,8500
NB P1: 0,8000

My system hasn't shown any sign of stability so far within months doing 
undervolting.
Likely it is just a single PState setting, which makes your system instable, 
which is why you thoroughly need to test EACH on its own. Please, see the Wiki 
for details. 

In my opinion, there is no need to have undervolting for a certain power 
profile. The goal is to keep a stable system, not to trade better batter life 
with stability issues. If the settings don't work always, please don't use them 
at all.

Best regards and hope it helps,
Sven 

Original comment by sven.wit...@gmail.com on 19 Oct 2011 at 11:21

GoogleCodeExporter commented 9 years ago
I'll handle this one.

Original comment by sven.wit...@gmail.com on 19 Oct 2011 at 11:21

GoogleCodeExporter commented 9 years ago

Original comment by sven.wit...@gmail.com on 7 Mar 2013 at 9:32