iMac Pro X299 - live the future new with macOS 10.14 Mojave [Successful Build/Successful Guide]

[Acden]

Dear friends,

why do you buy expensive Radeon VII cards, if they are not compatible with Macs and Mojave at the moment? So, you have no hardware acceleration, what is the resson to use it?

[KGP-iMacPro]

1 hour ago, Acden said:

Dear friends,

why do you buy expensive Radeon VII cards, if they are not compatible with Macs and Mojave at the moment? So, you have no hardware acceleration, what is the resson to use it?

 

I never recommended to anybody to buy a Radeon VII for now. I use one which is not even my own for testing purposes and system development only. 

Edited March 4, 2019 by KGP-iMacPro

[Acden]

A was asking because I'm buying Vega 56 (a week ago I bought RX580, but decided to buy Vega 56 instead). And now I'm not sure to buy Vega 56 or wait for Radeon VII for video editing / encoding.

[KGP-iMacPro]

Just now, Acden said:

A was asking because I'm buying Vega 56 (a week ago I bought RX580, but decided to buy Vega 56 instead). And now I'm not sure to buy Vega 56 or wait for Radeon VII for video editing / encoding.

 

If you are thinking on purchasing a VII you should wait in any case, until it is fully implemented under macOS and also confirmed to work on your specific system. 

[KGP-iMacPro]

2 hours ago, Acden said:

A was asking because I'm buying Vega 56 (a week ago I bought RX580, but decided to buy Vega 56 instead). And now I'm not sure to buy Vega 56 or wait for Radeon VII for video editing / encoding.

 

If you are thinking on purchasing a VII you should wait in any case, until it is fully implemented under macOS and also confirmed to work on your specific system. 

 

BTW.. still no native Radeon VII implementation under 10.14.4 Beta 4 18E205e. 

[CrazyC7]

KGP, I would like to thank you for all of your hard work on the X299 Hackintosh builds.  You have done a wonderful job compiling all this very detailed information which has helped me get my Hackintosh running splendidly.

 

My main system components: 

 - MSI X299 Xpower Gaming AC Motherboard

 - i9 7900x 10 core CPU

 - Radeon RX 580 video card

 - 64 gb of ram (extra leftover from my unraid build)

 - (2) Samsung EVO 860 M.2 SSD

 - other various sata SSD and/or mechanical drives (not sure what I want to leave in this system yet)

 

The keys to my build working:

 

 EFI

 - use your EFI configuration to start

 - for my board added the "ncpi=0x2000" boot flag in Clover.

 - configured TSCAdjustRest.kext for my CPU

 

For bios settings:

 - all of the Hyper Threading and VTx/d settings are enabled

 - my bios has an MSR Lock Control setting  - disabled

 - Enhanced Halt State (C1E) - Enabled

 - CPU C6 report - Enabled

 - Package C-State - C6(non-retention) state

 

My system is VERY fast.  I had High Sierra installed per your guide last year, but I was having graphics issues with dual Nvidia 960 cards at the time and wanted to try a dual OS unraid build, so I switched to unraid for the last year.  I'm pretty sure the dual graphics card issue was related to having Above 4G Memory disabled now.

I was pretty happy with performance, but just wanted to get the most out of my hardware.  An upgrade to my NAS freed up some extra hardware to separate out my Windows 10 PC from my unraid build which gave me the push to go back to the bare metal Hackintosh.  I was already upgraded to Mojave and having passed a couple drives directly to my OS under Unraid, it was very easy to setup and configure my bootable drive for testing the bare metal configuration.  I think the biggest thing I missed, because it was buried deep in the advanced settings of the CPU OC settings, was the MSR Lock setting.  I scoured through everything multiple times before I came across it.  I think the GitHub page for AptioMemoryFix.efi is what got me to enable the advanced CPU settings and find it. 

 

So again, thank you for all your hardwork!  I'm loving my Hackintosh build!

 

I have sound with an OWC USB-C doc, but may try the Apple ALC Audio implementation to enable my onboard audio and I'm thinking about looking into adding a Thunderbolt 3 card.  Thunderbolt on my Macbook Pro is great and I can definitely see where I would make use of it on my desktop machine.

 

