Contribute
Register

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

Status
Not open for further replies.
But you still use HWMonitor instead of iStatmenus and I don't know if you use the Sensor kexts of @interference also as suggested..

How indeed, I hadn't noticed that your screenshots were of iStat Menu, it's displaying what it should now..
perfect thank you.

If I may suggest, telling someone "you're running HWMonitor rather than iStatmenus" is more constructive than "Again you don‘t do what I suggested to do! [..] If you refuse the information I provide I am not able to further help or support you, sorry.". But maybe that's just me...

The same likely states to your BIOS patching remarks, which are simply misleading for all other readers..
That's two people reporting the same thing... can't be a coincidence.

Anyhow, I'm happy with the outcome now.
 
How indeed, I hadn't noticed that your screenshots were of iStat Menu, it's displaying what it should now..
perfect thank you.

If I may suggest, telling someone "you're running HWMonitor rather than iStatmenus" is more constructive than "Again you don‘t do what I suggested to do! [..] If you refuse the information I provide I am not able to further help or support you, sorry.". But maybe that's just me...


That's two people reporting the same thing... can't be a coincidence.

Anyhow, I'm happy with the outcome now.

Do you really think there is any ambiguity in what I am proposing in post #5537?

Screen Shot 2018-02-23 at 10.46.51.png


If you suddenly come up with HWmonitor instead of iStatmenus 100 posts afterwards, it is not surprising that others also suddenly and immediately will follow your misleading example. That's why I have to immediately interfere when somebody distributes misleading indications, instructions, results or advises.

Believe me, after nearly 6000 posts I know that it is indeed deemed necessary to kill "fake news" at first instance. :lol:

Nothing for bad, man! :thumbup:;) let's keep on rocking..
 
Because you do not have a ASUS board! What the guide states is only valid for ASUS boards! So please do not state that the RDSMR value of the guide is wrong!

I actually see the same result where it show RDMSR e2 returns value 0x402 . I have asus prime deluxe. Only reason i think it's unlocked because i dont have any kernel panic without the the kernel kext patches and the power management shows 1 when I issued the command systl xpm something.

also my clover boot log has this:
MSR 0xE2 before patch 00000402
MSR 0xCE 00070C2C_F3012100 <---this number is different from the guide
MSR 0x1B0 00000000
 
Hi, @kgp @DSM2 i hope everything goes well my friends, on the contrary today i upgraded to 10.13.3 SA, i've installed the new NVIDIA drivers added the sensors kext and replacing fakesmc.
now sleep/wake does not work anymore :( ) and i have lost 1000points in Multi-Core score geekbenck4)
what could be the problem?
thanks.
 

Attachments

  • Schermata 2018-02-23 alle 11.59.06.png
    Schermata 2018-02-23 alle 11.59.06.png
    975.4 KB · Views: 155
I actually see the same result where it show RDMSR e2 returns value 0x402 . I have asus prime deluxe. Only reason i think it's unlocked because i dont have any kernel panic without the the kernel kext patches and the power management shows 1 when I issued the command systl xpm something.

also my clover boot log has this:
MSR 0xE2 before patch 00000402
MSR 0xCE 00070C2C_F3012100 <---this number is different from the guide
MSR 0x1B0 00000000

Well I really don't know what you guys are doing. Both @interferenc and me are getting exactly the same results after applying his actual patches, as outlined in my guide .
 
Hi, @kgp @DSM2 i hope everything goes well my friends, on the contrary today i upgraded to 10.13.3 SA, i've installed the new NVIDIA drivers added the sensors kext and replacing fakesmc.
now sleep/wake does not work anymore :( ) and i have lost 1000points in Multi-Core score geekbenck4)
what could be the problem?
thanks.

Hello my friend,

Don't worry too much about the Geekbench multi-core scores.. they vary a lot from test to test ..

Here sleep/wake still works fine, but I skipped the GPUSensor.kext. When implementing the latter, I witnessed black screen issues on wake. Note that the sensor kexts are still experimental.. if you have problems... remove them for now..

