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

[kgp]

Never will I exclude your beloved MSI. I'm down with the budget too now don't get things twisted as I too have a MSI Raider mb. I was just wondering if @kgp was gonna shed light on the Page VI Ex due to that DIMM.2 tech. I just recently got it as an upgrade to my raider board. Just got the board and just got back to tonymac as I've stepped away from Hackintoshing for a few years. Still trying to catch up as to all the new stuff and guides there is since snow leopard and lion back when I was heavy into it. So don't feel bad or appalled, that was just something I was curious about as thats the most obvious difference from the other X299 outside of the APEX which is also Asus. But @kgp already had mentioned to me some users in the thread also have it as well and got I to run so I assume the DIMM.2 is not a big deal at all to have it operate normally. All in grown folks business ... lmao jk.

Don't ask me to shed light onto this questions. I have absolutely no experience with this board. I also forgot about that one out of three M.2's has to use the DIMM.2 slot. I do not know at all if this slot will ever work. I told you to address your questions to those people along this thread using this specific mobo. I also understood that you hold the mobo already in your hands. So what are you waiting for? .. Give it a try and you will se what works and what not..

 

[AnaktuvGod]

Don't ask me to shed light onto this questions. I have absolutely no experience with this board. I also forgot about that one out of three M.2's has to use the DIMM.2 slot. I do not know at all if this slot will ever work. I told you to address your questions to those people along this thread using this specific mobo. I also understood that you hold the mobo already in your hands. So what are you waiting for? .. Give it a try and you will se what works and what not..

I got you @kgp as this was more a response to @paulotex and not you lol. Yes we've already discussed on how I would address others who have this same board regarding DIMM.2. I was just elaborating to @paulotex my reasoning of asking about this high-end board as if I don't have a MSI raider myself. I'm down with budget as that's what it's all about right? Running mac for cheaper than apple's suggesting prices?

FYI, if I may chime on some post back, I forgot the user asking something about option A and B and not sure why you're not a fan of option A either. He made some sense as it would limit your questions and it also helps the simplicity of preconfigured builds ready to go. Just my 2 cents. The purpose of your guide is great and suited for anyone wanting to understand the background of things and is more than welcome to the knowledge, research and time you spent putting into it. As for some others, they simply want to have a Hackintosh working asap. There's geniuses and there's intelligent people... there's developers and there's users... there's folks who who really want to understood under the hood of how Mac works and then there's those who simply care about - setting the bios / Unibeast / Multibeast / enjoy the new Hackintosh. And we ALL come to tonymacx86 for the latest and greatest with Hackintosh related inquiries. Just sayin, option A wouldn't be bad to add that's all. Would only help and not delay a handful still having some issues from getting there rigs running efficiently. Let's be real @kgp , we all don't have your background and level of intelligence you may have. Just my thoughts but keep it up man. You rocking thus far

 

[kgp]

I got you @kgp as this was more a response to @paulotex and not you lol. Yes we've already discussed on how I would address others who have this same board regarding DIMM.2. I was just elaborating to @paulotex my reasoning of asking about this high-end board as if I don't have a MSI raider myself. I'm down with budget as that's what it's all about right? Running mac for cheaper than apple's suggesting prices?

FYI, if I may chime on some post back, I forgot the user asking something about option A and B and not sure why you're not a fan of option A either. He made some sense as it would limit your questions and it also helps the simplicity of preconfigured builds ready to go. Just my 2 cents. The purpose of your guide is great and suited for anyone wanting to understand the background of things and is more than welcome to the knowledge, research and time you spent putting into it. As for some others, they simply want to have a Hackintosh working asap. There's geniuses and there's intelligent people... there's developers and there's users... there's folks who who really want to understood under the hood of how Mac works and then there's those who simply care about - setting the bios / Unibeast / Multibeast / enjoy the new Hackintosh. And we ALL come to tonymacx86 for the latest and greatest with Hackintosh related inquiries. Just sayin, option A wouldn't be bad to add that's all. Would only help and not delay a handful still having some issues from getting there rigs running efficiently. Let's be real @kgp , we all don't have your background and level of intelligence you may have. Just my thoughts but keep it up man. You rocking thus far