Edited March 25, 2019 by CrazyC7
fixing incorrect components

[KGP-iMacPro]

ASUS WS X299 Sage 10G system configuration successfully added to general guidelines in the originating post of this thread (guide).

 

[blackrunnero]

Hi.
Hope everyone's fine. 
Recently I started this hack - dual 16-core on Supermicro X11DPG-qt
Thank you KGP and thank you all for sharing your systems' development.
After over a week of working on this machine, I am finally STUCK!

Here are the full specs and below, the progress, some pics and my EFI folder

The System pictures are from the High Sierra installation but Mojave has the exact same behaviour

The EFI files and the Korey dump are attached to a link on my personal cloud as they are too big to uploaded here

For some reason, I can't upload all the bios photos, they are also attached to my link
Mainboard: Supermicro X11DPG-QT, bios revision 2 from 2017 

I cannot update to a later version as the Thunderbolt support will not be available no more.

CPUs - 2x Xeon Gold 6142 @2.4GHz engineering samples(stepping B0)
Memory - 8x 8GB Micron DDR4 ecc @ 2666MHz
GPU's - Monitors GPU - AMD RX560, processing GPUs - AMD Vega 56 and Vega 64
I am running on dual PSU - Supermicro 860W for the logic board and Corsair HX1200i for the GPUS and drives
System drives - both NVMEs -Samsung 970 EVO 2TB on the native M.2 port for Mac and 970 EVO 500GB for Windows on a PCIe adapter, 
Storage - 6X HGST 7k3000 3TB - Striped RAID
WiFi+BT - FENVI FV9801
Displays: Apple Thunderbolt Display 2K, Apple Cinema Display 23 and Dell 22"
Progress so far:
after 3 days of restarting and swiping the USB stick from my laptop to the beast and back --- I have successfully booted and installed both High Siera 10.13.6(16G45) and Mojave 10.14.3

This X11DPG-QT board has the PCIe ports ordering the opposite of any board I've seen so far, you can see on the attached picture

With High Sierra I was able to use a pretty clean EFI bootloader, I tried to respect the KGP guidance as much as I could but, the only way to boot was to use another kernel patch and the KernelPM checked in clover.

The system works almost ok but using 1 video board only. 
My goal is to have the RX560 for the monitors and the Vega GPUs for processing
so far, only the monitor GPU gets acceleration and Metal support. I swap them and doesn't matter with one is the primary, the other two will not be recognized by the system.
I installed Whatevergreen and Lilu(many versions tried) and I could have the boards recognised by the system but no acceleration and no Metal(you can see one pic from DaVinci Resolvew with only 1 GPU available)

I tried to follow some instructions for creating a SSD for each additional GPU but still no go.
I am not very advanced in doing that so, maybe someone could verify if DSDT and SSDT patching was done properly.

I had successfully booted High Sierra or Mojave with the monitor GPU in PCIe slot-9(CPU1 Slot). Any other choice it hangs at PCI configuration. beginsWindows boots ok from any slot

With these CPUs the only way to boot the installer was to use 0x0040670 as fakecpuid, droping the MATS table instead of the DMAR in Clover's ACPI, Pike's xpcm_pkg_scope kernel patch instead of xpcm_core_scope as the guide is recommending.
I configured the BIOS settings as close as I could to the original guide, I would like to say that it took me a lot of time to discover the Extended APIC in bios needs to be disabled for this board.

Still not working:
Thunderbolt GA Titan Ridge card - it was initialised in Windows, I connected a thunderbolt hard drive but macOS wouldn't even see it in the PCI branch of System Profiler, nor the IORegistryExplorer, I have way less TB options in bios than the guides

Bluetooth for the FENVI adapter not showing up.

USB 3 not working.

All of the above is happening both with High Sierra and Mojave, the only difference is that the EFI structure for Mojave is an ambiguous one, especially the config.plist that, honestly, after days of trying to boot, just matched a downloaded one from another forum.

