How to build your own iMac Pro [Successful Build/Extended Guide]

[nachosband]

Hello guys, one of my builds suddenly wont boot macOS today, I can get past clover but then I get stucked at the attached image. It's weird because last night it was working perfectly.

Can anyone point me in the right direction? @kgp? Tried searching along the thread with no success

The system the same as my profile but a 1050 Ti instead the Vega 64

 

[kgp]

Hello guys, one of my builds suddenly wont boot macOS today, I can get past clover but then I get stucked at the attached image. It's weird because last night it was working perfectly.

Can anyone point me in the right direction? @kgp? Tried searching along the thread with no success

The system the same as my profile but a 1050 Ti instead the Vega 64

It is unusual that the system behaves different over night without external changes. Did you try to clear the CMOS or reset your BIOS (save your settings before)? Are you sure that you are booting with the correct EFI-Folder?

Good luck,

KGP

 

[RuleBreaker01]

Anyway, if your former TB-SSDT worked close to perfection with all GB motherboards, why don't you keep on using it?

Because I no longer use a GB motherboard? (I didn't want a TB implementation using PCH lanes)

 

[poshook]

Any1 here successfully using any android emulators for OSX? I tried many and none of them worked. Is there any special settings on hackintosh required?

 

[taylorsyn]

@kgp
Just to clairfy, I should be using these two you provided for Gigaybte?:
SSDT-TB3-L02-PR2X.aml
SSDT-TB3-X299-Lolo.aml

 

[kgp]

@kgp
Just to clairfy, I should be using these two you provided for Gigaybte?:
SSDT-TB3-L02-PR2X.aml
SSDT-TB3-X299-Lolo.aml

You can use SSDT-TB3-X299-Lolo.aml or SSDT-TB3-X299-Gigabyte.aml (implemented in the guide). For adopting SSDT-TB3-L02-PR2X.aml please ask @nmano for help (he will require your original DSDT.aml). For the ASUS Prime X299 Deluxe, I am actually using SSDT-TB3-L69-BR1X.aml.

 

[tonyarnold]

I'm having an interesting problem - and I'm still looking for solutions (I haven't tried too hard to resolve it yet - I intend to when I have a bit of spare time), but I thought I'd record it here for posterity. My Gigabyte Alpine Ridge rev 2.0 ThunderBolt 3 card causes a kernel panic when waking from sleep, with the following panic report:

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8a29c275): "UPSB(iMacPro1,1): thunderbolt power on failed 0xffffffff\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-320.60.2/IOPCIBridge.cpp:1307
Backtrace (CPU 0), Frame : Return Address
0xffffffa3ca21ba80 : 0xffffff8009a6d166 mach_kernel : _handle_debugger_trap + 0x4c6
0xffffffa3ca21bad0 : 0xffffff8009b95824 mach_kernel : _kdp_i386_trap + 0x114
0xffffffa3ca21bb10 : 0xffffff8009b87b10 mach_kernel : _kernel_trap + 0x4d0
0xffffffa3ca21bb90 : 0xffffff8009a1f180 mach_kernel : _return_from_trap + 0xe0
0xffffffa3ca21bbb0 : 0xffffff8009a6cbdc mach_kernel : _panic_trap_to_debugger + 0x21c
0xffffffa3ca21bce0 : 0xffffff8009a6c99c mach_kernel : _panic + 0x5c
0xffffffa3ca21bd40 : 0xffffff7f8a29c275 com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge19_restoreDeviceStateEP11IOPCIDevicej + 0x1e9
0xffffffa3ca21bdb0 : 0xffffff7f8a29cdca com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge18restoreDeviceStateEP11IOPCIDevicej + 0x5a
0xffffffa3ca21bdd0 : 0xffffff7f8a29b0bf com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge19setDevicePowerStateEP11IOPCIDevicejmm + 0x27d
0xffffffa3ca21be20 : 0xffffff7f8a2a59f1 com.apple.iokit.IOPCIFamily : __ZN11IOPCIDevice13setPowerStateEmP9IOService + 0x63
0xffffffa3ca21be40 : 0xffffff800a07ef65 mach_kernel : __ZN9IOService19driverSetPowerStateEv + 0x185
0xffffffa3ca21beb0 : 0xffffff800a07ed0a mach_kernel : __ZN9IOService15pmDriverCalloutEPS_ + 0x2a
0xffffffa3ca21bed0 : 0xffffff8009aa67e4 mach_kernel : _thread_call_delayed_timer + 0xeb4
0xffffffa3ca21bf40 : 0xffffff8009aa6345 mach_kernel : _thread_call_delayed_timer + 0xa15
0xffffffa3ca21bfa0 : 0xffffff8009a1e4f7 mach_kernel : _call_continuation + 0x17
      Kernel Extensions in backtrace:
         com.apple.iokit.IOPCIFamily(2.9)[1057F053-73DE-33E4-B5BE-09DA28715DB4]@0xffffff7f8a294000->0xffffff7f8a2c8fff

I'm using the SSDTs provided in post one of this thread with one difference - my Alpine Ridge card is in slot 6, not slot 4 (I've updated the SSDTs accordingly). As noted earlier in the thread, while my LG 5K UltraFine display is connected, I see no USB ports/hub under DSB2, but I don't think that's causing me any major grief.

