Phil - if you have rigs that show the "300/300" thing..... if you upgrade to this kernel - will it go away? Thanks
the 300/300 seems to occur if it is clocked a bit off. Try to change clocks or see if with higher or lower dpm it will gone.
I will see if I can make it show by moving core higher
The 300/300 is meaby becasue it it experimental powerstage.
Right now if we have for example
0: 300Mhz
1: 466Mhz
2: 751Mhz
3: 1019Mhz
4: 1074Mhz
5: 1126Mhz
6: 1150Mhz
7: 1230Mhz
And we will set 4 DPM stage to for example 1150, then the table will look like:
0: 300Mhz
1: 466Mhz
2: 751Mhz
3: 1019Mhz
4: 1150Mhz <--- this had higher MHz than 5 DPM
5: 1126Mhz
6: 1150Mhz
7: 1230Mhz
I think that kernel dont like this experimenting situations
Wolf0 confirmed me that kernel doesnt like this.
Anyway this is possible reason, and accually it could be something else.
I wan to test it by doing some more scripting so if we want 4 dpm level to be 1150 MHZ then next DPMs stage should have bigger clocks, and lower dpms should have lower clocks.
This is what i want to try in my scripts.
0: 300Mhz
1: 466Mhz
2: 751Mhz
3: 1019Mhz
4: 1150Mhz <-- we are using this DPM and setting 1150 clocks to it
5: 1160Mhz <-- this needs to be bigger
6: 1170Mhz <-- this needs to be bigger
7: 1230Mhz <-- this needs to be bigger
BUT ITS "MEABY"
