Contribute
Register

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

Status
Not open for further replies.

kgp

Retired
Joined
May 30, 2014
Messages
6,907
Motherboard
ASUS WS X299 Sage 10G
CPU
i9-7980XE
Graphics
Vega 64
Mac
iMac, MacBook Pro, Mac mini
Mobile Phone
iOS
Thanks for your response. Unfortunately I have no clue what are you talking about - how to adopt Vega/Nvidia SSDTs. I have to dig a bit.
On the other hand it is weird that it is impossible to simply plug and play graphic cards in legendary and user friendly macOS.
User friendly? Don't forget that macOS is meant to be exclusively installed on Apple devices and to be exclusively compatible with Apple devices.

Cannot provide more than all necessary guidelines you should be able to follow.
 
Last edited:
Joined
Feb 12, 2018
Messages
15
Motherboard
MSI X299 XPOWER GAMING AC
CPU
i9-7900X
Graphics
Vega 56, GTX 1080, GTX 1060
User friendly? Don't forget that macOS is meant to be exclusively installed on Apple devices and to be exclusively compatible with Apple devices.

Cannot provide more than all necessary guidelines you should be able to follow.
I don't forget. And I don't forget I am using hacked system with hacked hardware. I said 'weird' and 'user friendly' from the 3D/Graphic designer point of view for whom hackintosh is not a hobby. iHack is a working tool.
I'm currently using 4x Nvidia GTX cards with High Sierra on desktop and I did not have to deal with rocket science to make it work. Recently I switched GTX1060 for RX570 in my Macbook's eGPU box and it works beautiful. I don't expected Apple recommended Vega to be a problem. I am happy I did not buy a "working OOB" Vega Froniter right away :)
I do not blame Apple or anyone. Sh*t happens.
 
Last edited:
Joined
Jun 26, 2011
Messages
2
Motherboard
Supermicro X11DPG-QT
CPU
2x Xeon 6142 ES
Graphics
Vega 64, Vega 56, RX 560
Long story short questions:

1.) Is the MSR register in your BIOS locked o unlocked? If locked, you have to check "Kernel PM" and enable xpcm_core_scope. The need of xpcm_pgk_scope would imply that your CPU is not fully natively implemented by macOS. Drop Table DMAR should be fine also in your case. Also note that respective XCPM patches change from 10.13 to 10.14.

2.) You should use AppleALC.kext, Lilu.kext and WEG.kext in your EFI-Folder, otherwise neither HDAU nor HDEF will be properly implemented.

3.) Under "System Parameters" you have Nvidia Web checked although you seem not to use any Nvidia GPU.

4.) You are using USBInjectAll.kext and SSDT-1-SMCI--MB for XHCI USB. You might ask for help in the respective thread. I recommend to create and use a board specific XHC USB kext instead and even provide a dedicated guideline to do so. BTW.. what is SSDT-2-SpsNm for? And finally, I never recommended at any place do use a DSDT in /EFI/CLOVER/ACPI/patched.

5.) You do not use SSDT-DTPG.aml and you did not properly adopt SSDT-Vega64.aml to your system. The implemented SSDT-Vega64.aml is for PC02.BR2A while your ACPI table reads PC03.BR3A. I am also missing a properly adapted SSDT-RX560.aml in your EFI-Folder. The current GFX0 and GFX2 ACPI implementation of your two GPUs is solely thanks to WEG.kext and not due to any SSDT implementation. Also all other System SSDTs provided in the X299 Github library (yet to be properly adapted to your system) are be missing in your current EFI-Folder distribution.

6.) Concerning TB, I did not find any traces of any TB adapter in your IOREG.save, which rather suggests that either your TB adapter is not installed at all or at least not properly enabled in your BIOS. Once the TB adapter will be part of your ACPI table, you anyway should use a properly adapted SSDT-TB3HP.aml in /EFI/CLOVER/ACPI/patched.

For properly adapting available system SSDTs to your motherboard and particular PCIe slot population, this small guideline might be helpful in any case (standard sentence, repeated dozens of times). Else it might be beneficial to repeat reading also the main guide in your case.

Good luck,

KGP
Hi KGP
Thank you for your quick response.

I will put the GPUs in the original configuration and extract the correct information again. Do you recommend not to use patched dsdt and ssdt for accuracy?
The DSDT and SSDT in patches folder, I did that hoping that it will help to properly detect the cards. I patched the tables following RahabMan guidlines for this.
The Nvidia Web thicked in plist - I tested 2 Nvidia GPUs to see what’s happening and it’s similar. The system will boot with the monitors card only. Second card will causea reboot at the loginscreen. Usin AMD I un-checked web drivers.
I understand what I have to do for the USB, I will do ito e of these days.
Thunderbolt- as it’s working on windows, does it help if I extract the resources with a software similar to IORegistryExplorer?