You will rock it anyway, I am sure

Now:

If you would have asked me to decide between Option A) ROG Rampage VI Extreme and Option B) ASUS Prime X299 Deluxe, I would definitely have chosen Option B) without any doubt. Option A) appears to me a kind of technological overkill, too many OSX incompatible components to be implemented, at the end too expensive (double price) for likely very small effective benefits.

But.... We will see what you do out of it

In any case, option A) is definitely not a board for uni- and multibeast and will require high intelligence and much of background and knowledge to entirely work... nothing to plug & play

Good luck, man

 

[kgp]

Can you tell me the output of this log search?

log show --predicate 'eventMessage CONTAINS "CPUSensors"' --last "24h"

Your prediction for a message about an official event with the presentation of the successful solution of the CPUSensors problem within the last 24 hours?

Seriously, I don't understand at all the context of the log search output provided above

 

[PedroJSkywalker]

Hello paulotex, I have passed several tests because as you say you would have to discard the hardware integration first and in that I am with the help of whatshisname who advised me to switch to sync all cores (I did not have it enabled because I have a disipiador of air specifically the Cooler Master MasterAir Maker 8).

I also activated following his advice the Speed Shift and AVX offset set the value 3, AVX512 and set this value to 4.

It has improved in the tests but when activating for example 8 tracks in Logic creaks.

I do not know if these values are as expected for this hardware.

The screenshots of iStat menus were made while running Cinebench in both the CPU and GPU tests.

 

[kgp]

This log search should produce a line like this (if you booted in the last 24h)
kernel: (kernel) CPUSensors: CPU family 0x6, model 0x55, stepping 0x4, cores 8, threads 16, TJmax 105

If the core number is already wrong in your log, I know where to look. If it is correct, I can look elsewhere. Depending where to look, I might be able to guess how much time it will take.

Alright!

Here you go !

Timestamp                       Thread     Type        Activity             PID    TTL
2017-12-01 06:54:14.568500+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: CPU family 0x6, model 0x55, stepping 0x4, cores 18, threads 36, TJmax 105
2017-12-01 06:54:14.587769+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: setting platform keys to [j45     ]
2017-12-01 06:54:14.596177+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-12-01 06:54:14.654819+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-12-01 06:54:14.655177+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: base CPU multiplier is 26
2017-12-01 06:54:14.663838+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-12-01 07:50:31.296577+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: CPU family 0x6, model 0x55, stepping 0x4, cores 18, threads 36, TJmax 105
2017-12-01 07:50:31.316300+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: setting platform keys to [j45     ]
2017-12-01 07:50:31.324943+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 09:31:22.520543+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: CPU family 0x6, model 0x55, stepping 0x4, cores 18, threads 36, TJmax 105
2017-11-30 09:31:22.520899+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: setting platform keys to [j45     ]
2017-11-30 09:31:22.528212+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 09:31:22.528379+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 09:31:22.528697+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: base CPU multiplier is 26
2017-11-30 09:31:22.529380+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 09:31:22.529655+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 09:31:22.530638+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 09:31:22.530936+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 09:31:22.537698+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: started
2017-11-30 12:40:51.244897+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: CPU family 0x6, model 0x55, stepping 0x4, cores 18, threads 36, TJmax 105
2017-11-30 12:40:51.245222+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: setting platform keys to [j45     ]
2017-11-30 12:40:51.253615+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 12:40:51.253796+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 12:40:51.255087+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: base CPU multiplier is 26
2017-11-30 12:40:51.255495+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 12:40:51.261432+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 12:40:51.262941+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 12:40:51.268828+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 12:40:51.270865+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: started
2017-11-30 15:20:55.986341+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: CPU family 0x6, model 0x55, stepping 0x4, cores 18, threads 36, TJmax 105
2017-11-30 15:20:55.986668+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: setting platform keys to [j45     ]
2017-11-30 15:20:55.994053+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 15:20:55.994234+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 15:20:55.994567+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: base CPU multiplier is 26
2017-11-30 15:20:55.995272+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 15:20:55.996500+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 15:20:55.996665+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 15:20:55.996950+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 15:20:56.004781+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: started
2017-11-30 18:48:02.820070+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: CPU family 0x6, model 0x55, stepping 0x4, cores 18, threads 36, TJmax 105
2017-11-30 18:48:02.837848+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: setting platform keys to [j45     ]
2017-11-30 18:48:02.846108+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 18:48:02.856039+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 22:08:15.188737+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: CPU family 0x6, model 0x55, stepping 0x4, cores 18, threads 36, TJmax 105
2017-11-30 22:08:15.189455+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: setting platform keys to [j45     ]
2017-11-30 22:08:15.196563+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 22:08:15.196735+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key TCAD handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 22:08:15.198009+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: base CPU multiplier is 26
2017-11-30 22:08:15.199336+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 22:08:15.206887+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 22:08:15.207203+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKeyStore: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 22:08:15.207484+0100 0x89       Default     0x0                  0      0    kernel: (kernel) FakeSMCKey: key MlC1 handler CPUSensors has been replaced with new prioritized handler CPUSensors
2017-11-30 22:08:15.213910+0100 0x89       Default     0x0                  0      0    kernel: (kernel) CPUSensors: started
--------------------------------------------------------------------------------------------------------------------
Log      - Default:         53, Info:                0, Debug:             0, Error:          0, Fault:          0
Activity - Create:           0, Transition:          0, Actions:           0

