Important: 10.7.4 and Sandy Bridge CPU PM Temporary Fix

[tegezee]

This fix worked for me just a little slow... Great work...

 

[Alfa147x]

May 15 02:41:59 alfas-mac-pro kernel[0]: MSRDumper: multiplier: 16
May 15 02:42:14: --- last message repeated 2 times ---
May 15 02:42:14 alfas-mac-pro kernel[0]: MSRDumper: multiplier: 35
May 15 02:42:19 alfas-mac-pro kernel[0]: MSRDumper: multiplier: 16
May 15 02:42:24 alfas-mac-pro kernel[0]: MSRDumper: multiplier: 35
May 15 02:42:54: --- last message repeated 5 times ---
May 15 02:42:54 alfas-mac-pro kernel[0]: MSRDumper: multiplier: 35

So it looks like it is switching between it's highest and lowest multiplier. I guess that's fine as long as it's not stuck at it's lowest.

 

[jambek2003]

racerx90 Thanx for your clear post Hopefully this will help us a lot, me for sure!

What also comes handy is Diff Merge. It's a free tool to compare files

Download DiffMerge 3.3.2

Visually compare and merge files within Windows, Mac OS X
and Linux.

So you can compare your SSDT.dsl with one posted here. http://www.sourcegear.com/diffmerge/downloads.php

 

[indy911]

I have the same!

There is something strange with my system, I cant use DropSSDT=Yes because the system does not boot, it is stuck at TjMax = 0. Because of that I am not able to use my own SSDT also, with my own SSDT for 2500K and DropSSDT=Yes it does not boot also.

Any idea? Why can I not boot with DropSSDT=Yes? Chmiera 1.9.2.

I found a solution. As I expected there was something wrong with Bios 2307. I flashed new patched 3K Bios for P8P67, SSDT from Revo, DropSSDT=Yes and I have a lot of P-States! But there is no way to enable sound on new P8P67 yet on 3K bios... ;(

I can confirm this solution works for the P8P67 Pro board (rev 3.0). Flashed it to the 3207 patched BIOS as provided in Samisnake's BIOS repository (remember to flash twice as instructed by Asus), cleared the CMOS by enabling the jumper (also as instructed by Asus) and reconfigured all the necessary BIOS settings. Had already deleted my DSDT.aml before.

Now for the fun part:

- In 10.7.3 everything works as before, even without a DSDT. Yes, this includes sleep and wakeup!
- I can't be bothered with onboard sound, as I use an M-Audio C400 and a $1.25 (yes, $1.25!) USB soundcard from eBay that just works out-of-the-box, including volume control and muting.
- My geekbench score RAISED to almost 12500
- I have several P-states, including full turbo 38.
- BDMesg now reports successfully creation of P and C states.

In other words, I would say the whole system has dramatically improved after this BIOS upgrade. Since DropSSDT now works, next step is to upgrade to 10.7.4 again and create the SSDT for my processor as instructed in this thread.

 

[Craigrox]

I forgot to mention earlier - Asus P8P67 LE with i5-2400 is affected by updating to 10.7.4

 

[brams]

Apparently this is not supposed to work, I thought I would give it a shot anyway. I've only ever been able to get 6 P states whatever I try and most of them are low 20's with big jump to 44. So I removed most of the intermediate P states from my SSDT and have jumps of 600mhz except for the last two which are 500mhz. I was surprised to find that this apparently works.

However no matter what I try I cannot 10.7.4 to speedstep

See screen shots.

brams

 

[LosChristianos]

Apparently this is not supposed to work, I thought I would give it a shot anyway. I've only ever been able to get 6 P states whatever I try and most of them are low 20's with big jump to 44. So I removed most of the intermediate P states from my SSDT and have jumps of 600mhz except for the last two which are 500mhz. I was surprised to find that this apparently works.

However no matter what I try I cannot 10.7.4 to speedstep

See screen shots.

brams

Screen grab taken from 10.7.3 then?

 

[brams]

Sorry yes it is I just restored 10.7.3 after trying again the get speedstep to work on 10.7.4, the reason I mentioned it is that according to various sources this should generate "P-State Stepper Error 18 at step 2 on CPU 0" but it doesn't and I wondered if there was something in my DSDT and SSDT which prevented this and also prevented speedstep in 10.7.4 as there is a post in this thread of a P8P67-M-Pro working and mine won't as I am not much of a DSDT/SSDT expert but some folks posting on this thread are.

 

[indy911]

Update on the P8P67 Pro system:

After upgrading the BIOS to 3207 and ditching the DSDT I upgraded to 10.7.4. As expected CPU multiplier got stuck on 16. Changed the boot.plist as described in the OP and got two P-states back (16 and 35 if I recall correctly).

Added the ssdt.aml from earlier in this thread to the extra folder and now have 5 P-states. Changing system profile to Mac Pro 3.1 added a few more (compared to the original iMac 12.2).

I have three settings for turbo in my bios: "auto", "by all cores (can adjust in OS)" and "by per core (cannot adjust in OS)". If I pick "by all core" I get the "P-state stepping error 18" in my kernel log and Im stuck at 16 again. If I pick "by per core" I get a handful of P-states.

Looks like everything is running smoothly again...

 

[geigi]

My extracted ssdt looks like this:

DefinitionBlock ("ssdt.aml", "SSDT", 1, "AMICPU", "PROC", 0x00000001)
{
    External (\_PR_.OSC_, IntObj)
    External (\_PR_.PDC_, MethodObj)    // 1 Arguments
    Scope (\_PR)
    {
        Processor (P000, 0x01, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_PR.PDC (Arg0)
            }
            Method (_OSC, 4, NotSerialized)
            {
                Return (\_PR.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }
        Processor (P001, 0x02, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_PR.PDC (Arg0)
            }
            Method (_OSC, 4, NotSerialized)
            {
                Return (\_PR.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }
        Processor (P002, 0x03, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_PR.PDC (Arg0)
            }
            Method (_OSC, 4, NotSerialized)
            {
                Return (\_PR.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }
        Processor (P003, 0x04, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_PR.PDC (Arg0)
            }
            Method (_OSC, 4, NotSerialized)
            {
                Return (\_PR.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }
        Processor (P004, 0x05, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_PR.PDC (Arg0)
            }
            Method (_OSC, 4, NotSerialized)
            {
                Return (\_PR.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }
        Processor (P005, 0x06, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_PR.PDC (Arg0)
            }
            Method (_OSC, 4, NotSerialized)
            {
                Return (\_PR.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }
        Processor (P006, 0x07, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_PR.PDC (Arg0)
            }
            Method (_OSC, 4, NotSerialized)
            {
                Return (\_PR.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }
        Processor (P007, 0x08, 0x00000410, 0x06)
        {
            Method (_PDC, 1, NotSerialized)
            {
                \_PR.PDC (Arg0)
            }
            Method (_OSC, 4, NotSerialized)
            {
                Return (\_PR.OSC)
                Arg0
                Arg1
                Arg2
                Arg3
            }
        }
    }
}

wth? 2600k (extracted with aida64)

mine looks similar (2500k) also extracted with aida64 under windows (no vm...) did you found a solution?

EDIT:
same with extracted from ubuntu...