Please let me know what other info about this build I should share.

 

https://mega.nz/#F!pR0nFaRL!QXLQESnahJ54reVL57scJQ

[KGP-iMacPro]

3 hours ago, blackrunnero said:

Hi.
Hope everyone's fine. 
Recently I started this hack - dual 16-core on Supermicro X11DPG-qt
Thank you KGP and thank you all for sharing your systems' development.
After over a week of working on this machine, I am finally STUCK!

Here are the full specs and below, the progress, some pics and my EFI folder

The System pictures are from the High Sierra installation but Mojave has the exact same behaviour

The EFI files and the Korey dump are attached to a link on my personal cloud as they are too big to uploaded here

For some reason, I can't upload all the bios photos, they are also attached to my link
Mainboard: Supermicro X11DPG-QT, bios revision 2 from 2017 

I cannot update to a later version as the Thunderbolt support will not be available no more.

CPUs - 2x Xeon Gold 6142 @2.4GHz engineering samples(stepping B0)
Memory - 8x 8GB Micron DDR4 ecc @ 2666MHz
GPU's - Monitors GPU - AMD RX560, processing GPUs - AMD Vega 56 and Vega 64
I am running on dual PSU - Supermicro 860W for the logic board and Corsair HX1200i for the GPUS and drives
System drives - both NVMEs -Samsung 970 EVO 2TB on the native M.2 port for Mac and 970 EVO 500GB for Windows on a PCIe adapter, 
Storage - 6X HGST 7k3000 3TB - Striped RAID
WiFi+BT - FENVI FV9801
Displays: Apple Thunderbolt Display 2K, Apple Cinema Display 23 and Dell 22"
Progress so far:
after 3 days of restarting and swiping the USB stick from my laptop to the beast and back --- I have successfully booted and installed both High Siera 10.13.6(16G45) and Mojave 10.14.3

This X11DPG-QT board has the PCIe ports ordering the opposite of any board I've seen so far, you can see on the attached picture

With High Sierra I was able to use a pretty clean EFI bootloader, I tried to respect the KGP guidance as much as I could but, the only way to boot was to use another kernel patch and the KernelPM checked in clover.

The system works almost ok but using 1 video board only. 
My goal is to have the RX560 for the monitors and the Vega GPUs for processing
so far, only the monitor GPU gets acceleration and Metal support. I swap them and doesn't matter with one is the primary, the other two will not be recognized by the system.
I installed Whatevergreen and Lilu(many versions tried) and I could have the boards recognised by the system but no acceleration and no Metal(you can see one pic from DaVinci Resolvew with only 1 GPU available)

I tried to follow some instructions for creating a SSD for each additional GPU but still no go.
I am not very advanced in doing that so, maybe someone could verify if DSDT and SSDT patching was done properly.

I had successfully booted High Sierra or Mojave with the monitor GPU in PCIe slot-9(CPU1 Slot). Any other choice it hangs at PCI configuration. beginsWindows boots ok from any slot

With these CPUs the only way to boot the installer was to use 0x0040670 as fakecpuid, droping the MATS table instead of the DMAR in Clover's ACPI, Pike's xpcm_pkg_scope kernel patch instead of xpcm_core_scope as the guide is recommending.
I configured the BIOS settings as close as I could to the original guide, I would like to say that it took me a lot of time to discover the Extended APIC in bios needs to be disabled for this board.

Still not working:
Thunderbolt GA Titan Ridge card - it was initialised in Windows, I connected a thunderbolt hard drive but macOS wouldn't even see it in the PCI branch of System Profiler, nor the IORegistryExplorer, I have way less TB options in bios than the guides

Bluetooth for the FENVI adapter not showing up.

USB 3 not working.

All of the above is happening both with High Sierra and Mojave, the only difference is that the EFI structure for Mojave is an ambiguous one, especially the config.plist that, honestly, after days of trying to boot, just matched a downloaded one from another forum.

Please let me know what other info about this build I should share.

 

https://mega.nz/#F!pR0nFaRL!QXLQESnahJ54reVL57scJQ

 

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,  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. 

 

