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

[antagon]

I just tried to delete AptioMemoryFix.efi and switched back to EmuVariableUefi-64.efi & OsxAptioFixDrv-64.efi.
For me restart and shutdown work again.

 

[kgp]

I just tried to delete AptioMemoryFix.efi and switched back to EmuVariableUefi-64.efi & OsxAptioFixDrv-64.efi.
For me restart and shutdown work again.

Which makes me indefinitely happy...

 

[TECH_ATTACK]

Yes, switching back to OsyAptioFixDrv.efi and Test2-2016.efi helped me too.

@kgp
Just one (last) question.... my Wifi is located at PCI0.RP19.PXSX... what do I have to set in ACPI patches. PXSX -> APRT can not be right, because then I would replace/rename all PXSX to APRT, which would not work, because there are other locations with contains needed important PXSX. So what would you say, how to replace/rename only this single PXSX?

 

[kgp]

Yes, switching back to OsyAptioFixDrv.efi and Test2-2016.efi helped me too.

@kgp
Just one (last) question.... my Wifi is located at PCI0.RP19.PXSX... what do I have to set in ACPI patches. PXSX -> APRT can not be right, because then I would replace/rename all PXSX to APRT, which would not work, because there are other locations with contains needed important PXSX. So what would you say, how to replace/rename only this single PXSX?

Look how I did it in case of XHC2, XHC3 and XC4 and do it the same way with ARPT

External (_SB_.PCI0.RP01.XHC2, DeviceObj)    // (from opcode)

Device (\_SB.PCI0.RP01.XHC2)
{
}
Name (_SB.PCI0.RP01.PXSX._STA, Zero)  // _STA: Status

Thus in your case it would be:

External (_SB_.PCI0.RP19.ARPT, DeviceObj)    // (from opcode)

Device (\_SB.PCI0.RP19.ARPT)
{
}
Name (_SB.PCI0.RP19.PXSX._STA, Zero)  // _STA: Status

No ACPI DSDT Replacement Patch.. that's totally correct!.. yes sir, great and correct conclusion

The replacement has do be correctly done within the SSDT-X299-iMacPro.aml

 

[PedroJSkywalker]

Hi KGP, in section B of the guide you explain in detail how to proceed to patch the Bios and at the end of this section there is the link to download the X299D.CAP, so I deduce that the detailed explanation is so that everyone can do it by step if you wish but your X299D.CAP is ready and complete to proceed directly to patch the Bios without having to do anything previously.

Is my deduction correct?

A greeting.

 

[kgp]

Hi KGP, in section B of the guide you explain in detail how to proceed to patch the Bios and at the end of this section there is the link to download the X299D.CAP, so I deduce that the detailed explanation is so that everyone can do it by step if you wish but your X299D.CAP is ready and complete to proceed directly to patch the Bios without having to do anything previously.

Is my deduction correct?

A greeting.

Yes sir, bit only because you have the same mobo like me...

 

[PedroJSkywalker]

 

[antagon]

Which makes me indefinitely happy...

That's what I hoped for

 

[SomersetM]

Thank you very much for your guide.
I'm using 7820 x.
Your guide says that 7820x, 7900x do not use ssdtprgen.
Can you tell me why these two models are the only ones?

 

[lamidue]

Good evening @kgp I've been struggling for several hours getting the USB installer to show in Clover with no luck. USB installers containing older versions of OSX do show up in Clover. So, I know the problem is related to OSX 10.13.2 and how I create the USB installer. Now, everything seems to work out well till the point where I have to make it bootable.

cd /Volumes/Install\ macOS\ High\ Sierra
mkdir .IABootFiles
cd .IABootFiles
cp /Volumes/Install\ macOS\ High\ Sierra/System/Library/CoreServices/boot.efi .

I receive the response:

usage: cp [-R [-H | -L | -P]] [-fi | -n] [-apvX] source_file target_file
cp [-R [-H | -L | -P]] [-fi | -n] [-apvX] source_file ... target_directory

Afterwards the the hidden folder .IABootFiles is empty? Could you please let me know if this is correct behaviour?
I can't eject the USB before I quit Terminal (As Terminal is using the USB disk). I fear it might be in process of something it never finishes