Contribute
Register

Quick Guide to Generate a SSDT for CPU Power Management

I've got a 6700k on a z170 mobo with a Radeon RX580 and iMacPro1,1 as a system definition. OP lists iMac17,1 as the preferred system definition for my proc/mobo combo. I've tried the clover PluginType method, but that doesn't seem to work. Will this method work, or must I use the correct system definition to get power management to work?
 
I've got a 6700k on a z170 mobo with a Radeon RX580 and iMacPro1,1 as a system definition. OP lists iMac17,1 as the preferred system definition for my proc/mobo combo. I've tried the clover PluginType method, but that doesn't seem to work. Will this method work, or must I use the correct system definition to get power management to work?

I've tried both iMacPro1,1 and iMac17,1. I think iMac17,1 is more stable with no issues. You're not the only one who is experiencing PM issues with 6700K. I spent hours reading thru the forum and nobody had solutions to fix it. I'm using OpenCore and its PM seems to do a better job than Clover. I was able to get idle speed at 1 Ghz. It's close enough to 800 Mhz.

I plan to do some more testings with iMacPro1,1 to see if I can get it down to 800 Mhz at idle.

 
I did more test. The results are the same, however, there was kernel panic with iMacPro1,1 with OpenCore using the same configuration for iMac17,1. I was using my custom SSDT-USBX to assign 15 ports but I had to enable USB patches in Kernel for it to boot up properly with iMacPro1,1. It doesn't make any sense to use both USB patches and it is strongly discouraged to use SSDT-USBX along with USB patches as it may cause conflicts or panic down the road. This is not an issue with iMac17,1 so it's obviously iMac17,1 is a better choice for the type of motherboard and processor we have.

Therefore, I think that with iMac17,1 with 1 Ghz as idle speed is acceptable as it's more likely Apple designed this way for 6700K. It looks like there is nothing else I can do from this point unless if someone found a workable solution.
 
Last edited:
I tried dynamically loading the Appleintelnfo.kext but system froze with Kernel panic:
Code:
l trap at 0xffffff7f9c953b4c, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x000070000da6e2d8, CR3: 0x000000001d2f9000, CR4: 0x00000000000226e0
RAX: 0xffffff8118bfb2f8, RBX: 0x0000000000000000, RCX: 0x000000000000060a, RDX: 0xffffff8118bfb2f8
RSP: 0xffffff8e330a2804, RBP: 0xffffff8e330a2810, RSI: 0x0000000000000000, RDI: 0x000000000000060a
R8:  0xffffff8118bfb2f8, R9:  0xffffff810bcc9300, R10: 0x0000000021fed857, R11: 0x000000000000009d
R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0xffffff810afc3220, R15: 0xffffff8118bfb100
RFL: 0x0000000000010292, RIP: 0xffffff7f9c953b4c, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x000070000da6e2d8, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 0

Backtrace (CPU 2), Frame : Return Address
0xffffff8017952220 : 0xffffff8017b3bb1b mach_kernel : _handle_debugger_trap + 0x47b
0xffffff8017952270 : 0xffffff8017c733e5 mach_kernel : _kdp_i386_trap + 0x155
0xffffff80179522b0 : 0xffffff8017c64e5e mach_kernel : _kernel_trap + 0x4ee
0xffffff8017952300 : 0xffffff8017ae2a40 mach_kernel : _return_from_trap + 0xe0
0xffffff8017952320 : 0xffffff8017b3b207 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff8017952420 : 0xffffff8017b3b5eb mach_kernel : _panic_trap_to_debugger + 0x21b
0xffffff8017952470 : 0xffffff80182d24f9 mach_kernel : _panic + 0x61
0xffffff80179524e0 : 0xffffff8017c6520a mach_kernel : _sync_iss_to_iks + 0x2aa
0xffffff8017952660 : 0xffffff8017c64f08 mach_kernel : _kernel_trap + 0x598
0xffffff80179526b0 : 0xffffff8017ae2a40 mach_kernel : _return_from_trap + 0xe0
0xffffff80179526d0 : 0xffffff7f9c953b4c com.pikeralpha.driver.AppleIntelInfo : __ZL7rdmsr64j + 0x1c
0xffffff8e330a2810 : 0xffffff7f9c95adde com.pikeralpha.driver.AppleIntelInfo : __ZN14AppleIntelInfo10reportMSRsEv + 0x54ae
0xffffff8e330a3ac0 : 0xffffff7f9c95dfbb com.pikeralpha.driver.AppleIntelInfo : __ZN14AppleIntelInfo5startEP9IOService + 0x8fb
0xffffff8e330a3de0 : 0xffffff801821ae46 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6
0xffffff8e330a3e40 : 0xffffff801821a9f1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21
0xffffff8e330a3ef0 : 0xffffff8018219d3e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce
0xffffff8e330a3f50 : 0xffffff801821c4dd mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d
0xffffff8e330a3fa0 : 0xffffff8017ae213e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.pikeralpha.driver.AppleIntelInfo(2.9)[9193A175-01D2-3CC0-B6FC-534059A69B84]@0xffffff7f9c950000->0xffffff7f9c966fff

