Jump to content

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


KGP-iMacPro
 Share

iMacPro Build/Guide Feedback   

26 members have voted

  1. 1. Does this guide help you in your endeavour?

    • yes
      21
    • no
      5

This poll is closed to new votes


656 posts in this topic

Recommended Posts

1 hour ago, KGP-iMacPro said:

 

Uppppsss... many, many errors :rolleyes:...

 

Try to use this totally revised EFI-Folder. If it does not work OoB as now implemented, we will have to fix remaining errors and issues.

 

What needs to be done in addition:

 

1.) Reinstall unpatched vanilla AppleHDA.kext in /S/L/E by means of kext utility. 

2.) For 10.14.1 you will have to disable the USB port limit patch and create a board-specific truncated 15-port XHC USB kext for your X299 Sage by following my respective guideline linked within the main guide in the originating pot of this thread. The board-specific truncated 15-port XHC USB kext needs to be implemented in /EFI/CLOVER/kexts/Other. I recommend to disable the USB port limit patch and to use the truncated 15-port XHC USB kext also under 10.13.6 (SU) or 10.14.0. 

3.) Confirm all actual device implementations by means of IOREG and Section "PCI" of Apple's system report. 

 

Good luck,

 

KGP

 

 

Thank you very much, so far everything except the Wireless works like a charm, even got the little boost on the CPU/GPU side, so I guess WhateverGreen was needed.


On the USB part I don't have only 9 USB ports on the motherboard if I'll add 6 more from the USB3 Pcie card that'll be exactly 15.


 

With SSDT-ARPT my wifi gets disabled.

1718551348_Screenshot2018-11-1503_51_32.png.13d0626dc74930a79a4ffa49ecedd424.png

 

27999111_Screenshot2018-11-1503_51_21.thumb.png.9a30a3d910d2444951e2377f01843655.png

 

 

 

And when removed:

2021952217_Screenshot2018-11-1504_02_01.thumb.png.13055abd91f10508862fa47fd6a6d027.png
 

661328559_Screenshot2018-11-1504_06_22.thumb.png.aedbe484bf5826321c57ca07fc62207d.png


The only thing I'm wondering is why HDMI didn't stick, and will be fun to do second GPU.

 

Edited by Balamut
USB information.
Link to comment
Share on other sites

43 minutes ago, Balamut said:

 

Thank you very much, so far everything except the Wireless works like a charm, even got the little boost on the CPU/GPU side, so I guess WhateverGreen was needed.


On the USB part I don't have only 9 USB ports on the motherboard if I'll add 6 more from the USB3 Pcie card that'll be exactly 15.


 

With SSDT-ARPT my wifi gets disabled.

1718551348_Screenshot2018-11-1503_51_32.png.13d0626dc74930a79a4ffa49ecedd424.png

 

27999111_Screenshot2018-11-1503_51_21.thumb.png.9a30a3d910d2444951e2377f01843655.png

 

 

 

And when removed:

2021952217_Screenshot2018-11-1504_02_01.thumb.png.13055abd91f10508862fa47fd6a6d027.png
 

661328559_Screenshot2018-11-1504_06_22.thumb.png.aedbe484bf5826321c57ca07fc62207d.png


The only thing I'm wondering is why HDMI didn't stick, and will be fun to do second GPU.

 

 

Can you upload once more an IOREG.save, this time with all SDDTs in your EFI-Folder during boot?  

Link to comment
Share on other sites

1 hour ago, Balamut said:

 

Thank you very much, so far everything except the Wireless works like a charm, even got the little boost on the CPU/GPU side, so I guess WhateverGreen was needed.


On the USB part I don't have only 9 USB ports on the motherboard if I'll add 6 more from the USB3 Pcie card that'll be exactly 15.


 

With SSDT-ARPT my wifi gets disabled.

1718551348_Screenshot2018-11-1503_51_32.png.13d0626dc74930a79a4ffa49ecedd424.png

 

27999111_Screenshot2018-11-1503_51_21.thumb.png.9a30a3d910d2444951e2377f01843655.png

 

 

 

And when removed:

2021952217_Screenshot2018-11-1504_02_01.thumb.png.13055abd91f10508862fa47fd6a6d027.png
 

661328559_Screenshot2018-11-1504_06_22.thumb.png.aedbe484bf5826321c57ca07fc62207d.png


The only thing I'm wondering is why HDMI didn't stick, and will be fun to do second GPU.

 

 