Best
Cosministor
 

kgp

Retired
Joined
May 30, 2014
Messages
6,907
Motherboard
ASUS WS X299 Sage 10G
CPU
i9-7980XE
Graphics
Vega 64
Mac
iMac, MacBook Pro, Mac mini
Mobile Phone
iOS
Hi KGP
Thank you for your quick response.

I will put the GPUs in the original configuration and extract the correct information again. Do you recommend not to use patched dsdt and ssdt for accuracy?
The DSDT and SSDT in patches folder, I did that hoping that it will help to properly detect the cards. I patched the tables following RahabMan guidlines for this.
The Nvidia Web thicked in plist - I tested 2 Nvidia GPUs to see what’s happening and it’s similar. The system will boot with the monitors card only. Second card will causea reboot at the loginscreen. Usin AMD I un-checked web drivers.
I understand what I have to do for the USB, I will do ito e of these days.
Thunderbolt- as it’s working on windows, does it help if I extract the resources with a software similar to IORegistryExplorer?

Best
Cosministor
I don't use any DSDT or DSDT patches, all patching here is done within the config.plist and respective SSDTs, and all guidelines in the originating post of this thread (guide) as well as this small guideline describe how to do so properly. There is another thread that explains how to derive motherboard specific XHC USB kexts (if not already part of the respective Github library) instead of using USBInjectAll.kext + additional SSDT.

If you decided to opt for methods not being part of my guidelines totally fine with me, but in this case you are also invited to publish your issues in respective threads describing thus methods and not here.

Best,

KGP
 

kgp

Retired
Joined
May 30, 2014
Messages
6,907
Motherboard
ASUS WS X299 Sage 10G
CPU
i9-7980XE
Graphics
Vega 64
Mac
iMac, MacBook Pro, Mac mini
Mobile Phone
iOS
I don't forget. And I don't forget I am using hacked system with hacked hardware. I said 'weird' and 'user friendly' from the 3D/Graphic designer point of view for whom hackintosh is not a hobby. iHack is a working tool.
I'm currently using 4x Nvidia GTX cards with High Sierra on desktop and I did not have to deal with rocket science to make it work. Recently I switched GTX1060 for RX570 in my Macbook's eGPU box and it works beautiful. I don't expected Apple recommended Vega to be a problem. I am happy I did not buy a "working OOB" Vega Froniter right away :)
I do not blame Apple or anyone. Sh*t happens.
Well.. I also used my hacks for scientific work and not just for fun or as a hobby, although my work rather relates to parallel computing and number crunching than 3D/Graphic design and I am doing my further build and guide development not only for my own benefit but hopefully also for the benefit of the respective Hackintosh community.

Talking about the Vega being part of the iMacPro, it does work OoB on the respective Apple device. Also all commercial Vegas including the Vega Frontier do also work OoB on Hackintosh systems, as long as one does not need to use all DP and HDMI ports and also as long one one does not aim at Display Hotplug, multi-monitor support and proper sleep/wake functionality. For achieving the latter on Hackintosh systems , WEG.kext and the respective SSDT-X299-Vega64.aml seem unavoidable, whereas the latter is also used by Apple and in fact has been derived from a dump of a real iMacPro system. If you simply respect these few necessary requisites, everything works as expected also on Hackintosh systems and you can even fine-tune your Vega by adding a dedicated load table to SSDT-X299-Vega64.aml. Finally, any Vega X299 system behaves fully vanilla with respect to macOS updates. Concerning RX560, RX570 or RX580, I never used any of these GPUs myself and up to my knowledge and based on respective user feedback, they are fully natively supported starting with 10.14.4 and at least also require WEG.kext or likely also a respective SSDT for overall compatibility with macOS.

Talking about Nvidia, you might know that I supported and recommended Nvidia myself within my guidelines for long and that I myself formerly used a water blocked Nvidia GTX 1080 Ti on my X299 system. However, the permanent dropout of available Web Drivers during early macOS public betas between June and October each year, in line with several repetitive severe issues and flaws in respective WEB and CUDA driver functionality over the years, and finally given the simple fact that in terms of Mojave and future macOS versions there is no further Nvidia support, I was forced to finally drop my Nvidia GPU from my system one year ago and also forced to change all respective guidelines.

I did never regret my drop of Nvidia and with the Vega we finally reached a fully vanilla macOS Hackintosh system most users are totally satisfied with. Finally I want to emphasise, that it isn't and never was the aim or interest of Apple to provide a "user friendly" and "legendary" or "plug and play" macOS operating system for any Hackintosh system. Provided the proper companies economical interests, rather the opposite is the case. Thus absolutely no reason to blame Apple for anything. And based on recent response by e.g. AMD or ASUS, the Hackintosh sector seems apparently too small for investing additional money for optimising their respective of-the-shelf PC products for additional unrestricted use under macOS rather than Windows, thus the latter rather seems to be our job in this case.