Else it is would be more than sufficient to post your perspective questions in one forum only. It just requires additional work at my side to respond with identical answers to identical questions in both forums at the same time.  

Good luck,

KGP

Edited March 25, 2019 by KGP-iMacPro

[KGP-iMacPro]

Guide update to 10.14.4 (18E226) completed

 

 

 

New 10.14.4 EFI-Folder distribution EFI-X299-10.14.4-Release-iMacPro1,1-250319.zip in the X299 EFI-Folder Github repository. Clover_v2.4k_r4903 and new 10.14.4 USB port limit patch implementation. Updated FakeSMC and HWSensor distribution. One should also implement latest Lilu.kext, AppleALC.kext and Whatevergreen.kext distributions.

Still no native vanilla Radeon VII macOS implementation (still no default Radeon VII device-ID 0x66AF1002 in the vanilla AMDRadeonX5000.kext).

Also note new Xcode 10.2 and Xcode 10.2 Command Line distributions.

Enjoy and have fun,

 

[Rania_d]

Hi, 

thanks for sharing ! 

 

 

 

 

Dafont 192.168.l.l FileHippo

 

 

Edited March 27, 2019 by Rania_d

[KGP-iMacPro]

MacOS 10.14.4 (18E2034) - special build 

This afternoon @DSM2 advised me that yesterday Apple seems to have added a second special build of MacOS 10.14.4 (18E2034) on swcdn.apple.com, likely for new devices.

 

 

 

 

And here is the script for the respective Install MacOS.app creation: createInstaller-10.14.4-SB.sh.zip.

EFI-X299-10.14.4-Release-iMacPro1,1-250319.zip is also fully valid in this case. 

No native vanilla implementation of the Radeon VII also with this macOS build yet. 

Enjoy and have fun,

 

Edited March 26, 2019 by KGP-iMacPro

[KGP-iMacPro]

Native Radeon VII support with MacOS 10.14.5 public beta 1

 

See respective IM thread.

 

Unfortunately I am not able to confirm this by myself as I cannot implement the air flow Radeon VII in my water blocked X299 system and my X99 system with the air flow Radeon VII does not boot with 10.14.5 beta 1 as the XCPM_pkg_scope kernel patch (not required for X299) seems broken with 10.14.5 beta 1. I was not able to reach @PMheart for the necessary XCPM_core_scope kernel patch update and in 4 hours I have to leave to the airport and will not have any access to my computers for 6 days.

 

Thus, all X299 guys, enjoy Radeon VII with 10.14.5 beta 1. All necessary kext and kernel patches implemented in EFI-X299-10.14.4-Release-iMacPro1,1-250319.zip are working. I already updated to 10.14.5 beta 1 on X299 and everything is fine and working. 

 

All X99 guys should wait with the update to 10.14.5 beta 1 until an updated XCPM_pkg_scope kernel patch is available. All other kext and kernel patches implemented in EFI-X99-10.14.4-Release-iMacPro1,1-250319.zip should continue working also under 10.14.5 beta 1.

 

There are Radeon VII SSDTs in the X99 (Slot-1, ASUS X99-A II) and X299 (Slot-1, ASUS Prime X299 Deluxe; Slot-5 ASUS WS X299 Sage 10G) SSDT Github directories, which yet need to be verified and hopefully will also work with the native Radeon VII implementation after a likely necessary ACPI path and ACPI replacement adaptation depending on your motherboard and Radeon VII PCIe slot population.  

 

Also it is recommended to use the latest versions of Lilu.kext (1.3.5), AppleALC.kext (1.3.6) and Whatevergreen.kext (1.2.7). 

 

Good luck and see you in one week from now.

 

KGP

[KGP-iMacPro]

Back from Rome, quick update to 10.14.5 Beta on X99 with Radeon VII

 

Native Radeon VII implementation, including Hardware Acceleration, Display HotPlug, multi-monitor support, DP/HDMI Audio and system sleep/wake on X99.

 

For further details, remarks and benchmark results see: 

 

 

 

