Contribute
Register

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

Status
Not open for further replies.
If you can also disable the xcpm_core_scope_msrs kernel patch, then yes..

View attachment 367417

Turns out MSR is not unlocked. Kernel Panics at random seed, then reboots.

I know I patched this though. UEFI Patcher > Original BIOS > XXX.CAP.patched
Screenshot 2018-11-23 at 21.10.05.png

When Flashing:

I inserted the USB in the flash port. reset CMOS, then Held in the bios button for about 5 seconds. Gave it 2 minutes and the light was still on (blue). Then booted and setup the BIOS. I left SpeedStep enabled though.

Curious/\/\ac
 
Turns out MSR is not unlocked. Kernel Panics at random seed, then reboots.

I know I patched this though. UEFI Patcher > Original BIOS > XXX.CAP.patched
View attachment 367423

When Flashing:

I inserted the USB in the flash port. reset CMOS, then Held in the bios button for about 5 seconds. Gave it 2 minutes and the light was still on (blue). Then booted and setup the BIOS. I left SpeedStep enabled though.

Curious/\/\ac

Maybe your stick was in the wrong USB port. Usually you need to press the flashback button for 3 sec. As soon you release it, it starts blinking. During the firmware flashing it will continue blinking. As soon the flashing is finished the blue led will turn off. Never the blue led should turn solid or continuous.

You know that in order to properly flash the patched firmware you need to rename the file by following the EZ flashback filename convention for your mainboard? E.g. for the ASUS X99-A II it is X99A2.CAP! You have to google to find the proper EZ flashback filename convention for your mainbaord. Without the proper filename, the firware will be ignored by EZ Flashback!
 
Last edited:
I updated my fully functioning 10.13.6 rig to 10.14.1 without realizing that the web drivers weren't out yet. I have a Nvidia 1060 6GB. The fix you listed on the guide has a broken link. Do you still know of a way to patch it and if not should I just go back to 10.13.6?
 
I updated my fully functioning 10.13.6 rig to 10.14.1 without realizing that the web drivers weren't out yet. I have a Nvidia 1060 6GB. The fix you listed on the guide has a broken link. Do you still know of a way to patch it and if not should I just go back to 10.13.6?

The link is not broken. You must be logged in to Insanelymac to download the file.

Anyway.. forget about patching the web driver for 10.14.. you won’t be happy with the result.

Stay away from 10.14 if you want to keep your Nvidia GPU or change to Vega.
 
Maybe your stick was in the wrong USB port. Usually you need to press the flashback button for 3 sec. As soon you release it, it starts blinking. During the firmware flashing it will continue blinking. As soon the flashing is finished the blue led will turn off. Never the blue led should turn solid or continuous.

You know that in order to properly flash the patched firmware you need to rename the file by following the EZ flashback filename convention for your mainboard? E.g. for the ASUS X99-A II it is X99A2.CAP! You have to google to find the proper EZ flashback filename convention for your mainbaord. Without the proper filename, the firware will be ignored by EZ Flashback!

Okay so after some research and gathering info on how Asus bioses work. I found that using a 3.0 USB and having a GUID partition will not allow the bios to update.

Although when using a 2.0 USB with no GUID partition and having formatted the USB to FAT32 having it on diskXs1 instead of diskXs2.

As of now, I can say my MSR is fully unlocked and my bios has been updated with the patch as I booted up using the following:
Screenshot 2018-11-24 at 01.34.55.png Screenshot 2018-11-24 at 01.35.26.png Screenshot 2018-11-24 at 01.35.30.png


Curious/\/\ac
 
Okay so after some research and gathering info on how Asus bioses work. I found that using a 3.0 USB and having a GUID partition will not allow the bios to update.

Although when using a 2.0 USB with no GUID partition and having formatted the USB to FAT32 having it on diskXs1 instead of diskXs2.

As of now, I can say my MSR is fully unlocked and my bios has been updated with the patch as I booted up using the following:
View attachment 367543 View attachment 367542 View attachment 367541


Curious/\/\ac

Now you still have to update the microcodes within the firmware.

BTW.. you can disable boot flag -xcpm, which is obsolete for more than one year.

Also ssdt.aml is obsolete for xcpm, as we now enable plugintype in config.plist in section ACPI of Clover Configurator!

You should also use npci=0x2000 instead of 0x3000! My EFI-folder works as previously implemented. Nothing needs to be changed.

For darkwake you should use darkwake=0. I did not send you the new EFI-Folder just for fun, my friend.
 
I did not send you the new EFI-Folder just for fun, my friend.

True, I have a habit of tinkering with things I don't fully understand I have your config.plist as the main and have backups for testing purposes.

Going to use your 1 as the main now. Do I Disable the kernel patches ?

Curious/\/\ac
 
True, I have a habit of tinkering with things I don't fully understand I have your config.plist as the main and have backups for testing purposes.

Going to use your 1 as the main now. Do I Disable the kernel patches ?

Curious/\/\ac

No... you will need all 4 remaining kernel patches, wich are still enabled. Do not further touch the actual xcpm configuration. It should work as expected as soon you reflashed your mainboard with the the patched firmware (unlocked MSR) that should also contain the microcode updates.
 
No... you will need all 4 remaining kernel patches, wich are still enabled. Do not further touch the actual xcpm configuration. It should work as expected as soon you reflashed your mainboard with the the patched firmware (unlocked MSR) that should also contain the microcode updates.

Booted 100% with your specified config.plist and left the remaining 4 kernel patches untouched.

Unfortunately I cannot do the microcode update as I have not installed windows yet. I will be downloading and installing it shortly. Will reply back when the microcode has been updated.

Current CPU stats:
  • Still locked in at 1.19Ghz
  • 0.68 watt cpu usage on load and idle.
Sleep:
  • Currently testing
EDIT : Sleep is working


Curious/\/\ac
 
Last edited:
Booted 100% with your specified config.plist and left the remaining 4 kernel patches untouched.

Unfortunately I cannot do the microcode update as I have not installed windows yet. I will be downloading and installing it shortly. Will reply back when the microcode has been updated.

Current CPU stats:
  • Still locked in at 1.19Ghz
  • 0.68 watt cpu usage on load and idle.
Sleep:
  • Currently testing

Curious/\/\ac

For sleep you still have to adopt and implement my system ssdts.
 
Status
Not open for further replies.
Back
Top