toleda
Moderator
- Joined
- May 19, 2010
- Messages
- 22,834
- Motherboard
- Asus Maximus VII Impact
- CPU
- i7-4770K
- Graphics
- RX 560 + HD4600
- Mac
- Classic Mac
- Mobile Phone
My mistake.I did not manually change
My mistake.I did not manually change
Not recommended. Removing states is a bad idea. The edited .aml is not correct.The .edited.aml file is the result of removing
the 'extra' speed state indicated elsewhere in this thread.
Now the real question is: Why would the SSDT cause Time Machine to see a 'High Thermal State'?
Script problem. Contact the author as noted.Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <
Ivy Bridge Core i5-3317U processor [0x306A9] setup [0x0604]
With a maximum TDP of 17 Watt, as specified by Intel
Warning: Low Frequency Mode is 0 (unknown/unconfirmed)
Now using 1200 MHz for Mobile processor
It looks to me like the 3570k has some XCPM issues, especially with clover. I have it working, but it took me a while.
be sure that:
-AppleLPC.kext is loaded
-use -w 3 for SSDT generator
-use -xcpm flag
if XCPM is loading then that is a good start. Missing states can be remedied.
also test sleep.
**EDIT**
SORRY MY BAD 3570K
UGH! Sorry about that, and for taking so long to check back. My System is stable, but every once in a while it will not wake from sleep. (turns on, but no gfx, no networking, no usb) Does anyone else have a different experience with 3570K/Cover/XCPM?
[FONT=Menlo]imac:pm madman$ cat /var/log/system.log | grep "XCPM"[/FONT]
[FONT=Menlo]May 28 01:52:04 localhost kernel[0]: XCPM: registered[/FONT]
[FONT=Menlo]May 28 01:52:25 imac kernel[0]: IOPPF: XCPM mode[/FONT]
[FONT=Menlo]May 28 01:52:25 imac kernel[0]: XCPM: P-state table mismatch (error:0x12)[/FONT]
[FONT=Menlo]May 28 01:52:25 imac kernel[0]: X86PlatformShim::sendPStates - pmCPUControl (XCPMIO_SETPSTATETABLE) returned 0x12[/FONT]
Oh and AICPUPMI logging should always be done with logIGPStyle set to FALSE otherwise is serves no purpose. At least not for debugging problems.
The first turbo ratio should be set to 36, manually, because 'Auto' is still not functioning properly. Look here:
MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x27272727
With that even a single core will run at 3.9 GHz. Not good for power management.
Title of thread, Native CPU/IGPU Power Management. I set to True for IGPU PM confirmation. Users should remove AICPUPMI.kext when satisfied CPU/IGPU PM is working.Why is this value set to TRUE in the AppleIntelCPUPowerManagementInfo.kext attached in post #1 then? Should it not be?
Title of thread, Native CPU/IGPU Power Management. I set to True for IGPU PM confirmation. Users should remove AICPUPMI.kext when satisfied CPU/IGPU PM is working.
You have a 3.5GHz processor and thus you should use that and nothing else. Also. The first turbo ratio should be set to 36, manually, because 'Auto' is still not functioning properly. Look here:
MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x27272727
With that even a single core will run at 3.9 GHz. Not good for power management.
Oh and AICPUPMI logging should always be done with logIGPStyle set to FALSE otherwise is serves no purpose. At least not for debugging problems.