@rdurty2
The AGPM.kext contains values I haven't seen before.
Somebody has put higher values in Threshold_Low compared to Threshold_High.
It doesn't make sense. Unless you wouldn't wanted G-state 1 and 2 executed. Looking at your benchmarks it seems to go all the way up correctly to G-state 0. I'd like to know if it still downclocks correctly to G-state 3 and the history of G-states. I am not going to put these values in my system. Someone other shall do it please.
The GTX 570 and 580 are very power demanding cards, so I don't want to either use the highest or lowest power mode. The lowest power mode is lagging and as a former Ati 5770 card owner it's just unbearable for me.
The following threshold values are chosen to stay most of the time in G-state 2.
It’s sufficient for most “everyday” usage.
With these settings I can save up to 50~110W
High
0::25
1::50
2::99
3::100
Low
0::0
1::26
2::51
3::99
I have also set
IdleInterval to 400 and
SensorSamplingRate to 25
By doing so, you get 92s delay between G-state changes. Luckily it goes up to high performance modes quickly enough. It takes about 3 seconds to get in a higher G-state.
CAUTION:
I have found out how they work myself by trying a few different values. I don't know if it's ok to alter them actually. I am no GPU developer.
== Cinebench's score mystery ==
When running it with above thresholds I get ~30fps just like I did with other settings before. I could see that cinebench isn't demanding enough to invoke G-state 0. It used to change between G-state 2 and 1 back and forth during the benchmark. GPU load is 70%!!! idle during benchmark at G-state 1.
Well, that has changed with the new values for IdleInterval and SensorSamplingRate.
Now G-state 1 is being activated all the time the bechmark is running. Annnnd, guess what? I still get only ~30 fps.
@Rick5
npci=0x2000 is used to get beyond the infamous [PCI config begin] issue at boot time. You can only see it when starting up using verbose mode. In reality it boots fine till the login screen without npci-0x2000. But as you can imagine, people think the machine has frozen at [PCI config begin] and are starting to reset/reboot their machines.
That's why