Jump to content
542 posts in this topic

Recommended Posts

  • 2 months later...

Greetings,

 

Will this work for El Capitan 10.11.6?

 

I have as follows:

 

Intel core i3 2nd Generation Sandybridge 2310 @ 2100GHz 

TDP: 35

Intel HD3000

 

This information provided by Ark at Intel, thanks to your link.

 

Had to use Enoch latest version 2839.  

Clover latest caused my desktop to have 4 screens. or 4 mini desktops.  Haven't figured out why yet because this is my first go.  Been at this now for 1 month.  Many long nights.

 

I'm still not sure what to use strictly in org.chameleon.boot.plist, its' been quite trying.  But it's fun.

 

Before I embark I would like a definite as I'm overseas in nomansland and I don't have a PC store to go and buy a new pc if I brick this one.  Have had many reinstalls due to not knowing what to configure in the boot loader and  what kexts to place in SLE.  Wow what a tremendous learning curve.

 

However it is fun.

 

Thank you for providing this post.

 

I hope it works for my unit.

 

Mak

 

 

Yes this works for all OS X versions, including EC 10.11.x and Sierra 10.12 too.

 

You'd normally never brick a PC by trying to Hackintosh it unless you hit it with a hammer. The risk of bricking is usually limited to more adventurous stuff like modifying the BIOS.

  • 3 weeks later...
  • 2 weeks later...

Thank you Herve' and Bronxtek

 

 

Readout from AppleIntel kext:

 

CPU P-States [ (8) 19 21 ] iGPU P-States [ (13) ]

CPU C3-Cores [ 0 2 ]

CPU C6-Cores [ 2 3 ]

CPU C7-Cores [ 0 1 2 3 ]

CPU P-States [ (8) 9 19 21 ] iGPU P-States [ (13) ]

CPU C3-Cores [ 0 1 2 3 ]

CPU C6-Cores [ 0 1 2 3 ]

CPU P-States [ (8) 9 17 19 21 ] iGPU P-States [ (13) ]

CPU P-States [ (8) 9 10 17 19 21 ] iGPU P-States [ (13) ]

CPU P-States [ (8) 9 10 12 17 19 21 ] iGPU P-States [ (13) ]

CPU P-States [ (8) 9 10 12 14 17 19 21 ] iGPU P-States [ (13) ]

CPU P-States [ (8) 9 10 11 12 14 17 19 21 ] iGPU P-States [ (13) ]

CPU P-States [ (8) 9 10 11 12 14 17 19 20 21 ] iGPU P-States [ (13) ]

CPU P-States [ (8) 9 10 11 12 13 14 17 19 20 21 ] iGPU P-States [ (13) ]

CPU P-States [ (8) 9 10 11 12 13 14 15 17 19 20 21 ] iGPU P-States [ (13) ]

CPU P-States [ 8 9 10 11 12 13 14 15 17 18 19 20 (21) ] iGPU P-States [ (13) ]

CPU P-States [ (8) 9 10 11 12 13 14 15 16 17 18 19 20 21 ] iGPU P-States [ (13) ]

 

 

BoboTechs-MacBook-Pro:~ bobotech$ kextstat|grep -y applelpc

   99    0 0xffffff7f82199000 0x3000     0x3000     com.apple.driver.AppleLPC (3.1) F51595F0-F9B1-3B85-A1C3-F984DAD4107E <90 12 5 4 3>

BoboTechs-MacBook-Pro:~ bobotech$ kextstat|grep -y applelintel