There have been still errors in both SSDT-X299-Nvidia.aml and  SSDT-X299-ARPT.aml. Please find both files once more attached below. 

 

If HDAU still does not work try

 

                Device (HDAU)
                {
                    Name (_ADR, One)  // _ADR: Address

 

instead of 

 

                Device (HDAU)
                {
                    Name (_ADR, Zero)  // _ADR: Address

 

In principle both files should work now properly.

 

I also once more uploaded the complete EFI-Folder including the revised version of SSDT-X299-Nvidia.aml and  SSDT-X299-ARPT.aml. Here the corresponding LINK for download. 

SSDT-X299-ARPT.aml.zip

SSDT-X299-Nvidia.aml.zip

  • Like 1
Link to comment
Share on other sites

Weird, I had to redo my post twice.

 

 

Wifi worked like a charm, but HDAU still shows weirdly even though it is registered in the IOReg.

 

2108840447_Screenshot2018-11-1515_10_54.thumb.png.5d012cf71b8b8223dd213e50d8505f19.png

429732167_Screenshot2018-11-1515_12_34.thumb.png.415968391639cc2e235c506ade638912.png

 

 

 

 

Also got this errors:

 

2018-11-15 15:08:45.887269-0800 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) GPE _L6B has no implementation
2018-11-15 15:08:45.887270-0800 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) GPE _L6B has no implementation

 

2018-11-15 15:09:06.200715-0800 0x34e      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::configResourceCallback - DeepSleep is not supported!
2018-11-15 15:09:06.200716-0800 0x34e      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::configResourceCallback - DeepSleep is not supported!

 

This I'm assuming is normal:

2018-11-15 15:09:07.960067-0800 0x5e5      Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Warning: \_SB.PC02.BR2A.PEGP.EGP0.GFX0._DSM:
2018-11-15 15:09:07.960067-0800 0x5e5      Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Warning: \_SB.PC02.BR2A.PEGP.EGP0.GFX0._DSM:
2018-11-15 15:09:07.960069-0800 0x5e5      Default     0x0                  0      0    kernel: (AppleACPIPlatform) Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]
2018-11-15 15:09:07.960070-0800 0x5e5      Default     0x0                  0      0    kernel: (AppleACPIPlatform) Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]

 

 

 

Edited by Balamut
Link to comment
Share on other sites

8 hours ago, Balamut said:

Weird, I had to redo my post twice.

 

 

Wifi worked like a charm, but HDAU still shows weirdly even though it is registered in the IOReg.

 

2108840447_Screenshot2018-11-1515_10_54.thumb.png.5d012cf71b8b8223dd213e50d8505f19.png

429732167_Screenshot2018-11-1515_12_34.thumb.png.415968391639cc2e235c506ade638912.png

 

 

 

 

Also got this errors:

 


2018-11-15 15:08:45.887269-0800 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) GPE _L6B has no implementation
2018-11-15 15:08:45.887270-0800 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) GPE _L6B has no implementation

 


2018-11-15 15:09:06.200715-0800 0x34e      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::configResourceCallback - DeepSleep is not supported!
2018-11-15 15:09:06.200716-0800 0x34e      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::configResourceCallback - DeepSleep is not supported!

 

This I'm assuming is normal:


2018-11-15 15:09:07.960067-0800 0x5e5      Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Warning: \_SB.PC02.BR2A.PEGP.EGP0.GFX0._DSM:
2018-11-15 15:09:07.960067-0800 0x5e5      Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Warning: \_SB.PC02.BR2A.PEGP.EGP0.GFX0._DSM:
2018-11-15 15:09:07.960069-0800 0x5e5      Default     0x0                  0      0    kernel: (AppleACPIPlatform) Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]
2018-11-15 15:09:07.960070-0800 0x5e5      Default     0x0                  0      0    kernel: (AppleACPIPlatform) Argument #4 type mismatch - Found [Buffer], ACPI requires [Package]

 

 

 

 

Can you try the revised SSDT-X299-Nvidia.aml attached below?

 

