ssdtPRGen v12.0 with multi-processor support

A new version of ssdtPRGen (v12.0) with multi-processor support is now available from my Github repository. It should just work, but you are warned: Didn’t have a lot of time to work on it and I also don’t have all sorts of different configurations to test the script on. I guess that it where you come in handy.

Please report bugs and other oddities over at: https://github.com/Piker-Alpha/ssdtPRGen.sh/issues

Thank you for testing this update!

54 thoughts on “ssdtPRGen v12.0 with multi-processor support

  1. I do not have account in github for this reason I leave the bug found here. When I try create a ssdt for other processor that is no mine doesnt work and display this message Error: Invalid argument detected: i7-XXXX (X is the processor I want)

      • Good Morning Pike, thz thz you are a great
        But why have this two warning …this is a normal?

        Generating ssdt.dsl for a ‘MacPro6,1’ with board-id [Mac-F60DEB81FF30ACF6]
        Ivy Bridge Core i7-3930K processor [0x206D7] setup [0x0402]
        With a maximum TDP of ‘130’ Watt, as specified by argument: -t 130
        Number logical CPU’s: 12 (Core Frequency: 3200 MHz)
        Number of Turbo States: 15 (3300-4700 MHz)
        Number of P-States: 36 (1200-4700 MHz)
        Injected C-States for P000 (C1,C3,C6)
        Injected C-States for P001 (C1,C3,C6)
        Warning: ‘cpu-type’ may be set improperly (0x0402 instead of 0x0a02)
        Warning: ‘system-type’ may be set improperly (1 instead of 3)

      • What do you mean by “you should try -h”? Where do I type that? When? In what context? I know absolutely nothing but I am getting the same error. I have an i7 2600k and ASUS P8Z68-V as Yosemite, attempting 4200mhz. Here is my terminal readout after I created an SSDT and tried to add a new frequency:

        ssdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl
        v6.6 Copyright (c) 2013 by † Jeroen
        v15.6 Copyright (c) 2013-2015 by Pike R. Alpha
        ———————————————————–
        Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <

        gDataPath: /Users/miminguyen/Library/ssdtPRGen/Data

        Error: Invalid argument detected: 4200
        Aborting …
        Done.

  2. Hi Pike. thanks for the sharing.

    When I use the Scripts v12, I have two warning message. Would you help to explain more ?

    1. ‘system-type’ may be set improperly (3 instead of 1)

    2. plus, I’m using XEON 1230 V2 IVY version. If I put the script suggested processor type code((I can’t remember but such as below ) in my config.plist, The system profiler shows Xeon 1235 E5 not a 1230 V2..

    Do I need to fix ? if so, How I can fix it

    if not, those two warnings are only for the cosmetic ?

    Thank you

  3. Pike,

    I had to add a definition for the Sandy Bridge Xeon E5-2620 v1…

    # E5-2600 Xeon Processor Series
    E5-2687W,150,0,3100,3800,8,16
    ++E5-2620,95,0,2000,2500,6,12

    If I don’t use this it pulls the v2 Ivy Bridge data instead.
    Just an FYI if this looks right to you and you want to add it to the script.

    Can’t fully test as it’s not working yet… On a P9X79WS and the MSR might be locked… not sure yet.
    Thanks!
    David

  4. For some reason i always get unknown error with extracting ssdt from 1650v2
    Is it correct and not in the list?
    E5-1650v2 130w 3600-3900 6-12

    thnx
    T2S

  5. Thnx. testing in 5min. Let you know

    Hi Pike,

    Sorry to say but still the same error.
    If i look into the cpu types in the latest 12,6 script there appears to be a small typo. 2x 1660 v2 at line 594/595.
    Don’t know how i can edit script.

    Thnx t2m

    Btw what kind off settings would you us for the 1650 v2 cpu with unlocked msr?

    • Oh boy. What a stupid error. Fixed in v12.7 Thanks!

      That depends on what you want to use. Is that XCPM (mach_kernel power management) or not? If not, then I would suggest to use -w 3

      • Pike, why are you saying depends on what you want to use?
        Please, could you elaborate better this point?
        Till now I was thinking that It depends by the kind of CPU that users have and maybe, like Apple wants that PM is used in their system.
        or not?
        Thank you again for your help and efforts

      • Big thnx.
        But it seems that there’s 1 other problem that I need to address.
        It appears that my bootloader (Chameleon) prevents it from correct detection ( getCPUIDInfo: this is an unknown CPU model 0x3e) whatever cpuid I use in smbios. without cpuid added, Mac detected it correct in “about this mac”
        Not sure if thats true, but testing different loader is the next thing to test.

        Let you know
        t2m

  6. Hey Piker, just wanted to thank you for writing such a great script! My CPU thanks you even more for being able to rest and kick in Turbo when needed!

    Sabertooth X79, 3930k, BIOS 4608. Clover & Chameleon boot options. Rampage ssdt & ssdt-1, YOUR generated ssdt-2, Mac Pro 6,1 with stepdict patch from Macmini,

    I used -f 3200 -turbo 3800 -c 1 -w 3 -x 1
    with your ssdtPRGen.sh version 12.6

    When using Chameleon bootloader I was able to use Omni’s MSRpatcher.dylib v007 to change the MSR_PKGC3_IRTL & MSR_PKGC6_IRTL to a proper number.

    Although, I have to say, I get the same exact performance on clover where it shows 0x0 for MSR_PKGC3_IRTL & MSR_PKGC6_IRTL …cause I don’t know how to implement what’s happening in MSRpatcher.dylib v007 in Clover….but from what I can tell, the computer seems to act exactly the same either way I boot.

    Good Frequency changes from 1.2 – 3.8Ghz and good power from roughly 8W up to 102 W in HWMonitor & IPG

    Everything seems to be working great as far as I can tell…
    As you can see below, I never see the P-State (**) on 13-21, or in HWmon, but in IPG see lots of 1.3Ghz, 1.35Ghz, 1.4Ghz…etc…

    : AICPUPMI: logMSRs……………………….: 1
    : AICPUPMI: logIGPU……………………….: 0
    : AICPUPMI: logCStates…………………….: 1
    : AICPUPMI: logIPGStyle……………………: 1
    : AICPUPMI: MWAIT C-States…………………: 135456
    : AICPUPMI: MSR_CORE_THREAD_COUNT……(0x35) : 0x6000C
    : AICPUPMI: MSR_PLATFORM_INFO……….(0xCE) : 0xC0070012000
    : AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E000403
    : AICPUPMI: MSR_PMG_IO_CAPTURE_BASE….(0xE4) : 0x10414
    : AICPUPMI: IA32_MPERF……………..(0xE7) : 0x22C08074
    : AICPUPMI: IA32_APERF……………..(0xE8) : 0x1756B746
    : AICPUPMI: MSR_FLEX_RATIO………….(0x194) : 0xE0000
    : AICPUPMI: MSR_IA32_PERF_STATUS…….(0x198) : 0x278D00002300
    : AICPUPMI: MSR_IA32_PERF_CONTROL……(0x199) : 0x2300
    : AICPUPMI: IA32_CLOCK_MODULATION……(0x19A) : 0x0
    : AICPUPMI: IA32_THERM_STATUS……….(0x19C) : 0x88360000
    : AICPUPMI: IA32_MISC_ENABLES……….(0x1A0) : 0x850089
    : AICPUPMI: MSR_MISC_PWR_MGMT……….(0x1AA) : 0x400001
    : AICPUPMI: MSR_TURBO_RATIO_LIMIT……(0x1AD) : 0x2323232324252626
    : AICPUPMI: IA32_ENERGY_PERF_BIAS……(0x1B0) : 0x0
    : AICPUPMI: MSR_POWER_CTL…………..(0x1FC) : 0x2504005B
    : AICPUPMI: MSR_RAPL_POWER_UNIT……..(0x606) : 0xA1003
    : AICPUPMI: MSR_PKG_POWER_LIMIT……..(0x610) : 0x69F40005A9F40
    : AICPUPMI: MSR_PKG_ENERGY_STATUS……(0x611) : 0xAB7A8D4
    : AICPUPMI: MSR_PKGC3_IRTL………….(0x60a) : 0x8850
    : AICPUPMI: MSR_PKGC6_IRTL………….(0x60b) : 0x8868
    : AICPUPMI: MSR_PKGC7_IRTL………….(0x60c) : 0x0
    : AICPUPMI: MSR_PP0_CURRENT_CONFIG…..(0x601) : 0x141494800007F8
    : AICPUPMI: MSR_PP0_ENERGY_STATUS……(0x639) : 0x6186938
    : AICPUPMI: MSR_PP0_POLICY………….(0x63a) : 0x0
    : AICPUPMI: MSR_PKG_C2_RESIDENCY…….(0x60d) : 0x491475020
    : AICPUPMI: MSR_PKG_C3_RESIDENCY…….(0x3f8) : 0x89126460
    : AICPUPMI: MSR_PKG_C7_RESIDENCY…….(0x3fa) : 0x0
    : AICPUPMI: CPU Low Frequency Mode………….: 1200 MHz
    : AICPUPMI: CPU Maximum non-Turbo Frequency….: 3200 MHz
    : AICPUPMI: CPU Maximum Turbo Frequency……..: 3800 MHz
    : AICPUPMI: CPU P-States [ (12) 18 35 ]
    : AICPUPMI: CPU C3-Cores [ 1 5 6 8 9 ]
    : AICPUPMI: CPU C6-Cores [ 0 1 3 6 ]
    : AICPUPMI: CPU P-States [ (12) 18 26 35 ]
    AICPUPMI: CPU C3-Cores [ 1 2 4 5 6 7 8 9 10 ]
    AICPUPMI: CPU C6-Cores [ 0 1 3 6 10 11 ]
    AICPUPMI: CPU P-States [ (12) 15 18 26 35 ]
    : AICPUPMI: CPU C3-Cores [ 0 1 2 4 5 6 7 8 9 10 ]
    AICPUPMI: CPU C6-Cores [ 0 1 2 3 5 6 7 8 9 10 11 ]
    AICPUPMI: CPU P-States [ (12) 15 16 18 26 35 ]
    AICPUPMI: CPU C3-Cores [ 0 1 2 4 5 6 7 8 9 10 11 ]
    : AICPUPMI: CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]
    : AICPUPMI: CPU P-States [ (12) 15 16 18 26 27 35 ]
    : AICPUPMI: CPU C3-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]
    : AICPUPMI: CPU P-States [ (12) 15 16 18 19 26 27 35 ]
    : AICPUPMI: CPU P-States [ (12) 15 16 18 19 20 26 27 35 ]
    : AICPUPMI: CPU P-States [ (12) 15 16 17 18 19 20 26 27 35 ]
    : AICPUPMI: CPU P-States [ (12) 13 15 16 17 18 19 20 26 27 35 ]
    : AICPUPMI: CPU P-States [ (12) 13 15 16 17 18 19 20 25 26 27 35 ]
    : AICPUPMI: CPU P-States [ (12) 13 15 16 17 18 19 20 22 25 26 27 35 ]
    : AICPUPMI: CPU P-States [ 12 13 15 16 17 18 19 20 22 25 26 27 29 (35) ]
    : AICPUPMI: CPU P-States [ 12 13 15 16 17 18 19 20 22 25 26 27 29 (32) 35 ]
    : AICPUPMI: CPU P-States [ (12) 13 15 16 17 18 19 20 22 25 26 27 29 30 32 35 ]
    : AICPUPMI: CPU P-States [ (12) 13 15 16 17 18 19 20 22 25 26 27 29 30 31 32 35 ]
    : AICPUPMI: CPU P-States [ 12 13 15 16 17 18 19 20 22 25 26 27 29 30 31 32 35 (37) ]
    : AICPUPMI: CPU P-States [ 12 13 15 16 17 18 19 20 22 25 26 27 28 29 30 31 32 (35) 37 ]
    : AICPUPMI: CPU P-States [ (12) 13 15 16 17 18 19 20 22 23 25 26 27 28 29 30 31 32 35 37 ]
    : AICPUPMI: CPU P-States [ 12 13 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32 (35) 37 ]
    : AICPUPMI: CPU P-States [ 12 13 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32 (35) : AICPUPMI: CPU P-States [ (12) 13 15 16 17 18 19 20 22 23 24 25 26 27 28 29 30 31 32 34 35 36 37 ]
    : AICPUPMI: CPU P-States [ 12 13 15 16 17 18 19 20 21 (22) 23 24 25 26 27 28 29 30 31 32 34 35 36 37 ]
    ]: AICPUPMI: CPU P-States [ (12) 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 34 35 36 37 ]
    : AICPUPMI: CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 34 35 36 37 (38) ]
    : AICPUPMI: CPU P-States [ 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 (35) 36 37 38 ]

    • You see more power state changes with the Intel Power Gadget and AppleIntelCPUPowerManagmenetInfo.kext in IPG mode because they basically ignore what Apple’s XCPM and other drivers (kexts) triggers. In other words; there is hardware and software power management at work, but some of it won’t show up in MSRDumper and HWMonitor (apparently) or other tools.

      • Pike, during my tests I did many tries to understand what happens with different tools to have an output to compare datas.

        In my case, using X86Platform* to manage PM and, due my CPU type (IVY Bridge EP), a MacPro.6.1 smbios.plist, I have all C3 , C6 and P states from 12 to 36 printed by your latest AICPUPMI 3.3 tool
        In this case. PM is working with low wattage values according to IPG and HW.
        But, according to these tools multiplier doesn’t reach lower states
        I see that changing system definition from MacPro6.1 to others like MacMini6,2 or iMac , also IPG and HW have an output similar (pretty identical) to AICPUPMI output.
        Further investigation produced this statement.
        It is possible to change in X86PlatformPluginFamily.kext/Contents/Plugin/X86PlatformPlugin.kext/Contents/resourcesMac-F60DEB81FF30ACF6/IOPlatformPowerProfile/StepContextDict with others like Mac Mini 6.2 ( Mac-F65AE981FFA204ED) to have all tools working “well” with same output, but I know this should not be our goal.
        Now my question is…
        What does it means? 🙂

  7. Hey Pike,

    sorry to bother you, but since 10.9.2 my computer crashes, when i try to wake it from sleep.
    Without your ssdt, everything seems to work just fine.

    If there is any way, to provide more information. Just ask.

    My Configuration:

    System: 10.9.2
    BL: Clover
    CPU: i5-4570
    Mainboard: GA-Z87-D3HP
    Graphics: ASUS GeForce GTX 650

    Anonymous UUID: 1CA4801E-F7E3-DXXXXXXXXXXXXXXXX

    Tue Mar 4 14:21:58 2014
    panic(cpu 3 caller 0xffffff80002dbe2e): Kernel trap at 0xffffff80002a3278, type 13=general protection, registers:
    CR0: 0x000000008001003b, CR2: 0x00007fff55564ea8, CR3: 0x0000000012552004, CR4: 0x00000000001606e0
    RAX: 0xffefff800aee4460, RBX: 0xffffff800aee2018, RCX: 0xffffff8018b44000, RDX: 0x0000000000000821
    RSP: 0xffffff80f69bb9d0, RBP: 0xffffff80f69bba00, RSI: 0x0000000000004000, RDI: 0xffffff801a3d1000
    R8: 0x00000000000051eb, R9: 0x0000000000000000, R10: 0x00007fff722313e0, R11: 0x0000000000000246
    R12: 0x0000000000000000, R13: 0x0000000000004000, R14: 0x0000000000004000, R15: 0xffffff801a3d1000
    RFL: 0x0000000000010206, RIP: 0xffffff80002a3278, CS: 0x0000000000000008, SS: 0x0000000000000010
    Fault CR2: 0x00007fff55564ea8, Error code: 0x0000000000000000, Fault CPU: 0x3

    Backtrace (CPU 3), Frame : Return Address
    0xffffff80eec45df0 : 0xffffff8000222fa9
    0xffffff80eec45e70 : 0xffffff80002dbe2e
    0xffffff80eec46040 : 0xffffff80002f3326
    0xffffff80eec46060 : 0xffffff80002a3278
    0xffffff80f69bba00 : 0xffffff800026cddb
    0xffffff80f69bbb90 : 0xffffff80003d2773
    0xffffff80f69bbbf0 : 0xffffff800041502d
    0xffffff80f69bbcf0 : 0xffffff800056b02a
    0xffffff80f69bbd80 : 0xffffff80003fd9b1
    0xffffff80f69bbe00 : 0xffffff80003f3565
    0xffffff80f69bbe50 : 0xffffff80005efa7e
    0xffffff80f69bbef0 : 0xffffff80005ef88f
    0xffffff80f69bbf50 : 0xffffff800063e363
    0xffffff80f69bbfb0 : 0xffffff80002f3b26

    BSD process name corresponding to current thread: taskgated
    Boot args: -v slide=0

    Mac OS version:
    13C64

    Kernel version:
    Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64
    Kernel UUID: 9FEA8EDC-B629-3ED2-XXXXXXXXXXXXXXX
    System model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)

    System uptime in nanoseconds: 327056527299
    last loaded kext at 53573100098: com.apple.filesystems.msdosfs 1.9 (addr 0xffffff7f817ed000, size 65536)
    loaded kexts:

    • Make sure to use “Macmini6,2” and not “MacMini6,2”
      For Ivy Bridge processors you should run ./ssdtPRGen.sh -w 3
      Compile the AppleIntelCPUPowerManagmementInfo.kext from the source code and the KP will be solved.

  8. Hello p.alpha and ty for everything you done for hackintosh 🙂 After long test I noticed that intel power gadget show full speedstep on my i5-4670k. from x8 to 4.5ghz. I cheecked same programs, like adobe PS ,illustrator,handbrake,web browsers… And result in frequency is close to same +- 0,2Ghz. with windows 8.1 task manager readings or intel app for windows.. Can we trust Intel app and his speedstep or frequency???

  9. Pike,

    Thanks for adding E5-2620 V1 data to the script.
    I still cannot get this to with with anything I try…
    Have used -turbo 2500, tried -c 0, -w 0, and a few other combinations.
    I am using 10.9.2 (the released version) and Rampage Dev’s SSDT-based solution on a P9X79WS. The only way I can get any throttling at all is to add NullCPU. Any solution that is expected to work gives only 20x (and no turbo).

    1. Any basic ideas in troubleshooting? Do you perchance have a working power SSDT for the v1 E5-2620?

    2. What is the most “stable” version of the script to troubleshoot from?

    3. AICPMInfo.kext still gives me a KP. Any suggestion on mods/switches to allow this work so I can get more debugging data?

    Thanks!
    David

    • BTW I was able to get AICPMInfo.kext to not KP by simply re-compiling it locally. I’m getting output that makes me think the states might not even be recognized:
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: logMSRs……………………….: 1
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_CORE_THREAD_COUNT……(0x35) : 0x6000C
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PLATFORM_INFO……….(0xCE) : 0xC0064011400
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E000407
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PMG_IO_CAPTURE_BASE….(0xE4) : 0x10414
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_FLEX_RATIO………….(0x194) : 0x0
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_IA32_PERF_STATUS…….(0x198) : 0x1DF100001400
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_IA32_PERF_CONTROL……(0x199) : 0x1400
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_MISC_PWR_MGMT……….(0x1AA) : 0x400000
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_TURBO_RATIO_LIMIT……(0x1AD) : 0x1717171718181919
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_POWER_CTL…………..(0x1FC) : 0x2504005B
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_RAPL_POWER_UNIT……..(0x606) : 0xA1003
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PKG_POWER_LIMIT……..(0x610) : 0x68390005A82F8
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PKG_ENERGY_STATUS……(0x611) : 0x5D9F848
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PKGC3_IRTL………….(0x60a) : 0x0
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PKGC6_IRTL………….(0x60b) : 0x0
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PKGC7_IRTL………….(0x60c) : 0x0
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PP0_CURRENT_CONFIG…..(0x601) : 0x141494800007F8
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PP0_POWER_LIMIT……..(0x638) : 0x0
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PP0_ENERGY_STATUS……(0x639) : 0x3C04319
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PP0_POLICY………….(0x63a) : 0x0
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PKG_C2_RESIDENCY…….(0x60d) : 0x0
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PKG_C3_RESIDENCY…….(0x3f8) : 0x0
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PKG_C6_RESIDENCY…….(0x3f9) : 0x0
      Mar 15 16:08:50 localhost kernel[0]: AICPUPMI: MSR_PKG_C7_RESIDENCY…….(0x3fa) : 0x0

    • Got throttling to work… Turned out there was an older conflicting kext in myHack.kext.
      Using patched AICPM.kext from RampageDev.
      Still not getting lower states, but a major breakthrough!

      • That is good news!

        Sorry that I couldn’t be of any help. Still busy with my home. Hopelessly behind schedule, going over our budget. Need to catch up with my work.

      • Ha! I so know what that is like… working on the home or homestead. Keep plugging along and thanks for all your help!

  10. ssdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl
    v6.6 Copyright (c) 2013 by † Jeroen
    v12.7 Copyright (c) 2013-2014 by Pike R. Alpha
    ———————————————————–
    Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <

    Override value: (-c) CPU type, now using: Sandy Bridge!
    Override value: (-d) debug mode, now using: 0!
    Override value: (-f) clock frequency, now using: 2500 MHz!
    Override value: (-t) maximum TDP, now using: 130 Watt!

    System information: Mac OS X 10.9.2 (13C64)
    Brandstring 'Genuine Intel(R) CPU @ 2.50GHz'

    Error: Unknown processor model …
    Aborting …
    Done

    Nay Hint? I'm using intel Xeon ES. thanks

  11. Pike, I’m using a 3rd Gen i7-3537U (Ivy Bridge mobile), here’s the info from my SSDT.
    {
    Store (“ssdtPRGen version….: 12.8 / Mac OS X 10.9.2 (13C64)”, Debug)
    Store (“target processor…..: i7-3537U”, Debug)
    Store (“running processor….: Intel(R) Core(TM) i7-3537U CPU @ 2.00GHz”, Debug)
    Store (“baseFrequency……..: 800”, Debug)
    Store (“frequency…………: 2000”, Debug)
    Store (“busFrequency………: 100”, Debug)
    Store (“logicalCPUs……….: 4”, Debug)
    Store (“maximum TDP……….: 17”, Debug)
    Store (“packageLength……..: 24”, Debug)
    Store (“turboStates……….: 11”, Debug)
    Store (“maxTurboFrequency….: 3100”, Debug)
    Store (“machdep.xcpm.mode….: 1”, Debug)
    }
    I’m using a MacBookPro11,1 smbios.plist and booting with Clover. Everything is beautiful. I am wondering if this set-up is okay because this smbios is for Haswell? Also, under energy saver prefs display sleep is the only option (and prevent sleep when display sleeps on AC)? Basically, if the display sleeps the system sleeps (which kinda makes sense) and seeing as the wake from sleep is instant, it isn’t an issue. I’m seeing GT idle freq 0.35 Ghz with Intel Power Gadget and it steps up to 1.20, which meets spec. BUT I’m seeing power go above 17W, sometimes up-to 20W from time to time. It idles around 5-6W. I tried AICPUPM.kext but it gave me a kernel panic. I have no issues with the setup, I just want to be sure I’m not going to fry my CPU.

    • I should add, my motherboard is patched with PMPatch, its a “Lenovo” board, I’m not entirely sure of the chipset, DPCIManager lists it as a C210 Series. HM77, but also a Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port.

    • Hi,

      First. Welcome here. But no. I myself would not use a Haswell SMBIOS config for Ivy Bridge processors, and that is also why I would say that it is better for you to use a MacBookPro10,N SMBIOS config, especially for your mobility processor.

      TIP: run ./ssdtPRGen.sh -w 3

      This will make the script inject workarounds for Ivy Bridge processors, something Apple expects for your processor 😉

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s