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

[CoxOrange]

I received my Broadcom Airport card today (this product on Amazon). It's the "…CS" version, and it got recognized and worked immediately after installation – I didn't have to add @kgp's patches or any other aml changes. Earlier iterations have received bad Amazon feedback because of poor signal range and flimsy antennas, but in the meantime the Chinese seem to have upped their game. My card came with 3 large (5dBi gain) antennas, and 802.11n as well as BT range is much better now than with my former MacBook Pro in the same location. Airdrop from my iPhone 8 also works… this X299 build is rapidly becoming so much better than any genuine Mac I owned before

 

[CoxOrange]

Remaining USB ejection issues during sleep/wake likely can be fixed by means of SafeSleepUSB.app or Jettison.app

I'd like to add "Mountain" (http://appgineers.de/mountain/) to the mix. Like Jettison, it costs a few Euros. Its features are mostly identical to the other two; just thought I'd mention this as an additional choice.

 

[CoxOrange]

Noticed some free software that may be useful: "Macs Fan Control"
http://mac.majorgeeks.com/files/details/macs_fan_control.html

I've been using this on my genuine iMac for some time to override the 100% fan spin caused by a 3rd party SSD without thermal sensor. On my Hackintosh however, no sensors are recognized (with the exception of hard disk SMART temperatures). Does this work with the HWSensor kexts too, like iStat? My X299 motherboard already manages fan control so I don't need the app for that, but its temperature display in the menubar would be handy nevertheless… and it's free.

 

[kgp]

I'd like to add "Mountain" (http://appgineers.de/mountain/) to the mix. Like Jettison, it costs a few Euros. Its features are mostly identical to the other two; just thought I'd mention this as an additional choice.

Good advice! Seems to be the most reliable of all related apps..

 

[Zephlon]

I managed to get HDMI audio working. I scanned your post and saw where you mentioned that other GPUs might would be different on the Fredwst patch. Duh! I'd changed the device IDs in the SSDT but not here. For anyone else who might be reading this with the same problem for a 1060 you do the following for the Fredwst patch:

Name*                                 Find* [HEX]         Replace* [HEX]        Comment
com.apple.driver.AppleHDAController   DE100B0E            DE10F110              FredWst DP/HDMI patch

For some reason since I changed this disabling the ACPI Patch for CAVS->HDEF doesn't break audio anymore, so the SSDT must be working. Now onward to thunderbolt and Windows. Audio has been an adventure to say the least.

@dustinwilson what did you use to get the new HEX number in your "Replace" section specific for your card? I am having the same issue with my Nvidia audio not implementing. I know how to convert a number into HEX, but in reading through the forum I am not tracking on what identifying number from the card do I use to convert into HEX for this replacement to work.

 

[x-9er]

After my third Nvidia related kernel panic today, I am officially done trying to make these cards work. It's heartbreaking, because I really do need CUDA for my Adobe applications, but the constant KPs are just not acceptable.

@kgp : can I verify with you that the card you are talking about here

By means of my Vega SSDT PCI device implementation outlined in Section 9.2.2, all available ports on the Gigabyte Vega 64 (3x HDMI, 3x DP), including multi-monitor support and display hot plug are automatically and successfully implemented.

Is specifically the RX VEGA 64 GAMING OC 8G?

Because that is the only Vega 64 card from that company that has those ports.

 

[kgp]

After my third Nvidia related kernel panic today, I am officially done trying to make these cards work. It's heartbreaking, because I really do need CUDA for my Adobe applications, but the constant KPs are just not acceptable.

@kgp : can I verify with you that the card you are talking about here

By means of my Vega SSDT PCI device implementation outlined in Section 9.2.2, all available ports on the Gigabyte Vega 64 (3x HDMI, 3x DP), including multi-monitor support and display hot plug are automatically and successfully implemented.

Is specifically the RX VEGA 64 GAMING OC 8G?

Because that is the only Vega 64 card from that company that has those ports.

yes

 

[mm2margaret]

After my third Nvidia related kernel panic today, I am officially done trying to make these cards work. It's heartbreaking, because I really do need CUDA for my Adobe applications, but the constant KPs are just not acceptable.

I work with Adobe applications every day. After Effects, Premiere, Audition, Media Encoder, Photoshop, and others, and I don't use Cuda and I have no issues......Cuda is not required for these apps, and benchmarks show that Metal and Open CL both work just fine.....Metal seems to be equal if not more powerful than Cuda in some of the tests I've performed, and the "new" Metal in Mojave (Metal 2?) seems even better....

 

[mcity]

Metal seems to be equal if not more powerful than Cuda in some of the tests I've performed, and the "new" Metal in Mojave (Metal 2?) seems even better....

Did you compare Metal performance with Nvidia card or just with Vega 64?
I think Metal perform differently with each card.
Mcity

 

[izo1]

After my third Nvidia related kernel panic today, I am officially done trying to make these cards work. It's heartbreaking, because I really do need CUDA for my Adobe applications, but the constant KPs are just not acceptable.

@kgp : can I verify with you that the card you are talking about here

By means of my Vega SSDT PCI device implementation outlined in Section 9.2.2, all available ports on the Gigabyte Vega 64 (3x HDMI, 3x DP), including multi-monitor support and display hot plug are automatically and successfully implemented.

Is specifically the RX VEGA 64 GAMING OC 8G?

Because that is the only Vega 64 card from that company that has those ports.

If it's kernel panics in Premiere, it also happens with Vega, FYI.

This seems to be related to the iMac Pro SMBIOS/macOS/Adobe