EFI-X299-10.14.4-Release-iMacPro1,1-250319.zip also fully valid for 10.14.5 Betas.

There are Slot-1 and Slot-5 SSDT-X299-Radeon-VII.amls for the Deluxe and Sage 10G, respectively in the respective X299 SSDT Github repositories, yet to be successfully verified by somebody. 

Enjoy and have fun,

 

Edited April 5, 2019 by KGP-iMacPro

[KGP-iMacPro]

New X299 10.14.5 Beta EFI-Folder distribution adding Radeon VII GPU Temp sensor information for iStatMenus. 

EFI-X299-10.14.5-Beta-iMacPro1,1-050419.zip

1.) I just modified Kozlek/Interferenc FakeSMC/HWSensor source code distribution for adding Radeon VII GPU Temp sensor information and subsequently added new FakeSMC.kext and HWSensor.kexts to /EFI/Clover/kexts/Other. The new GPU Sensor kext should now support all Vegas and also the new Radeon VII, when using iStatMenus. 

 

 

2.) Implementing Clover_v2.4k_r4918. 

Enjoy and have fun, 

 

Edited April 6, 2019 by KGP-iMacPro

[KGP-iMacPro]

Flawless update to 10.14.5 Beta 2 (18F108f)

 

 

No further improvements in Radeon VII performance on my X99 system so far (quite identical overall benchmark scores when compared with Beta 1) but H264 and HEVC support. 

 

 

Enjoy and have fun,

 

[Tony Arnold]

I've also noticed that hot plug for the USB hub in my LG UltraFine 5K display now works as expected. I can sleep/wake the machine (and have done, multiple times) and the hub comes back reliably. 

 

There were problems with the screen not waking properly in 10.14.5b1, but a simple plug/unplug of the TB3 cable into the display resolved the problem every time. Nice!

[Wackymac]

19 hours ago, KGP-iMacPro said:

Flawless update to 10.14.5 Beta 2 (18F108f)

 

 

No further improvements in Radeon VII performance on my X99 system so far (quite identical overall benchmark scores when compared with Beta 1) but H264 and HEVC support. 

 

 

Enjoy and have fun,

 

Just to note. benchmarks for my vega frontier have dropped from around 200 000 in geekbench to 140 000...my guess is that unless its using the same driver as the VII, its a software compatibility issue? or apple really messed something up in the amd driver due to the reduction of coil whine... even with editing the powerplay table. still no real gains in performance

[KGP-iMacPro]

1 hour ago, Wackymac said:

Just to note. benchmarks for my vega frontier have dropped from around 200 000 in geekbench to 140 000...my guess is that unless its using the same driver as the VII, its a software compatibility issue? or apple really messed something up in the amd driver due to the reduction of coil whine... even with editing the powerplay table. still no real gains in performance

 

Looks rather like some Apple beta driver mess in the frame of the actual VII implementation or some missing update of respective benchmark tools different than Luxmark. I can confirm a drop of 30.000 (200.00 vs 170.000) scores in Geekbench OpenGL and Metal scores with 10.14.5 Beta 2 also in case of my Nitro+ Vega 64. In contrary, Luxmark Scores slightly increased from 28.000 to 33.000.

 

Update: I now also performed a Cinebench OpenGL benchmark for my Nitro+ Vega 64 and surprisingly even there scores slightly increased from 162 fps to 166 fps.  

 

Thus in conclusion, seems we are rather missing some Geekbench update and should not blame Apple. 

Edited April 9, 2019 by KGP-iMacPro

[Wackymac]

26 minutes ago, KGP-iMacPro said:

 

Looks rather like some Apple beta driver mess in the frame of the actual VII implementation or some missing update of respective benchmark tools different than Luxmark. I can confirm a drop of 30.000 (200.00 vs 170.000) scores in Geekbench OpenGL and Metal scores with 10.14.5 Beta 2 also in case of my Nitro+ Vega 64. In contrary, Luxmark Scores slightly increased from 28.000 to 33.000.

 

