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

[izo1]

Just wanted to post latest results and thank @kgp and @interferenc for their hard work and everyone else for suggestions.

I will be OC'ing a bit since I'm running on a BeQuiet! AIO but that will come later. (I'm sure we can do a better score in Cinebench on the 7900x )

Once I figure out the RX560 system freeze issue I will report back and hope it helps others.

I am able to loan a RX580 from a friend to see if this problem is indeed related to Polaris or specifically the lower end RX560.
I am very curious to find out because a "perfect" iMac Pro clone would be amazing and we can reach that with the Vega Frontier Edition.

But I will report back regarding the RX580.

The other thing I want to try is putting the RX560 as the main display GPU and a 980Ti as a secondary (I have 2x 980Tis, maybe I will put both in for total of 3GPUs) GPU for CUDA in Davinci Resolve, After Effects and Premiere. This way we can also avoid the current nVidia "lag" issue with 10.13.3 and latest nVidia drivers. Most likely 10.13.4 will fix these issues as Apple IS aware of the lag (I speak directly with their engineers) but this will require nVidia's attention.

Thanks all!

 

[izo1]

Is the Gigabyte bios locked? Or do your patches do other things?
Sorry, maybe I missed something. I thought I didn't need the patch.

My Designare EX is locked for sure. I had to use TSCAdjustReset.kext and the 2 patched ssdt's to get it working properly. I also had to enable "xcpm_core_scope_msrs" patch in config.plist. All works well now.

It seems like most mobos are locked (ie CFG-Lock). Maybe if someone is super good at modifying bioses can unlock the Gigabyte X299 boards as well

 

[kgp]

Is the Gigabyte bios locked? Or do your patches do other things?
Sorry, maybe I missed something. I thought I didn't need the patch.

pete1959, @izo1,

The thing is that the actual ASUS firmware patches of @interferenc do not only unlock the MSR 0XE" register on ASUS mainboards, as previously, but now also fix the Skylake-X TSC Issue as described in my guide. Unfortunately, the Firmware patch currently cannot be applied on Gigabyte Firmware. Your boards anyway do have unlocked MSR register, thus the patches of @interferenc in their current state are also not adequate for your BIOS Firmware. You just would need the TSC patch, but even this simplified patch actually would fail due to the different firmware.

So you are left with using TSCAdjustReset.kext or VoodooTSCSync.kext as the only alternative option to circumvent the Skylake-X TSC issue and to successfully boot and wake your systems.

Cheers,

KGP

 

[Loloflatsix]

My Designare EX is locked for sure. I had to use TSCAdjustReset.kext and the 2 patched ssdt's to get it working properly. I also had to enable "xcpm_core_scope_msrs" patch in config.plist. All works well now.

It seems like most mobos are locked (ie CFG-Lock). Maybe if someone is super good at modifying bioses can unlock the Gigabyte X299 boards as well

Same configuration for me.

Notice the coast for RX 580 has becoming more expensive at beginning of 2018 , I purchased my Sapphire Radeon nitro+ Special Edition RX 580 for 319 € about 396 USD in November 2017 (on Amazon.fr).

 

[mgregrs]

Hello Genius - especially @interferenc and @kgp !
It's a really great to see a good news here when you have 'not great day'...
Especially VERY BIG pleasure to boot without TSCSync
You are THE best!

My info from last 2 hours of
1st paching bios,
2nd: TSCSync test on 2 version of OSX
3rd: Sleep/Wake tests on 10.13.3 and 10.13.4 public beta
(of course with the same BIOS options, verification with bdmesg, voltageshift,
notes from E.1 etc... )
(I use only ssdt.aml in patched folder, and 85%of paches/replacements in clover enabled,
2nd iMac Pro.aml not touched yet, and of course not used... yet)

I can boot without TSC Sync on 10.13.3 and 13.4b without problems.

Then: first wake and sleep (like a baby) on 10.13.4
everything works great:

2018-02-04 19:08:01.337480+0100 0x3001     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000626.868317 AppleUSB20XHCIPort@03200000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 19:08:01.337573+0100 0x2f6f     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000626.868411 AppleUSB20XHCIPort@03100000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 19:08:01.337603+0100 0x2f19     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000626.868443 AppleUSB30XHCIPort@03400000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 19:08:01.337765+0100 0x2f12     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000626.868604 AppleUSB30XHCIPort@03300000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 19:08:01.760340+0100 0x2faa     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000627.291178 AppleUSB30XHCIPort@03400000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 19:08:01.760355+0100 0x309a     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000627.291194 AppleUSB20XHCIPort@03200000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 19:08:01.760475+0100 0x3087     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000627.291315 AppleUSB30XHCIPort@03300000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 19:08:01.760551+0100 0x3078     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000627.291390 AppleUSB20XHCIPort@03100000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 19:08:02.183428+0100 0x30ce     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000627.714267 AppleUSB20XHCIPort@03100000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)