Anyway, I am not a friend of fundamental debates and I therefor would rather prefer if we could stop also with the ongoing discussion at this place.

If you are happy with Nvidia and you also want to remain with High Sierra or your RX570, totally fine with me in this case.

Best,

KGP
 
Last edited:
Joined
Feb 12, 2018
Messages
15
Motherboard
MSI X299 XPOWER GAMING AC
CPU
i9-7900X
Graphics
Vega 56, GTX 1080, GTX 1060
I implemented WEG / VGTab and Vega works absolutely great for me too - but only when there is no other graphic card in the system.
I agree Nvidia Web Drivers is crap but unfortunately at the moment for me there is no way to drop Nvidia.
One more question: have you tested Vega in multi GPU setup, especially in mix with Nvidia? I put Vega for sale already but maybe a bit hurry...
 
  • Like
Reactions: kgp

kgp

Retired
Joined
May 30, 2014
Messages
6,907
Motherboard
ASUS WS X299 Sage 10G
CPU
i9-7980XE
Graphics
Vega 64
Mac
iMac, MacBook Pro, Mac mini
Mobile Phone
iOS
I implemented WEG / VGTab and Vega works absolutely great for me too - but only when there is no other graphic card in the system.
I agree Nvidia Web Drivers is crap but unfortunately at the moment for me there is no way to drop Nvidia.
One more question: have you tested Vega in multi GPU setup, especially in mix with Nvidia? I put Vega for sale already but maybe a bit hurry...
I never used more than one Vega on my system, but it is commonly know that at least two Vegas work without any issues under macOS, while you have to dedicate separate SSDTs for you each of the Vegas in use by considering the respective slot population.

I remember that @flymovies was using a hybrid Vega/Nvdida system by employing his Vega under macOS and his Nvidia under Windows (no web driver installed under macOS). I myself consider Vega/Nvidia hybrid configurations under macOS as critical and I would rather strongly discourage from such macOS hardware configurations. Maybe somebody else successfully driving a Vega/Nvidia hybrid configuration under macOS can oppose my personal impressions.

Thus I would rather recommend two stay with Nvidia in your case or opt for respective multi-Vega but Vega only implementations.
 

kgp

Retired
Joined
May 30, 2014
Messages
6,907
Motherboard
ASUS WS X299 Sage 10G
CPU
i9-7980XE
Graphics
Vega 64
Mac
iMac, MacBook Pro, Mac mini
Mobile Phone
iOS
This is to let you know that due to vacations, I will be basically unavailable from 28th March until 3rd April 2019.

Thanks for your comprehension, my friends..

395188
 
Joined
Feb 12, 2018
Messages
15
Motherboard
MSI X299 XPOWER GAMING AC
CPU
i9-7900X
Graphics
Vega 56, GTX 1080, GTX 1060
I never used more than one Vega on my system, but it is commonly know that at least two Vegas work without any issues under macOS, while you have to dedicate separate SSDTs for you each of the Vegas in use by considering the respective slot population.

I remember that @flymovies was using a hybrid Vega/Nvdida system by employing his Vega under macOS and his Nvidia under Windows (no web driver installed under macOS). I myself consider Vega/Nvidia hybrid configurations under macOS as critical and I would rather strongly discourage from such macOS hardware configurations. Maybe somebody else successfully driving a Vega/Nvidia hybrid configuration under macOS can oppose my personal impressions.

Thus I would rather recommend two stay with Nvidia in your case or opt for respective multi-Vega but Vega only implementations.
I used HD7950 (for viewport) and a GTX580s (for CUDA) in one system some time ago without problems. I wanted to do it again because of AMD great support (theoretically) in macOS.
 
Joined
Apr 18, 2011
Messages
245
Motherboard
Asus WS X299 Sage/10G
CPU
i9-7980XE
Graphics
Vega Frontier Edition
Mac
MacBook Pro
Mobile Phone
iOS
I used HD7950 (for viewport) and a GTX580s (for CUDA) in one system some time ago without problems. I wanted to do it again because of AMD great support (theoretically) in macOS.
I’m currently running a vega frontier and rtx 2080 ti combo and it’s been working so far. I just null out the rtx card in Mac OS with a SSDT so it doesn’t show up and I disable the vega in windows via device manager. Disabling the Vega in windows makes the fan run at full speed so it’s not ideal until I can get it under water. So it’s entirely doable but not sure if ideal.
I’m not gaming as much as I thought I would though so I might just end up selling both and switching to a vega vii once there is native support in Mac OS to clean things up a bit. Should also be enough gaming hp for me.
 
Status
Not open for further replies.
Top