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

[kgp]

Well these matches are not in the kext executable, but in the Info.plist in kext's directory (all kexts are directories). Check AppleBusPowerController.kext/Info.plist

There could be references of DSDT device in the kext executables themselves, and yes, you could probably find them as strings in the executable. However, reverse engineering even a small kext is very hard work.

I recommend matching to the iMacPro ioreg as close as possible, but the benefit compared to no renames at all might not be that much. There are special cases like onboard sound, you need that. The others are less obvious.

There have been even clearly disadvantages when strictly staying with the iMacPro IOREG. For instance, your suspicion that renaming XHCI to XHC1 was not a good idea has been confirmed later on. After implementing XHC1, some of the USB2.0 onboard connectors failed (as the XHC USB configuration of the iMacPro deviates from the XHC USB configurations of most of the X299 boards in use). Thus, in the actual version of my config.plist and SSDT-X299-iMacPro.aml, I reintroduced XHCI, which is clearly non-iMacPro.

 

[Thireus]

View attachment 309062 Hi guys!

Anyone tried to turn on Intel Quick Sync? I tried Lilu.kext + Shiki.kext but it's still doesn't work... any idea?

Thanks in advance!

I tried several combinations to make it work, but didn't succeed. At some point it was suggested to rename GFX0 to IGPU, but for some reason I wasn't able to rename GFX0 to IGPU... I don't know why, it seems that Clover doesn't want to apply the DSDT patch or maybe a kext registers the name after the patch is applied.

You can check out the following links, maybe you'll have more success than me:

http://www.insanelymac.com/forum/to...eo-playback-support-on-recent-hardware/page-9
https://www.tonymacx86.com/threads/...antly-crashing-random-messages.233135/page-34
https://github.com/vit9696/Lilu/issues/20
https://www.tonymacx86.com/threads/itunes-protected-video-black-screen-solution-hdcp.195083/

What you can try:

Latest Lilu, Shiki, NvidiaGraphicsFixup
Renamed GFX0 to IGPU and HECI to IMEI
ig-platform-id 0x19120001
shikigva=28 or 12

 

[kgp]

I tried several combinations to make it work, but didn't succeed. At some point it was suggested to rename GFX0 to IGPU, but for some reason I wasn't able to rename GFX0 to IGPU... I don't know why, it seems that Clover doesn't want to apply the DSDT patch or maybe a kext registers the name after the patch is applied.

You can check out the following links, maybe you'll have more success than me:

http://www.insanelymac.com/forum/topic/312278-shiki-—-protected-video-playback-support-on-recent-hardware/page-9
https://www.tonymacx86.com/threads/...antly-crashing-random-messages.233135/page-34
https://github.com/vit9696/Lilu/issues/20
https://www.tonymacx86.com/threads/itunes-protected-video-black-screen-solution-hdcp.195083/

What you can try:

Latest Lilu, Shiki, NvidiaGraphicsFixup
Renamed GFX0 to IGPU and HECI to IMEI
ig-platform-id 0x19120001
shikigva=28 or 12

HECI to IMEI is fine.. But why one wants to rename GFX0 to IGPU?

The GFX0 implementation in my actual config.plist and SSDT-X299-iMacPro.aml just works fine and is also in line with the iMacPro IOREG.

 

[Thireus]

Well these matches are not in the kext executable, but in the Info.plist in kext's directory (all kexts are directories). Check AppleBusPowerController.kext/Info.plist

There could be references of DSDT device in the kext executables themselves, and yes, you could probably find them as strings in the executable. However, reverse engineering even a small kext is very hard work.

I recommend matching to the iMacPro ioreg as close as possible, but the benefit compared to no renames at all might not be that much. There are special cases like onboard sound, you need that. The others are less obvious.

Sweet!

So pretty much doing the following would help:

for plist in $(find /System/Library/Extensions/ /Library/Extensions/ | grep Info.plist); do echo $plist; cat $plist | awk '/IONameMatch/,/IOProviderClass/'; done

 

[kgp]

NvidiaGrapgicsFixup renames the card to gfx0 in all cases, that's why you can't rename it to anything else, and that's why the SL0x -> GFX0 rename in clover is not needed.

It is certainly true that NvidiaGraphicsFixup and Whatevergreen already rename the GPU to GFX0 as they also already implement HDAU. However, the persistent SL01 to GFX0 replacement and GPU/HDAU implementations do not harm and are needed in case that the AGDPFix is just applied instead. If you do neither use NvidiaGraphicsFixup nor Whatevergreen, these implementations are indeed deemed necessary or have been deemed necessary at least.

 