and 100x the almost the same thing

then 2nd sleep: I have to reboot manually and I can see...

iMac-Pro-de-G-BCP:~ gwbcp$ log show --last 10m | grep TSC
2018-02-04 18:50:41.138243+0100 0x0        Default     0x0                  0      0    kernel: TSC Deadline Timer supported and enabled
2018-02-04 18:50:43.002951+0100 0x8e       Default     0x0                  0      0    kernel: Unsynchronized  TSC for cpu 6: 0x00000027924ee04c, delta 0x14491ab3c
2018-02-04 18:50:43.018880+0100 0x91       Default     0x0                  0      0    kernel: Unsynchronized  TSC for cpu 9: 0x00000027957e5a74, delta 0x14491ab96
2018-02-04 18:50:43.045990+0100 0x9b       Default     0x0                  0      0    kernel: Unsynchronized  TSC for cpu 13: 0x000000279ad5e326, delta 0x14491ab88
2018-02-04 18:50:43.063784+0100 0x9e       Default     0x0                  0      0    kernel: Unsynchronized  TSC for cpu 16: 0x000000279e598240, delta 0x14491ab88
2018-02-04 18:50:44.677339+0100 0x99       Default     0x0                  0      0    kernel: Unsynchronized  TSC for cpu 11: 0x00000027984569c4, delta 0x14491ab94
2018-02-04 18:30:32.108225+0100 0x0        Default     0x0                  0      0    kernel: TSC Deadline Timer supported and enabled
2018-02-04 18:44:04.340061+0100 0x3c1d     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000593.599352 AppleUSB20XHCIPort@03100000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 18:44:04.340083+0100 0x3b07     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000593.599373 AppleUSB30XHCIPort@03400000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 18:44:04.340088+0100 0x3c28     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000593.599380 AppleUSB20XHCIPort@03200000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
a lot of times the same line and
at the end
2018-02-04 18:52:37.108119+0100 0x0        Default     0x0                  0      0    kernel: TSC Deadline Timer supported and enabled

Without patch AppleUSBXHCI (USB port limit)
(it's weird because my ports which doesn't work before, now work pretty nice without that patch, maybe I missed something)
and result after 2nd wake: (after manually reset and reboot)

2018-02-04 19:44:01.108309+0100 0x0        Default     0x0                  0      0    kernel: TSC Deadline Timer supported and enabled
2018-02-04 19:47:23.338801+0100 0x1fad     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000148.877448 AppleUSB30XHCIPort@03300000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 19:47:23.338803+0100 0x2019     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000148.877449 AppleUSB20XHCIPort@03200000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
the same line xxxx times and:
2018-02-04 19:49:16.453395+0100 0x2e98     Default     0x0                  0      0    kernel: (AppleUSBXHCI) 000261.523363 AppleUSB30XHCIPort@03300000: AppleUSBXHCIPort::powerOn: deadline passed (PORTSC 0x00000000)
2018-02-04 19:51:10.108557+0100 0x0        Default     0x0                  0      0    kernel: TSC Deadline Timer supported and enabled

