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

[Ramalama]

I have the LG version.
From what I understand Nightshift will not work as Apple recognises the monitor as a TV. This is only because of the '3840' resolution which is associated with 4K televisions. I have tried running a custom EDID profile on the monitor of '3839' pixels and Nightshift appears. This proves that to have nightshift natively, the resolution cannot be '3840'. I have tried reaching out to Apple to change this silly MacOS assumption with no luck.

There is already a fix (FixEDID) which spoofs the display to be a Thunderbolt Display.
Here is my discussion.

Personally I have been using f.lux and its working perfectly. I also enabled automatic transitions and the end result is exactly like NightShift just not native.

If you end up using FixEDID ensure that whenever you do any changes to the X299 SSDT relating to the GPU (eg. PEGP -> GFX1, PEG1 -> GFX0 etc) you regenerate a new modified kext.

Hopefully Apple can resolve this silly issue sometime

I have it working with our native resolution 3840x1600...

The acer 38inch which have the same panel have working nightshift, native
The dell does not...

So im searching anyone with acer 38imch panel... I need the edid to modify our lg 38 inch...

I have it at the moment working with a display override profile. We dont need the mergenub kext...
I just want to make a clover edid patch, that we dont need a override profile...

But native resolution with nightshift is not a problem here.

You dont need to go below 3840 to disable the tv mode, there are other ways

Cheers

 

[ccozmo]

The iMacPro is using RAID 0 with two drives - giving it better performance.

I tried back on Sierra to use Apple RAID on 2 x NVME drives, however the performance was not much better than a single drive.\

Does anyone know how the iMacPro is doing RAID ? Is it BIOS or using the Apple RAID ?

Would like to try and create the RAID and see if performance is now improved

 

[DanyH]

@DanyH : Sorry I have to
disappoint you, I don’t share my personal EFI Folder for this board. If you can’t install MacOS boot in verbose and upload a picture from the output.

I can’t pass this step at the start IOAHCIBlock , I have the config.plist of the guide.
Thanks

 

[kgp]

I can’t pass this step at the start IOAHCIBlock , I have the config.plist of the guide.
Thanks

View attachment 307863

Did you adopt and implement VoodooTSCSync.kext?

 

[DanyH]

Did you adopt and implement VoodooTSCSync.kext?

yes kgp, After adopting the IOCPUNumber "15" for the 7820X save the nfo.plist file and copy the modified VoodooTSCSync.kext to the /EFI/CLOVER/kexts/Other/

what could be the problem for you? sorry for my english, i'm italian and I would like to take this opportunity to thank you kgp and other members of the forum for the immense work on the guide.

 

[DanyH]

my cpu is on stock 3.6Mhz, i follow the guide on start for the Gigabyte Auros 9 bios, 3 days ago i had a 17,1 macosx with 13.12 but with the update i have corrupt the osx.
i would like install 17C2120 with IMacPro1,1.
i've only change the IntelMausiEthernet.kext with the AppleIntelE1000e.kext and add NvidiaGraphicsFixup.kext and Lilu.kext
edit the VoodooTSCSync.kext with "15" core

i compared my old "config.plist" with the new of the kgp and see that kgp remove the fakecpuID for the native support....
(i used in the precedent config OsxAptioFix2Drv-64.efi and EmuVariableUefi-64.efi but i read the guide and there are obsolete)

i've different mainboard and different vga nvidia 1080ti

 

[DanyH]

Let me guess... You use the whole EFI folder of KGP for an motherboard which is a totally different one then the ASUS X299 Deluxe...? Correct? DID you overclock your CPU?

Just by the way lilu is causing an kernel panic on your rig...

@DanyH : Please upload your whole EFI folder!

ok!!

PS:
i've dowload only the latest Lilu and add on kexts\other
in the "config.plist " with Clover Configurator-Sections-KernelToPatch- (find HAX) 8a0284c0 7444 (replace HAX) 8a0284c0 eb44 (comment) Lilu 1.2.x debug
ive tryed to boot clover usb with -v darkvake=0 slide=0 npci=0x2000 ( and the keepsyms=1 debug=0x1000)

i'm using a macbookpro8,2 for prepare the usb.
I remove the lilu.kext and disable in config.plist now the install start but stuck in D.4/ 8 of the guide.

 

[kgp]

iMacPro XHC USB Kext to be tested by all users facing issues with XHC USB3.0 under 10.13.3 public betas

Within the 10.13.3 betas, Apple suddenly assigns to XHCI@14000000 an AppleUSBXHCIPCI driver with IOPCIClassMatchID 0x0c033000 instead of 0xa2af8086. This results in the loss of native XHC USB3.0 support and in the malfunction of all XHC USB3.0 ports at least on the ASUS Prime X299 Deluxe. I don't know if we can find a way to properly inject the AppleUSBXHCIPCI driver with IOPCIClassMatchID 0xa2af8086 via our SSDT-X299-iMacPro.aml.

However it can be easily injected via the XHC USB kext attached below. With KGP-iMacPro-XHCI.kext, all USB2.0 and USB3.0 ports will become fully functional. This kext should be at least fully compatible with the ASUS Prime X299 Deluxe, but hopefully it will be also compatible with all other mainboards facing the same IOPCIClassMatchID issue.

Under 10.13.2, this kext also properly implements all USB HDDs and SSDs as external drives, where else all USB2.0 and USB3.0 drives are also still correctly and fully natively implemented by OSX, thanks to the AppleUSBXHCIPCI driver with IOPCIClassMatchID 0xa2af8086.

Your user feedback about XHC USB Kext compatibly and functionality is highly desired and appreciated.

 

[LateBloomer]

Let me guess... You use the whole EFI folder of KGP for an motherboard which is a totally different one then the ASUS X299 Deluxe...? Correct? DID you overclock your CPU?

Just by the way lilu is causing an kernel panic on your rig...

@DanyH : Please upload your whole EFI folder!

Hey, DSM2. I apologize for a slightly off-topic question, but I wanted to know if Thunderbolt ports are functional on your Designare EX board?

 

[DanyH]

I removed Lilu.kext and after 40min, I have this error now, problem in the verification and repair of the file system. (guide D.4 /8 )