BSD process name corresponding to current thread: kernel_task
Boot args: -v agdpmod=pikera keepsyms=1 -liludbgall liludump=10 debug=0x144 -no_compat_check -wegtree shikigva=144

Mac OS version:
19C57

Kernel version:
Darwin Kernel Version 19.2.0: Sat Nov  9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64
Kernel UUID: C3E7E405-C692-356B-88D3-C30041FD1E72
Kernel slide:     0x0000000017800000
Kernel text base: 0xffffff8017a00000
__HIB  text base: 0xffffff8017900000
System model name: MacPro5,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: NO (0xe00002bc)
Will this kext work on dual CPU systems?
 
Hi
I have compile errors with a Gigabyte H61N-USB3 Bios F8/Pentium G2020 IveBidge (log below) or a Gigabyte GA-H67MA-UD2H-B3 Bios F8/Core i3-2105 SandyBridge

Log below is with the G2020 and -d 2 option, ACPI folder content attached.

What's wrong ?
Thanks

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

System information: Mac OS X 10.13.6 (17G65)
Brandstring: "Intel(R) Pentium(R) CPU G2020 @ 2.90GHz"

Override value: (-d) debug mode, now using: 2!

Setting executing bit of extractACPITables ...
_checkForExecutableFile(extractACPITables) Done.
Extracting ACPI tables ... Done.
Checking User Defined processor data ...
Checking Sandy Bridge processor data ...
Checking Ivy Bridge processor data ...
Processor data found for the Intel G2020
Version: models.cfg v171 / Ivy Bridge.cfg v150

Name (_HID, "ACPI0004") NOT found in DSDT
1 Scope (\_PR_) {..} object(s) found in DSDT
scopeObjectData: 104f095c5f50525f
Two-byte encoding detected (maximum length 0x0FFF/4095)
pkgLengthByte: 0x4f/79
packageLength: 0x09f/159
scopeLength: 159
scopeLength: 304 (egrep pattern length: 14)
scopeObjectData length 320 (includes egrep pattern)
Overriding processor enable state (now enabled)!
processorID: 5f ._PR
Overriding processor enable state (now enabled)!
processorID: 5f ._PR

Scope (\_PR_) {320 bytes} with ACPI Processor declarations found in DSDT (ACPI 1.0 compliant)
Number of Scopes: 1
Generating ssdt.dsl for a 'Macmini6,1' with board-id [Mac-031AEE4D24BFF0B1]
Ivy Bridge Core G2020 processor [0x306A9] setup [0x]
With a maximum TDP of 55 Watt, as specified by Intel
Number logical CPU's: 2 (Core Frequency: 2900 MHz)
Number of Turbo States: 0
Number of P-States: 14 (1600-2900 MHz)
targetCStates: 13
Adding C1
Adding C3
Adding C6
targetCStates: 7
Adding C1
Adding C2
Adding C3
Injected C-States for ._PR (C1,C3,C6)
Injected C-States for ._PR (C1,C2,C3)
Warning: 'cpu-type' may be set improperly (0x instead of 0x07)
- Clover users should read https://clover-wiki.zetam.org/Configuration/CPU#cpu_typeSetting executing bit of iasl ...
_checkForExecutableFile(iasl) Done.