If you have problems with Web Dirver xxx.159 change to xxx106..

Good luck,

KGP
 
Hey @poshook, @oznem



That's kind of what I was seeing, I think I've got my head round what is going on my board, so in windows im all good now.





1. Indeed, that's what appears to be happening

2. I'm more than happy to help if I can, I've quite familiar with the ASrock BIOS now...lol
I've tried my hand at a few custom SSDTs with varying degrees of success. On the surface my power management looks good, benchmarks are what you'd expect for any given clock speed, even without an SSDT...

View attachment 290916


View attachment 290912
3. I've sorted things on the windows side now, which is good. We'll get there in the end! Again if I can help at all, more than happy to .
Please, can you share your SSDT & config.plist... I updated my computer with similar mobo. Thx a lot
At this moment, I was unable to load from clover :(
 
Hello my friend,

Don't worry too much about the Geekbench multi-core scores.. they vary a lot from test to test ..

Here sleep/wake still works fine, but I skipped the GPUSensor.kext. When implementing the latter, I witnessed black screen issues on wake. Note that the sensor kexts are still experimental.. if you have problems... remove them for now..

If you have problems with Web Dirver xxx.159 change to xxx106..

Good luck,
KGP
Thanks for the quickly reply, i have removed first the gpusensor and i've tried in a second moment to remove the other sensor kexts and replaced my old fakeSMC.After the Reboot now i have black screen issues on wake just like you said, forcing me to reboot.
Do you think can be the new Nvidia driver? if yes i try to install the 106 tonight.
otherwise I would not know what it could be..
thanks and good day @kgp

*** Panic Report ***
panic(cpu 0 caller 0xffffff800d76e349): Kernel trap at 0xffffff800d78c6b4, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x00000001027c2000, CR3: 0x00000000234cd000, CR4: 0x00000000003627e0
RAX: 0x000000007e008003, RBX: 0xffffff800de57320, RCX: 0x00000000000000e2, RDX: 0x0000000000000000
RSP: 0xffffff920b363bf0, RBP: 0xffffff920b363c20, RSI: 0x0000000000000003, RDI: 0xffffff800de572c0
R8: 0x0000000100000201, R9: 0x0000000000000000, R10: 0x0000000000000003, R11: 0xffffff800dd70eeb
R12: 0xffffff800dd78896, R13: 0x0000000000000001, R14: 0x0000000000000000, R15: 0xffffff800dd7887c
RFL: 0x0000000000010046, RIP: 0xffffff800d78c6b4, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00000001027c2000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 0

Backtrace (CPU 0), Frame : Return Address
0xfffffd000004c270 : 0xffffff800d64f606 mach_kernel : _handle_debugger_trap + 0x506
0xfffffd000004c2c0 : 0xffffff800d77c744 mach_kernel : _kdp_i386_trap + 0x114
0xfffffd000004c300 : 0xffffff800d76e159 mach_kernel : _kernel_trap + 0x5e9
0xfffffd000004c380 : 0xffffff800d601120 mach_kernel : _return_from_trap + 0xe0
0xfffffd000004c3a0 : 0xffffff800d64f03c mach_kernel : _panic_trap_to_debugger + 0x25c
0xfffffd000004c4d0 : 0xffffff800d64edbc mach_kernel : _panic + 0x5c
0xfffffd000004c530 : 0xffffff800d76e349 mach_kernel : _kernel_trap + 0x7d9
0xfffffd000004c6b0 : 0xffffff800d601120 mach_kernel : _return_from_trap + 0xe0
0xfffffd000004c6d0 : 0xffffff800d78c6b4 mach_kernel : _xcpm_perf_bias_set + 0x294
0xffffff920b363c20 : 0xffffff800d78c9be mach_kernel : _xcpm_init + 0xde
0xffffff920b363c60 : 0xffffff800d77ac91 mach_kernel : _acpi_sleep_kernel + 0x471
0xffffff920b363cd0 : 0xffffff7f9046bfb8 com.apple.driver.AppleACPIPlatform : __ZN23AppleACPIPlatformExpert13sleepPlatformEv + 0x1ee
0xffffff920b363d20 : 0xffffff7f90470415 com.apple.driver.AppleACPIPlatform : __ZN12AppleACPICPU7haltCPUEv + 0x75
0xffffff920b363d40 : 0xffffff800dcb03f8 mach_kernel : __Z16IOCPUSleepKernelv + 0x248
0xffffff920b363d90 : 0xffffff800dcdddd5 mach_kernel : __ZN14IOPMrootDomain15powerChangeDoneEm + 0x335
0xffffff920b363e00 : 0xffffff800dc7877b mach_kernel : __ZN9IOService8all_doneEv + 0x6fb
0xffffff920b363e50 : 0xffffff800dc75968 mach_kernel : __ZN9IOService23actionPMWorkQueueInvokeEP11IOPMRequestP13IOPMWorkQueue + 0x878
0xffffff920b363eb0 : 0xffffff800dc72993 mach_kernel : __ZN13IOPMWorkQueue17checkRequestQueueEP11queue_entryPb + 0x43
0xffffff920b363ef0 : 0xffffff800dc72822 mach_kernel : __ZN13IOPMWorkQueue12checkForWorkEv + 0x82
0xffffff920b363f30 : 0xffffff800dc8ef42 mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x1e2
0xffffff920b363f70 : 0xffffff800dc8e57c mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x2c
0xffffff920b363fa0 : 0xffffff800d6004f7 mach_kernel : _call_continuation + 0x17
Kernel Extensions in backtrace:
com.apple.driver.AppleACPIPlatform(6.1)[C03BFA43-0B1C-3065-BAD7-EAD7EE152F84]@0xffffff7f90460000->0xffffff7f904fbfff
dependency: com.apple.iokit.IOACPIFamily(1.4)[8794C760-FDD9-3664-ADED-4A9BBEC6E517]@0xffffff7f8eb68000
dependency: com.apple.iokit.IOPCIFamily(2.9)[194AA5A0-E772-3515-A771-6DC41FB9A361]@0xffffff7f8df34000
dependency: com.apple.driver.AppleSMC(3.1.9)[C0EDA8D1-B854-3BE7-A2AF-DF27F893962D]@0xffffff7f8eb71000
 
Last edited:
@stevelucky, @jaraheel :

Perhaps you can start without the full copy of KGP's CLOVER folder. I also don't have an Asus mobo (mine is MSI) and nonetheless the system is working fine.

For example, I suggest you start with a very simple kext/Other/ folder. Go for a vanilla FakeSMC from Rehabman (@stevelucky, you had a KP after loading the FakeSMC kext); make sure you use VoodooTSCSync (correctly configured with the # of cores - 1); remove other kexts.

@jaraheel: it seems you get a KP with the network kext. Are you trying to load an external ethernet kext? If yes, make sure you remove it.

I also suggest you start with a very plain config.plist. Unselect most of the things, don't add the patches that kgp has.

And finally, check the BIOS. You might have some setting there that does not show on the Asus or MSI or Gigabyte mobo and that might be causing the KP.

Just to make this clear: I don't think the distro here is wrong. But I suspect there is a tiny issue in your mobo that is making it impossible to use it as it is. So by going to a very bare-bones installation, and then slowly adding the different settings, you might be able to find out what could be the issue.

I find it hard to believe that there is a X299 mobo out there that does not work on a hackintosh, and that can't use this guide.

Good luck!

Thanks a ton for the diagnosis @paulotex. I disabled all the onboard Ethernets (and WiFi cards) and it booted right up! I have a USB WiFi adapter so I don’t care to use the onboard ones.

Thanks again, and thanks to you @kgp for the guide.
 
Last edited:

Attachments

  • BCM_Loloflat6_23_02_2018.png
    BCM_Loloflat6_23_02_2018.png
    1.1 MB · Views: 213
Status
Not open for further replies.
Back
Top