If it still does not work try to change 

 

                Device (HDAU)
                {
                    Name (_ADR, Zero)  // _ADR: Address

 

to

 

                Device (HDAU)
                {
                    Name (_ADR, One)  // _ADR: Address

 

SSDT-X299-Nvidia.aml.zip

  • Like 1
Link to comment
Share on other sites

12 hours ago, KGP-iMacPro said:

 

Can you try the revised SSDT-X299-Nvidia.aml attached below?

 

If it still does not work try to change 

 


                Device (HDAU)
                {
                    Name (_ADR, Zero)  // _ADR: Address

 

to

 


                Device (HDAU)
                {
                    Name (_ADR, One)  // _ADR: Address

 

SSDT-X299-Nvidia.aml.zip

 

 

Worked like a charm! Monday will test out 2 GPUs, lets see how that works out.

 

614453927_Screenshot2018-11-1612_42_05.thumb.png.8e8aa1b1a6e6766ba7abfeab9adde48c.png

 

 

 

 

  • Like 1
Link to comment
Share on other sites

@Balamut

 

sudo ethtool -E enp225s0f0 magic 0x15638086 offset 0x242 value 0x0a
sudo ethtool -E enp225s0f0 magic 0x15638086 offset 0x243 value 0x00
sudo ethtool -E enp225s0f1 magic 0x15638086 offset 0x242 value 0x0a
sudo ethtool -E enp225s0f1 magic 0x15638086 offset 0x243 value 0x00

 

but check if your enp is correct.

This example is from my WS X299 Sage/10G and this way it works on my build without any problems.

 

 

1.png

Edited by DSM2
  • Like 2
Link to comment
Share on other sites

1 hour ago, DSM2 said:

@Balamut

 

sudo ethtool -E enp225s0f0 magic 0x15638086 offset 0x242 value 0x0a
sudo ethtool -E enp225s0f0 magic 0x15638086 offset 0x243 value 0x00
sudo ethtool -E enp225s0f1 magic 0x15638086 offset 0x242 value 0x0a
sudo ethtool -E enp225s0f1 magic 0x15638086 offset 0x243 value 0x00

 

but check if your enp is correct.

This example is from my WS X299 Sage/10G and this way it works on my build without any problems.

 

 

1.png

 

In fact I already provided @Balamut the correct patch for his enp already in post:

 

 

sudo ethtool -E enp179s0f1 magic 0x15638086 offset 0x242 value 0x0a

sudo ethtool -E enp179s0f1 magic 0x15638086 offset 0x243 value 0x00

 

This patch in fact already considers two LAN ports (0x0a and 0x00). Thus I am somewhat surprised that the to onboard LAN connectors of the WS X299 Sage/10G seem to be assigned to two different enp controllers.

 

Based on the previous info provided by @Balamut, his patches might be then:

 

sudo ethtool -E enp179s0f0 magic 0x15638086 offset 0x242 value 0x0a

sudo ethtool -E enp179s0f0 magic 0x15638086 offset 0x243 value 0x00

sudo ethtool -E enp179s0f1 magic 0x15638086 offset 0x242 value 0x0a

sudo ethtool -E enp179s0f1 magic 0x15638086 offset 0x243 value 0x00

 

He just needs to confirm that his second enp is indeed enp179s0f0. So far he only provided info for enp179s0f1. 

  • Like 1
Link to comment
Share on other sites

7 minutes ago, DSM2 said:

@KGP-iMacProThere are two entries and have to be patched both... otherwise it will not work! 

Like I see he use aswell an WS X299 Sage/10G so it can't be different then on my build :) 

Besides from the enp of course...

 

Sure.. that's what I was saying. Following your recent information, it seems that due to unknown reason the 2 10GB LAN connectors are distributed over two separate enp controllers.

 

Thus the patch I provided in post 

 

 

in fact needs to be applied twice for both enps as you did...

 

If the former enp info provided by @Balamut was correct, his patches should properly read:

 

sudo ethtool -E enp179s0f0 magic 0x15638086 offset 0x242 value 0x0a

sudo ethtool -E enp179s0f0 magic 0x15638086 offset 0x243 value 0x00

sudo ethtool -E enp179s0f1 magic 0x15638086 offset 0x242 value 0x0a

sudo ethtool -E enp179s0f1 magic 0x15638086 offset 0x243 value 0x00

 

no idea why the enps are different in his and your case under Linux. 

Edited by KGP-iMacPro
  • Like 2
Link to comment
Share on other sites

56 minutes ago, DSM2 said:

@BalamutSure, why they shouldnt?

 

Was it succesfull with your X550-AT2 ?

 

Which enps values did you use in the end?

 

 

 

 

 

 

Haven't done it yet, been rendering on it and when it's done will do it.

 

My old system was giving issues with the dual Titan Xps

 

 

Link to comment
Share on other sites

  • 2 weeks later...

Hey guys!

 

Was wondering if it's at least theoretically possible to use the VROC technology in the OP's build.  If not, what would be a good option for a non-boot drive internal SSD raid?  (I'd be using it for high-end visual effects - e.g. realtime 4K playback)   

(https://www.intel.com/content/www/us/en/support/articles/000024498/memory-and-storage/ssd-software.html

 

thx!

Link to comment
Share on other sites

  • 2 months later...
  • 1 month later...

Hey guys, I'm pulling my hair here.

 

The system was working perfectly fine with the latest supplemental update until I decided like an idiot to update the BIOS to 0905 then the hell broke loose, first Nvidia decided that it doesn't wanna play nice anymore so I can't even boot without nvda_drv=0 second my USB 3.0 is gone, missing MIA, tried many many things including USBAll kext only USB 3.1 is there, IOReg, System pref same thing. I know usb 3.0 is working because bluetooth is connected to it and keyboard works perfectly in BIOS and Clover.

Reversed the BIOS to the original one that was working before but I the same issue persists.

Also as a test I booted the installer that worked perfectly fine before and I get the same USB issue.

I gonna try installing windows and see what will happen. 

 

Any suggestions?

Link to comment
Share on other sites

Bios update shouldn't break the OS, unless you are using DSDT.

In that case you need to re-apply your DSDT fixes to a DSDT from the new bios.

 

AS for not working when going back to old bios, you may need to make a new

kernelcache as the one you are probably booting with is from the new bios.

 

Hope this helps, but maybe you know who will make a better suggestion.

What do I know, I've only been doing this for 11 years.

Edited by STLVNUB
  • Like 1
Link to comment
Share on other sites

21 minutes ago, STLVNUB said:

Bios update shouldn't break the OS, unless you are using DSDT.

In that case you need to re-apply your DSDT fixes to a DSDT from the new bios.

 

AS for not working when going back to old bios, you may need to make a new

kernelcache as the one you are probably booting with is from the new bios.

 

Hope this helps, but maybe you know who will make a better suggestion.

What do I know, I've only been doing this for 11 years.

 

@STLVNUB no-one is questions your experience and knowledge, well at least not this guy.

 

I'm not using DSDT.

I'll redo the kernel cache and will report back, must be having a brain fart haven't thought of that. Thank you

 

What about the USB Installer? Same issue. 

 

 

 

Edited by Balamut
Link to comment
Share on other sites

1 minute ago, Balamut said:

 

@STLVNUB no-one is questions your experience and knowledge, well at least not this guy.

 

I'm not using DSDT.

I'll redo the kernel cache and will report back, must be having a brain fart haven't thought of that. Thank you

 

 

 

 

 

The first part is aimed at someone, not mentioning any names. He knows who he is :hysterical:

 

If the kernelcache has changed, I wonder what caused the change.

Good luck.

  • Like 1
Link to comment
Share on other sites

16 minutes ago, STLVNUB said:

The first part is aimed at someone, not mentioning any names. He knows who he is :hysterical:

 

If the kernelcache has changed, I wonder what caused the change.

Good luck.

 

 

What about the Installer? Same usb issue. 

Link to comment
Share on other sites

Try re-installing the NVIDA Web driver

 

And again, you know who will probably have the right answer, if so, well done...

Edited by STLVNUB
  • Like 1
Link to comment
Share on other sites

Found the issue.

 

On the X299 Sage/10G boards when updating to 0905 please MAKE SURE to turn on the Above 4G and set it to Auto, if disabled it will for some odd reason disable USB 3.0 ports when booting into High Sierra. 

  • Like 2
Link to comment
Share on other sites

Known issue with recent ASUS X299 firmware distributions not only affecting the Sage and extensively discussed in my respective threads in the other forum. 

 

Above 4G decoding btw also needs to be enabled to avoid GPU firware load issues at early UEFI boot. 

 

Alternative solution, downgrade to former BIOS firmware and also apply CMOS reset, if necessary. 

Edited by KGP-iMacPro
  • Like 2
Link to comment
Share on other sites

11 hours ago, KGP-iMacPro said:

Known issue with recent ASUS X299 firmware distributions not only affecting the Sage and extensively discussed in my respective threads in the other forum. 

 

Above 4G decoding btw also needs to be enabled to avoid GPU firware load issues at early UEFI boot. 

 

Alternative solution, downgrade to former BIOS firmware and also apply CMOS reset, if necessary. 

 

Sorry man didn't see it, wish I could have though, would have save me a lot of headache and time. Also seems like downgrade with reset didn't work in my case. Thanks for the help and heads up.

 

  • Like 2
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...