[Dan968]

View attachment 309062 Hi guys!

Anyone tried to turn on Intel Quick Sync? I tried Lilu.kext + Shiki.kext but it's still doesn't work... any idea?

Thanks in advance!

Intel Quick Sync Video is a technology only supported by CPU with integrated GPU...like i7-7700K with HD Graphics 630 incorporated.

 

[rabish]

Hi @rabish

I am in the process of building a new X299 system that is very similar to your configuration, ASUS X200 Prime-A but with an Intel Core i9-7920X CPU. One of the first things I tried to do was update the BIOS. I followed KGP's guide in secant B1 exactly, everything went as planned, although my Terminal output in part 8 was slightly different, which I didn't think was an issue.

However, when I went to update the BIOS, it states that the file (named X299D.CAP as required) is not a valid BIOS file. I was able to update to an unpatched version or 1102 but not the patched one.

If/when you update your BIOS, I would appreciate any help or insight you could offer as to what you did to make it work.

Bagi1992 in #4394 already answered why your BIOS update didnt work.
For me there were no problems patching 1102 BIOS and updating it. If you still have problems I can upload patched BIOS for Asus Prime X299-A, but you are gonna have to wait a few days for that, as I wont have access to my hack till Wednesday.

 

[hagybear]

Thank You @kgp and everybody who contributed to this Life Saving Masterpiece Guide !!

I am successfully running High Sierra 10.13.3 with latest EFI folder and Bios Patch !

EFI-X299-10.13.3-Release-iMacPro1,1-270118 !!

System boots flawlessly no glitches so far! brilliant !!
Gpu works Oob ! no need for WhateverGreen.kext v1.1.4. and Lilu.kext v1.2.1 !

Setup :

Mainboard: Asus Prime X299 Deluxe
CPU: i9-7980XE (18 core, 4.4Ghz)
RAM Memory: Tridentz DDR-4 3200 Mhz 32GB (2x16GB)
GPU: XFX Radeon RX VEGA 64 8GB Liquid Cooling
System Disks: EVO 960 NVMe M.2 1TB
Power Supply: Corsair AX1200i
CPU/GPU Cooling: Thermaltake Water 3.0 Riing RGB 240 Liquid cooling system
Case: Thermaltake View 71 RGB 4-Sided Tempered Glass

Thank you !!

PS.
was wondering if its possible to make the clover boot faster with maybe some flags turned off or on ?

 

[Thireus]

Nah it's just that I was still on 17C88 , I've upgraded to 17C2120 and all is good now, I can see the 10.13.3 package in the appstore from which I can upgrade, and the standalone 10.13.3 installer also works as intended on APFS volume, no need of extra kexts.



Nah, there was no need to start from scratch, APFS was not the issue. The issue was that I was still on 17C88 and I thought I would upgrade from there.

Just wanted to come back on this statement for everyone here who's using NVME. Do not use APFS file system, instead force the use of HFS+. Boot is faster and the OS is more stable on HFS+, and most importantly no more mouse lags (teleports).

You can read more about it there:

https://www.tonymacx86.com/threads/readme-common-problems-in-10-13-high-sierra.233582/

To force the use of HFS+ and avoid the conversion to APFS (during fresh install or when upgrading from Sierra to High Sierra):

https://www.tonymacx86.com/threads/...n-high-sierra-update-or-fresh-install.232855/

Cc: @AnaktuvGod

 

[nnorris7]

Bagi1992 in #4394 already answered why your BIOS update didnt work.
For me there were no problems patching 1102 BIOS and updating it. If you still have problems I can upload patched BIOS for Asus Prime X299-A, but you are gonna have to wait a few days for that, as I wont have access to my hack till Wednesday.

@rabish and @Bagi1992,

Thanks for you help. Renaming the file to X299A.CAP and using the Flashback button on the back of the motherboard allowed me to update my BIOS to the patched version of 1102.

It's interesting that I was not able to complete this task using the BIOS EZFlash Update option under Tools, which is how I originally tried it. Regardless of the name of the file, it would not accept the patched BIOS file.

I have a follow up question. I'm running into Aptio memory issues. I've tried all the various combinations but nothing seems to work, I continually get stuck at the ++++++, line. I'n going to go back an retry all combinations but if you have a combination that is working well, I would greatly appreciate the insight.

Thanks!