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

[nnorris7]

.106 seems to be more stable and smoother than 103.. I've just experienced some major lag in iTunes, especially with scrolling in the library, not to mention the system almost locked up while the audio seem to start and stop a couple of times.

Update : Also experienced Graphic glitches in iTunes with .106 so u reverted to the old Lilu and NvidiaGraphicsFixup 1.2.3 with seems to have normalised my system and fixed the screen resolution issue from wake from sleep.

Will stick to this version till somebody else reports better stability with the new updates.

Hey @perfecto245,

I'm about to update to 10.13.4, so your input regarding the Nvidia drivers is greatly appreciated.

We have almost the exact same system. I've never been able to get sleep/wake to work but I haven't implemented an SSDT. The difference in our system is the graphics card (I have a 1070 Ti) but I'm wondering if there are differences in our setup.

Have you implemented an SSDT? If so, would you be open to sharing it with me?

I'm trying to run a lean a system as possible. The following are the only kexts I have installed:
AppleALC (1.2.4)
FakeSMC (6.26.1463, with sensors included as plugins)
IntelMausiEthernet (2.3.0)
Lilu (1.2.2)
TSCAdjustReset (from @interfernc, I'm running the new BIOS - 1301 and use it to unlock the MSR register)

Any insight you have would be extremely welcome.

 

[oznem]

hello @kgp and @justdatruth, in the last few months I have been really busy working, so since my Skylake-X implementation with iMac17,1 definition was stable and solid I didn't bother updating to iMacPro1,1 definition nor to 10.13.3.
But lately for unknown reasons (at least to me) I have been getting many kernel panics! (see picture):

Any Idea to what might be the cause? Apparently I did not do any upgrades or changes to system related files, so why does it occur?

Anyway I thought it was time for an an update to Mac OS 12.13.4 and of course to iMacPro1,1 definition.
So this weekend I read KGP's updated guide, very detailed as usual, created a brand-new USB stick using 31-03-2018 EFI folder distribution and I followed all instructions to create a brand new fresh install, but no! USB stick brings me to Clover UI but after during the boot process it gets stuck right here (see picture):

I thought I did everything I needed to, but I guess it is not the case. From what I gather in my ASrock mobo the MSR 0xE2 register is unlocked when the CFG Lock is left disabled; I then just followed instructions from D.1 to D.4 also trying to prevent errors looking at section C.) Important General Note/Advice and Error Prevention.
any advices?

thanks

OZ

 

[macs_forever]

I just purchased a Radeon Pro WX 7100 for my Asus Prime X299-Deluxe for my new build. Your info means that I expect this to work for me. I'm sure that the rest of this discussion will help me when I try this now.

I wanted to start with 10.12.6 as it works on my current listed system. It sounds like 10.13.0 is working very well & may be the better choice. What is your opinion on that point or any one elses.

How did the WX7100 work out?

 

[egroys]

Hi @kgp,

I have everything working by following you amazing guide closely, but I still cannot get hotswap on my TB3 -> TB2 adapter working.
On the clover entry am I supposed to leave the PCI Address as 01:00.00 or do I track it down in my boot.log or IOReg and replace it?
View media item 190316Thank you in advance!

View media item 190315

 

[RuleBreaker01]

Hey, Rulebreaker01, have you found a solution to the "USB Current Overload" message at boot with the TB Display plugged in? I've made it work by plugging the display during clover as you recommended, but I fear it could damage something on the mobo by doing it that way, I'm I just being paranoid?

I no longer use the Asus ThunderboltEX card, but the ASRock which doesn't have this problem.
Mind you, while I was troubleshooting an issue with the ASRock card and the new Asus BIOS, I used the Asus TB3 card and I didn't get the USB current overload message. So maybe that got fixed.

The connectors are designed to be hotpluggable. I wouldn't worry about plugging it in...

 

[RuleBreaker01]

Anyway I thought it was time for an an update to Mac OS 12.13.4 and of course to iMacPro1,1 definition.
So this weekend I read KGP's updated guide, very detailed as usual, created a brand-new USB stick using 31-03-2018 EFI folder distribution and I followed all instructions to create a brand new fresh install, but no! USB stick brings me to Clover UI but after during the boot process it gets stuck right here (see picture):

View attachment 322879

I thought I did everything I needed to, but I guess it is not the case.

If it's a Gigabyte motherboard you have, then no, you haven't followed the guide closely enough
You need to have npci=0x2000 added to the arg boot. That detail is easy to miss as the mention of this boot flag isn't with the rest of the GB instructions.

In clover, while booting, if you go into clover settings, you can add the "npci=0x2000" to the boot flags, easier than mounting the EFI partition and modifying the config.plist.
Once booted, start Clover Configurator and check npci=0x2000 in the Boot section

 

[RuleBreaker01]

View media item 190316Thank you in advance!

View media item 190315

The .ioreg you've provided wasn't saved using a version of IORegistry Explorer that would allow anyone else to open it. Use IOJones to save it

 

[egroys]

The .ioreg you've provided wasn't saved using a version of IORegistry Explorer that would allow anyone else to open it. Use IOJones to save it

My bad. I just replaced it. Uploading to this post as well.

It looks like DSB0 shows PCIHotplugCapable set as 0x1, but DSB1 (where the device is actually plugged into and showing up under) and DSB2 do not.

 

[RuleBreaker01]

My bad. I just replaced it. Uploading to this post as well.

It looks like DSB0 shows PCIHotplugCapable set as 0x1, but DSB1 (where the device is actually plugged into and showing up under) and DSB2 do not.

If you look at a real mac pro ioreg PCIHotplugCapable is set to 0x0 only on the DSB0 and DSB2 device. So I'm not sure having the value set to 0x1 is compulsory. Seems that only have the key is required.

You can add that key to DSB1 and DSB4 too and see how you go...

(I'm fairly convinced hotplug works for other reasons than what most believe, as we're far from universal success with this: it only works for some)

 

[ImaPirate]

OH MY GOODNESS! 677 pages?!?! WOW!!! That's amazing! They should rename this site KGPx86.com! Anyhoo, I just wanted to say hi KGP. I've been very busy and very soon I'm going to attempt to update from 10.13.2 to 10.13.4 within the next few days when I have time. I hope you won't mind if I have a question that I can ask you for help if I need it. Thank you again for all that you're doing to stay on top of this post!