- Joined
- Jun 4, 2011
- Messages
- 50
- Motherboard
- Gigabyte Z170X-UD3 Rev 1.0
- CPU
- i7 6700k
- Graphics
- Radeon RX Vega 64
Here's my setup:
i7 2600k
Gigabyte Z68XP-UD3P, UEFI
8GB RAM
Radeon 6870
Mac OS 10.8.5
DSDT-less installation, Multibeast 5.5, MacMini 5,1 SMBIOS
Some time ago (Before flashing to UEFI), I had this thing up in the mid-4ghz range no problem. Once I flashed with UEFI and installed 10.8, I didn't really bother until recently. I installed the default 4.2ghz SSDT and have been able to crank it up no problem. However, getting it past that point has been utterly impossible. What I've done thus far:
-Ensured that I'm only pushing the turbo up, not the multiplier
-Make sure it's something akin to 43, 42, 42, 42 in the turbo settings.
-Checked voltages to make sure they'd work (they darned well should)
After verifying that, I tried:
-A 4.7ghz SSDT provided here.
-An autogenerated SSDT from MaciASL that went up to 4.8ghz
-Trimming that autogenerated SSDT down to 8 P-States, topping out at 4.3ghz
Nothing works. Any attempt to push the turbo anywhere north of 4.2ghz spits up a "P-State Stepper Error 18 at step 29 in context 2 on CPU X" kernel panic. I recall CPU 2 and CPU 4 being mentioned, but that's probably arbitrary. Stepping works when below 4.2ghz no problem.
I did notice one oddity: No matter what P-States I put in the SSDT.aml in /Extra, they do NOT get recognized. At all. Using AppleCPUPowerManagementInfo.kext, I see what appears to be the stock steppings being reached. No set stepping in the SSDT is used, or at least it's inserting its own when convenient. Right now I have the following steppings in the SSDT.aml (and yes, I cut down the APSS value to match:
43, 42, 41, 35, 30, 24, 20, 16
What I'm seeing from the ACPMI dump (running at 4.2/4.1/4.1/4.1) is:
16 27 33 34 40 41 42
Either it's only using a few from the top or it's following some sort of formula to calculate ideal P-States, but it's definitely not restricting itself to the SSDT.
Any ideas? Something I missed? I've heard that there's a sort of "maximum" on P-States that can be utilized by the system, but I haven't seen that clarified. I also know that things get a little wonky if you go above 4.2ghz, but again, nothing solid on what exactly that may be. I've dug around on the forum and elsewhere, but much of the information is or could easily be outdated. What else can I try to get this above 4.2ghz?
i7 2600k
Gigabyte Z68XP-UD3P, UEFI
8GB RAM
Radeon 6870
Mac OS 10.8.5
DSDT-less installation, Multibeast 5.5, MacMini 5,1 SMBIOS
Some time ago (Before flashing to UEFI), I had this thing up in the mid-4ghz range no problem. Once I flashed with UEFI and installed 10.8, I didn't really bother until recently. I installed the default 4.2ghz SSDT and have been able to crank it up no problem. However, getting it past that point has been utterly impossible. What I've done thus far:
-Ensured that I'm only pushing the turbo up, not the multiplier
-Make sure it's something akin to 43, 42, 42, 42 in the turbo settings.
-Checked voltages to make sure they'd work (they darned well should)
After verifying that, I tried:
-A 4.7ghz SSDT provided here.
-An autogenerated SSDT from MaciASL that went up to 4.8ghz
-Trimming that autogenerated SSDT down to 8 P-States, topping out at 4.3ghz
Nothing works. Any attempt to push the turbo anywhere north of 4.2ghz spits up a "P-State Stepper Error 18 at step 29 in context 2 on CPU X" kernel panic. I recall CPU 2 and CPU 4 being mentioned, but that's probably arbitrary. Stepping works when below 4.2ghz no problem.
I did notice one oddity: No matter what P-States I put in the SSDT.aml in /Extra, they do NOT get recognized. At all. Using AppleCPUPowerManagementInfo.kext, I see what appears to be the stock steppings being reached. No set stepping in the SSDT is used, or at least it's inserting its own when convenient. Right now I have the following steppings in the SSDT.aml (and yes, I cut down the APSS value to match:
43, 42, 41, 35, 30, 24, 20, 16
What I'm seeing from the ACPMI dump (running at 4.2/4.1/4.1/4.1) is:
16 27 33 34 40 41 42
Either it's only using a few from the top or it's following some sort of formula to calculate ideal P-States, but it's definitely not restricting itself to the SSDT.
Any ideas? Something I missed? I've heard that there's a sort of "maximum" on P-States that can be utilized by the system, but I haven't seen that clarified. I also know that things get a little wonky if you go above 4.2ghz, but again, nothing solid on what exactly that may be. I've dug around on the forum and elsewhere, but much of the information is or could easily be outdated. What else can I try to get this above 4.2ghz?