Closed edin555 closed 8 years ago
Start by adding the -d 2
argument to see if your processor labels are detected.
Thank you for your reply. i will try it now! -d 2 -p -x5680
but: X5680, 130, 1600, 3330, 3600, 6, 12, 4, 133 is okay?
This is the output!
Do i have to copy the SSDT and the DSDT? from your ACPI Folder to my patched in EFI? or the ssdt.aml from the main folder?
Last login: Sun Jul 3 14:18:15 on console ebs-Mac-Pro:~ eb$ curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/Beta/ssdtPRGen.sh % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 147k 100 147k 0 0 65203 0 0:00:02 0:00:02 --:--:-- 65224 ebs-Mac-Pro:~ eb$ chmod +x ~/ssdtPRGen.sh ebs-Mac-Pro:~ eb$ ~/ssdtPRGen.sh -d 2 -p X5680
ssdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl v6.6 Copyright (c) 2013 by † Jeroen
Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <
System information: Mac OS X 10.11.5 (15F34) Brandstring: "Intel(R) Xeon(R) CPU X5680 @ 3.33GHz"
Override value: (-d) debug mode, now using: 2! Override value: (-p) processor model, now using: X5680!
Setting executing bit of extractACPITables ..._checkForExecutableFile(extractACPITables) Done.Extracting ACPI tables ... Done. Checking User Defined processor data ... Processor data found for the Intel X5680 Name (_HID, "ACPI0004") NOT found in the DSDT 1 Scope (PR) {..} object(s) found in the DSDT scopeObjectData: 10471f5f50525f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x47/71 packageLength: 0x1f7/503 scopeLength: 503 scopeLength: 994 (egrep pattern length: 12) scopeObjectData length 1008 (includes egrep pattern) processorID: 01 P001 processorID: 02 P002 processorID: 03 P003 processorID: 04 P004 processorID: 05 P005 processorID: 06 P006 processorID: 07 P007 processorID: 08 P008 processorID: 09 P009 processorID: 0a P010 processorID: 0b P011 processorID: 0c P012
processorID: 10 001
Scope (PR) {229 bytes} without ACPI Processor declarations ...
1 Scope (_PR) {..} object(s) found in the DSDT scopeObjectData: 10471f5f5052 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x47/71 packageLength: 0x1f7/503 scopeLength: 503 scopeLength: 996 (egrep pattern length: 10) scopeObjectData length 1008 (includes egrep pattern) processorID: 01 P001 processorID: 02 P002 processorID: 03 P003 processorID: 04 P004 processorID: 05 P005 processorID: 06 P006 processorID: 07 P007 processorID: 08 P008 processorID: 09 P009 processorID: 0a P010 processorID: 0b P011 processorID: 0c P012
processorID: 10 001
Scope (_PR) {231 bytes} without ACPI Processor declarations ...
1 Scope (SB) {..} object(s) found in the DSDT scopeObjectData: 104d075c5f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4d/77 packageLength: 0x07d/125 scopeLength: 125 scopeLength: 236 (egrep pattern length: 14) scopeObjectData length 252 (includes egrep pattern) Scope (SB) {236 bytes} without ACPI Processor declarations ...
1 Scope (_SB) {..} object(s) found in the DSDT scopeObjectData: 104d075c5f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4d/77 packageLength: 0x07d/125 scopeLength: 125 scopeLength: 238 (egrep pattern length: 12) scopeObjectData length 252 (includes egrep pattern) Scope (_SB) {238 bytes} without ACPI Processor declarations ...
3 Scope (SB) {..} object(s) found in the DSDT scopeObjectData: 104e455f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4e/78 packageLength: 0x45e/1118 scopeLength: 1118 scopeLength: 2224 (egrep pattern length: 12) scopeObjectData length 2238 (includes egrep pattern) Scope (SB) {184 bytes} without ACPI Processor declarations ...
scopeObjectData: 1049255f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x49/73 packageLength: 0x259/601 scopeLength: 601 scopeLength: 1190 (egrep pattern length: 12) scopeObjectData length 1204 (includes egrep pattern) Scope (SB) {170 bytes} without ACPI Processor declarations ...
scopeObjectData: 1045195f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x45/69 packageLength: 0x195/405 scopeLength: 405 scopeLength: 798 (egrep pattern length: 12) scopeObjectData length 812 (includes egrep pattern) Scope (SB) {33 bytes} without ACPI Processor declarations ...
4 Scope (SB) {..} object(s) found in the DSDT scopeObjectData: 108c92045f53425f Three-byte encoding detected (maximum length 0x0FFFFF/1048575) pkgLengthByte: 0x8c/140 packageLength: 0x0492c/18732 scopeLength: 18732 scopeLength: 37450 (egrep pattern length: 14) scopeObjectData length 37466 (includes egrep pattern) Scope (SB) {220 bytes} without ACPI Processor declarations ...
scopeObjectData: 104d075c5f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4d/77 packageLength: 0x07d/125 scopeLength: 125 scopeLength: 236 (egrep pattern length: 14) scopeObjectData length 252 (includes egrep pattern) Scope (SB) {236 bytes} without ACPI Processor declarations ...
scopeObjectData: 104e132e5f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4e/78 packageLength: 0x13e/318 scopeLength: 318 scopeLength: 622 (egrep pattern length: 14) scopeObjectData length 638 (includes egrep pattern) Scope (SB) {112 bytes} without ACPI Processor declarations ...
scopeObjectData: 10430b2e5f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x43/67 packageLength: 0x0b3/179 scopeLength: 179 scopeLength: 344 (egrep pattern length: 14) scopeObjectData length 360 (includes egrep pattern) Scope (SB) {89 bytes} without ACPI Processor declarations ...
3 Scope (_SB) {..} object(s) found in the DSDT scopeObjectData: 104e455f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4e/78 packageLength: 0x45e/1118 scopeLength: 1118 scopeLength: 2226 (egrep pattern length: 10) scopeObjectData length 2238 (includes egrep pattern) Scope (_SB) {186 bytes} without ACPI Processor declarations ...
scopeObjectData: 1049255f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x49/73 packageLength: 0x259/601 scopeLength: 601 scopeLength: 1192 (egrep pattern length: 10) scopeObjectData length 1204 (includes egrep pattern) Scope (_SB) {172 bytes} without ACPI Processor declarations ...
scopeObjectData: 1045195f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x45/69 packageLength: 0x195/405 scopeLength: 405 scopeLength: 800 (egrep pattern length: 10) scopeObjectData length 812 (includes egrep pattern) Scope (_SB) {35 bytes} without ACPI Processor declarations ...
4 Scope (_SB) {..} object(s) found in the DSDT scopeObjectData: 108c92045f5342 Three-byte encoding detected (maximum length 0x0FFFFF/1048575) pkgLengthByte: 0x8c/140 packageLength: 0x0492c/18732 scopeLength: 18732 scopeLength: 37452 (egrep pattern length: 12) scopeObjectData length 37466 (includes egrep pattern) Scope (_SB) {222 bytes} without ACPI Processor declarations ...
scopeObjectData: 104d075c5f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4d/77 packageLength: 0x07d/125 scopeLength: 125 scopeLength: 238 (egrep pattern length: 12) scopeObjectData length 252 (includes egrep pattern) Scope (_SB) {238 bytes} without ACPI Processor declarations ...
scopeObjectData: 104e132e5f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4e/78 packageLength: 0x13e/318 scopeLength: 318 scopeLength: 624 (egrep pattern length: 12) scopeObjectData length 638 (includes egrep pattern) Scope (_SB) {114 bytes} without ACPI Processor declarations ...
scopeObjectData: 10430b2e5f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x43/67 packageLength: 0x0b3/179 scopeLength: 179 scopeLength: 346 (egrep pattern length: 12) scopeObjectData length 360 (includes egrep pattern) Scope (_SB) {91 bytes} without ACPI Processor declarations ...
ACPI Processor {} Declaration(s) found in DSDT
Warning: No ACPI Processor declarations found in the DSDT! Using assumed Scope (_PR) {}
Number of Scopes: 1 Generating ssdt.dsl for a 'MacPro5,1' with board-id [Mac-F221BEC8] Intel X5680 processor [0x206C2] setup [0x0501] With a maximum TDP of 130 Watt, as specified by Intel Number logical CPU's: 12 (Core Frequency: 3330 MHz) Number of Turbo States: 2 (3463-3600 MHz) Number of P-States: 16 (1600-3600 MHz) targetCStates: 29 Adding C1 Adding C3 Adding C6 Adding C7 targetCStates: 7 Adding C1 Adding C2 Adding C3 Injected C-States for P001 (C1,C3,C6,C7) Injected C-States for P002 (C1,C2,C3) Warning: 'cpu-type' may be set improperly (0x0501 instead of 0x0701)
Error: board-id [Mac-F221BEC8] not supported by Ivy Bridge – check SMBIOS data / use the -target option
Do you want to continue (y/n)? y Warning: 'system-type' may be set improperly (1 instead of 2) Setting 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
/Users/eb/Library/ssdtPRGen/ssdt.dsl 37: Name (APSS, Package (0x19) Remark 2063 - Initializer list shorter than declared package length ^
ASL Input: /Users/eb/Library/ssdtPRGen/ssdt.dsl - 350 lines, 9428 bytes, 81 keywords AML Output: /Users/eb/Library/ssdtPRGen/ssdt.aml - 1812 bytes, 39 named objects, 42 executable opcodes
Compilation complete. 0 Errors, 0 Warnings, 1 Remarks, 0 Optimizations
Do you want to copy /Users/eb/Library/ssdtPRGen/ssdt.aml to /Extra/ssdt.aml? (y/n)? n Do you want to open ssdt.dsl (y/n)? n ebs-Mac-Pro:~ eb$
The processor labels are all found, so that is fine, but don't forget to add the -turbo 3300 -w 1
arguments for your final run(s).
Also. You used -cpus 2
at first, but that is for a dual processor configuration only so do not use it for a single processor configuration.
Thank you for your fast reply. But Piker, look at the Topic, i got a dual cpu configuration. Thats why i used the -cpus 2. So i will test it again with my my first command... I will tell you the terminal stuff.
Yes I know. You have a motherboard with two processors installed, but the ACPI tables in your BIOS use _PR instead of two separate processor devices, (_SB.SCK0 and _SB.SCK1) and the former should only be used a single processor configuration, and thus you cannot use -cpus 2
but must use -l 24
instead.
Okay! I will try that as well. So i will just copy the SSDT.aml from ACPI to patched in EFI. I will tell you later if it works. I hope so! Thank you!
I am booting in -v mode, but it is too fast to see anything... but there is showing up something new, with a lot of lines about CPUs and about... puh ehm... where is the log file for this part? :D i need to show it to you. geekbench is running slow an hwmonitor is displaying 12x multi and 1,6ghz.
This i found in my system.log Jul 3 20:11:13 ebs-Mac-Pro com.apple.kextcache[391]: kext-dev-mode allowing invalid signature -67062 0xFFFFFFFFFFFEFA0A for kext FakeSMC_CPUSensors.kext Jul 3 20:19:18 ebs-Mac-Pro kernel[0]: Process launchd [1] disabling system-wide CPU Throttling Jul 3 20:19:18 ebs-Mac-Pro kernel[0]: Process mds_stores [167] disabling system-wide CPU Throttling Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=0 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=2 LocalApicId=2 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=3 LocalApicId=4 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=4 LocalApicId=16 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=5 LocalApicId=18 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=6 LocalApicId=20 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=7 LocalApicId=32 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=8 LocalApicId=34 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=9 LocalApicId=36 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=10 LocalApicId=48 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=11 LocalApicId=50 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=12 LocalApicId=52 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=13 LocalApicId=1 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=14 LocalApicId=3 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=15 LocalApicId=5 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=16 LocalApicId=17 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=17 LocalApicId=19 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=18 LocalApicId=21 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=19 LocalApicId=33 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=20 LocalApicId=35 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=21 LocalApicId=37 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=22 LocalApicId=49 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=23 LocalApicId=51 Enabled Jul 3 20:20:22 localhost kernel[0]: AppleACPICPU: ProcessorId=24 LocalApicId=53 Enabled Jul 3 20:20:22 localhost kernel[0]: CPUSensors: CPU family 0x6, model 0x2c, stepping 0x2, cores 6, threads 12, TJmax 101 Jul 3 20:20:22 localhost kernel[0]: CPUSensors: setting platform keys to [k74 ] Jul 3 20:20:22 localhost kernel[0]: CPUSensors: base CPU multiplier is 25 Jul 3 20:20:22 localhost kernel[0]: CPUSensors: started Jul 3 20:20:22 localhost kernel[0]: pci (build 19:40:46 Apr 19 2016), flags 0xe3000, pfm64 (40 cpu) 0xff80000000, 0x80000000 Jul 3 20:20:22 localhost kernel[0]: AppleIntelCPUPowerManagement: Turbo Ratios 111122 Jul 3 20:20:22 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 19:39:50 Apr 19 2016) initialization complete Jul 3 20:20:22 localhost kernel[0]: mcache: 24 CPU(s), 64 bytes CPU cache line size Jul 3 20:20:22 localhost kernel[0]: AppleIntelCPUPowerManagementClient: readyGot boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/NPE3@3/IOPP/pci-bridge@0/IOPP/pci-bridge@0/IOPP/pci2646,10@0/AppleAHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Kingston SHPM2280P2H/480G Media/IOGUIDPartitionScheme/Untitled@2 Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P013 ACST and _CST evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P013 APSS and _PSS evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P014 ACST and _CST evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P014 APSS and _PSS evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P015 ACST and _CST evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P015 APSS and _PSS evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P016 ACST and _CST evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P016 APSS and _PSS evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P017 ACST and _CST evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P017 APSS and _PSS evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P018 ACST and _CST evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P018 APSS and _PSS evaluations failed! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:22 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P019 ACST and _CST evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P019 APSS and _PSS evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P020 ACST and _CST evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P020 APSS and _PSS evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P021 ACST and _CST evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P021 APSS and _PSS evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P022 ACST and _CST evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P022 APSS and _PSS evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P023 ACST and _CST evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P023 APSS and _PSS evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - P024 ACST and _CST evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUCStates - _CST did not return a package Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P024 APSS and _PSS evaluations failed! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 3 20:20:23 ebs-Mac-Pro kernel[0]: IOPPF: AppleIntelCPUPowerManagement mode
Did you re-run the script with all arguments? Especially the -l 24
argument, since it fails for the second processor.
Also. You should understand that without the (log) output of the script, the generated SSDT, DSDT.aml and APIC.aml I will need to guess about what you are doing.
Im Sorry, here are all informations, also my plist out of clover.
ACPI.zip This is my created Folder.
I run this code: -p X5680 -turbo 3330 -l 24
output: ssdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl v6.6 Copyright (c) 2013 by † Jeroen
Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <
System information: Mac OS X 10.11.5 (15F34) Brandstring: "Intel(R) Xeon(R) CPU X5680 @ 3.33GHz"
Override value: (-p) processor model, now using: X5680! Override value: (-turbo) maximum (turbo) frequency, now using: 3330 MHz! Override value: (-l) number of logical processors, now using: 24!
ACPI Processor {} Declaration(s) found in DSDT
Warning: No ACPI Processor declarations found in the DSDT! Using assumed Scope (_PR) {}
Generating ssdt.dsl for a 'MacPro5,1' with board-id [Mac-F221BEC8] Intel X5680 processor [0x206C2] setup [0x0501] With a maximum TDP of 130 Watt, as specified by Intel Number logical CPU's: 24 (Core Frequency: 3330 MHz) Number of Turbo States: 0 Number of P-States: 14 (1600-3330 MHz) Injected C-States for P001 (C1,C3,C6,C7) Injected C-States for P002 (C1,C2,C3) Warning: 'cpu-type' may be set improperly (0x0501 instead of 0x0701)
Error: board-id [Mac-F221BEC8] not supported by Ivy Bridge – check SMBIOS data / use the -target option
Do you want to continue (y/n)? y Warning: 'system-type' may be set improperly (1 instead of 2)
Compiling: ssdt_pr.dsl Intel ACPI Component Architecture ASL Optimizing Compiler version 20140926-64 [Nov 6 2014] Copyright (c) 2000 - 2014 Intel Corporation
/Users/eb/Library/ssdtPRGen/ssdt.dsl 68: Name (APSS, Package (0x17) Remark 2063 - Initializer list shorter than declared package length ^
ASL Input: /Users/eb/Library/ssdtPRGen/ssdt.dsl - 525 lines, 13812 bytes, 170 keywords AML Output: /Users/eb/Library/ssdtPRGen/ssdt.aml - 3425 bytes, 76 named objects, 94 executable opcodes
Compilation complete. 0 Errors, 0 Warnings, 1 Remarks, 0 Optimizations
Do you want to copy /Users/eb/Library/ssdtPRGen/ssdt.aml to /Extra/ssdt.aml? (y/n)? n Do you want to open ssdt.dsl (y/n)? n ebs-Mac-Pro:log eb$
config.plist.zip My config.plist
Thank You!
With: ebs-Mac-Pro:log eb$ ~/ssdtPRGen.sh -p X5680 -turbo 3330 -l 24 -w 1 ACPI.zip
ssdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl v6.6 Copyright (c) 2013 by † Jeroen
Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <
System information: Mac OS X 10.11.5 (15F34) Brandstring: "Intel(R) Xeon(R) CPU X5680 @ 3.33GHz"
Override value: (-p) processor model, now using: X5680! Override value: (-turbo) maximum (turbo) frequency, now using: 3330 MHz! Override value: (-l) number of logical processors, now using: 24! Override value: (-w) Ivy Bridge workarounds, now set to: 1!
ACPI Processor {} Declaration(s) found in DSDT
Warning: No ACPI Processor declarations found in the DSDT! Using assumed Scope (_PR) {}
Generating ssdt.dsl for a 'MacPro5,1' with board-id [Mac-F221BEC8] Intel X5680 processor [0x206C2] setup [0x0501] With a maximum TDP of 130 Watt, as specified by Intel Number logical CPU's: 24 (Core Frequency: 3330 MHz) Number of Turbo States: 0 Number of P-States: 14 (1600-3330 MHz) Injected C-States for P001 (C1,C3,C6,C7) Injected C-States for P002 (C1,C2,C3) Warning: 'cpu-type' may be set improperly (0x0501 instead of 0x0701)
Error: board-id [Mac-F221BEC8] not supported by Ivy Bridge – check SMBIOS data / use the -target option
Do you want to continue (y/n)? y Warning: 'system-type' may be set improperly (1 instead of 2)
Compiling: ssdt_pr.dsl Intel ACPI Component Architecture ASL Optimizing Compiler version 20140926-64 [Nov 6 2014] Copyright (c) 2000 - 2014 Intel Corporation
ASL Input: /Users/eb/Library/ssdtPRGen/ssdt.dsl - 521 lines, 13504 bytes, 170 keywords AML Output: /Users/eb/Library/ssdtPRGen/ssdt.aml - 3364 bytes, 76 named objects, 94 executable opcodes
Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
Do you want to copy /Users/eb/Library/ssdtPRGen/ssdt.aml to /Extra/ssdt.aml? (y/n)? n Do you want to open ssdt.dsl (y/n)? n ebs-Mac-Pro:log eb$
Thank you for the data, and what is the result with the last run here?
No changes at all, the same errors in the system.log i've copied over here. ill check it again, here we go: https://github.com/Piker-Alpha/ssdtPRGen.sh/files/345292/config.plist.zip Maybe the config.plist is wrong?
Jul 4 00:24:16 ebs-Mac-Pro kernel[0]: IOPPF: AppleIntelCPUPowerManagement mode Jul 4 00:27:34 ebs-Mac-Pro kernel[0]: Process launchd [1] disabling system-wide CPU Throttling Jul 4 00:27:34 ebs-Mac-Pro kernel[0]: Process mds_stores [158] disabling system-wide CPU Throttling Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=1 LocalApicId=0 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=2 LocalApicId=2 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=3 LocalApicId=4 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=4 LocalApicId=16 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=5 LocalApicId=18 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=6 LocalApicId=20 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=7 LocalApicId=32 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=8 LocalApicId=34 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=9 LocalApicId=36 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=10 LocalApicId=48 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=11 LocalApicId=50 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=12 LocalApicId=52 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=13 LocalApicId=1 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=14 LocalApicId=3 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=15 LocalApicId=5 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=16 LocalApicId=17 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=17 LocalApicId=19 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=18 LocalApicId=21 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=19 LocalApicId=33 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=20 LocalApicId=35 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=21 LocalApicId=37 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=22 LocalApicId=49 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=23 LocalApicId=51 Enabled Jul 4 00:28:55 localhost kernel[0]: AppleACPICPU: ProcessorId=24 LocalApicId=53 Enabled Jul 4 00:28:55 localhost kernel[0]: CPUSensors: CPU family 0x6, model 0x2c, stepping 0x2, cores 6, threads 12, TJmax 101 Jul 4 00:28:55 localhost kernel[0]: CPUSensors: setting platform keys to [k74 ] Jul 4 00:28:55 localhost kernel[0]: CPUSensors: base CPU multiplier is 25 Jul 4 00:28:55 localhost kernel[0]: CPUSensors: started Jul 4 00:28:55 localhost kernel[0]: pci (build 19:40:46 Apr 19 2016), flags 0xe3000, pfm64 (40 cpu) 0xff80000000, 0x80000000 Jul 4 00:28:55 localhost kernel[0]: AppleIntelCPUPowerManagement: Turbo Ratios 111122 Jul 4 00:28:55 localhost kernel[0]: AppleIntelCPUPowerManagement: (built 19:39:50 Apr 19 2016) initialization complete Jul 4 00:28:55 localhost kernel[0]: mcache: 24 CPU(s), 64 bytes CPU cache line size Jul 4 00:28:55 localhost kernel[0]: AppleIntelCPUPowerManagementClient: readySuperIODevice: found Fintek F71808E on port=0x2e address=0xa10 Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P013 APSS and _PSS evaluations failed! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P014 APSS and _PSS evaluations failed! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P015 APSS and _PSS evaluations failed! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P016 APSS and _PSS evaluations failed! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P017 APSS and _PSS evaluations failed! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P018 APSS and _PSS evaluations failed! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P019 APSS and _PSS evaluations failed! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P020 APSS and _PSS evaluations failed! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P021 APSS and _PSS evaluations failed! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P022 APSS and _PSS evaluations failed! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:55 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P023 APSS and _PSS evaluations failed! Jul 4 00:28:56 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:56 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:56 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - P024 APSS and _PSS evaluations failed! Jul 4 00:28:56 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray Jul 4 00:28:56 ebs-Mac-Pro kernel[0]: X86PlatformPlugin::publishACPIStates - Failed to get CPU P States! Jul 4 00:28:56 ebs-Mac-Pro kernel[0]: IOPPF: AppleIntelCPUPowerManagement mode
Sorry, but that is impossible. All the objects are there. At least in the SSDT that I got here. You must be doing something wrong.
Hello Piker, i deleted all the files from ~/Library/ssdtPRGen/ included the folder. In users i deleted the script.
Step 1: curl -o ~/ssdtPRGen.sh https://raw.githubusercontent.com/Piker-Alpha/ssdtPRGen.sh/master/ssdtPRGen.sh0
Step 2: chmod +x ~/ssdtPRGen.sh
Step 3b: ~/ssdtPRGen.sh -p X5680 -turbo 3330 -l 24 -w 1
Step 3a: insert User Defined.cfg with gUserDefinedCPUList=( X5680,130,1600,3330,3600,6,12,4,133 in Data and re run the script.
Step 4: Copy created SSDT.aml from the created ACPI Folder to my EFI/Clover/ACPI/patched
This is what i've done, so what is wrong? :(
Yeah that looks alright to me, but it still fails to locate the objects for P013 - P024 so something is not right. And if you look at issue #231 then you see that this actually works for him. Same _PR scope for a multi processor setup. Only a few logical processors less. Did you check if the generated SSDT is actually getting loaded?
Hello Piker! Im sorry for my late reply, but i was in a hospital and then i was two weeks offline. Neeeded that. Tonight or tomorrow i will try it again. Do you had any issues with same processors in the meanwhile?
Thank you Edin
Hello Piker, it seems to work, HW Monitor is showing x16 and x25, but what its about the Turbo of 3,6? its just show 1600 and 3333 MHZ. Nothing between. Even after sleep it is changing from x16 to x25, thats great, for now 💃
How i can check if the Turbo is working as well? and what about the other states?
I edited the user config from 3330 to 3333 MHZ. then i used this: the created ssdt.aml i put in the efi... folder.
ebs-Mac-Pro:~ eb$ ~/ssdtPRGen.sh -d 2 -p X5680 -turbo 3333 -l 24 -w 1
ssdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl v6.6 Copyright (c) 2013 by † Jeroen
Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <
System information: Mac OS X 10.11.5 (15F34) Brandstring: "Intel(R) Xeon(R) CPU X5680 @ 3.33GHz"
Override value: (-d) debug mode, now using: 2! Override value: (-p) processor model, now using: X5680! Override value: (-turbo) maximum (turbo) frequency, now using: 3333 MHz! Override value: (-l) number of logical processors, now using: 24! Override value: (-w) Ivy Bridge workarounds, now set to: 1!
Setting executing bit of extractACPITables ..._checkForExecutableFile(extractACPITables) Done.Extracting ACPI tables ... Done. Checking User Defined processor data ... Processor data found for the Intel X5680 Name (_HID, "ACPI0004") NOT found in the DSDT 1 Scope (PR) {..} object(s) found in the DSDT scopeObjectData: 10471f5f50525f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x47/71 packageLength: 0x1f7/503 scopeLength: 503 scopeLength: 994 (egrep pattern length: 12) scopeObjectData length 1008 (includes egrep pattern) processorID: 01 P001 processorID: 02 P002 processorID: 03 P003 processorID: 04 P004 processorID: 05 P005 processorID: 06 P006 processorID: 07 P007 processorID: 08 P008 processorID: 09 P009 processorID: 0a P010 processorID: 0b P011 processorID: 0c P012 processorID: 0d P013 processorID: 0e P014 processorID: 0f P015 processorID: 10 P016 processorID: 11 P017 processorID: 12 P018 processorID: 13 P019 processorID: 14 P020 processorID: 15 P021 processorID: 16 P022 processorID: 17 P023 processorID: 18 P024
processorID: 10 001
Scope (PR) {229 bytes} without ACPI Processor declarations ...
1 Scope (_PR) {..} object(s) found in the DSDT scopeObjectData: 10471f5f5052 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x47/71 packageLength: 0x1f7/503 scopeLength: 503 scopeLength: 996 (egrep pattern length: 10) scopeObjectData length 1008 (includes egrep pattern) processorID: 01 P001 processorID: 02 P002 processorID: 03 P003 processorID: 04 P004 processorID: 05 P005 processorID: 06 P006 processorID: 07 P007 processorID: 08 P008 processorID: 09 P009 processorID: 0a P010 processorID: 0b P011 processorID: 0c P012 processorID: 0d P013 processorID: 0e P014 processorID: 0f P015 processorID: 10 P016 processorID: 11 P017 processorID: 12 P018 processorID: 13 P019 processorID: 14 P020 processorID: 15 P021 processorID: 16 P022 processorID: 17 P023 processorID: 18 P024
processorID: 10 001
Scope (_PR) {231 bytes} without ACPI Processor declarations ...
1 Scope (SB) {..} object(s) found in the DSDT scopeObjectData: 104d075c5f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4d/77 packageLength: 0x07d/125 scopeLength: 125 scopeLength: 236 (egrep pattern length: 14) scopeObjectData length 252 (includes egrep pattern) Scope (SB) {236 bytes} without ACPI Processor declarations ...
1 Scope (_SB) {..} object(s) found in the DSDT scopeObjectData: 104d075c5f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4d/77 packageLength: 0x07d/125 scopeLength: 125 scopeLength: 238 (egrep pattern length: 12) scopeObjectData length 252 (includes egrep pattern) Scope (_SB) {238 bytes} without ACPI Processor declarations ...
3 Scope (SB) {..} object(s) found in the DSDT scopeObjectData: 104e455f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4e/78 packageLength: 0x45e/1118 scopeLength: 1118 scopeLength: 2224 (egrep pattern length: 12) scopeObjectData length 2238 (includes egrep pattern) Scope (SB) {184 bytes} without ACPI Processor declarations ...
scopeObjectData: 1049255f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x49/73 packageLength: 0x259/601 scopeLength: 601 scopeLength: 1190 (egrep pattern length: 12) scopeObjectData length 1204 (includes egrep pattern) Scope (SB) {170 bytes} without ACPI Processor declarations ...
scopeObjectData: 1045195f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x45/69 packageLength: 0x195/405 scopeLength: 405 scopeLength: 798 (egrep pattern length: 12) scopeObjectData length 812 (includes egrep pattern) Scope (SB) {33 bytes} without ACPI Processor declarations ...
4 Scope (SB) {..} object(s) found in the DSDT scopeObjectData: 108c92045f53425f Three-byte encoding detected (maximum length 0x0FFFFF/1048575) pkgLengthByte: 0x8c/140 packageLength: 0x0492c/18732 scopeLength: 18732 scopeLength: 37450 (egrep pattern length: 14) scopeObjectData length 37466 (includes egrep pattern) Scope (SB) {220 bytes} without ACPI Processor declarations ...
scopeObjectData: 104d075c5f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4d/77 packageLength: 0x07d/125 scopeLength: 125 scopeLength: 236 (egrep pattern length: 14) scopeObjectData length 252 (includes egrep pattern) Scope (SB) {236 bytes} without ACPI Processor declarations ...
scopeObjectData: 104e132e5f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4e/78 packageLength: 0x13e/318 scopeLength: 318 scopeLength: 622 (egrep pattern length: 14) scopeObjectData length 638 (includes egrep pattern) Scope (SB) {112 bytes} without ACPI Processor declarations ...
scopeObjectData: 10430b2e5f53425f Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x43/67 packageLength: 0x0b3/179 scopeLength: 179 scopeLength: 344 (egrep pattern length: 14) scopeObjectData length 360 (includes egrep pattern) Scope (SB) {89 bytes} without ACPI Processor declarations ...
3 Scope (_SB) {..} object(s) found in the DSDT scopeObjectData: 104e455f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4e/78 packageLength: 0x45e/1118 scopeLength: 1118 scopeLength: 2226 (egrep pattern length: 10) scopeObjectData length 2238 (includes egrep pattern) Scope (_SB) {186 bytes} without ACPI Processor declarations ...
scopeObjectData: 1049255f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x49/73 packageLength: 0x259/601 scopeLength: 601 scopeLength: 1192 (egrep pattern length: 10) scopeObjectData length 1204 (includes egrep pattern) Scope (_SB) {172 bytes} without ACPI Processor declarations ...
scopeObjectData: 1045195f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x45/69 packageLength: 0x195/405 scopeLength: 405 scopeLength: 800 (egrep pattern length: 10) scopeObjectData length 812 (includes egrep pattern) Scope (_SB) {35 bytes} without ACPI Processor declarations ...
4 Scope (_SB) {..} object(s) found in the DSDT scopeObjectData: 108c92045f5342 Three-byte encoding detected (maximum length 0x0FFFFF/1048575) pkgLengthByte: 0x8c/140 packageLength: 0x0492c/18732 scopeLength: 18732 scopeLength: 37452 (egrep pattern length: 12) scopeObjectData length 37466 (includes egrep pattern) Scope (_SB) {222 bytes} without ACPI Processor declarations ...
scopeObjectData: 104d075c5f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4d/77 packageLength: 0x07d/125 scopeLength: 125 scopeLength: 238 (egrep pattern length: 12) scopeObjectData length 252 (includes egrep pattern) Scope (_SB) {238 bytes} without ACPI Processor declarations ...
scopeObjectData: 104e132e5f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x4e/78 packageLength: 0x13e/318 scopeLength: 318 scopeLength: 624 (egrep pattern length: 12) scopeObjectData length 638 (includes egrep pattern) Scope (_SB) {114 bytes} without ACPI Processor declarations ...
scopeObjectData: 10430b2e5f5342 Two-byte encoding detected (maximum length 0x0FFF/4095) pkgLengthByte: 0x43/67 packageLength: 0x0b3/179 scopeLength: 179 scopeLength: 346 (egrep pattern length: 12) scopeObjectData length 360 (includes egrep pattern) Scope (_SB) {91 bytes} without ACPI Processor declarations ...
ACPI Processor {} Declaration(s) found in DSDT
Warning: No ACPI Processor declarations found in the DSDT! Using assumed Scope (_PR) {}
Number of Scopes: 1 Generating ssdt.dsl for a 'MacPro5,1' with board-id [Mac-F221BEC8] Intel X5680 processor [0x206C2] setup [0x0501] With a maximum TDP of 130 Watt, as specified by Intel Number logical CPU's: 24 (Core Frequency: 3333 MHz) Number of Turbo States: 0 Number of P-States: 14 (1600-3333 MHz) targetCStates: 13 Adding C1 Adding C3 Adding C6 Injected C-States for P001 (C1,C3,C6) Warning: 'cpu-type' may be set improperly (0x0501 instead of 0x01) Warning: 'board-id' [Mac-F221BEC8] is not supported by Unknown power management Warning: 'system-type' may be set improperly (1 instead of 0) Setting 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
ASL Input: /Users/eb/Library/ssdtPRGen/ssdt.dsl - 361 lines, 8238 bytes, 100 keywords AML Output: /Users/eb/Library/ssdtPRGen/ssdt.aml - 2049 bytes, 51 named objects, 49 executable opcodes
Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
Do you want to copy /Users/eb/Library/ssdtPRGen/ssdt.aml to /Extra/ssdt.aml? (y/n)? n Do you want to open ssdt.dsl (y/n)? n ebs-Mac-Pro:~ eb$ [Restored 25 Jul 2016 23:28:10] Last login: Mon Jul 25 23:28:09 on console Restored session: Mon Jul 25 23:26:47 CEST 2016 ebs-Mac-Pro:~ eb$
Also my Geekbench drops from 2700 single core to 1800, and Multi from 27000 to 25000, maybe the turbo is not running? should i try the 6,1 SMBIOS?
Using AppleIntelInfo.kext immediately crashes my system using the "kextload ~/Desktop/AppleIntelInfo.kext" in terminal.
Even without the SSDT and putting in Clover "Generate P and C States and set Drop OEM in SSDT" is working in the same way, only x12 /x25 but the Turbo i think is not running.
The last generated is: ebs-Mac-Pro:~ eb$ ~/ssdtPRGen.sh -p X5680 -turbo 3333 -l 24 -w 1
When i go to Systemlog my Turboratios are 111122, i need the 222233 right? When i am coming home, i will send you pictures of my Bios with CPU Configurations.
So, what i have to do?
I've checked the Bench's its 2450 on single with NullPowerManagment. With the SSDT or the Clover-Solution its around 1800.
I recently fixed a KP in the source code of AppleIntelInfo.kext so which version are you using?
Hi, good to see you back. I've never done the compile stuff, so i found a v1.5 on web. Do you have a link to your v1.5 as a .kext?
I got this one!
How ever i know v1.0 and v1.5 crash's I would like to check out if the Turbo is loading or not... but when i see the Benchs, i think no.
What could it be?
For now. The x12/x25 is functioning, and the temperature is changing a lot. HW Monitor is telling me the V Core is changing as well.
The 5,1 SMBios is the "Native for this type of CPUs" because in the real ones, they got them too. Maybe this info could help you.
Later the day i will post everything.
One question i have as well. Your script is creating in the APCI Folder around 10-11 Files, sometimes a SSDT and DSDT and so on. What does it mean? I am copying the ssdt.aml from the main folder. The APCI Folder got a SSDT.aml as well. But in the Mainfolder it is written in small letters.
We need data and you are using an previous version so please ask Allan to update the kext or compile it yourself. His instructions are crystal clear and Xcode is a free download.
The files that you found in the ACPI folder are files that the script extracted from memory (read the BIOS) and it uses two of them to generate the target power management ssdt.aml
Please do not use any of the files from the ACPI folder. The script shows you where the new file is, and it depends on the boot loader where it should be copied to.
Okay, i've done it. The .kext is still crashing, but this time i used "sudo kextutil AppleIntelInfo.kext " and i photographed the kernel panic.
here is my created ssdt.aml ssdt.aml.zip
with: gUserDefinedCPUList=( X5680,130,1600,3333,3600,6,12,0,133 and ~/ssdtPRGen.sh -p X5680 -turbo 3333 -l 24 -w 1
and config.plist config.plist.zip
Here is the kernel.log:
Aug 2 22:33:25 --- last message repeated 1 time ---
Aug 2 22:33:25 localhost kernel[0]: Longterm timer threshold: 1000 ms
Aug 2 22:33:25 localhost kernel[0]: PMAP: PCID enabled
Aug 2 22:33:25 localhost kernel[0]: Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64
Aug 2 22:33:25 localhost kernel[0]: vm_page_bootstrap: 12219601 free pages and 330543 wired pages
Aug 2 22:33:25 localhost kernel[0]: kext submap [0x
i found a error: X5680,130,1600,3333,3600,6,12,0,133 must be X5680,130,1600,3333,3600,6,12,4,133
i will report.
What do you get when you run:
ioreg -p IODeviceTree -c IOACPIPlatformDevice -k cpu-type -k clock-frequency | egrep name | sed -e 's/ *[-|="<a-z>]//g'
About the error: Correct. With 0 instead of 4 it won't add the top turbo p-state.
I get this: P001 P002 P003 P004 P005 P006 P007 P008 P009 P010 P011 P012 P013 P014 P015 P016 P017 P018 P019 P020 P021 P022 P023 P024
I've tested it with the 4 and the booting is much longer with some sendPStates success and so on... but it ends in a PM. here are some screenshots:
Right. That is the same KP as issue #231 Time to track the KP and fix it...
What is the next step?
The last comment of you in the #231 thread. "And now I wonder if you copied a plist of a supported Ivy Bridge model to [your board-id].plist in: /S/L/E/IOPlatformPluginFamily.kext/C/P/X86PlatformPlugin.kext/C/R*"
Do i have to generate a board-id.plist, if yes how? I have a Westmere EP which is found in SMBios 5,1. I don't understand. :-(
Edit: i don't have any Board-ID like mine. Maybe because i needed to install El Cap on 3,1 and it don't copied the files of newer ones?
here what i got:
Thank you!
No. That isn't it.
Do you use FakeCPUID?
No, i tried without the FakeCPUID.
Here is my config.plist of clover. config.plist.zip
You are looking at the wrong plists. This is your plist:
/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/ACPI_SMC_PlatformPlugin.kext/Contents/Resources/MacPro5_1.plist
Hmm? I don't get it. I talked about the clovers config.plist
How the MacPro5,1.plist can help me? do i have to edit something?
You get a KP with the text: "Setting P-Limit is unsupported on this system" and thus we need to figure out what the problem is. Now look at the data in the MacPro5_1.plist
<dict>
<key>Desc-Key</key>
<string>CPU_PLIMIT</string>
<key>IOClass</key>
<string>AppleSMCControl</string>
<key>control-flags</key>
<integer>2</integer>
<key>control-id</key>
<integer>10</integer>
<key>location</key>
<string>cpu plimit</string>
<key>type</key>
<string>smc</string>
</dict>
This plus the fact that AppleSMC.kext is in the list with kernel extensions in the backtrace... and since I don't know what the exact problem is.. you yourself have to go dig deep. Please comment this section out like so:
<!-- dict>
<key>Desc-Key</key>
<string>CPU_PLIMIT</string>
<key>IOClass</key>
<string>AppleSMCControl</string>
<key>control-flags</key>
<integer>2</integer>
<key>control-id</key>
<integer>10</integer>
<key>location</key>
<string>cpu plimit</string>
<key>type</key>
<string>smc</string>
</dict -->
Boot with -f and see if that gets you past the KP. There are also some other sections with P limit stuff in, so if this doesn't work then comment some other sections out.
Time for me to go to bed. Good luck with hacking!
I will try it! But tomorrow as well, i need my head clear as you. okay, I'm not a programmer but ui/graphic designer. i will continue tomorrow, but this i will do now. Nite!
Hello Piker-Alpha,
i've done it yesterday in the MacPro5_1 and haven't found a MacPro5_2. I Used Textedit to edit the code but i think, thats the wrong way. Which tool is for that .plists?
Also Clover: -f -v -dart=0 -nvda_drv=1
Maybe i just done it wrong and need a proper tool. I will try other parts of the code, if this is not working :/ What would happen if i change my SMBios to 6,1 or 3,1?
What about the Method u mentioned here: #236 because we got the same CPU Family.
Thank you Edin
Right. The MacPro5_2.plist was a typo. Should have been MacPro5_1.plist Sorry, but please remember that it was way past my bedtime already. Anyway. Here are the steps to follow:
1.) cd /S/L/E/IOPlatformPluginFamily.kext/C/P_/ACPI_SMCPlatformPlugin.kext/C/R*/ 2.) sudo nano MacPro5_1.plist 3.) enter password 4.) scroll down/right to the target dictionary and make the suggested changes 5.) use ctrl+o to save the file 6.) use ctrl+x to exit 7.) sudo reboot
Sure. You can remove the _DSM method and see what that brings, but please try this first.
Edit: I think to have located the problem in the X86PlatformShim binary, it looks for a property with the name InitialPLimit and when found it skips the call to read the SMC key. The plist for the MacPro6,1 has this key so that may be an option or you add the missing key to the plist and see if that works.
Hello Piker-Alpha, i will follow your instructions, i've tried it with MacKextLight, but i think that was wrong. I've done a backup of the Kext and i installed it with Kextwizard again, now the plist is vanilla again.
So.
Edit:
Did you added: <!-- dict> ? i could swear yesterday the "!" wasn't there... i will try it now. rebooting.
Okay, i've done it, but i couldn't boot again. It's the same P-Limit KP on SMBios 5,1. In that Kext-Folder(/S/L/E/IOPlatformPluginFamily.kext/C/P/ACPI_SMC_PlatformPlugin.kext/C/R*/) is nowhere a MacPro6_1 - right?
So i will change my SMBios with Clover to 6,1, reboot and try the script again with the: -p X5680 -turbo 3333 -l 24 -w 1
It didn't work for me with 6,1. What do you meant with yout edit-post? You said you located the problem...:D i hope this is first step.
Thank you and sleep well
Hello Pike,
i've done a update of your script. I commented the stuff back in MacPro5_1.
Now i run it again with the update of your script: let's see if it works! Btw. i have a x12 /x25 with clovers ssdt drop oem generate p-states and generate c-states. without any ssdt.
Edit: no its not working with created ssdt.aml
my ssdt.aml: ssdt.aml.zip
and here is the output:
Mac-Pro:~ eb$ ~/ssdtPRGen.sh -p X5680 -turbo 3333 -l 24 -w 1
ssdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl v6.6 Copyright (c) 2013 by † Jeroen
Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues <
System information: Mac OS X 10.11.5 (15F34) Brandstring: "Intel(R) Xeon(R) CPU X5680 @ 3.33GHz"
Override value: (-p) processor model, now using: X5680! Override value: (-turbo) maximum (turbo) frequency, now using: 3333 MHz! Override value: (-l) number of logical processors, now using: 24! Override value: (-w) Ivy Bridge workarounds, now set to: 1!
ACPI Processor {} Declaration(s) found in DSDT
Warning: No ACPI Processor declarations found in the DSDT! Using assumed Scope (_PR) {}
Generating ssdt.dsl for a 'MacPro5,1' with board-id [Mac-F221BEC8] Intel X5680 processor [0x206C2] setup [0x0501] With a maximum TDP of 130 Watt, as specified by Intel Number logical CPU's: 24 (Core Frequency: 3333 MHz) Number of Turbo States: 0 Number of P-States: 14 (1600-3333 MHz) Injected C-States for P001 (C1,C3,C6,C7) Injected C-States for P002 (C1,C2,C3) Warning: 'cpu-type' may be set improperly (0x0501 instead of 0x0701)
Error: board-id [Mac-F221BEC8] not supported by Ivy Bridge – check SMBIOS data / use the -target option
Do you want to continue (y/n)? y Warning: 'system-type' may be set improperly (1 instead of 2)
Compiling: ssdt_pr.dsl Intel ACPI Component Architecture ASL Optimizing Compiler version 20140926-64 [Nov 6 2014] Copyright (c) 2000 - 2014 Intel Corporation
ASL Input: /Users/eb/Library/ssdtPRGen/ssdt.dsl - 521 lines, 13504 bytes, 170 keywords AML Output: /Users/eb/Library/ssdtPRGen/ssdt.aml - 3364 bytes, 76 named objects, 94 executable opcodes
Compilation complete. 0 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
Do you want to copy /Users/eb/Library/ssdtPRGen/ssdt.aml to /Extra/ssdt.aml? (y/n)? n Do you want to open ssdt.dsl (y/n)? n Mac-Pro:~ eb$
Hello Pike!
maybe this thread helps you:
I don't understand everything... :/
Don't worry. You are not the only person who doesn't understand everything. That is simply impossible without having all of Apple's source code.
Now. You should know that there are not two but three types of power management. Most people only talk about AppleIntelCPUPowerManagement and XCPM but it's not that simple. There is also something in between. A mix of AppleIntelCPUPowerManagement and XCPM. This also confused me at times. I'm so used to think in terms of (full) XCPM mode that I easily forget that there are two others as well. And I think that we need to drop the _DSM method for your (and other older) setup(s).
Can you do that? Can you open the ssdt.dsl in an editor and comment out/rip out the Method __DSM) {} and recompile it with iasl?
Good morning Piker,
thank you for your help. I just done it like the guy with the issue #236 He posted a screenshot.
My Turbo is now working!
HW Monitor shows 3.46 and 3.58 GHz But, why does is never go down to 1.6? The Temperature is low, so what is the point?
How all of the Cores are running over 3,33 GHz, is this even possible in this Turbomode? its 3,33 in Bios. Just the Turbo is 3,6, and i thought the turbo is just by some cores.
Why does it never drop down to 1,6? does this mean, my CPUs are always on 100& wattage? That wouldn't be funny.
Also the Geekbench raises in 32 bit = 2500/27000, 64 bit = 2700/30000 - nice!
Have a great night
EDIT: i think its dropping (just few times) after fresh reboot. after sleep, it won't work. Just x25 / x26 / x27 are working. Today or tomorrow i want to do my APCI for the DSDT/SSDT, after that i will run your patch again. Maybe there will be some bugs fixxed.
EDIT 2:
Turboratio is: 111122 This is my systemlog:
Aug 12 02:25:17 --- last message repeated 1 time ---
Aug 12 02:25:17 localhost kernel[0]: Longterm timer threshold: 1000 ms
Aug 12 02:25:17 localhost kernel[0]: PMAP: PCID enabled
Aug 12 02:25:17 localhost kernel[0]: Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64
Aug 12 02:25:17 localhost kernel[0]: vm_page_bootstrap: 12227821 free pages and 322323 wired pages
Aug 12 02:25:17 localhost kernel[0]: kext submap [0x
Good morning Piker, i have ome problems to create the DSDT, when i apply the patches i need, olarilas admin done it for me - but after injected DSDT. -yes sleep/ no wakeup - it just reboots the machine. -no NPM (without the ssdt) -Yes NPM (with the before created SSDT, bu just 3,46 ghz, no 3,6 ghz) -No sleepbutton in function
Do i have to create the new ssdt, after booting with the new DSDT?
Could the SSDT solve the problems with sleep etc?
Now i have my old config running, like before, without DSDT: this is a screenshot of:
1 benchmark at the beggining, after booting (2790/29600) 2 then idling, 3 then sleep/wake up (you can see it at the break of temps and fans)
i think this looks good? should NPM looks like this?
Is the CPU Package Average the important?
Thank you Edin555
I don't know what changes were made in your DSDT, but that isn't really important (to me) since this issue is about the script and the generated SSDT. We've solved that issue so we should close this one. Please do not add new/unrelated issues.
Anyway. You should first fix the reboot/sleep button problems and then re-run the script to see if that gets you what you want.
Okay, you're right. I tried to re-run the new version of your script, but i cant even create a SSDT. It's just interupted and tells me it must be break up.
Today in the evening i will download it again and do the step by step.
Is this still working with the new version?
X5680,130,1600,3333,3600,6,12,4,133 -p X5680 -turbo 3333 -l 24 -w 1
I copied my line into the new custom config file.
I would like to try to run the AppleIntelInfo - hope the crash was fixxed.
Thank You!
Hello Piker-Alpha,
my MacPro 5,1 is booting fine, without NullCPUPowerManagement.kext - i can sleep/reboot/shutdown
But when im geeking i just score: 14.000 With the Kext injected in L/E it scores about 27.000
So, i tried your script with: X5680, 130, 1600, 3330, 3600, 6, 12, 4, 133
Also -cpu 2 -p -x5680 -turbo 3300 -w 1
got this from the dude with the two x5550 cpus, from his thread.
i copied the file from ACPI to Patched in Clover/EFI/ACPI/Patched/...
Nothing happens at the boot of clover, when i open geekbench, my temperature is not rising, that is my indicator for not going up with the MHZ and the geekbench of course scores around 14k points.
What i am doing wrong? i dont have a DSDT at all. Any special Clover configurations maybe?
Thank you Edin555