BoboTechs-MacBook-Pro:~ bobotech$ kextstat|grep -y appleintel

   21    0 0xffffff7f82329000 0x2b000    0x2b000    com.apple.driver.AppleIntelCPUPowerManagement (219.0.0) E9D6E863-1BAB-345E-99EC-1C076E486F53 <7 6 5 4 3 1>

   30    0 0xffffff7f82324000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (219.0.0) B802638B-251C-3602-BA8C-001F87228765 <7 6 5 4 3 1>

   82    0 0xffffff7f82207000 0x2e000    0x2e000    com.apple.driver.AppleIntelSNBGraphicsFB (10.0.2) 488CC632-6F2B-3C8E-967C-4E95AF80AD6E <41 12 11 7 6 5 4 3 1>

   93    0 0xffffff7f8229a000 0x63000    0x63000    com.apple.driver.AppleIntelHD3000Graphics (10.0.2) 0D59523E-6E97-3ACE-B872-DF98D91B871C <41 12 7 5 4 3 1>

   97    0 0xffffff7f82247000 0x2000     0x2000     com.apple.driver.AppleIntelSlowAdaptiveClocking (4.0.0) 6FE984DD-A1FE-309E-83CF-B346989A6F17 <96 4 3>

BoboTechs-MacBook-Pro:~ bobotech$ kextstat|grep -y appleacpi

   13    2 0xffffff7f826f0000 0x66000    0x66000    com.apple.driver.AppleACPIPlatform (5.0) 27390D7F-A778-320C-A8DC-502A98AA531B <12 11 7 6 5 4 3 1>

   33    0 0xffffff7f82756000 0x7000     0x7000     com.apple.driver.AppleACPIEC (5.0) E87B6F88-364D-389C-8634-B14BE43240B7 <32 13 11 5 4 3>

   37    0 0xffffff7f82810000 0x3000     0x3000     com.apple.AppleACPIPS2Nub (1.1) 5A15C9C7-C029-3082-B7A0-36FFC5CA3F1B <11 7 4 3>

   40    0 0xffffff7f82760000 0x4000     0x4000     com.apple.driver.AppleACPIButtons (5.0) 2620A06F-8838-31F0-BB1D-D709C02B7F54 <39 15 13 11 7 6 5 4 3 1>

BoboTechs-MacBook-Pro:~ bobotech$ kextstat|grep -y acpi_smc

   92    0 0xffffff7f8167a000 0x10000    0x10000    com.apple.driver.ACPI_SMC_PlatformPlugin (1.0.0) 7224B682-B40F-3A4A-BCA0-82727D251ECB <91 90 85 12 11 7 6 5 4 3>

BoboTechs-MacBook-Pro:~ bobotech$ 

 
 
I patched the ACPICPUPM and ran the new ssdtPRGen for Sierra 10.12.1
the drivers or kexts are loading as before.  Power Off would not happen.  The system would halt and restart.
Been using Clovers Fix_Shutdown, Restart Reset values and played around with ACPI fixes and adds.
 
However I'm getting ready to test "shutdown" in a few.
 
I set the Kernel PM.  but at first was unsure because of the information.
 
Should I use "Kernel CPU?"  
 
I have checked in Kernel and Kext Patches:
 
AppleRTC
AsusAICPUPM
Kernel PM
 
These three only, but after patching with the script do I need to check the AsusAI in Clover config.plist?
 
I have SSDT sorted have 4 total as a result of ssdtPRGen in Patched folder + DSDT patched.
 
I have DropTables DMAR, SSDTCpuPM and SSDTCpuIOst
 
Drop OEM  checked
 
plugin type 0
 
Sorted SSDT's
SSDT.aml
SSDT-1.aml
SSDT-2.aml
SSDT-3.aml
 
Patch ACIP and Halt enabler
and Reset Address and Value to Mac
 
I noticed that ssdtPRGen uses my patched DSDT.  Should I put that into the patched folder?
 
Thank you for your guidance.
 
 
 
 
 
 
 
 

Herve'

 

I found your other site and downloaded the files:  ACPI, RTC, and kernel for 10.12.1.

 

In my config.plist what should I check and uncheck?

 

thank you very much!

 

Mak


Herve'

 

You're a genius!

 

My system POWERS OFF! 

 

Mac OS X Sierra 10.12.1

 

Kernel 

AsusAI

AppleIntelCPU

 

what should I do for my Clover config.plist?

 

I can send you my files?

 

Mak

  • 2 months later...

