Contribute
Register

How to extend the iMac Pro to X99 [Successful Build/Extended Guide]

Status
Not open for further replies.
Major revision of my Broadwell-E/EP (Haswell-E/EP)/X99 macOS High Sierra 10.13 Desktop Guide

New EFI-Folder attached at the end of the originating post/guide and here below.

EFI-Folder modifications:
  • DMAR, Cpu0lst and CpuPm "Drop Tables" entries added to the config.plist in the "ACPI"-Section of the Clover Configurator
  • Revision of all config.plist KernelToPatch-entries in the "Kernel and Kext Patches" Section of the Clover Configurator
  • Removal of SSDT-Sleep.aml from /EFI/Clover/ACPI/patched
Guide modifications:
  • Complete revision of the KernelToPatch figure, table and text in the XCPM guideline.
  • Refinement of the black screen prevention when using Nvidia Graphics Cards with SMBIOS macPro6,1
  • Additional minor bug fixing..

kgp.png
 

Attachments

  • EFI-X99-10.13-Final-Release-300917.zip
    20.1 MB · Views: 64
Last edited:
Blacky said:
I'm very confused now. So which entries should be enabled and which not?
I have 6900K

Your Cloverconfig enables these by default: http://www.mediafire.com/view/iokvyvuehgegi5x/Screen Shot 2017-10-01 at 11.09.27.png

But your guide suggests I should only have these enabled: http://www.mediafire.com/view/799w9ts2jxw76v2/Screen Shot 2017-10-01 at 11.08.31.png
Click to expand...

You are faster than the wind ;)

Please see post #477 .... KernelToPatch Figure, Table and Text now should be in concordance with the most actual EFI-Folder.
 
Blacky said:
1. All USB ports seem to be working, I've tested them. Not sure if they are properly implemented , I think some USB 3.0 and USB 2.0 ports are interchanged: http://www.mediafire.com/view/439m0efc2d3g1ym/Screen Shot 2017-10-01 at 10.47.09.png

2. XCMP is working
sysctl -n machdep.xcpm.vectors_loaded_count returns 1

3. ssdtPRGen complains that the board ID is unsupported but still generates everything.
Not sure if it's fine but:
plugin-type Number 0x1 - is set like this is IORegistry
kextstat|grep -y x86plat - returns the two X86PlatformPlugin and PlatformShim entries
kextstat|grep -y appleintelcpu. - is empty

Everything seems to be fine or am I missing something?
Click to expand...

a.) That USB2.0 devices appear in Apple's System Report on the USB 3.0 Bus is not very handy but rather a cosmetic drawback, which should not affect the overall USB2.0 and USB3.0 functionality.

b.) Of yet unknown reason, I am currently not able to successfully boot the macOS 10.13 USB Flash Drive Installer and distributed EFI-folder via one of the internal and external USB2.0 and USB3.0 connectors available on the ASUS X99-A II, when using the X99_Injector USB 3.kext. However, a macOS 10.13 USB3.0 Flash Drive Installer with the same EFI-Folder successfully boots on a natively implemented additional PCIe USB3.0 controller. In the same way, I am able to successfully boot a macOS 10.13 USB3.1 Flash Drive Installer with the same EFI-Folder on one of the onboard USB3.1 Type-A and Type-C ports of the ASUS X99-A II. That's why I recommended for now to use a USB3.1 USB Flash Drive Installer on one of the USB3.1 Type-A and Type-C ports.

If in your case, the USB3.0 Flash Drive Installer with the distributed EFI-Folder even boots on one of your onboard USB2.0 or USB3.0 ports, even better. I am totally happy in this case.

I hope this also answers the questions and comments of @GDS!

If XCPM is fully functional on your system with your current SMBIOS Implementation, I am happy too! I don't think the you are missing something.

Cheers,

KGP
 
kgp

I found a new fact.

EmuVariableUefi-64.efi when installing graphic driver If this file does not exist, black screen black screen appears

kgp efi folder does not have this file.
 
sweetsnap said:
kgp

I found a new fact.

EmuVariableUefi-64.efi when installing graphic driver If this file does not exist, black screen black screen appears

kgp efi folder does not have this file.
Click to expand...

Thanks for your appreciated comment, which I immediately implemented in my guide!

Not however the following:

The necessity of EmuVariableUefi-64.efi is not a fact!

I am just able to emphasise once more that on my system with SMBIOS macPro6.1, the Gigabyte AORUS GTX 1080 Ti Extreme 11GB and the ASUS X99-A II, it was completely sufficient just to apply the AGDPfix.app in order to avoid the black screen issue with Nvidia Graphics Cards.