For now, I've set my machine to just sleep the display.

 

[morh]

@apfelnico - is it possible to have a version of your Vega 64 SSDT without the overclock shown in the tutorial? I know it’s in the power play tables bit but I’m not sure how to edit it back to the stock version.

The fan profile is perfect but I’m processing some bits which send my gpu temps through the roof and then it crashes.

---- edit - feel free to ignore this, think my KP's were from overheating CPU....

 

[kgp]

I'm having an interesting problem - and I'm still looking for solutions (I haven't tried too hard to resolve it yet - I intend to when I have a bit of spare time), but I thought I'd record it here for posterity. My Gigabyte Alpine Ridge rev 2.0 ThunderBolt 3 card causes a kernel panic when waking from sleep, with the following panic report:

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8a29c275): "UPSB(iMacPro1,1): thunderbolt power on failed 0xffffffff\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOPCIFamily/IOPCIFamily-320.60.2/IOPCIBridge.cpp:1307
Backtrace (CPU 0), Frame : Return Address
0xffffffa3ca21ba80 : 0xffffff8009a6d166 mach_kernel : _handle_debugger_trap + 0x4c6
0xffffffa3ca21bad0 : 0xffffff8009b95824 mach_kernel : _kdp_i386_trap + 0x114
0xffffffa3ca21bb10 : 0xffffff8009b87b10 mach_kernel : _kernel_trap + 0x4d0
0xffffffa3ca21bb90 : 0xffffff8009a1f180 mach_kernel : _return_from_trap + 0xe0
0xffffffa3ca21bbb0 : 0xffffff8009a6cbdc mach_kernel : _panic_trap_to_debugger + 0x21c
0xffffffa3ca21bce0 : 0xffffff8009a6c99c mach_kernel : _panic + 0x5c
0xffffffa3ca21bd40 : 0xffffff7f8a29c275 com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge19_restoreDeviceStateEP11IOPCIDevicej + 0x1e9
0xffffffa3ca21bdb0 : 0xffffff7f8a29cdca com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge18restoreDeviceStateEP11IOPCIDevicej + 0x5a
0xffffffa3ca21bdd0 : 0xffffff7f8a29b0bf com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge19setDevicePowerStateEP11IOPCIDevicejmm + 0x27d
0xffffffa3ca21be20 : 0xffffff7f8a2a59f1 com.apple.iokit.IOPCIFamily : __ZN11IOPCIDevice13setPowerStateEmP9IOService + 0x63
0xffffffa3ca21be40 : 0xffffff800a07ef65 mach_kernel : __ZN9IOService19driverSetPowerStateEv + 0x185
0xffffffa3ca21beb0 : 0xffffff800a07ed0a mach_kernel : __ZN9IOService15pmDriverCalloutEPS_ + 0x2a
0xffffffa3ca21bed0 : 0xffffff8009aa67e4 mach_kernel : _thread_call_delayed_timer + 0xeb4
0xffffffa3ca21bf40 : 0xffffff8009aa6345 mach_kernel : _thread_call_delayed_timer + 0xa15
0xffffffa3ca21bfa0 : 0xffffff8009a1e4f7 mach_kernel : _call_continuation + 0x17
      Kernel Extensions in backtrace:
         com.apple.iokit.IOPCIFamily(2.9)[1057F053-73DE-33E4-B5BE-09DA28715DB4]@0xffffff7f8a294000->0xffffff7f8a2c8fff

I'm using the SSDTs provided in post one of this thread with one difference - my Alpine Ridge card is in slot 6, not slot 4 (I've updated the SSDTs accordingly). As noted earlier in the thread, while my LG 5K UltraFine display is connected, I see no USB ports/hub under DSB2, but I don't think that's causing me any major grief.

For now, I've set my machine to just sleep the display.

Against all instructions you are using MatchOS entries in your AppleUSBXHCI Kernel patches and you enable both patches (10.13 and 10.14) at the same time.

Please disable one of the two patches in concordance with your MacOS and remove both MatchOS entries from the config.plist.

Does this solve your issue?

Also, when do you observe the KP? With TB or XHC USB devices connected? Which TB devices are you employing? How often do you witness the KP on wake?

 

[tonyarnold]

Please disable one of the two patches in concordance with your MacOS and remove both MatchOS entries from the config.plist.

Ugh, so I got the MatchOS format incorrect? Why do you advocate not using it? I need to be developing under both OS releases throughout the day, and I thought that this is what MatchOS is for.

Does this solve your issue?

Sadly, no - there's still nothing under _SB/PC03@0/BR3X@10000/UPSB@0/DSB2@20000 save for a lonely IOPP entry.

Also, when do you observe the KP? With TB or XHC USB devices connected? How often do you witness the KP on wake?

I use an LG 5K UltraFine display as my only display - it's a TB3 display, so there is always a TB device connected. The KP happens every time I try to wake the machine, sadly.

Thanks for your help.