Did you read p1 of this thread?

 

Sandy Bridge and Ivy Bridge CPU power management operates through AICPUPM kext. So you need to patch the kext:

  1. if you use Clover, apply/activate the AsusAICPUPM patch
  2. if you use Chameleon/Enoch, patch the vanilla kext using the script provided on p1. Alternatively, replace the vanilla kext with a pre-patched copy or place the pre-patched kext in /L*/E*. If you up' the kext version to, say, 9xx, you'll sustain OS update without any CPU power management KP. In either case, you'll need to repair permissions and rebuild your cache.

CPU Power Management is handled by the kernel for Haswell CPU and beyond, so the vanilla kernel prevails in your case.

Did you read p1 of this thread?

 

Sandy Bridge and Ivy Bridge CPU power management operates through AICPUPM kext. So you need to patch the kext:

  1. if you use Clover, apply/activate the AsusAICPUPM patch
  2. if you use Chameleon/Enoch, patch the vanilla kext using the script provided on p1. Alternatively, replace the vanilla kext with a pre-patched copy or place the pre-patched kext in /L*/E*. If you up' the kext version to, say, 9xx, you'll sustain OS update without any CPU power management KP. In either case, you'll need to repair permissions and rebuild your cache.

CPU Power Management is handled by the kernel for Haswell CPU and beyond, so the vanilla kernel prevails in your case.

Thank you so much,I have power management by using Clover,but he is not clearly say Sandy Bridge and Ivy Bridge only need kext patch and Haswell need kext and kernel patch

<dict>
<key>Comment</key>
<string>AppleIntelCpuPM Kernel Panic fix</string>
<key>Find</key>
<data>4gAAAA8w</data>
<key>Name</key>
<string>AppleIntelCPUPowerManagement</string>
<key>Replace</key>
<data>4gAAAJCQ</data>
</dict>

The AICPUPM kext patch is for SB and IB CPUs only.

 

It's not required for Haswell CPUs and beyond. Those require the kernel patch, nothing else, i.e. since CPU PM is handled by kernel, the AICPUPM patch is not required.

so I do not need patch kernel and AICPUPM because i have ivy bridge?if I have haswell or skylake i need patch kernel,but no need patch AICPUPM?

Hi

 

I have a Sandy Bridge i5-2400 (Sandy Bridge) currently running Sierra with NullCPUPowerManagement.kext. To achieve working PM, Can I just apply the AsusAICPUPM patch on clover even though my machine is not an asus?

 

Do I also have to remove NullCPUPowerManagement.kext too?

 

 

 

 

  • 7 months later...

Did you read p1 of this thread?

 

Sandy Bridge and Ivy Bridge CPU power management operates through AICPUPM kext. So you need to patch the kext:

  1. if you use Clover, apply/activate the AsusAICPUPM patch
  2. if you use Chameleon/Enoch, patch the vanilla kext using the script provided on p1. Alternatively, replace the vanilla kext with a pre-patched copy or place the pre-patched kext in /L*/E*. If you up' the kext version to, say, 9xx, you'll sustain OS update without any CPU power management KP. In either case, you'll need to repair permissions and rebuild your cache.

CPU Power Management is handled by the kernel for Haswell CPU and beyond, so the vanilla kernel prevails in your case.

 

 I know its been a long time since this post but had question about my processor E5-2697v2 Ivy Bridge 12 core.  This is the same processor you can upgrade the real MacPro6,1 trashcan to :). Would you know offhand if this processor is natively supported by XCPM or AICPUPM?  I have an Asus X79 Sabertooth MB with that processor and although CPUPM seems to be working fine, X86PlatformPlugin loads and CPUPM is handled by AICPUPM and if XCPM is used natively on the real mac I am at a complete loss as to why it does not launch for my CPU?

 

Edited Next Day:

 

I got the answer looks like the real MacPro6,1 is natively using AICPUPM kext and not XCPM, Ivy Bridge-E

  • Allan unpinned this topic
×
×
  • Create New...