Contribute
Register

[CLOSED] Multibeast doesn't patch CPU Power Management

Status
Not open for further replies.
Joined
Jul 25, 2012
Messages
8
Motherboard
P8Z77-V LE
CPU
Intel i7 2600K 4.6Ghz
Graphics
nVidia GTX 680 4GB
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. iOS
Hello,
I'm trying to run the Patched AppleIntelCPUPowerManagement option, and Multibeast reports success at the end, but when I reboot, the file isn't patched and NullCPUManagement is still there. Any ideas?

Also just a side note that I thought was weird. Even though NullCPUManagement is there and loading each time I start my computer, speedstep and sleep works perfectly fine. I was under the impression that those wouldn't work with NullCPU in place.
 
Multibeast doesn't patch CPU Power Management

According to that log:

./postinstall: Found and deleted /System/Library/Extensions/NullCPUPowerManagemenm.kext

So it was deleted and:

Installed "AppleIntelCPUPowerManagement-216.0.0"

and the patched AppleIntelCPUPowerManagement was installed.
 
Multibeast doesn't patch CPU Power Management

I know the log says that, but if you look at my verbose start up log, you'll see NullCPU is still loading. Also if you look at the image of my finder window, you'll see it's still there in my extensions. If I remove it and reboot, the system panics. Which leads me to believe the other file is not being patched...

Nov 3 13:36:58 --- last message repeated 6 times ---
Nov 3 13:36:57 localhost kernel[0]: Longterm timer threshold: 1000 ms
Nov 3 13:36:57 localhost kernel[0]: PMAP: PCID enabled
Nov 3 13:36:57 localhost kernel[0]: Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
Nov 3 13:36:57 localhost kernel[0]: vm_page_bootstrap: 4057595 free pages and 103941 wired pages
Nov 3 13:36:57 localhost kernel[0]: kext submap [0xffffff7f807a5000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff80007a5000]
Nov 3 13:36:57 localhost kernel[0]: zone leak detection enabled
Nov 3 13:36:57 localhost kernel[0]: "vm_compressor_mode" is 4
Nov 3 13:36:57 localhost kernel[0]: standard timeslicing quantum is 10000 us
Nov 3 13:36:57 localhost kernel[0]: standard background quantum is 2500 us
Nov 3 13:36:57 localhost kernel[0]: mig_table_max_displ = 74
Nov 3 13:36:57 localhost kernel[0]: TSC Deadline Timer supported and enabled
Nov 3 13:36:57 localhost kernel[0]: NullCPUPowerManagement::init: properties=0xffffff801fe369c0
Nov 3 13:36:57 localhost kernel[0]: NullCPUPowerManagement::start
Nov 3 13:36:57 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=0 Enabled
Nov 3 13:36:57 localhost kernel[0]: AppleACPICPU: ProcessorId=2 LocalApicId=2 Enabled
Nov 3 13:36:57 localhost kernel[0]: AppleACPICPU: ProcessorId=3 LocalApicId=4 Enabled
Nov 3 13:36:57 localhost kernel[0]: AppleACPICPU: ProcessorId=4 LocalApicId=6 Enabled
Nov 3 13:36:57 localhost kernel[0]: calling mpo_policy_init for TMSafetyNet
Nov 3 13:36:57 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Nov 3 13:36:57 localhost kernel[0]: calling mpo_policy_init for Sandbox
Nov 3 13:36:57 localhost kernel[0]: Security policy loaded: Seatbelt sandbox policy (Sandbox)
Nov 3 13:36:57 localhost kernel[0]: calling mpo_policy_init for Quarantine
Nov 3 13:36:57 localhost kernel[0]: Security policy loaded: Quarantine policy (Quarantine)
Nov 3 13:36:57 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Nov 3 13:36:57 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Nov 3 13:36:57 localhost kernel[0]: MAC Framework successfully initialized
Nov 3 13:36:57 localhost kernel[0]: using 16384 buffer headers and 10240 cluster IO buffer headers
Nov 3 13:36:57 localhost kernel[0]: AppleKeyStore starting (BUILT: Sep 19 2013 22:20:34)
Nov 3 13:36:57 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Nov 3 13:36:57 localhost kernel[0]: ACPI: sleep states S3 S4 S5
Nov 3 13:36:57 localhost kernel[0]: pci (build 22:16:29 Sep 19 2013), flags 0x63008, pfm64 (36 cpu) 0xf80000000, 0x80000000
Nov 3 13:36:57 localhost kernel[0]: HWSensors v5.3.820 Copyright 2013 netkas, slice, usr-sse2, kozlek, navi, THe KiNG, RehabMan. All rights reserved.
Nov 3 13:36:57 localhost kernel[0]: waitForSystemMapper
Nov 3 13:36:57 localhost kernel[0]: Backtrace 0xffffff80006b7239 0xffffff80006b6d1d 0xffffff7f8191a9a6 0xffffff7f8191a0f1 0xffffff8000692180 0xffffff800068e119 0xffffff8000693093
34B5mbL.png
 
Multibeast doesn't patch CPU Power Management

According to the log file:

Configuring volume "Mac OS X"

So that is the volume you ran MultiBeast against and I bet is not the volume your are booting from.

Do a Get Info on NullCPU so I can see the volume name of where it is installed.
 
Multibeast doesn't patch CPU Power Management

I'm not exactly sure what you mean. When I run Get Info on NullCPU it shows it being on Mac OS X volume. Also when I install Mac, I install it with only one hard drive plugged in and then connect the others once it has been completely set up. There are no other partitions on the hard drive or any other options when installing other than the volume Mac OS X.
 
Multibeast doesn't patch CPU Power Management

According to the logs MultiBeast worked correctly. But I found the bug, a typo in the name being deleted. So it installed the patched AppleIntelCPUPowerManagement.kext but isn't deleting NullCOPUPowerManagement.kext.

Good catch as this bug also exists in MultiBeast 5.5.3 for Mountain Lion.

This will be fixed in next build of MultiBeast.
 
Multibeast doesn't patch CPU Power Management

According to the logs MultiBeast worked correctly. But I found the bug, a typo in the name being deleted. So it installed the patched AppleIntelCPUPowerManagement.kext but isn't deleting NullCOPUPowerManagement.kext.

Good catch as this bug also exists in MultiBeast 5.5.3 for Mountain Lion.

This will be fixed in next build of MultiBeast.

Alright, thanks man for all your hard work! :)
 
Multibeast doesn't patch CPU Power Management

Would this affect my ability to wake from sleep? At the moment waking results in a system reboot.
 
Status
Not open for further replies.
Back
Top