I guess you have to look elsewhere

As I already mentioned a few posts ago, I think the problem is the interface between your sensor data and and monitoring apps like HWmonitor or iStat, which makes me somewhat worried. HWMontor, which you might be able to adopt in some way, shows severe problems with the fan control. iStat shows better performance, but you might not have any access to apply interface related modifications.

You certainly know better where to screw at this place...

 

[kgp]

Important notification for @ALL Nvidia Users with respect to the recent macOS 10.13.1 Apple Security Updates

Note that there have been two macOS 10.13.1 Security Updates within 48 hours, which did not require any system reboot or further system modification.

Note however, that the former 10.13.1 Nvidia web driver is incompatible with new build 17B1003.

Thus, after one reboot of your updated system, you will find your system in the OS X Default Graphics Driver configuration.

In case that your Nvidia Web Driver Manager does not yet automatically find the updated web driver for build 17B1003 and thus does not perform the web driver update directly either, please manually download and install the updated WebDriver-378.10.10.10.20.109.pkg package.

Both Security Update and Web Driver Update work straight forward and absolutely flawless and do not require any additional changes or measurements on your system.

Cheers,

 

[oznem]

What about placing my EFI-Folder in the EFI-Partition of the disk you intent to boot?

Hello @kgp , it was not the case. I did what you suggested, but got the same hang. My EFI folder had nothing wrong with it, nor did the whole boot disk. It turned out to be just a Bios problem, the machine was simply NOT recognising the clover bootable partition. I had to reset to defaults (in the meantime I also upgraded to newest firmware version), than redo the setup of all specific bios parameters, and voilà, everything went in place again. Guess UEFI Bios is a little bit picky on my mobo...

thanks anyway.

OZ

 

[kgp]

Hello @kgp , it was not the case. I did what you suggested, but got the same hang. My EFI folder had nothing wrong with it, nor did the whole boot disk. It turned out to be just a Bios problem, the machine was simply NOT recognising the clover bootable partition. I had to reset to defaults (in the meantime I also upgraded to newest firmware version), than redo the setup of all specific bios parameters, and voilà, everything went in place again. Guess UEFI Bios is a little bit picky on my mobo...

thanks anyway.

OZ

No.. but it was the correct guess that your EFI partition did not work

Good that you found a solution for the issue anyway

 

[oznem]

No.. but it was the correct guess that your EFI partition did not work

Good that you found a solution for the issue anyway

Yep, glad you broke the 60K barrier!