RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,056
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
Following step 4 of the original post, I get the following:
Code:ssdtPRGen.sh v0.9 Copyright (c) 2011-2012 by † RevoGirl v6.6 Copyright (c) 2013 by † Jeroen v15.6 Copyright (c) 2013-2017 by Pike R. Alpha ----------------------------------------------------------- Bugs > https://github.com/Piker-Alpha/ssdtPRGen.sh/issues < gDataPath: /Users/hiro/Library/ssdtPRGen/Data System information: Mac OS X 10.11.6 (15G1510) Brandstring 'Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz' 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] Sandy Bridge Core E5-2670 processor [0x206D7] setup [0x0402] With a maximum TDP of 115 Watt, as specified by Intel Number logical CPU's: 32 (Core Frequency: 2600 MHz) Number of Turbo States: 7 (2700-3300 MHz) Number of P-States: 22 (1200-3300 MHz) Injected C-States for CP00 (C1,C3,C6,C7) Warning: 'cpu-type' may be set improperly (0x0402 instead of 0x0602) Error: board-id [Mac-F221BEC8] not supported by Sandy Bridge – check SMBIOS data / use the -c option Do you want to continue (y/n)? y Warning: 'system-type' may be set improperly (1 instead of 2) Intel ACPI Component Architecture ASL Optimizing Compiler version 20140926-64 [Nov 6 2014] Copyright (c) 2000 - 2014 Intel Corporation ACPI Warning: NsLookup: Type mismatch on APSS (Package), searching for (Method) (20140926/nsaccess-729) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 36: External (\_PR.CP00, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP00) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 37: External (\_PR.CP01, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP01) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 38: External (\_PR.CP02, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP02) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 39: External (\_PR.CP03, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP03) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 40: External (\_PR.CP04, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP04) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 41: External (\_PR.CP05, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP05) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 42: External (\_PR.CP06, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP06) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 43: External (\_PR.CP07, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP07) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 44: External (\_PR.CP08, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP08) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 45: External (\_PR.CP09, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP09) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 46: External (\_PR.CP0A, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP0A) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 47: External (\_PR.CP0B, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP0B) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 48: External (\_PR.CP0C, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP0C) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 49: External (\_PR.CP0D, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP0D) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 50: External (\_PR.CP0E, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP0E) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 51: External (\_PR.CP0F, DeviceObj) Error 6074 - Name already exists in scope ^ (\_PR.CP0F) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 330: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 340: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 350: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 360: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 370: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 380: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 390: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 400: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 410: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 420: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 430: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 440: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 450: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 460: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 470: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) /Users/hiro/Library/ssdtPRGen/ssdt.dsl 480: Method (APSS, 0, NotSerialized) Error 6074 - Name already exists in scope ^ (APSS) ASL Input: /Users/hiro/Library/ssdtPRGen/ssdt.dsl - 489 lines, 11908 bytes, 144 keywords Compilation complete. 32 Errors, 0 Warnings, 0 Remarks, 0 Optimizations Do you want to open ssdt.dsl (y/n)?
Any way I should interpret this?
It is not possible to diagnose errors by error message alone.
This is why each error indicates the line number where the error was encountered.
You should look at the generated SSDT.dsl in MaciASL so you can see what is causing the error.