I cannot confirm the requirement of EmuVariableUefi-64.efi in the /EFI/CLOVER/drivers64UEFI/ directory in case of my system and I do not use EmuVariableUefi-64.efi in the /EFI/CLOVER/drivers64UEFI/ directory of my System Disk!!!!

Cheers,

KGP
 
Blacky said:
Excellent!

So for Broadwell-E , 6900K it should look like this: https://www.mediafire.com/file/4xn4g3hylyg9764/Screen Shot 2017-10-01 at 13.57.05.png

Correct?
Click to expand...

Not at all!!!!

It should exactly look like in the actual figure in my guide and as already implemented in the recently distributed and most actual EFI-Folder attached at the end of the originating post/guide!

For the Broadwell-E i7-6900K you have not to change anything with respect to the already implemented KernelTopPatch entries! For both the i7-6950X and i7-6900K, the KernelToPatch entries are absolutely identical (both are Broadwell-E processors)!

Cheers,

KGP
 
kgp said:
Not at all!!!!

It should exactly look like in the actual figure in my guide and as already implemented in the recently distributed and most actual EFI-Folder attached at the end of the originating post/guide!

For the Broadwell-E i7-6900K you have not to change anything with respect to the already implemented KernelTopPatch entries! For both the i7-6950X and i7-6900K, the KernelToPatch entries are absolutely identical (both are Broadwell-E processors)!

Cheers,

KGP
Click to expand...

I removed the first 2 entries.

But then why did you write in the guide:
c.) "KernelToPatch" entries in the "Kernel and Kext Patches" Section:

View attachment 270231
  • Broadwell-E/EP "xcpm_cpuid_set_info" and "xcpm_bootstrap":
Code (Text):
Find: Replace: Comment: MatchOS:
723cd077 500fb6c0 6a3cd077 500fb6c0 xcpm_cpuid_set_info © Pike R. Alpha 10.13.x
89d804c4 3c227722 89d804c3 3c227722 xcpm_bootstrap © Pike R. Alpha 10.13.x
 
kgp said:
Allright! :thumbup:

In any case, if you would need help in creating an XHC USB Kext for the ASUS X99 Deluxe II , let me know!

By the way :!::!::!:

Is the ASUS X99-A II not identical with the ASUS X99 Deluxe II in the USB-Port Configuration? :idea::idea::idea:

Please check :!::!::!:

If the ASUS X99 Deluxe II has the same internal and external USB ports like the ASUS X99-A II you could just directly use the XHC USB Kext attached for the ASUS X99-A II, which works much better than the x99USB kext!!! ;););)

For sure both boards also use the same XHC USB controller!

Can you give it a try??? Maybe the XHC USB Kext for the ASUS X99-A II works OoB also for the ASUS X99 Deluxe II ! ;)

Cheers,

KGP
Click to expand...


I actually missed reading this post of yours....

I tried using the clover r4220 but was told performance will be hurt.... so I tried your x99USBkext, and it worked!!! everything as described in your guide, one of the internal doesn't work, and the usb 3.1 doesn't work as well. I was looking at your guide but I'm going to need to read very very hard to implement it.... So I tried your kext! I'm happy with the result now!!! does your 3.1 works??
 
kingkong89 said:
I actually missed reading this post of yours....

I tried using the clover r4220 but was told performance will be hurt.... so I tried your x99USBkext, and it worked!!! everything as described in your guide, one of the internal doesn't work, and the usb 3.1 doesn't work as well. I was looking at your guide but I'm going to need to read very very hard to implement it.... So I tried your kext! I'm happy with the result now!!! does your 3.1 works??
Click to expand...

Yes my USB3.1 Type-A and Type-C ports perfectly work... They are natively implemented by OS X on different controllers than XHC and are therefore independent from the XHC controller and related kexts... Did you enable the USB3.1 controller in the BIOS?

May I ask if you use the DSM2-ASUS-X99-A-II-USB.kext or the X99_Injector USB 3.kext for your onboard XHC USB Controller. If the primer is the case, you directly confirm the validity of the Asus X99-A II XHC USB Kext also for the Asus X99 Deluxe II, which would be an important breakthrough and progress also for the latter board.

Clover r4220 is by default implemented in my distributed EFI-Folder. It perfectly works and does not affect at all the System performance! The opposite is the case!

Cheers,

KGP
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top