What is the verbose output from bless? SIP disabled?That's the thing, I don't have boot screen support as I am using a 5700 XT in my cMP. I also tried blessing in multiple ways ie. --mount or --folder as well as with and without --file option
What is the verbose output from bless? SIP disabled?That's the thing, I don't have boot screen support as I am using a 5700 XT in my cMP. I also tried blessing in multiple ways ie. --mount or --folder as well as with and without --file option
What is the verbose output from bless? SIP disabled?
➜ ~ sudo bless --mount /Volumes/EFI --file /Volumes/EFI/EFI/OC/OpenCore.efi --setBoot --verbose
EFI found at IODeviceTree:/efi
Mount point for /Volumes/EFI is /Volumes/EFI
Mount point is '/Volumes/EFI'
No BootX creation requested
No boot.efi creation requested
found ioreg "FirmwareFeaturesMask"; featureMaskValue=0xFF1FFF3F
found ioreg "FirmwareFeatures"; featureFlagsValue=0xC00C5417
isPreBootEnvironmentUEFIWindowsBootCapable=0
preboot environment is not UEFI boot capable
isDVDWithElToritoWithUEFIBootableOS=0
Checking if disk is complex (if it is associated with booter partitions)
GPT detected
Booter partition required at index 2
System partition found
Preferred system partition found: disk4s1
Returning booter information dictionary:
{
"Auxiliary Partitions" = (
);
"Data Partitions" = (
disk3s1
);
"System Partitions" = (
disk4s1,
disk3s1
);
}
Relative path of /Volumes/EFI/EFI/OC/OpenCore.efi is \EFI\OC\OpenCore.efi
IOMedia disk3s1 has UUID DA611DE1-01D6-4520-A987-7D9D74439027
Setting EFI NVRAM:
efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>DA611DE1-01D6-4520-A987-7D9D74439027</string></dict></dict><key>BLLastBSDName</key><string>disk3s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\OC\OpenCore.efi</string></dict></array>'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-file'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-mkext'
Setting EFI NVRAM:
IONVRAM-DELETE-PROPERTY='efi-boot-kernelcache'
Old boot-args: -no_compat_check cwae=2 shikigva=160 shiki-id=Mac-7BA5B2D9E42DDD94
Got token: -no_compat_check
Preserving: -no_compat_check
Got token: cwae=2
Preserving: cwae=2
Got token: shikigva=160
Preserving: shikigva=160
Got token: shiki-id=Mac-7BA5B2D9E42DDD94
Preserving: shiki-id=Mac-7BA5B2D9E42DDD94
New boot-args unchanged, skipping update.
/dev/disk4 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk4
1: EFI EFI 209.7 MB disk4s1
2: Apple_CoreStorage TM 1.0 TB disk4s2
3: Apple_Boot Boot OS X 134.2 MB disk4s3
How many mounted EFI partitions you have? Are you spoofing the smbios? Which partition are you trying to boot Cat or Mojave? Single or dual CPU?Here you go:
Code:➜ ~ sudo bless --mount /Volumes/EFI --file /Volumes/EFI/EFI/OC/OpenCore.efi --setBoot --verbose EFI found at IODeviceTree:/efi Mount point for /Volumes/EFI is /Volumes/EFI Mount point is '/Volumes/EFI' No BootX creation requested No boot.efi creation requested found ioreg "FirmwareFeaturesMask"; featureMaskValue=0xFF1FFF3F found ioreg "FirmwareFeatures"; featureFlagsValue=0xC00C5417 isPreBootEnvironmentUEFIWindowsBootCapable=0 preboot environment is not UEFI boot capable isDVDWithElToritoWithUEFIBootableOS=0 Checking if disk is complex (if it is associated with booter partitions) GPT detected Booter partition required at index 2 System partition found Preferred system partition found: disk4s1 Returning booter information dictionary: { "Auxiliary Partitions" = ( ); "Data Partitions" = ( disk3s1 ); "System Partitions" = ( disk4s1, disk3s1 ); } Relative path of /Volumes/EFI/EFI/OC/OpenCore.efi is \EFI\OC\OpenCore.efi IOMedia disk3s1 has UUID DA611DE1-01D6-4520-A987-7D9D74439027 Setting EFI NVRAM: efi-boot-device='<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>DA611DE1-01D6-4520-A987-7D9D74439027</string></dict></dict><key>BLLastBSDName</key><string>disk3s1</string></dict><dict><key>IOEFIDevicePathType</key><string>MediaFilePath</string><key>Path</key><string>\EFI\OC\OpenCore.efi</string></dict></array>' Setting EFI NVRAM: IONVRAM-DELETE-PROPERTY='efi-boot-file' Setting EFI NVRAM: IONVRAM-DELETE-PROPERTY='efi-boot-mkext' Setting EFI NVRAM: IONVRAM-DELETE-PROPERTY='efi-boot-kernelcache' Old boot-args: -no_compat_check cwae=2 shikigva=160 shiki-id=Mac-7BA5B2D9E42DDD94 Got token: -no_compat_check Preserving: -no_compat_check Got token: cwae=2 Preserving: cwae=2 Got token: shikigva=160 Preserving: shikigva=160 Got token: shiki-id=Mac-7BA5B2D9E42DDD94 Preserving: shiki-id=Mac-7BA5B2D9E42DDD94 New boot-args unchanged, skipping update.
SIP is disabled.
Appreciate your help, thanks!
Edit:
Disk4 is Time machine connected via backplane sata -
Code:/dev/disk4 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk4 1: EFI EFI 209.7 MB disk4s1 2: Apple_CoreStorage TM 1.0 TB disk4s2 3: Apple_Boot Boot OS X 134.2 MB disk4s3
How many mounted EFI partitions you have? Are you spoofing the smbios? Which partition are you trying to boot Cat or Mojave? Single or dual CPU?
➜ ~ diskutil list
/dev/disk0 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk2 1.0 TB disk0s2
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk1
1: EFI NO NAME 104.9 MB disk1s1
2: Microsoft Reserved 16.8 MB disk1s2
3: Windows Recovery 554.7 MB disk1s3
4: Microsoft Basic Data WIN10 2.0 TB disk1s4
/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +1.0 TB disk2
Physical Store disk0s2
1: APFS Volume macOS - Data 83.9 GB disk2s1
2: APFS Volume Preboot 23.6 MB disk2s2
3: APFS Volume Recovery 528.5 MB disk2s3
4: APFS Volume VM 1.1 MB disk2s4
5: APFS Volume macOS 11.1 GB disk2s5
6: APFS Volume STOR 432.2 GB disk2s6
/dev/disk3 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *32.0 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_HFS BOOTER 31.7 GB disk3s2
/dev/disk4 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk4
1: EFI EFI 209.7 MB disk4s1
2: Apple_CoreStorage TM 1.0 TB disk4s2
3: Apple_Boot Boot OS X 134.2 MB disk4s3
G5% ./ssdtPRGen.sh -d 2 -p X5690 -turbo 3460 -l 24 -c 1 -target 2
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.14.6 (18G2007)
Brandstring: "Intel(R) Xeon(R) CPU X5690 @ 3.47GHz"
Override value: (-d) debug mode, now using: 2!
Override value: (-p) processor model, now using: X5690!
Override value: (-turbo) maximum (turbo) frequency, now using: 3460 MHz!
Override value: (-l) number of logical processors, now using: 24!
Override value: (-c) CPU workarounds, now set to: 1!
Override value: (-target) CPU, now using: Haswell!
Setting executing bit of extractACPITables ...
_checkForExecutableFile(extractACPITables) Done.
Extracting ACPI tables ... Done.
Checking User Defined processor data ...
Processor data found for the Intel X5690
Version: models.cfg v171 / User Defined.cfg v-1
Name (_HID, "ACPI0004") NOT found in DSDT
1 Scope (\_PR_) {..} object(s) found in DSDT
scopeObjectData: 104f135c5f50525f
Two-byte encoding detected (maximum length 0x0FFF/4095)
pkgLengthByte: 0x4f/79
packageLength: 0x13f/319
scopeLength: 319
scopeLength: 624 (egrep pattern length: 14)
scopeObjectData length 640 (includes egrep pattern)
processorID: 00 CPU0
processorID: 01 CPU1
processorID: 02 CPU2
processorID: 03 CPU3
processorID: 04 CPU4
processorID: 05 CPU5
processorID: 06 CPU6
processorID: 07 CPU7
processorID: 08 CPU8
processorID: 09 CPU9
processorID: 0a CPUA
processorID: 0b CPUB
processorID: 0c CPUC
processorID: 0d CPUD
processorID: 0e CPUE
processorID: 0f CPUF
processorID: 10 CPUG
processorID: 11 CPUH
processorID: 12 CPUI
processorID: 13 CPUJ
processorID: 14 CPUK
processorID: 15 CPUL
processorID: 16 CPUM
processorID: 17 CPUN
Scope (\_PR_) {640 bytes} with ACPI Processor declarations found in DSDT (ACPI 1.0 compliant)
Number of Scopes: 1
Generating ssdt.dsl for a 'MacPro5,1' with board-id [Mac-7BA5B2D9E42DDD94]
Intel X5690 processor [0x206C2] setup [0x0501]
With a maximum TDP of 130 Watt, as specified by Intel
Number logical CPU's: 24 (Core Frequency: 3460 MHz)
Number of Turbo States: 0
Number of P-States: 14 (1600-3460 MHz)
targetCStates: 29
Adding C1
Adding C3
Adding C6
Adding C7
targetCStates: 7
Adding C1
Adding C2
Adding C3
Injected C-States for CPU0 (C1,C3,C6,C7)
Injected C-States for CPU1 (C1,C2,C3)
Warning: 'system-type' may be set improperly (3 instead of 2)
- Clover users should read https://clover-wiki.zetam.org/Configuration/ACPI#acpi_smartups
Compiling: ssdt_pr.dsl
Intel ACPI Component Architecture
ASL+ Optimizing Compiler version 20161210-64(RM)
Copyright (c) 2000 - 2016 Intel Corporation
/Users/g5/Library/ssdtPRGen/ssdt.dsl 49: Name (APSS, Package (0x0E)
Error 6062 - Initializer list longer than declared package length ^
ASL Input: /Users/g5/Library/ssdtPRGen/ssdt.dsl - 482 lines, 13361 bytes, 148 keywords
Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
Error: IASL status: 255 (Failed)
Do you want to open ssdt.dsl (y/n)? y
So I started attempts on generating a working ssdt using https://github.com/Piker-Alpha/ssdtPRGen.sh
Code:Generating ssdt.dsl for a 'MacPro5,1' with board-id [Mac-7BA5B2D9E42DDD94]
Are all 3 of them mounted during blessing?Excluding the USB flash drive, I have 3 other ESP partitions
Are all 3 of them mounted during blessing?
But the idea is to use CPU power management with the iMac Pro board id injected. Will it work if I generate it for a different board id?Disable Lilu/WEG and boot to OEM cMP then try building again. First take on it - you may have surpassed the total number of valid cpu count for Mac-7BA5B2D9E42DDD94 so you should try building for Mac-F221BEC8.
Set the scan policy to 0. It is unrestricted scan.I may have to fiddle with the ScanPolicy setting to enable scanning of NVME, APFS and USB devices only
But the idea is to use CPU power management with the iMac Pro board id injected. Will it work if I generate it for a different board id?
[automerge]1576709813[/automerge]
Set the scan policy to 0. It is unrestricted scan.
Does anybody know what this error means? The DSL is attached.
Name (APSS, Package (0x0E)
Name (APSS, Package (0x13f)
With 0 your USB drive should be visible. Are you using Car with 2 CPU's and spoofed smbios? You may be getting a kernel panic or stalling or constant reboot. Try to disable the watchdog (True)Not sure, was planning on testing it this weekend. I noticed you used -c 1 -t 2 .. Shouldn't it be -c 2 for dual cpus? Also with cMP 5,1, westmere should be used instead of haswell but the script is lacking an option for it. It requires further developing.
I noticed the developer added X5680 under user defined.cfg - did you try to adding X5690?
[automerge]1576710768[/automerge]
ScanPolicy is already set to 0.
That did it. What is it doing?Name (APSS, Package (0x13f)
Yes the script has x5680 and other Xeon processors but they are set around Ivy Bridge (strange) Only if set for Haswel it does not complain.Also with cMP 5,1, westmere should be used instead of haswell but the script is lacking an option for it. It requires further developing.
G5% ./ssdtPRGen.sh -d 2 -p X5690 -turbo 3460 -cpus 2 -c 1 -target 2
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.14.6 (18G2007)
Brandstring: "Intel(R) Xeon(R) CPU X5690 @ 3.47GHz"
Override value: (-d) debug mode, now using: 2!
Override value: (-p) processor model, now using: X5690!
Override value: (-turbo) maximum (turbo) frequency, now using: 3460 MHz!
Override value: (-cpus) number of processors, now using: 2!
Override value: (-c) CPU workarounds, now set to: 1!
Override value: (-target) CPU, now using: Haswell!
Setting executing bit of extractACPITables ...
_checkForExecutableFile(extractACPITables) Done.
Extracting ACPI tables ... Done.
Checking User Defined processor data ...
Processor data found for the Intel X5690
Version: models.cfg v171 / User Defined.cfg v-1
Name (_HID, "ACPI0004") NOT found in DSDT
1 Scope (\_PR_) {..} object(s) found in DSDT
scopeObjectData: 104f135c5f50525f
Two-byte encoding detected (maximum length 0x0FFF/4095)
pkgLengthByte: 0x4f/79
packageLength: 0x13f/319
scopeLength: 319
scopeLength: 624 (egrep pattern length: 14)
scopeObjectData length 640 (includes egrep pattern)
processorID: 00 CPU0
processorID: 01 CPU1
processorID: 02 CPU2
processorID: 03 CPU3
processorID: 04 CPU4
processorID: 05 CPU5
processorID: 06 CPU6
processorID: 07 CPU7
processorID: 08 CPU8
processorID: 09 CPU9
processorID: 0a CPUA
processorID: 0b CPUB
Scope (\_PR_) {114 bytes} without ACPI Processor declarations ...
1 Scope (\_PR) {..} object(s) found in DSDT
scopeObjectData: 104f135c5f5052
Two-byte encoding detected (maximum length 0x0FFF/4095)
pkgLengthByte: 0x4f/79
packageLength: 0x13f/319
scopeLength: 319
scopeLength: 626 (egrep pattern length: 12)
scopeObjectData length 640 (includes egrep pattern)
processorID: 00 CPU0
processorID: 01 CPU1
processorID: 02 CPU2
processorID: 03 CPU3
processorID: 04 CPU4
processorID: 05 CPU5
processorID: 06 CPU6
processorID: 07 CPU7
processorID: 08 CPU8
processorID: 09 CPU9
processorID: 0a CPUA
processorID: 0b CPUB
Scope (\_PR) {640 bytes} with ACPI Processor declarations found in DSDT (ACPI 1.0 compliant)
Number of Scopes: 1
Generating ssdt.dsl for a 'MacPro5,1' with board-id [Mac-F221BEC8]
Intel X5690 processor [0x206C2] setup [0x0501]
With a maximum TDP of 130 Watt, as specified by Intel
Number logical CPU's: 24 (Core Frequency: 3460 MHz)
Number of Turbo States: 0
Number of P-States: 14 (1600-3460 MHz)
targetCStates: 29
Adding C1
Adding C3
Adding C6
Adding C7
targetCStates: 7
Adding C1
Adding C2
Adding C3
Injected C-States for CPU0 (C1,C3,C6,C7)
Injected C-States for CPU1 (C1,C2,C3)
Warning: File Mac-F221BEC8.plist Not Found!
Warning: 'system-type' may be set improperly (3 instead of 2)
- Clover users should read https://clover-wiki.zetam.org/Configuration/ACPI#acpi_smartups
Compiling: ssdt_pr.dsl
Intel ACPI Component Architecture
ASL+ Optimizing Compiler version 20161210-64(RM)
Copyright (c) 2000 - 2016 Intel Corporation
/Users/g5/Library/ssdtPRGen/ssdt.dsl 38: Name (APSS, Package (0x0E)
Error 6062 - Initializer list longer than declared package length ^
ASL Input: /Users/g5/Library/ssdtPRGen/ssdt.dsl - 327 lines, 9702 bytes, 76 keywords
Compilation complete. 1 Errors, 0 Warnings, 0 Remarks, 0 Optimizations
Error: IASL status: 255 (Failed)
With 0 your USB drive should be visible. Are you using Car with 2 CPU's and spoofed smbios? You may be getting a kernel panic or stalling or constant reboot. Try to disable the watchdog (True)
That did it. What is it doing?
[automerge]1576712404[/automerge]
My guess is expanding the range?
Catalina. Cat womanNot sure what you mean by 'Car'.
houldn't it be -c 2 for dual cpus?
Override value: (-cpus) number of processors, now using: 2! Override value: (-c) CPU workarounds, now set to: 1!
Catalina. Cat woman
I noticed the developer added X5680 under user defined.cfg - did you try to adding X5690?
panic(cpu 2 caller 0xffffff8017c6520a): Kernel 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 shiki-id=Mac-7BA5B2D9E42DDD94
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)
System uptime in nanoseconds: 658026767613
Now that I think I may be using the wrong approach for the CPU power management. We have perfect CpuPM SSDT in the original ACPI. So if spoofing the SMBIOS forces the use of a spoofed CpuPM SSDT, we need to drop it and load the original.
<key>ACPI</key>
<dict>
<key>Add</key>
<array>
<dict>
<key>Comment</key>
<string>Original 5,1 DSDT</string>
<key>Enabled</key>
<true/>
<key>Path</key>
<string>DSDT.aml</string>
</dict>
<dict>
<key>Comment</key>
<string>Original 5,1 SSDT</string>
<key>Enabled</key>
<true/>
<key>Path</key>
<string>SSDT.aml</string>
</dict>
<dict>
<key>Comment</key>
<string>Original 5,1 SSDT-1</string>
<key>Enabled</key>
<true/>
<key>Path</key>
<string>SSDT-1.aml</string>
</dict>
<dict>
<key>Comment</key>
<string>Original 5,1 SSDT-2</string>
<key>Enabled</key>
<true/>
<key>Path</key>
<string>SSDT-2.aml</string>
</dict>
</array>
I think there is more to that. First we need to drop the existing power management. Also we need to make sure that all the names for the CPU references are linked correctly to the existing names loaded in the registry. One way of doing it is to compare both SSDT's and see the differences. It is also possible to pach the loadedI dump the original SSDT and inject that by OpenCore with SMBIOS Spoofing, nothing changed.
For me SSDT-3 is the CpuPM, but when extracted from spoofed smbios it is labeled CpuPPM. Maybe there are other differences.I dump the original SSDT and inject that by OpenCore with SMBIOS Spoofing, nothing changed.
View attachment 883775
Code:<key>ACPI</key> <dict> <key>Add</key> <array> <dict> <key>Comment</key> <string>Original 5,1 DSDT</string> <key>Enabled</key> <true/> <key>Path</key> <string>DSDT.aml</string> </dict> <dict> <key>Comment</key> <string>Original 5,1 SSDT</string> <key>Enabled</key> <true/> <key>Path</key> <string>SSDT.aml</string> </dict> <dict> <key>Comment</key> <string>Original 5,1 SSDT-1</string> <key>Enabled</key> <true/> <key>Path</key> <string>SSDT-1.aml</string> </dict> <dict> <key>Comment</key> <string>Original 5,1 SSDT-2</string> <key>Enabled</key> <true/> <key>Path</key> <string>SSDT-2.aml</string> </dict> </array>
So, we cannot simply get that fix by using Hackintool.
I think there is more to that. First we need to drop the existing power management. Also we need to make sure that all the names for the CPU references are linked correctly to the existing names loaded in the registry. One way of doing it is to compare both SSDT's and see the differences. It is also possible to pach the loaded
[automerge]1576777151[/automerge]
For me SSDT-3 is the CpuPM, but when extracted from spoofed smbios it is labeled CpuPPM. Maybe there are other differences.
How are you CPU"s referred to in the loaded registry? Same as in the SSDT?When I boot as 5,1 natively.
My SSDT is CpuPPM, but not CpuPM. And I don't have SSDT-3. I just double checked it again. Really CpuPPM when boot without OpenCore, and no SSDT-3. May be that's the difference between single processor and dual processor cMP.
Also, when boot with SMBIOS spoofing (manual mode, only inject board-id), the Hackintool SSDT dump is identical to the dump that when boot as 5,1 (compared by iHex, the only difference is just the time mark).
sysctl -a | grep cpu
00:000 00:000 OC: OpenCore is now loading (Vault: 0/0, Sign 0/0)...
00:060 00:060 OC: Boot timestamp - 2019.12.19 20:42:34
00:129 00:069 OCCPU: Hypervisor: 0
00:188 00:058 OCCPU: Found Intel(R) Xeon(R) CPU X5690 @ 3.47GHz
00:251 00:062 OCCPU: Signature 206C2 Stepping 2 Model 2C Family 6 Type 0 ExtModel 2 ExtFamily 0
00:310 00:059 OCCPU: Detected Apple Processor Type: 05 -> 0501
00:368 00:058 OCCPU: Ratio Min 12 Max 26 Current 0 Turbo 28 28 27 27
00:428 00:059 OCCPU: Timer address is 408 from LPC
00:587 00:159 OCCPU: CPUFrequencyFromTSC 3457998909Hz 3457MHz
00:645 00:057 OCCPU: CPUFrequency 3457998909Hz 3457MHz
00:704 00:059 OCCPU: FSBFrequency 132999958Hz 132MHz
00:763 00:058 OCCPU: Pkg 1 Cores 6 Threads 12