Compiling: ssdt_pr.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20140926-64 [Nov 6 2014]
Copyright (c) 2000 - 2014 Intel Corporation

Compiler aborting due to parser-detected syntax error(s)
/Users/phil/Library/ssdtPRGen/ssdt.dsl 20: External (\_PR_.._PR, DeviceObj)
Error 6126 - ^ Invalid character (0x2E), expecting ASL keyword or name

/Users/phil/Library/ssdtPRGen/ssdt.dsl 20: External (\_PR_.._PR, DeviceObj)
Error 6126 - ^ Invalid character (0x2E), expecting ASL keyword or name

/Users/phil/Library/ssdtPRGen/ssdt.dsl 20: External (\_PR_.._PR, DeviceObj)
Error 6126 - ^ syntax error, unexpected PARSEOP_NAMESEG, expecting ')'

/Users/phil/Library/ssdtPRGen/ssdt.dsl 21: External (\_PR_.._PR, DeviceObj)
Error 6126 - ^ Invalid character (0x2E), expecting ASL keyword or name

/Users/phil/Library/ssdtPRGen/ssdt.dsl 21: External (\_PR_.._PR, DeviceObj)
Error 6126 - ^ Invalid character (0x2E), expecting ASL keyword or name

/Users/phil/Library/ssdtPRGen/ssdt.dsl 21: External (\_PR_.._PR, DeviceObj)
Error 6126 - ^ syntax error, unexpected PARSEOP_NAMESEG, expecting ')'

/Users/phil/Library/ssdtPRGen/ssdt.dsl 23: Scope (\_PR_.._PR)
Error 6126 - ^ Invalid character (0x2E), expecting ASL keyword or name

/Users/phil/Library/ssdtPRGen/ssdt.dsl 23: Scope (\_PR_.._PR)
Error 6126 - ^ Invalid character (0x2E), expecting ASL keyword or name

/Users/phil/Library/ssdtPRGen/ssdt.dsl 23: Scope (\_PR_.._PR)
Error 6126 - ^ syntax error, unexpected PARSEOP_NAMESEG, expecting ')'

/Users/phil/Library/ssdtPRGen/ssdt.dsl 137:
Error 6126 - syntax error, unexpected PARSEOP_SCOPE, expecting $end and premature End-Of-File

ASL Input: /Users/phil/Library/ssdtPRGen/ssdt.dsl - 137 lines, 4264 bytes, 14 keywords

Compilation complete. 10 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
Error: IASL status: 255 (Failed)

Do you want to open ssdt.dsl (y/n)? n
 

Attachments

  • ACPI.zip
    20.3 KB · Views: 223
Guys i need your thoughts. I generated my own ssdt using the script - ok, checked it with maciasl - no errors, copy-pasted it in efi/clover/acpi/patched but upon reboot the pc hangs right before entering desktop with no apparent error. I also tried a different ssdt for the same cpu made by others but the result is the same. Does anyone have any idea?
20200112_184003.jpg
 
Hi
I have compile errors with a Gigabyte H61N-USB3 Bios F8/Pentium G2020 IveBidge (log below) or a Gigabyte GA-H67MA-UD2H-B3 Bios F8/Core i3-2105 SandyBridge

Log below is with the G2020 and -d 2 option, ACPI folder content attached.

What's wrong ?
Thanks

Up. No idea ?

I saw other people having the same issue but found no solution.

There might be a good reason why this script generate these errors

Thanks
 
There might be a good reason why this script generate these errors
Pentium processors are unsupported, Apple do not use them in their builds.
 
Pentium processors are unsupported, Apple do not use them in their builds.

OK.

But I have the same issue with my two CPUs : Gigabyte H61N-USB3 Bios F8/Pentium G2020 IveBidge (log below) or a Gigabyte GA-H67MA-UD2H-B3 Bios F8/Core i3-2105 SandyBridge

Moreover there is the -p command line option that allow to force the type of CPU, no ?
 
Back
Top