autantpourmoi Posted January 14, 2019 Share Posted January 14, 2019 Hi KGP , I'm the oner of a X99 hackintosch with a Gigabyte X99 UD4 mainboard and a I7. 5930K proc I followed your guide line by line and I didn't went so far with my newbie knowledge I was able to do the CPU microcode update the bios F24b ( thanks to your very good explanation). I followed the MSR 0xE2 register unlock for OSX Kernel Write but it didn't patch anything ( I read somewhere else that maybe my mainboard doesn't need that , can you confirm ?) Then I rename the bios exactly like it was before but I ended with an unreadable bios when I'm trying to flash it . Do you know what is wrong ? So you see I still have a long path to follow to get a proper hackintosch running under Mojave Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2658976 Share on other sites More sharing options...
kgp Posted January 14, 2019 Author Share Posted January 14, 2019 (edited) 36 minutes ago, autantpourmoi said: Hi KGP , I'm the oner of a X99 hackintosch with a Gigabyte X99 UD4 mainboard and a I7. 5930K proc I followed your guide line by line and I didn't went so far with my newbie knowledge I was able to do the CPU microcode update the bios F24b ( thanks to your very good explanation). I followed the MSR 0xE2 register unlock for OSX Kernel Write but it didn't patch anything ( I read somewhere else that maybe my mainboard doesn't need that , can you confirm ?) Then I rename the bios exactly like it was before but I ended with an unreadable bios when I'm trying to flash it . Do you know what is wrong ? So you see I still have a long path to follow to get a proper hackintosch running under Mojave MSR register on GA motherboards is open for kernel write. No need to patch the BIOS firmware. Just do the microcode update, if necessary. Maybe somebody else can explain you how to properly flash the modified GA firmware. I do only use ASUS motherboard hardware. Good luck, KGP Edited January 14, 2019 by KGP-iMacPro Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2658988 Share on other sites More sharing options...
autantpourmoi Posted January 14, 2019 Share Posted January 14, 2019 ok thanks for your reactivity . I'll look for someone used to Gigabyte firmware thanks Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2658997 Share on other sites More sharing options...
Mystroe Posted January 23, 2019 Share Posted January 23, 2019 Thank you KGP for probably the most comprehensive and consolidated X99 guide. I am just getting prepared. Should C.4.e. be TSCAdjustRest instead of VoodooTSCSync ? Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2660849 Share on other sites More sharing options...
Mystroe Posted January 25, 2019 Share Posted January 25, 2019 Thanks again to KGP for a superb guide. I successfully and painlessly, and quite quickly installed Mojave following KGP's steps. However because of the present NVIDIA limitations on Mojave I'm now going to try KGP's High Sierra install instead. 1 Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2661216 Share on other sites More sharing options...
kgp Posted January 25, 2019 Author Share Posted January 25, 2019 15 minutes ago, Mystroe said: Thanks again to KGP for a superb guide. I successfully and painlessly, and quite quickly installed Mojave following KGP's steps. However because of the present NVIDIA limitations on Mojave I'm now going to try KGP's High Sierra install instead. To avoid future problems with Nvidia, which you will encounter for sure again along the upcoming 10.15 betas, I would directly change to Vega 56 or 64 instead Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2661218 Share on other sites More sharing options...
kgp Posted January 25, 2019 Author Share Posted January 25, 2019 macOS Mojave 10.14.4 beta1 (18E174f) Important Note: to properly load respective kexts under 10.14.4 beta1 during boot, Clover_v2.4k_r4862 is deemed necessary. @Slice recently committed respective modifications of kext_inject.c introduced by @PMheart . 10.14.4 Beta1 XCPM_performance patch by @PMHeart: Find : C1E30848 63D389D0 48C1EA20 B9990100 000F3048 FF05926E 76004883 C4085B5D C30F1F00 Replace: B800FF00 004863D3 89D048C1 EA20B999 0100000F 3048FF05 926E7600 4883C408 5B5DC390 Enjoy and have fun, Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2661227 Share on other sites More sharing options...
kgp Posted January 25, 2019 Author Share Posted January 25, 2019 Working USB port limit patches for 10.14.3 and 10.14.4 Beta1 Thanks to @ydeng, there are now working USB port limit patches for 10.14.3 kext : com.apple.iokit.IOUSBHostFamily Find : 83FB0F0F 871604 00 Replace : 83FB3F0F 871604 00 Name : USB Port Limit Patch 1 ©ydeng kext : com.apple.driver.usb.AppleUSBXHCI Find : 83FB0F0F 838F0400 00 Replace : 83FB3F0F 838F0400 00 Name : USB Port Limit Patch 2 ©ydeng kext : com.apple.iokit.IOUSBHostFamily Find : 83E30FD3 E34109DF Replace : 83E33FD3 E34109DF Name : USB Port Limit Patch 3 ©ydeng And here are the respective USB port limit patches for 10.14.4 Beta1 provided by @PMHeart kext : com.apple.iokit.IOUSBHostFamily Find : 83FB0F0F 870B0400 00 Replace : 83FB3F0F 870B0400 00 Name : USB Port Limit Patch 1 ©PMHeart kext : com.apple.driver.usb.AppleUSBXHCI Find : 4183FF0F 0F839404 0000 Replace : 4183FF3F 0F839404 0000 Name : USB Port Limit Patch 2 ©PMHeart kext : com.apple.iokit.IOUSBHostFamily Find : 83E30FD3 E34109DF Replace : 83E33FD3 E34109DF Name : USB Port Limit Patch 3 ©PMHeart The port limit patches should be used in line with the fully implemented XHC USB kexts. However, it is still recommended to disable the port limit patches and use truncated 15-port kexts instead. This might avoid buffer overruns and will make your system more vanilla with respect to future macOS updates. Enjoy and have fun, Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2661240 Share on other sites More sharing options...
susiklaus2011 Posted January 30, 2019 Share Posted January 30, 2019 (edited) Hi, thanks for your good Guide in Case of 10.14.3, with any of the Infos now have run the correct XCPM without any Errors after a longer Time in Idle State, before it was that my system stand to more than 50% still no Alan , no Clock (not count away) at 12:00 AM the time call 07:42 and any Parts of my system was run and I was able to restart the system. my System is a Asus Rampage V Extreme i7 5820K 4x4GB ( Quad) , a Samsung 960 Pro 512 as the SystemDisc, a Nvidia GTX 670 2GB and a GTX 970 4GB but in your Tutorial you have NVDAStartup.WEB.kext in /L/E after install the patched Web-Driver. I search in /S/L/E and I found a NVDAStartup.kext and I do the same as what says the Tutorial but in all cases I can not found a NVDAStartup.web.kext, what is here wrong I don't understand, in my Sierra 10.12.6 in L/E/ I found this one not so in my Mojave 10.14.3 (18D42), I'm wondering that you have 18D45 what is here different ? My Update is a German Update . In Case with Apple and Nvidia I found a Petition on change .org, Petition Mac OS 10.14 Apple does Nvidia not allow to make a Webdriver for Nvidia Products and we all help Apple to be a big Player and all Users have a chance to give Apple "Pressure" to work together with Nvidia to make Driver for Mojave. Please help me a little bit to understand what is wrong with my patched NVDA-Webdriver. My USB ports are all injected now and the Kext,.*ioreg and DSDT are here: PS my Bios is a patched 3901. MacPro6.1-ASUS-R5E-XHCI.kext.zip MacPro6.1 .ioreg.zip DSDT.aml.zip Edited January 30, 2019 by susiklaus2011 insert DSDT Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2661995 Share on other sites More sharing options...
kgp Posted January 30, 2019 Author Share Posted January 30, 2019 (edited) 10 minutes ago, susiklaus2011 said: Hi, thanks for your good Guide in Case of 10.14.3, with any of the Infos now have run the correct XCPM without any Errors after a longer Time in Idle State, before it was that my system stand to more than 50% still no Alan , no Clock (not count away) at 12:00 AM the time call 07:42 and any Parts of my system was run and I was able to restart the system. my System is a Asus Rampage V Extreme i7 5820K 4x4GB ( Quad) , a Samsung 960 Pro 512 as the SystemDisc, a Nvidia GTX 670 2GB and a GTX 970 4GB but in your Tutorial you have NVDAStartup.WEB.kext in /L/E after install the patched Web-Driver. I search in /S/L/E and I found a NVDAStartup.kext and I do the same as what says the Tutorial but in all cases I can not found a NVDAStartup.web.kext, what is here wrong I don't understand, in my Sierra 10.12.6 in L/E/ I found this one not so in my Mojave 10.14.3 (18D42), I'm wondering that you have 18D45 what is here different ? My Update is a German Update . In Case with Apple and Nvidia I found a Petition on change .org, Petition Mac OS 10.14 Apple does Nvidia not allow to make a Webdriver for Nvidia Products and we all help Apple to be a big Player and all Users have a chance to give Apple "Pressure" to work together with Nvidia to make Driver for Mojave. Please help me a little bit to understand what is wrong with my patched NVDA-Webdriver. My USB ports are all injected now and the Kext,.*ioreg and DSDT are here: PS my Bios is a patched 3901. MacPro6.1-ASUS-R5E-XHCI.kext.zip MacPro6.1 .ioreg.zip DSDT.aml.zip Forget about patching the 10.13.6 web driver for 10.14 anyway. Your Nvidia GPU still will be useless under 10.14. I highly recommend to change to a Vega 56 or 64 instead. BTW.. please try to create fully implemented and truncated XHC USB kexts for your motherboard by exactly following my respective guidelines! Your current kext attached above is largely inadequate and cannot be added such to my XHC USB kext Github library. Good luck, my friend! KGP Edited January 30, 2019 by KGP-iMacPro Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2661998 Share on other sites More sharing options...
NeXtor Posted February 1, 2019 Share Posted February 1, 2019 Hi, I have updated the bios first following this guide and then the system from 10.13.6 to 10.14.3. The pc starts and I think it recognizes all the peripherals but I have doubts about the xcpm since the AppleIntelInfo.kext log is very short and also for some errors at boot like Unsynchronized TSC for cpu ... I attach Ioreg, DarwinDumper log, EFI folder and AppleIntelInfo log Thanks for your help. https://ufile.io/nc9jg Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662307 Share on other sites More sharing options...
kgp Posted February 1, 2019 Author Share Posted February 1, 2019 2 hours ago, NeXtor said: Hi, I have updated the bios first following this guide and then the system from 10.13.6 to 10.14.3. The pc starts and I think it recognizes all the peripherals but I have doubts about the xcpm since the AppleIntelInfo.kext log is very short and also for some errors at boot like Unsynchronized TSC for cpu ... I attach Ioreg, DarwinDumper log, EFI folder and AppleIntelInfo log Thanks for your help. https://ufile.io/nc9jg Did you implement a properly adopted TSCAdjustReset.kext to your EFI-Folder by following my guidelines? Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662325 Share on other sites More sharing options...
NeXtor Posted February 1, 2019 Share Posted February 1, 2019 43 minutes ago, KGP-iMacPro said: Did you implement a properly adopted TSCAdjustReset.kext to your EFI-Folder by following my guidelines? I think so as you can see from the efi folder from the link. I followed step 4 of the guide and I modified the info.plist by setting IOCPUNumber to 11 because the cpu i7-5820k has 6 cores and then 12 threads (IOCPUNumber = threads - 1 = 11). I also tried to leave the old VoodooTSCSync file that I used before the update but the errors do not disappear Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662332 Share on other sites More sharing options...
kgp Posted February 1, 2019 Author Share Posted February 1, 2019 17 minutes ago, NeXtor said: I think so as you can see from the efi folder from the link. I followed step 4 of the guide and I modified the info.plist by setting IOCPUNumber to 11 because the cpu i7-5820k has 6 cores and then 12 threads (IOCPUNumber = threads - 1 = 11). I also tried to leave the old VoodooTSCSync file that I used before the update but the errors do not disappear Download and implement THIS EFI-Folder and your system should boot properly. Subsequently perform entire post installation outlined in Section E.). If you still witness boot issues check once more your BIOS settings. The EFI-Folder now should be MacOS 10.14 build independent. The EFI-Folder assumes that you patched your BIOS firmware and unlocked your MSR register for Kernel write. If the MSR register is still locked, check KernelPM and enable _xcpm_core_scope_msrs © Pike R. Alpha kernel patch in config.plist. For OC, you also need to apply the CPU microcode update to your firmware as outlined and described in my guide. Your GTX 780Ti is Kepler? In the latter case it will be natively supported by Mojave, but you might want to change to Vega 56 for 64 anyway when ever possible. Good luck, KGP Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662335 Share on other sites More sharing options...
NeXtor Posted February 2, 2019 Share Posted February 2, 2019 (edited) 2 hours ago, KGP-iMacPro said: Download and implement THIS EFI-Folder and your system should boot properly. Subsequently perform entire post installation outlined in Section E.). If you still witness boot issues check once more your BIOS settings. The EFI-Folder now should be MacOS 10.14 build independent. The EFI-Folder assumes that you patched your BIOS firmware and unlocked your MSR register for Kernel write. If the MSR register is still locked, check KernelPM and enable _xcpm_core_scope_msrs © Pike R. Alpha kernel patch in config.plist. For OC, you also need to apply the CPU microcode update to your firmware as outlined and described in my guide. Your GTX 780Ti is Kepler? In the latter case it will be natively supported by Mojave, but you might want to change to Vega 56 for 64 anyway when ever possible. Good luck, KGP Before moving to mojave I downloaded the last bios, updated CPU microcode and patched msr following the whole point B.1) Asus Mainboard BIOS Firmware Patching and B.2) Asus X99-A II BIOS Configuration but I enabled EIST and I deactivated 4G Decoding otherwise the system did not recognize the usb. Now I did as you told me but I still have Unsynchronized TSC for CPU 2 and Unsynchronized TSC for CPU 4 and now the CPU is not recognized. I replaced the whole efi folder and followed point E.1) XNU CPU Power Management (XCPM) Configuration with the following bios settings: Advanced\CPU Configuration\CPU Power Management Configuration\ Enhanced Intel SpeedStep Technology (EIST): Enabled Turbo mode: Enabled CPU C-State: Enabled Enhanced C1 State: Enabled CPU C3 Report: Enabled CPU C6 Report: Enabled Package C State Limit: C6(non Retention) state These are the clover settings for KernelToPatch and KextToPatch and the appleintelinfo log _xcpm_ performance_patch 10.14.2 © Pike R. Alpha C1E30848 63D389D0 48C1EA20 B9990100 000F3048 FF05C372 76004883 C4085B5D C30F1F40 00 with B800FF00 004863D3 89D048C1 EA20B999 0100000F 3048FF05 C3727600 4883C408 5B5DC390 90 EIST Performance fix by @PMheart for 10.14.2 by N.Mano C1E30848 63D389D0 48C1EA20 B9990100 000F3048 FF052383 76004883 C4085B5D C30F1F40 00 with BB00FF00 004863D3 89D048C1 EA20B999 0100000F 3048FF05 93AE7600 4883C408 5B5DC390 90 XCPM Perfo rmance fix by @PMheart Fixed 10.14.4 Beta 1 By N.Mano C1E30848 63D389D0 48C1EA20 B9990100 000F3048 FF05926E 76004883 C4085B5D C30F1F00 with BB00FF00 004863D3 89D048C1 EA20B999 0100000F 3048FF05 93AE7600 4883C408 5B5DC390 SammlerG Sierra xcpm MSR Patch 3 / xcpm support Pike R. Alpha/0x82D390/MSR_PP0_POLICY 0x63a 3A060000 DC330000 00000000 00000000 1F with 3A060000 00000000 00000000 00000000 00 Pike R. Alpha xcpm MSR Patch 4 42060000 DC330000 00000000 00000000 1F000000 00000000 18000000 00000000 00000000 00000000 00000000 00000000 with 42060000 00000000 00000000 00000000 1F000000 00000000 18000000 00000000 00000000 00000000 00000000 00000000 AppleIntelInfo.kext v2.9 Copyright © 2012-2017 Pike R. Alpha. All rights reserved. Settings: ------------------------------------------ logMSRs..................................: 1 logIGPU..................................: 0 logCStates...............................: 1 logIPGStyle..............................: 1 InitialTSC...............................: 0x4dd82e9df586 (2593 MHz) MWAIT C-States...........................: 8480 Processor Brandstring....................: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz Processor Signature..................... : 0x306F2 ------------------------------------------ - Family............................... : 6 - Stepping............................. : 2 - Model................................ : 0x3F (63) Model Specific Registers (MSRs) ------------------------------------------ MSR_IA32_PLATFORM_ID.............(0x17) : 0x8000000000000 ------------------------------------------ - Processor Flags...................... : 2 MSR_CORE_THREAD_COUNT............(0x35) : 0x6000C ------------------------------------------ - Core Count........................... : 6 - Thread Count......................... : 12 MSR_PLATFORM_INFO................(0xCE) : 0x20080C3BF3812100 ------------------------------------------ - Maximum Non-Turbo Ratio.............. : 0x21 (3300 MHz) - Ratio Limit for Turbo Mode........... : 1 (programmable) - TDP Limit for Turbo Mode............. : 1 (programmable) - Low Power Mode Support............... : 1 (LPM supported) - Number of ConfigTDP Levels........... : 1 (additional TDP level(s) available) - Maximum Efficiency Ratio............. : 12 - Minimum Operating Ratio.............. : 8 MSR_PMG_CST_CONFIG_CONTROL.......(0xE2) : 0x1E000005 ------------------------------------------ - I/O MWAIT Redirection Enable......... : 0 (not enabled) - CFG Lock............................. : 0 (MSR not locked) - C3 State Auto Demotion............... : 1 (enabled) - C1 State Auto Demotion............... : 1 (enabled) - C3 State Undemotion.................. : 1 (enabled) - C1 State Undemotion.................. : 1 (enabled) - Package C-State Auto Demotion........ : 0 (disabled/unsupported) - Package C-State Undemotion........... : 0 (disabled/unsupported) MSR_PMG_IO_CAPTURE_BASE..........(0xE4) : 0x10414 ------------------------------------------ - LVL_2 Base Address................... : 0x414 - C-state Range........................ : 1 (C-States not included, I/O MWAIT redirection not enabled) IA32_MPERF.......................(0xE7) : 0x58F6725D19 IA32_APERF.......................(0xE8) : 0x644D9B78A6 MSR_FLEX_RATIO...................(0x194) : 0xE0000 ------------------------------------------ MSR_IA32_PERF_STATUS.............(0x198) : 0x285B00002A00 ------------------------------------------ - Current Performance State Value...... : 0x2A00 (4200 MHz) MSR_IA32_PERF_CONTROL............(0x199) : 0x2A00 ------------------------------------------ - Target performance State Value....... : 0x2A00 (4200 MHz) - Intel Dynamic Acceleration........... : 0 (IDA engaged) IA32_CLOCK_MODULATION............(0x19A) : 0x0 IA32_THERM_INTERRUPT.............(0x19B) : 0x0 IA32_THERM_STATUS................(0x19C) : 0x88390000 ------------------------------------------ - Thermal Status....................... : 0 - Thermal Log.......................... : 0 - PROCHOT # or FORCEPR# event.......... : 0 - PROCHOT # or FORCEPR# log............ : 0 - Critical Temperature Status.......... : 0 - Critical Temperature log............. : 0 - Thermal Threshold #1 Status.......... : 0 - Thermal Threshold #1 log............. : 0 - Thermal Threshold #2 Status.......... : 0 - Thermal Threshold #2 log............. : 0 - Power Limitation Status.............. : 0 - Power Limitation log................. : 0 - Current Limit Status................. : 0 - Current Limit log.................... : 0 - Cross Domain Limit Status............ : 0 - Cross Domain Limit log............... : 0 - Digital Readout...................... : 57 - Resolution in Degrees Celsius........ : 1 - Reading Valid........................ : 1 (valid) MSR_THERM2_CTL...................(0x19D) : 0x0 IA32_MISC_ENABLES................(0x1A0) : 0x850089 ------------------------------------------ - Fast-Strings......................... : 1 (enabled) - FOPCODE compatibility mode Enable.... : 0 - Automatic Thermal Control Circuit.... : 1 (enabled) - Split-lock Disable................... : 0 - Performance Monitoring............... : 1 (available) - Bus Lock On Cache Line Splits Disable : 0 - Hardware prefetch Disable............ : 0 - Processor Event Based Sampling....... : 0 (PEBS supported) - GV1/2 legacy Enable.................. : 0 - Enhanced Intel SpeedStep Technology.. : 1 (enabled) - MONITOR FSM.......................... : 1 (MONITOR/MWAIT supported) - Adjacent sector prefetch Disable..... : 0 - CFG Lock............................. : 0 (MSR not locked) - xTPR Message Disable................. : 1 (disabled) MSR_TEMPERATURE_TARGET...........(0x1A2) : 0x690A00 ------------------------------------------ - Turbo Attenuation Units.............. : 0 - Temperature Target................... : 105 - TCC Activation Offset................ : 0 MSR_MISC_PWR_MGMT................(0x1AA) : 0x400000 ------------------------------------------ - EIST Hardware Coordination........... : 0 (hardware coordination enabled) - Energy/Performance Bias support...... : 1 - Energy/Performance Bias.............. : 0 (disabled/MSR not visible to software) - Thermal Interrupt Coordination Enable : 1 (thermal interrupt routed to all cores) - SpeedShift Technology Enable......... : 0 (disabled) - SpeedShift Interrupt Coordination.... : 0 (disabled) - SpeedShift Energy Efficient Perf..... : 0 (disabled) - SpeedShift Technology Setup for HWP.. : No (not setup for HWP) MSR_TURBO_RATIO_LIMIT............(0x1AD) : 0x22222A2A2A2A2A2A ------------------------------------------ - Maximum Ratio Limit for C01.......... : 2A (4200 MHz) - Maximum Ratio Limit for C02.......... : 2A (4200 MHz) - Maximum Ratio Limit for C03.......... : 2A (4200 MHz) - Maximum Ratio Limit for C04.......... : 2A (4200 MHz) - Maximum Ratio Limit for C05.......... : 2A (4200 MHz) - Maximum Ratio Limit for C06.......... : 2A (4200 MHz) IA32_ENERGY_PERF_BIAS............(0x1B0) : 0x1 ------------------------------------------ - Power Policy Preference...............: 1 (highest performance) MSR_POWER_CTL....................(0x1FC) : 0x2904005B ------------------------------------------ - Bi-Directional Processor Hot..........: 1 (enabled) - C1E Enable............................: 1 (enabled) MSR_RAPL_POWER_UNIT..............(0x606) : 0xA0E03 ------------------------------------------ - Power Units.......................... : 3 (1/8 Watt) - Energy Status Units.................. : 14 (61 micro-Joules) - Time Units .......................... : 10 (976.6 micro-Seconds) MSR_PKG_POWER_LIMIT..............(0x610) : 0x7FFF80015FFF8 ------------------------------------------ - Package Power Limit #1............... : 4095 Watt - Enable Power Limit #1................ : 1 (enabled) - Package Clamping Limitation #1....... : 1 (allow going below OS-requested P/T state during Time Window for Power Limit #1) - Time Window for Power Limit #1....... : 10 (2560 milli-Seconds) - Package Power Limit #2............... : 4095 Watt - Enable Power Limit #2................ : 1 (enabled) - Package Clamping Limitation #2....... : 1 (allow going below OS-requested P/T state setting Time Window for Power Limit #2) - Time Window for Power Limit #2....... : 3 (20 milli-Seconds) - Lock................................. : 0 (MSR not locked) MSR_PKG_ENERGY_STATUS............(0x611) : 0x2074E4 ------------------------------------------ - Total Energy Consumed................ : 129 Joules (Watt = Joules / seconds) MSR_CONFIG_TDP_NOMINAL...........(0x648) : 0x21 MSR_CONFIG_TDP_LEVEL1............(0x649) : 0x940000001E0460 MSR_CONFIG_TDP_LEVEL2............(0x64a) : 0x94000000000000 MSR_CONFIG_TDP_CONTROL...........(0x64b) : 0x0 MSR_TURBO_ACTIVATION_RATIO.......(0x64c) : 0x0 MSR_PKGC3_IRTL...................(0x60a) : 0x0 MSR_PKGC6_IRTL...................(0x60b) : 0x0 MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x20BCE36 MSR_PKG_C3_RESIDENCY.............(0x3f8) : 0x0 MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x20BCE36 MSR_PKG_C3_RESIDENCY.............(0x3f8) : 0x0 MSR_PKG_C6_RESIDENCY.............(0x3f9) : 0x533B512 IA32_TSC_DEADLINE................(0x6E0) : 0x4DD830E718FA CPU Ratio Info: ------------------------------------------ Base Clock Frequency (BLCK)............. : 100 MHz Maximum Efficiency Ratio/Frequency.......: 12 (1200 MHz) Maximum non-Turbo Ratio/Frequency........: 33 (3300 MHz) Maximum Turbo Ratio/Frequency............: 42 (4200 MHz) P-State ratio * 100 = Frequency in MHz ------------------------------------------ CPU P-States [ (12) 33 37 ] CPU C3-Cores [ 0 10 ] CPU C6-Cores [ 0 4 6 8 10 ] CPU C6-Cores [ 0 1 2 4 6 8 10 ] CPU P-States [ 12 33 37 (42) ] CPU C3-Cores [ 0 10 11 ] CPU C6-Cores [ 0 1 2 3 4 6 8 10 11 ] CPU P-States [ (12) 33 36 37 42 ] CPU P-States [ 12 33 36 37 41 (42) ] CPU P-States [ 12 (33) 35 36 37 41 42 ] CPU P-States [ (12) 25 33 35 36 37 41 42 ] CPU P-States [ 12 16 25 33 35 36 37 41 (42) ] CPU P-States [ (12) 13 16 25 33 35 36 37 41 42 ] CPU P-States [ (12) 13 16 25 33 34 35 36 37 41 42 ] CPU C3-Cores [ 0 1 10 11 ] CPU P-States [ (12) 13 16 25 27 33 34 35 36 37 41 42 ] CPU P-States [ (12) 13 16 21 25 27 33 34 35 36 37 41 42 ] CPU P-States [ (12) 13 16 21 24 25 27 33 34 35 36 37 41 42 ] CPU P-States [ (12) 13 16 21 23 24 25 27 33 34 35 36 37 41 42 ] CPU P-States [ (12) 13 16 21 23 24 25 26 27 33 34 35 36 37 41 42 ] CPU P-States [ (12) 13 16 21 23 24 25 26 27 32 33 34 35 36 37 41 42 ] CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 10 11 ] CPU P-States [ 12 13 16 19 21 23 24 25 26 27 32 33 34 35 36 37 41 (42) ] CPU P-States [ 12 13 16 19 21 22 23 24 25 26 27 32 33 34 35 36 37 41 (42) ] CPU P-States [ 12 13 16 19 21 22 23 24 25 26 27 28 32 33 34 35 36 37 41 (42) ] CPU P-States [ 12 13 16 19 21 22 23 24 25 26 27 28 32 33 34 35 36 37 38 41 (42) ] CPU P-States [ 12 13 16 19 21 22 23 24 25 26 27 28 30 32 33 34 35 36 37 38 41 (42) ] CPU P-States [ 12 13 16 18 19 21 22 23 24 25 26 27 28 30 32 33 34 35 36 37 38 41 (42) ] CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ] CPU P-States [ (12) 13 16 18 19 21 22 23 24 25 26 27 28 30 31 32 33 34 35 36 37 38 41 42 ] CPU P-States [ (12) 13 16 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 41 42 ] CPU P-States [ 12 13 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 41 (42) ] CPU C3-Cores [ 0 1 8 10 11 ] CPU P-States [ 12 13 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 (33) 34 35 36 37 38 41 42 ] CPU C3-Cores [ 0 1 8 9 10 11 ] CPU P-States [ (12) 13 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 41 42 ] CPU P-States [ 12 13 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 (33) 34 35 36 37 38 39 40 41 42 ] CPU P-States [ 12 13 14 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 (33) 34 35 36 37 38 39 40 41 42 ] CPU C3-Cores [ 0 1 2 8 9 10 11 ] CPU C3-Cores [ 0 1 2 3 8 9 10 11 ] CPU P-States [ (12) 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 ] CPU C3-Cores [ 0 1 2 3 6 8 9 10 11 ] CPU C3-Cores [ 0 1 2 3 4 6 8 9 10 11 ] CPU C3-Cores [ 0 1 2 3 4 6 7 8 9 10 11 ] CPU C3-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ] Edited February 2, 2019 by NeXtor Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662351 Share on other sites More sharing options...
kgp Posted February 2, 2019 Author Share Posted February 2, 2019 (edited) 19 minutes ago, NeXtor said: I did as you told me but I still have Unsynchronized TSC for CPU 2 and Unsynchronized TSC for CPU 4 and now the CPU is not recognized. These are the clover settings for KernelToPatch and KextToPatch and the appleintelinfo log AppleIntelInfo.kext v2.9 Copyright © 2012-2017 Pike R. Alpha. All rights reserved. Settings: ------------------------------------------ logMSRs..................................: 1 logIGPU..................................: 0 logCStates...............................: 1 logIPGStyle..............................: 1 InitialTSC...............................: 0x4dd82e9df586 (2593 MHz) MWAIT C-States...........................: 8480 Processor Brandstring....................: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz Processor Signature..................... : 0x306F2 ------------------------------------------ - Family............................... : 6 - Stepping............................. : 2 - Model................................ : 0x3F (63) Model Specific Registers (MSRs) ------------------------------------------ MSR_IA32_PLATFORM_ID.............(0x17) : 0x8000000000000 ------------------------------------------ - Processor Flags...................... : 2 MSR_CORE_THREAD_COUNT............(0x35) : 0x6000C ------------------------------------------ - Core Count........................... : 6 - Thread Count......................... : 12 MSR_PLATFORM_INFO................(0xCE) : 0x20080C3BF3812100 ------------------------------------------ - Maximum Non-Turbo Ratio.............. : 0x21 (3300 MHz) - Ratio Limit for Turbo Mode........... : 1 (programmable) - TDP Limit for Turbo Mode............. : 1 (programmable) - Low Power Mode Support............... : 1 (LPM supported) - Number of ConfigTDP Levels........... : 1 (additional TDP level(s) available) - Maximum Efficiency Ratio............. : 12 - Minimum Operating Ratio.............. : 8 MSR_PMG_CST_CONFIG_CONTROL.......(0xE2) : 0x1E000005 ------------------------------------------ - I/O MWAIT Redirection Enable......... : 0 (not enabled) - CFG Lock............................. : 0 (MSR not locked) - C3 State Auto Demotion............... : 1 (enabled) - C1 State Auto Demotion............... : 1 (enabled) - C3 State Undemotion.................. : 1 (enabled) - C1 State Undemotion.................. : 1 (enabled) - Package C-State Auto Demotion........ : 0 (disabled/unsupported) - Package C-State Undemotion........... : 0 (disabled/unsupported) MSR_PMG_IO_CAPTURE_BASE..........(0xE4) : 0x10414 ------------------------------------------ - LVL_2 Base Address................... : 0x414 - C-state Range........................ : 1 (C-States not included, I/O MWAIT redirection not enabled) IA32_MPERF.......................(0xE7) : 0x58F6725D19 IA32_APERF.......................(0xE8) : 0x644D9B78A6 MSR_FLEX_RATIO...................(0x194) : 0xE0000 ------------------------------------------ MSR_IA32_PERF_STATUS.............(0x198) : 0x285B00002A00 ------------------------------------------ - Current Performance State Value...... : 0x2A00 (4200 MHz) MSR_IA32_PERF_CONTROL............(0x199) : 0x2A00 ------------------------------------------ - Target performance State Value....... : 0x2A00 (4200 MHz) - Intel Dynamic Acceleration........... : 0 (IDA engaged) IA32_CLOCK_MODULATION............(0x19A) : 0x0 IA32_THERM_INTERRUPT.............(0x19B) : 0x0 IA32_THERM_STATUS................(0x19C) : 0x88390000 ------------------------------------------ - Thermal Status....................... : 0 - Thermal Log.......................... : 0 - PROCHOT # or FORCEPR# event.......... : 0 - PROCHOT # or FORCEPR# log............ : 0 - Critical Temperature Status.......... : 0 - Critical Temperature log............. : 0 - Thermal Threshold #1 Status.......... : 0 - Thermal Threshold #1 log............. : 0 - Thermal Threshold #2 Status.......... : 0 - Thermal Threshold #2 log............. : 0 - Power Limitation Status.............. : 0 - Power Limitation log................. : 0 - Current Limit Status................. : 0 - Current Limit log.................... : 0 - Cross Domain Limit Status............ : 0 - Cross Domain Limit log............... : 0 - Digital Readout...................... : 57 - Resolution in Degrees Celsius........ : 1 - Reading Valid........................ : 1 (valid) MSR_THERM2_CTL...................(0x19D) : 0x0 IA32_MISC_ENABLES................(0x1A0) : 0x850089 ------------------------------------------ - Fast-Strings......................... : 1 (enabled) - FOPCODE compatibility mode Enable.... : 0 - Automatic Thermal Control Circuit.... : 1 (enabled) - Split-lock Disable................... : 0 - Performance Monitoring............... : 1 (available) - Bus Lock On Cache Line Splits Disable : 0 - Hardware prefetch Disable............ : 0 - Processor Event Based Sampling....... : 0 (PEBS supported) - GV1/2 legacy Enable.................. : 0 - Enhanced Intel SpeedStep Technology.. : 1 (enabled) - MONITOR FSM.......................... : 1 (MONITOR/MWAIT supported) - Adjacent sector prefetch Disable..... : 0 - CFG Lock............................. : 0 (MSR not locked) - xTPR Message Disable................. : 1 (disabled) MSR_TEMPERATURE_TARGET...........(0x1A2) : 0x690A00 ------------------------------------------ - Turbo Attenuation Units.............. : 0 - Temperature Target................... : 105 - TCC Activation Offset................ : 0 MSR_MISC_PWR_MGMT................(0x1AA) : 0x400000 ------------------------------------------ - EIST Hardware Coordination........... : 0 (hardware coordination enabled) - Energy/Performance Bias support...... : 1 - Energy/Performance Bias.............. : 0 (disabled/MSR not visible to software) - Thermal Interrupt Coordination Enable : 1 (thermal interrupt routed to all cores) - SpeedShift Technology Enable......... : 0 (disabled) - SpeedShift Interrupt Coordination.... : 0 (disabled) - SpeedShift Energy Efficient Perf..... : 0 (disabled) - SpeedShift Technology Setup for HWP.. : No (not setup for HWP) MSR_TURBO_RATIO_LIMIT............(0x1AD) : 0x22222A2A2A2A2A2A ------------------------------------------ - Maximum Ratio Limit for C01.......... : 2A (4200 MHz) - Maximum Ratio Limit for C02.......... : 2A (4200 MHz) - Maximum Ratio Limit for C03.......... : 2A (4200 MHz) - Maximum Ratio Limit for C04.......... : 2A (4200 MHz) - Maximum Ratio Limit for C05.......... : 2A (4200 MHz) - Maximum Ratio Limit for C06.......... : 2A (4200 MHz) IA32_ENERGY_PERF_BIAS............(0x1B0) : 0x1 ------------------------------------------ - Power Policy Preference...............: 1 (highest performance) MSR_POWER_CTL....................(0x1FC) : 0x2904005B ------------------------------------------ - Bi-Directional Processor Hot..........: 1 (enabled) - C1E Enable............................: 1 (enabled) MSR_RAPL_POWER_UNIT..............(0x606) : 0xA0E03 ------------------------------------------ - Power Units.......................... : 3 (1/8 Watt) - Energy Status Units.................. : 14 (61 micro-Joules) - Time Units .......................... : 10 (976.6 micro-Seconds) MSR_PKG_POWER_LIMIT..............(0x610) : 0x7FFF80015FFF8 ------------------------------------------ - Package Power Limit #1............... : 4095 Watt - Enable Power Limit #1................ : 1 (enabled) - Package Clamping Limitation #1....... : 1 (allow going below OS-requested P/T state during Time Window for Power Limit #1) - Time Window for Power Limit #1....... : 10 (2560 milli-Seconds) - Package Power Limit #2............... : 4095 Watt - Enable Power Limit #2................ : 1 (enabled) - Package Clamping Limitation #2....... : 1 (allow going below OS-requested P/T state setting Time Window for Power Limit #2) - Time Window for Power Limit #2....... : 3 (20 milli-Seconds) - Lock................................. : 0 (MSR not locked) MSR_PKG_ENERGY_STATUS............(0x611) : 0x2074E4 ------------------------------------------ - Total Energy Consumed................ : 129 Joules (Watt = Joules / seconds) MSR_CONFIG_TDP_NOMINAL...........(0x648) : 0x21 MSR_CONFIG_TDP_LEVEL1............(0x649) : 0x940000001E0460 MSR_CONFIG_TDP_LEVEL2............(0x64a) : 0x94000000000000 MSR_CONFIG_TDP_CONTROL...........(0x64b) : 0x0 MSR_TURBO_ACTIVATION_RATIO.......(0x64c) : 0x0 MSR_PKGC3_IRTL...................(0x60a) : 0x0 MSR_PKGC6_IRTL...................(0x60b) : 0x0 MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x20BCE36 MSR_PKG_C3_RESIDENCY.............(0x3f8) : 0x0 MSR_PKG_C2_RESIDENCY.............(0x60d) : 0x20BCE36 MSR_PKG_C3_RESIDENCY.............(0x3f8) : 0x0 MSR_PKG_C6_RESIDENCY.............(0x3f9) : 0x533B512 IA32_TSC_DEADLINE................(0x6E0) : 0x4DD830E718FA CPU Ratio Info: ------------------------------------------ Base Clock Frequency (BLCK)............. : 100 MHz Maximum Efficiency Ratio/Frequency.......: 12 (1200 MHz) Maximum non-Turbo Ratio/Frequency........: 33 (3300 MHz) Maximum Turbo Ratio/Frequency............: 42 (4200 MHz) P-State ratio * 100 = Frequency in MHz ------------------------------------------ CPU P-States [ (12) 33 37 ] CPU C3-Cores [ 0 10 ] CPU C6-Cores [ 0 4 6 8 10 ] CPU C6-Cores [ 0 1 2 4 6 8 10 ] CPU P-States [ 12 33 37 (42) ] CPU C3-Cores [ 0 10 11 ] CPU C6-Cores [ 0 1 2 3 4 6 8 10 11 ] CPU P-States [ (12) 33 36 37 42 ] CPU P-States [ 12 33 36 37 41 (42) ] CPU P-States [ 12 (33) 35 36 37 41 42 ] CPU P-States [ (12) 25 33 35 36 37 41 42 ] CPU P-States [ 12 16 25 33 35 36 37 41 (42) ] CPU P-States [ (12) 13 16 25 33 35 36 37 41 42 ] CPU P-States [ (12) 13 16 25 33 34 35 36 37 41 42 ] CPU C3-Cores [ 0 1 10 11 ] CPU P-States [ (12) 13 16 25 27 33 34 35 36 37 41 42 ] CPU P-States [ (12) 13 16 21 25 27 33 34 35 36 37 41 42 ] CPU P-States [ (12) 13 16 21 24 25 27 33 34 35 36 37 41 42 ] CPU P-States [ (12) 13 16 21 23 24 25 27 33 34 35 36 37 41 42 ] CPU P-States [ (12) 13 16 21 23 24 25 26 27 33 34 35 36 37 41 42 ] CPU P-States [ (12) 13 16 21 23 24 25 26 27 32 33 34 35 36 37 41 42 ] CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 10 11 ] CPU P-States [ 12 13 16 19 21 23 24 25 26 27 32 33 34 35 36 37 41 (42) ] CPU P-States [ 12 13 16 19 21 22 23 24 25 26 27 32 33 34 35 36 37 41 (42) ] CPU P-States [ 12 13 16 19 21 22 23 24 25 26 27 28 32 33 34 35 36 37 41 (42) ] CPU P-States [ 12 13 16 19 21 22 23 24 25 26 27 28 32 33 34 35 36 37 38 41 (42) ] CPU P-States [ 12 13 16 19 21 22 23 24 25 26 27 28 30 32 33 34 35 36 37 38 41 (42) ] CPU P-States [ 12 13 16 18 19 21 22 23 24 25 26 27 28 30 32 33 34 35 36 37 38 41 (42) ] CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ] CPU P-States [ (12) 13 16 18 19 21 22 23 24 25 26 27 28 30 31 32 33 34 35 36 37 38 41 42 ] CPU P-States [ (12) 13 16 18 19 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 41 42 ] CPU P-States [ 12 13 16 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 41 (42) ] CPU C3-Cores [ 0 1 8 10 11 ] CPU P-States [ 12 13 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 (33) 34 35 36 37 38 41 42 ] CPU C3-Cores [ 0 1 8 9 10 11 ] CPU P-States [ (12) 13 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 41 42 ] CPU P-States [ 12 13 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 (33) 34 35 36 37 38 39 40 41 42 ] CPU P-States [ 12 13 14 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 (33) 34 35 36 37 38 39 40 41 42 ] CPU C3-Cores [ 0 1 2 8 9 10 11 ] CPU C3-Cores [ 0 1 2 3 8 9 10 11 ] CPU P-States [ (12) 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 ] CPU C3-Cores [ 0 1 2 3 6 8 9 10 11 ] CPU C3-Cores [ 0 1 2 3 4 6 8 9 10 11 ] CPU C3-Cores [ 0 1 2 3 4 6 7 8 9 10 11 ] CPU C3-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ] You did not do at all what I told you! I told you to use the linked EFI-Folder, you don’t! You use a total mess of kext and kernel patches instead! 3 performance patches enabled at the same time! No check of KernelPM yet! Etc., etc., etc. No surprise the this mess does not boot! If you do not do what I tell you, I cannot help you, sorry and I really don’t like to waste my time. Also patch your firmware to unlock MSR register for Kernel write. Good luck! Over and out, KGP Edited February 2, 2019 by KGP-iMacPro Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662352 Share on other sites More sharing options...
NeXtor Posted February 2, 2019 Share Posted February 2, 2019 (edited) 41 minutes ago, KGP-iMacPro said: You did not do at all what I told you! I told you to use the linked EFI-Folder, you don’t! You use a total mess of kext and kernel patches instead! 3 performance patches enabled at the same time! No check of KernelPM yet! Etc., etc., etc. No surprise the this mess does not boot! If you do not do what I tell you, I cannot help you, sorry and I really don’t like to waste my time. Also patch your firmware to unlock MSR register for Kernel write. Good luck! Over and out, KGP I downloaded and uploaded the efi folder you linked to and then modified kernels and kexts patches based on my system by taking them from this thread: Your guide in some sections speaks specifically of the cpu "Broadwell" and my CPU is instead a "Haswell-e" and I do not read anywhere in this guide about patches "SMT" and "PKG" for "Haswell-e" so I'll have to take them somewhere... then if some patches are generic I do not know but I do not see it written... Why should I use KernelPM if the MSR is unlocked? it seems to me that you do not absolutely read the logs, do I have to highlight it? because I do not see obvious differences with the log on the front page. mine: MSR_PMG_CST_CONFIG_CONTROL.......(0xE2) : 0x1E000005 ------------------------------------------ - I/O MWAIT Redirection Enable......... : 0 (not enabled) - CFG Lock............................. : 0 (MSR NOT LOCKED) - C3 State Auto Demotion............... : 1 (enabled) - C1 State Auto Demotion............... : 1 (enabled) - C3 State Undemotion.................. : 1 (enabled) - C1 State Undemotion.................. : 1 (enabled) - Package C-State Auto Demotion........ : 0 (disabled/unsupported) - Package C-State Undemotion........... : 0 (disabled/unsupported) your: MSR_PMG_CST_CONFIG_CONTROL.......(0xE2) : 0x1E000005 ------------------------------------------ - I/O MWAIT Redirection Enable......... : 0 (not enabled) - CFG Lock............................. : 0 (MSR not locked) - C3 State Auto Demotion............... : 1 (enabled) - C1 State Auto Demotion............... : 1 (enabled) - C3 State Undemotion.................. : 1 (enabled) - C1 State Undemotion.................. : 1 (enabled) - Package C-State Auto Demotion........ : 0 (disabled/unsupported) - Package C-State Undemotion........... : 0 (disabled/unsupported) if I'm wrong, correct me... And then I never said that the system does not start. The system starts but there are some errors in the log... now i'll try to put only the _xcpm performance Kernel patch 10.14.3 (kindly provided by @PMHeart) of the first page but for the rest of the patches I do not know what to put. If you still want to help me, maybe pointing out the correct patches for my system I'm grateful, otherwise thanks again for your help. Edited February 2, 2019 by NeXtor Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662355 Share on other sites More sharing options...
kgp Posted February 2, 2019 Author Share Posted February 2, 2019 (edited) Just now, NeXtor said: I downloaded and uploaded the efi folder you linked to and then modified kernels and kexts patches based on my system by taking them from this thread: Your guide in some sections speaks specifically of the cpu "Broadwell" and my CPU is instead a "Haswell-e" and I do not read anywhere in this guide about patches "SMT" and "PKG" for "Haswell-e" so I'll have to take them somewhere... then if some patches are generic I do not know but I do not see it written... Why should I use KernelPM if the MSR is unlocked? it seems to me that you do not absolutely read the logs, do I have to highlight it? because I do not see obvious differences with the log on the front page. mine: MSR_PMG_CST_CONFIG_CONTROL.......(0xE2) : 0x1E000005 ------------------------------------------ - I/O MWAIT Redirection Enable......... : 0 (not enabled) - CFG Lock............................. : 0 (MSR NOT LOCKED) - C3 State Auto Demotion............... : 1 (enabled) - C1 State Auto Demotion............... : 1 (enabled) - C3 State Undemotion.................. : 1 (enabled) - C1 State Undemotion.................. : 1 (enabled) - Package C-State Auto Demotion........ : 0 (disabled/unsupported) - Package C-State Undemotion........... : 0 (disabled/unsupported) your: MSR_PMG_CST_CONFIG_CONTROL.......(0xE2) : 0x1E000005 ------------------------------------------ - I/O MWAIT Redirection Enable......... : 0 (not enabled) - CFG Lock............................. : 0 (MSR not locked) - C3 State Auto Demotion............... : 1 (enabled) - C1 State Auto Demotion............... : 1 (enabled) - C3 State Undemotion.................. : 1 (enabled) - C1 State Undemotion.................. : 1 (enabled) - Package C-State Auto Demotion........ : 0 (disabled/unsupported) - Package C-State Undemotion........... : 0 (disabled/unsupported) if I'm wrong, correct me... And then I never said that the system does not start. The system starts but there are some errors in the log... now i'll try to put only the _xcpm performance Kernel patch 10.14.3 (kindly provided by @PMHeart) of the first page but for the rest of the patches I do not know what to put. If you still want to help me, maybe pointing out the correct patches for my system I'm grateful, otherwise thanks again for your help. I already optimised the EFI-Folder for your i7-5820K (I am not stupid) and all is set to work with 10.14.3 and any other Mojave build! The EFI-Folder linked in the other post already considers all necessary adaptations to your build outlined in your signature (again I am not stupid) and should work for your system without any further modifications, especially when your MSR register is unlocked and you also applied the microcode update to your firmware as outlined in my guide. The actually implemented settings have been verified by many users of the i7-5820K and work flawless! It is also nonsense that my guide only considers Broadwell-E, README.md of my X99 EFI-Folder Github respository exactly outlines all necessary changes for the i7-5820K! If with the linked EFI-Folder, your system still does not boot, check your BIOS settings. After successfully booting your system, you should still perform the post installation process outlined in Section E.) of my guide! However the post installation is not necessary for successfully booting your system, for the latter you just need to EFI-Folder linked in the other post without any further modifications! Good luck, KGP Edited February 2, 2019 by KGP-iMacPro Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662382 Share on other sites More sharing options...
NeXtor Posted February 2, 2019 Share Posted February 2, 2019 2 hours ago, KGP-iMacPro said: I already optimised the EFI-Folder for your i7-5820K (I am not stupid) and all is set to work with 10.14.3 and any other Mojave build! The EFI-Folder linked in the other post already considers all necessary adaptations to your build outlined in your signature (again I am not stupid) and should work for your system without any further modifications, especially when your MSR register is unlocked and you also applied the microcode update to your firmware as outlined in my guide. The actually implemented settings have been verified by many users of the i7-5820K and work flawless! It is also nonsense that my guide only considers Broadwell-E, README.md of my X99 EFI-Folder Github respository exactly outlines all necessary changes for the i7-5820K! If with the linked EFI-Folder, your system still does not boot, check your BIOS settings. After successfully booting your system, you should still perform the post installation process outlined in Section E.) of my guide! However the post installation is not necessary for successfully booting your system, for the latter you just need to EFI-Folder linked in the other post without any further modifications! Good luck, KGP I once again replaced the whole efi folder with the one that you linked to me without adding Kext and Kernel patch and I started the pc over and over again trying to modify each time a different thing into Bios to try ALL combinations. (The bios is already patched with microcode and msr unlock: When I edited the bios I did not find any problem while running the uefipatch and UBU programs, so I assume I patched it correctly) These are the items that I modified each time: EIST (now disabled) ASUS MultiCore Enhancement (now disabled) VT-d Note (now disabled) Decoding 4G (now disabled) In addition to these changes in the bios I also tried to change the FakeCPUID from 0x040674 to 0x0306F2 (Haswell-E) and activate/deactivate KernelPM and Cores Patch... The system starts ALWAYS but changes the number of "Unsynchronized TSC for CPU" entries in the boot log and the CPU is not recognized in the system info (3,3 Ghz Unknown CPU) . For all the combinations I tried, the following commands returned the correct values as indicated in the guide. "sysctl machdep.xcpm.mode" "kextstat|grep -y x86plat" "kextstat|grep -y appleintelcpu" "sysctl -n machdep.xcpm.vectors_loaded_count" What can I do? What am I doing wrong? Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662393 Share on other sites More sharing options...
kgp Posted February 2, 2019 Author Share Posted February 2, 2019 (edited) 21 minutes ago, NeXtor said: I once again replaced the whole efi folder with the one that you linked to me without adding Kext and Kernel patch and I started the pc over and over again trying to modify each time a different thing into Bios to try ALL combinations. (The bios is already patched with microcode and msr unlock: When I edited the bios I did not find any problem while running the uefipatch and UBU programs, so I assume I patched it correctly) These are the items that I modified each time: EIST (now disabled) ASUS MultiCore Enhancement (now disabled) VT-d Note (now disabled) Decoding 4G (now disabled) In addition to these changes in the bios I also tried to change the FakeCPUID from 0x040674 to 0x0306F2 (Haswell-E) and activate/deactivate KernelPM and Cores Patch... The system starts ALWAYS but changes the number of "Unsynchronized TSC for CPU" entries in the boot log and the CPU is not recognized in the system info (3,3 Ghz Unknown CPU) . For all the combinations I tried, the following commands returned the correct values as indicated in the guide. "sysctl machdep.xcpm.mode" "kextstat|grep -y x86plat" "kextstat|grep -y appleintelcpu" "sysctl -n machdep.xcpm.vectors_loaded_count" What can I do? What am I doing wrong? True.. I forgot to change FakeCPUID in your EFI-Folder.. may bad. You have to use 0x0306F2 of course. I don't really understand your problem. It is normal that TSCAdjustReset.kext fixes unsynchronised TSCs on boot or wake from sleep and the latter is also displayed within the verbose boot messages. This is just an expected behaviour and even mandatory in any case. The number of desynchronised TSCs to be synchronised varies from boot to boot (never the same). Without TSCAdjustReset.kext and without resynchronising the TSCs, your system would not even boot. That's why TSCAdjustReset.kext is absolutely mandatory. If you also successfully verified "sysctl machdep.xcpm.mode" "kextstat|grep -y x86plat" "kextstat|grep -y appleintelcpu" "sysctl -n machdep.xcpm.vectors_loaded_count" XCPM is properly installed and working on your system. As your MSR register is unlocked you do not need to check KernelPM and or enable the core scope patch. If your MSR register would be locked, your system would not even boot without checking KernelPm and enabling the core scope patch. I always understood that your system is not booting because of some TSC desynchronisations. But as I understand your report and results now, there is absolutely no issue and your system works and behaves absolutely as expected with the EFI-Folder linked in my other post, apart from the necessary FakeCPUID correction, as I forget to modify the latter for Haswell-E. Edited February 2, 2019 by KGP-iMacPro Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662398 Share on other sites More sharing options...
kgp Posted February 2, 2019 Author Share Posted February 2, 2019 (edited) Correction of former macOS independent XCPM_performance patch New EFI-Folders EFI-X99-10.14.3-Release-iMacPro1,1-020219.zip and EFI-X99-10.14.4-Beta1-Release-iMacPro1,1-020219.zip with Clover_v2.4k_r4862, working USB port limit patches and a macOS independent XCPM_performance patch valid for 10.13.4+ and all version of 10.14. The correct macOS independent XCPM_performance patch valid for 10.13.4+ and all 10.14 versions reads: Find: C1E30848 63D389D0 48C1EA20 B99901 Replace: C1E308B8 00FF0000 31D29090 B99901 Fully vanilla EFI-Folders that should work with 10.13.4+ and all versions of 10.14, always provided that one also uses a truncated 15-port XHC USB kext in addition, with disabled USB port limit patches in the config.plist. There are still separate EFI-Folders for 10.14.3 and 10.14.4 Beta1, in case that somebody still wants to use a fully implemented XHC USB kext and the necessary respective USB port limit patches, which are disabled by default in the config.plist of each respective EFI-Folder distribution. Edited February 2, 2019 by KGP-iMacPro Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662442 Share on other sites More sharing options...
NeXtor Posted February 2, 2019 Share Posted February 2, 2019 5 hours ago, KGP-iMacPro said: True.. I forgot to change FakeCPUID in your EFI-Folder.. may bad. You have to use 0x0306F2 of course. I don't really understand your problem. It is normal that TSCAdjustReset.kext fixes unsynchronised TSCs on boot or wake from sleep and the latter is also displayed within the verbose boot messages. This is just an expected behaviour and even mandatory in any case. The number of desynchronised TSCs to be synchronised varies from boot to boot (never the same). Without TSCAdjustReset.kext and without resynchronising the TSCs, your system would not even boot. That's why TSCAdjustReset.kext is absolutely mandatory. If you also successfully verified "sysctl machdep.xcpm.mode" "kextstat|grep -y x86plat" "kextstat|grep -y appleintelcpu" "sysctl -n machdep.xcpm.vectors_loaded_count" XCPM is properly installed and working on your system. As your MSR register is unlocked you do not need to check KernelPM and or enable the core scope patch. If your MSR register would be locked, your system would not even boot without checking KernelPm and enabling the core scope patch. I always understood that your system is not booting because of some TSC desynchronisations. But as I understand your report and results now, there is absolutely no issue and your system works and behaves absolutely as expected with the EFI-Folder linked in my other post, apart from the necessary FakeCPUID correction, as I forget to modify the latter for Haswell-E. my fault, I thought those "Unsynchronized TSC" entries were not in the log and I saw them as errors to be solved Only one thing, in the system info the cpu is seen as 3.3 GHz Unknown. What can I do to fix this? Thanks again for your help and your time. Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662471 Share on other sites More sharing options...
kgp Posted February 2, 2019 Author Share Posted February 2, 2019 (edited) 24 minutes ago, NeXtor said: my fault, I thought those "Unsynchronized TSC" entries were not in the log and I saw them as errors to be solved Only one thing, in the system info the cpu is seen as 3.3 GHz Unknown. What can I do to fix this? Thanks again for your help and your time. Just use Type 0x0F01 in config.plist as hardwired in my default 10.14 EFI-Folder distribution: This will replace "unknown" by Intel Xeon W, in concordance with SMBIOS iMacPro1,1 although in reality you use a Haswell-E. Unfortunately, the better cosmetic patch described in Section E.10) System Overview CPU Cosmetics of my HighSierra X299 iMacPro build and desktop guide does not work under Mojave. Hope this solves your last remaining issue. Edited February 2, 2019 by KGP-iMacPro Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662472 Share on other sites More sharing options...
nmano Posted February 4, 2019 Share Posted February 4, 2019 Hi KGP I update guide for X299-WU8 please check Thank you. Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662665 Share on other sites More sharing options...
kgp Posted February 4, 2019 Author Share Posted February 4, 2019 10 hours ago, nmano said: Hi KGP I update guide for X299-WU8 please check Thank you. Wrong thread, should be moved to: 1 Link to comment https://www.insanelymac.com/forum/topic/334342-imac-pro-x99-live-the-future-now-with-macos-1014-mojave-successful-buildsuccessful-guide/page/3/#findComment-2662703 Share on other sites More sharing options...
Recommended Posts