Update: I now also performed a Cinebench OpenGL benchmark for my Nitro+ Vega 64 and surprisingly even there scores slightly increased from 162 fps to 166 fps.  

 

Thus in conclusion, seems we are rather missing some Geekbench update and should not blame Apple. 

just saw your conclusion... well now back to beta 2. thanks for the info and your continued hard work

Edited April 9, 2019 by Wackymac

[KGP-iMacPro]

X299 System Upgrade Completed 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Happy Easter Holidays to all of you! 

 

[Guest]

Hi KGP, beautiful rig and photos

I would like to ask why you do not feed in your rig EATX12V3 additional power connector you see in this grab

 

TY

 

[KGP-iMacPro]

Radeon VII now considered within Whatevergreen Source Code distribution

 

I just asked @VIT9696 to consider all necessary Radeon VII details within his Whatevergreen Source Code distribution and he kindly did immediately.  

 

Radeon VII is now also part of WEG and all necessary cosmetics are now also properly displayed under "About this  Mac" and "Graphics/Displays" of Apple's system report also by means of WEG and not only as up to now by means of my SSDT-X299-Radeon-VII.aml available in my Github SSDT repositories. For respective testing purposes, I removed my respective Radeon VII SSDT temporarily. 

 

 

 

The new version of WEG however seems to work also well in line with the actual version of my SSDT-X299-Radeon-VII.aml and the Kozlek/Interferenc FakeSMC/HWSensor kext distribution that I recently modified to properly display Radeon VII GPU Temps under iStatMenus and which is also hardwired such within my 10.14.5 EFI-Folder Github distribution.

 

 

Against former claims of others, the current Radeon VII WEG consideration does not seem to have any effect on respective Geekbench scores either.

Let’s see if all the above remains valid after long term testing not only by myself but also by other users, moreover as everything related to the VII should be considered as beta in any case.

 

 

 

Enjoy and have fun,

 

 

 

Edit:

 

Note that the new WEG source code also seems to fix some actual or at least some former macOS inconsistencies concerning "compatible", "subvendor-ID",... GFX0 and HDAU properties. Thus anybody using my RadeonVII SSDT in addition to WEG, needs to download and implement the new modified RadeonVII-WEGVII SSDT from my respective Github libraries, after the usual adaptation to motherboard and PCI-Slot Population. I also dropped the formerly implemented load table created with VGTab (version for Vega64) but apparently not fully compatible with Radon VII, as it actually does not seem to provide major improvements and therefore rather would be confusing in the ongoing beta testing. All other above conclusion however seem still valid also after the actual changes in the RadeonVII-WEGVII SSDTs.

 

Edited April 19, 2019 by KGP-iMacPro

[KGP-iMacPro]

23 minutes ago, fabiosun said:

Hi KGP, beautiful rig and photos

I would like to ask why you do not feed in your rig EATX12V3 additional power connector you see in this grab

 

TY

 

 

Because connecting the 2x 8pin EATX connectors at the top to me seemed sufficient for usual OC purposes and because up to know I thought that one would need to connect the 3rd EATX connector only in case of special and extreme overclocking. 

 

Did you make any different experience and  observation on that? Certainly not a big deal to also connect the 3rd EATX connector if it would be really beneficial for the allover system performance.  

 

Please let me know about your appreciated opinion. 

[Guest]

2 minutes ago, KGP-iMacPro said:

 

Because connecting the 2x 8pin EATX connectors at the top to me seemed sufficient for usual OC purposes and because up to know I thought that one would need to connect the 3rd EATX connector only in case of special and extreme overclocking. 

 

Did you make any different experience and  observation on that? Certainly not a big deal to also connect the 3rd EATX connector if it would be really beneficial for the allover system performance.  

 

Please let me know about your appreciated opinion. 

 

I am new with sage 10g configuration and I have had no particular problem in setting it in a basic way. I use to feed also that connector because system could benefit of it in case (as you say) of an extreme OC, but also if you populate more PCIEX slot (in my case some time with a spare GFX or thunderbolt EX card or PCIEX NVME card)

In case I would feed it (if no extra power need it is also safe to have it connected)