then tests on final 10.13.3 (of course we don't need AppleUSBXHCI patch) so:

after clean boot:
2018-02-04 20:00:23.107853+0100 0x0 Default 0x0 0 0 kernel: TSC Deadline Timer supported and enabled

after sleep: (fail - manual reboot needed)

2018-02-04 20:00:23.107853+0100 0x0        Default     0x0                  0      0    kernel: TSC Deadline Timer supported and enabled
2018-02-04 20:06:39.108440+0100 0x0        Default     0x0                  0      0    kernel: TSC Deadline Timer supported and enabled

and 2nd try after boot then sleep.. and again fail - PC won't wake up.
after reboot: nothing
simply

2018-02-04 20:18:42.108034+0100 0x0        Default     0x0                  0      0    kernel: TSC Deadline Timer supported and enabled

So easy we can boot on both versions 10.13.3 and 13.4 public beta without TSC Sync which is great achievement in my opinion,
and sleep/wake tests (in my case) on 10.13.3 are wasting my time, what I said before, so it's good to know
(of course it's in my case.. which can be completely different for other people)

 

[kgp]

It's hard to say what the issue is without seeing your clover files. Possibly some of the issues are to do with trying to run an EFI designed and running perfectly on a locked Asus motherboard. If you have a Gigabyte (or any system not identical to kgp's for that matter), you need to remove all patches and SSDTs, get a basic running system and then add patches and kexts as necessary to fix up anything that's wrong.
I just find it weird that DSM and myself are able to run flawless hacks without firmware changes and you are not...

edit: VoodooTSCSync has always been needed for X299 and X99. Unless you have an identical CPU to a Mac system you will need something to help the OS utilise the CPU properly.

@Loloflatsix has a Gigabyte GA X299 UD4! Just look to his profile!

There is absolutely nothing weird on the fact that Gigabyte mainboards do have unlocked MSR 0xE2 register and ASUS mainboards don't.. This is a fact known for decades and that's the reason why we always have to patch the firmware of our ASUS mainboards and you Gigabyte guys don't..

Patching the BIOS firmware is no big deal once the correct patches are known. It's basically a question of 5 min..

After patching the ASUS firmware now, we don't need any VoodooTSCSync.kext anymore with ASUS boards. You Gigabyte guys do as you are unable to apply the necessary patch to your BIOS ...

And now all pseudo-experts, can we please stop all these discussions? This thread is again in danger to completely run out of control.

Thanks for your collaboration and comprehension!

KGP

 

[Loloflatsix]

It's not easy to configure correctly: I'm trying to adjust some parameters to have my build running well.

 

[izo1]

@izo1 : Gigabyte Designare and all other Gigabyte Boards are unlocked... please don’t spread rumours which are not true at all!

I cannot boot Designare EX without TSCAdjustReset.kext or VoodooTSCSync.kext.

Can you post your EFI in a zip file so I can see how you're doing it?

Thanks!

 

[izo1]

You'll just need Lilu and Whatevergreen in kexts other.
And take out the sensor kexts if you don't use sensors.
link:

I have all the necessary kexts in other.

Also if Gigabyte is indeed unlocked then how come on this board specifically I have to patch XCPM?

Also I don't believe things are running smoothly for the select few in this thread.

No one is posting what their day to day activity is. Ie do you grind all day in Adobe apps, Resolve, etc?

Running a few benchmarks and browsing YouTube doesn't mean the machine is stable.

Even real Macs have trouble with how I work with them. I might need to get a Mac Pro 2018 when it comes out this year.

Too bad whoever has Designare EX won't post their EFI

 

[kgp]

Here is the VoodooTSCSync kext for your processor (with 6 cores right)
In kexts others you will need FakeSMC, your ethernet kext, Lilu and whatevergreen for your GPU, and this VoodooTSCSync kext.
In ACPI, nothing in origin or patched folders.
In config.plist, no patches in kexts or kernels to patch.

Good luck!

edit: @izo1
Just be thankful you don't have to do a bios mod, a kext is way easier and safer. Plus it survives bios updates and OS updates.
As I said before, X99 and X299 systems have always needed VoodooTSCSync and as interferenc said, it's a very low impact kext. We don't need to be scared to use it.

Pete, you jump into this thread without having read my guide nor followed the last 200 posts and dozens of pages with recent discussion and recent improvements and implementations!

VoodooTSCSync.kext is OBSOLETE, also for Gigabyte boards! You can use TSCAdjustReset.kext know if you are not able to fix your BIOS for the Skylake-X TSC issue.

Your actions are more than confusing, you are not up-to-date and you just further confuse the readers with your marvellous suggestions, ideas and comments.

Can you please stop at this place to put the entire thread upside down?

Is anybody here able to read and follow my guide or at least to follow the recent discussion?

I will stop my support of this thread for now. We reached a point of no-go.

All my work just seems a total waste of time..

Have a great day or night.

All the best,

KGP