Contribute
Register

iMac Pro X99 - Live the Future now with macOS 10.14 Mojave [Successful Build/Extended Guide]

Status
Not open for further replies.
According to your guide for creation of a kext like KGP-ASUS-X99-A-II-iMacPro-XHCI-15port.kext, shouldn't the port-count value be modified to 0e000000 instead of the value you have of 16000000? Apparently it still works with an incorrect value. Perhaps this value is more of a comment than a number used by the system.

The port-count refers to the highest implemented SS-port hex number, which is still 16000000 (SSP6).
 
macOS Mojave 10.14.2 Beta 2 (18C38b)

Screenshot 2018-11-08 at 12.27.15.png


Code:
macOS: 10.14.2
Build: 18C38b
_xcpm performance_patch @PMHeart
Find: C1E3084863D389D048C1EA20B9990100000F3048FF05B37076004883C4085B5DC30F1F4000
Repl: B800FF00004863D389D048C1EA20B9990100000F3048FF05B37076004883C4085B5DC39090


Screenshot 2018-11-08 at 12.33.37.png


Screenshot 2018-11-08 at 12.34.28.png


Screenshot 2018-11-08 at 12.37.51.png


Screenshot 2018-11-08 at 12.38.11.png


Enjoy and have fun,

kgp.png
 
Last edited:
My friends,

From today, I will be on holidays and hardly able to connect for some days.

Enjoy, have fun and thanks for your patience,

kgp.png
 
Hi @kgp !! I have seen you finally fixed OC problem in 10.13.6 and mojave with bios patching :)
Just one question, the X99A2.CAP.zip you provided in your files is already patched to have all cpu microcodes enabled? Or it just has the MSR 0xE2 register unlocked? I need it and I dont have w10 installed to patch CPU microcode :)
Thanks a lot!
 
Hi @kgp !! I have seen you finally fixed OC problem in 10.13.6 and mojave with bios patching :)
Just one question, the X99A2.CAP.zip you provided in your files is already patched to have all cpu microcodes enabled? Or it just has the MSR 0xE2 register unlocked? I need it and I dont have w10 installed to patch CPU microcode :)
Thanks a lot!

Contains both patch and Microde update.
 
Hi,
first of all thanks for the detailed guide. I am really close to having a fully working Hackintosh.
However, the power management has always been an issue for me. I have an ASUS X99-A/USB3.1 with a Xeon E5-2658v3 ES.
I first hoped it would just work with your BIOS settings and the configured Clover folder. I enabled the necessary patches but when booting I get a lot of errors looking like this:
Code:
kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - CP00 APSS and _PSS evaluations failed!
2018-11-10 13:46:37.638449+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - CP00 APSS and _PSS evaluations failed!
2018-11-10 13:46:37.638607+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray
2018-11-10 13:46:37.638609+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray
2018-11-10 13:46:37.650257+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::publishACPIStates - Failed to get CPU P States!
2018-11-10 13:46:37.650259+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::publishACPIStates - Failed to get CPU P States!
2018-11-10 13:46:37.650531+0100 0x50c      Default     0x0                  0      0    kernel: DSMOS has arrived
2018-11-10 13:46:37.655941+0100 0x50c      Default     0x0                  0      0    kernel: (pmtelemetry) Unsupported CPU
2018-11-10 13:46:37.663771+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::publishACPIStates - Failed to get max non-turbo PState. Set max non-turbo PState to default value 1
2018-11-10 13:46:37.663774+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::publishACPIStates - Failed to get max non-turbo PState. Set max non-turbo PState to default value 1
2018-11-10 13:46:37.664628+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - CP01 APSS and _PSS evaluations failed!
2018-11-10 13:46:37.664630+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - CP01 APSS and _PSS evaluations failed!
2018-11-10 13:46:37.675598+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray
2018-11-10 13:46:37.675599+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray
2018-11-10 13:46:37.675880+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::publishACPIStates - Failed to get CPU P States!
2018-11-10 13:46:37.675882+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::publishACPIStates - Failed to get CPU P States!
2018-11-10 13:46:37.676756+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - CP02 APSS and _PSS evaluations failed!
2018-11-10 13:46:37.676758+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - CP02 APSS and _PSS evaluations failed!
2018-11-10 13:46:37.677032+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray
2018-11-10 13:46:37.677033+0100 0x50f      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformPlugin::getCPUPStates - acpiPSArrayObj is not an valid OSArray

I also tried generating a SSDT for my cpu which resulted in this:

Code:
kernel: (IOPlatformPluginFamily) X86PlatformShim::sendPStates - Success!
2018-11-10 11:03:52.354379+0100 0x53b      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformShim::sendPStates - Success!
2018-11-10 11:03:52.354662+0100 0x53b      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformShim::sendPStates - Success!
2018-11-10 11:03:52.354664+0100 0x53b      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformShim::sendPStates - Success!
2018-11-10 11:03:52.355229+0100 0x53b      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformShim::sendStepper - Stepper dictionary from plist is NULL!
2018-11-10 11:03:52.355231+0100 0x53b      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformShim::sendStepper - Stepper dictionary from plist is NULL!
2018-11-10 11:03:52.367265+0100 0x53b      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformShim::start - Failed to send stepper
2018-11-10 11:03:52.367267+0100 0x53b      Default     0x0                  0      0    kernel: (IOPlatformPluginFamily) X86PlatformShim::start - Failed to send stepper
This is also what I get with no SSDT and just by enabling EIST. Then however my constant CPU clock goes from 2.3GHz down to 2GHz. You can find my clover folder in the attachments.

I Hope someone can help me
 

Attachments

  • EFI.zip
    18.2 MB · Views: 81
Contains both patch and Microde update.
Great!! I will update to 10.13.6 today. I have to wait until nvidia release mojave drivers to update to 10.14. Im using the efi folder you uploaded when you updated the guide to 10.13.5, some months ago. I think that I can keep that efi folder in 10.13.6 instead of downloading your most updated efi folder (mojave one). But, maybe I can update some kext like lilu, whatevergreeb, ALC, and so. Do you have the 10.13.6 efi folder in your hard drive to upload it again? Or is not neccesary?

Thank you and sorry if I disturb you on your holidays.

EDIT: I've found your github repository!! this is new for me in your guide, thank you again! :)
 
Last edited:
I everything would be fine your CPU would not constantly clock at 1,2 GHz...

Note that the performance kernel patch actually seems not correctly working under 10.14 PB1.. Thus, no OC.. However your CPU definitely should exceed 1.2Ghz.
I also experienced the same thing. My CPU clock is 1.2GHz. I checked my BIOS setting. Enhanced intel speed step technology was enabled. My CPU clock works properly after I disabled Enhanced intel speed step technology in the Bios setting.
Would you try?
 
@kgp I noticed that "E.10) System Overview CPU Cosmetics" was removed from this guide as it was included in your High Sierra. I can confirm that the method does not work anymore as I am using 10.4.1 with Rampage V Edition 10

Screenshot 2018-11-13 at 09.21.25.png
 
@kgp I noticed that "E.10) System Overview CPU Cosmetics" was removed from this guide as it was included in your High Sierra. I can confirm that the method does not work anymore as I am using 10.4.1 with Rampage V Edition 10

View attachment 365164

That's why the method is not anymore part of my 10.14 guides.

Note that I currently use CPU Type entry "0x0F01" instead, which is now hardwired in the config.plist of my actual 10.14 EFI-Folder distributions.

Screenshot 2018-11-13 at 09.52.13.png
 
Status
Not open for further replies.
Back
Top