Mavericks ACPI / appleintelcpupowermanagement.kext Question

[RehabMan]

Again "Thank You RehabMan"!

There were 2 changes I made which solved my problem (all of which came to light after your assistance).

1. Used SSDT from MultiBeast instead of the one I created.

Interesting. A custom SSDT, if created correctly, is better than those in Multibeast.

2. Edited my "org.chameleon.Boot.plist" to include
<key>GenerateCStates</key>
<string>No</string>
<key>GeneratePStates</key>
<string>No</string>

Originally I omitted that since I thought default has those set at "No".

If omitted, they are default to No.

Currently I'm able to boot with the Patched AICPM.kext, have yet to try reinstalling the naive AICPM.kext

Based on my system specifications, do you think that's the way to go (Naive AICPM)?

1. UEFI (Patched)
2. Sandy Bridge Processor 2600K
3. (EVGA) Nvidia GTX 570
4. EVGA Z68 FTW MB

GOLD SERVICE STAR! ---------> RehabMan!

It will depend on whether your BIOS implements locked 0xE2 MSR or not, and how successful you were with the UEFI BIOS patch.

 

[BadKarma]

Interesting. A custom SSDT, if created correctly, is better than those in Multibeast.

I agree with every word of your statement. Especially "If created correctly". Most of the time it's something I missed which resulted in Error/Problem.

However, I've tried several methods of generating my own SSDT that resulted in not being able to boot 10.9 successfully. (Weird was being able to boot 10.8 and 10.7 with the same SSDT).

First attempt:
(From Terminal) RevoGirl ssdtPRGen.sh 34 3800

Second attempt:
MaciASL - pretty straight forward.

My inputs for i7 2600K (No OverClock)
TDP Max: 95
Max Turbo Frequency: 3800 (3.8 GHz)
Logical CPUs (Greater Than 0): 8
CPU Frequency (MHz): 3400

As for the correction to my org.chameleon.Boot.plist, thanks for the confirmation of the Defaults=No for P and C states.

As for the patched UEFI, I have since misplaced my copy of the original terminal output. It did patch one item, which is about all that I could remember and I recall finding someone else here in the forums asking PJALM about similar results (terminal output) and PJALM confirmed a successful patch.

All in all, thank you again for your assistance in resolving my AICPM issues. Very happy to be rid of NullCPUPowermanagement!

Cheers.

UPDATE: My system now works with naive AICPM (Patched UEFI).

 

[JackSlain]

hi,

i have the same problem like you have with booting maverick...kp with aicpm.

can you tell me your BIOS settings and exactly what you entered in MultiBeast?

 

[JackSlain]

BadKarma can you help me?

 

[BadKarma]

hi,

i have the same problem like you have with booting maverick...kp with aicpm.

can you tell me your BIOS settings and exactly what you entered in MultiBeast?

My problem was a bad SSDT. Though there's no way to know if that's the same for you.

You need to provide some information (Such as your System specifications (i.e. Motherboard, CPU, Graphics Card) and Verbose image of boot process hang) for someone to help you.

MultiBeast selections are made based on system configurations, again ours are probably different. No way of knowing unless you provide more details.

 

[N00Bster]

hey man i have sort of the same problem.

KP appleintelcpupowermanagement

I have a
I7 turbo boost CPU
Mavericks 10.9.1
Can boot with cpus=1 but not with cpus=4

I get an apple intel cpu power management kp with cpus=4 . I installed the appleintelcpupowermanagement patch from MB and still get a kp.

 

[davidm71]

Hi,

I just upgraded or did a fresh install of Mavericks 10.9.2 and found I needed NullCpu to boot into OSX whereas before I didn't need it as my Bios was patched to allow native power management. Little confused how to fix it. Can anyone post a 2600K ssdt also?

Thank you.

 

[RehabMan]

Hi,

I just upgraded or did a fresh install of Mavericks 10.9.2 and found I needed NullCpu to boot into OSX whereas before I didn't need it as my Bios was patched to allow native power management. Little confused how to fix it. Can anyone post a 2600K ssdt also?

Thank you.

You probably need DSDT patches as well as DropSSDT=Yes. The OEM CPU SSDT objects on many 6-series boards tends to cause problems for OS X...

This is the patch I use on my Intel DH67GD (amongst many others)

into definitionblock code_regex . insert
begin
Scope (_PR)\n
{\n
    Processor (CPU0, 0x00, 0x00000410, 0x06) {}\n
    Processor (CPU1, 0x01, 0x00000410, 0x06) {}\n
    Processor (CPU2, 0x02, 0x00000410, 0x06) {}\n
    Processor (CPU3, 0x03, 0x00000410, 0x06) {}\n
    Processor (CPU4, 0x04, 0x00000410, 0x06) {}\n
    Processor (CPU5, 0x05, 0x00000410, 0x06) {}\n
    Processor (CPU6, 0x06, 0x00000410, 0x06) {}\n
    Processor (CPU7, 0x07, 0x00000410, 0x06) {}\n
}\n
end;

You can generate an SSDT using either MaciASL or ssdtPRgen.sh.

 

[Mcherry4]

Hi I'm new to this site and I have a problem with booting up my newly installed os x maverick. When I use boot flag -v it shows that appleintelcpupowermanagement timed out, can you help?

 

[RehabMan]

Hi I'm new to this site and I have a problem with booting up my newly installed os x maverick. When I use boot flag -v it shows that appleintelcpupowermanagement timed out, can you help?

What hardware?