Jump to content
KGP-iMacPro

iMac Pro X299 - live the future new with macOS 10.14 Mojave [Successful Build/Successful Guide]

143 posts in this topic

Recommended Posts

Dear friends,

why do you buy expensive Radeon VII cards, if they are not compatible with Macs and Mojave at the moment? So, you have no hardware acceleration, what is the resson to use it?

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)
1 hour ago, Acden said:

Dear friends,

why do you buy expensive Radeon VII cards, if they are not compatible with Macs and Mojave at the moment? So, you have no hardware acceleration, what is the resson to use it?

 

I never recommended to anybody to buy a Radeon VII for now. I use one which is not even my own for testing purposes and system development only. 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites

A was asking because I'm buying Vega 56 (a week ago I bought RX580, but decided to buy Vega 56 instead). And now I'm not sure to buy Vega 56 or wait for Radeon VII for video editing / encoding.

Share this post


Link to post
Share on other sites
Just now, Acden said:

A was asking because I'm buying Vega 56 (a week ago I bought RX580, but decided to buy Vega 56 instead). And now I'm not sure to buy Vega 56 or wait for Radeon VII for video editing / encoding.

 

If you are thinking on purchasing a VII you should wait in any case, until it is fully implemented under macOS and also confirmed to work on your specific system. 

Share this post


Link to post
Share on other sites
2 hours ago, Acden said:

A was asking because I'm buying Vega 56 (a week ago I bought RX580, but decided to buy Vega 56 instead). And now I'm not sure to buy Vega 56 or wait for Radeon VII for video editing / encoding.

 

If you are thinking on purchasing a VII you should wait in any case, until it is fully implemented under macOS and also confirmed to work on your specific system. 

 

BTW.. still no native Radeon VII implementation under 10.14.4 Beta 4 18E205e. 

Share this post


Link to post
Share on other sites
Posted (edited)

KGP, I would like to thank you for all of your hard work on the X299 Hackintosh builds.  You have done a wonderful job compiling all this very detailed information which has helped me get my Hackintosh running splendidly.

 

My main system components: 

 - MSI X299 Xpower Gaming AC Motherboard

 - i9 7900x 10 core CPU

 - Radeon RX 580 video card

 - 64 gb of ram (extra leftover from my unraid build)

 - (2) Samsung EVO 860 M.2 SSD

 - other various sata SSD and/or mechanical drives (not sure what I want to leave in this system yet)

 

The keys to my build working:

 

 EFI

 - use your EFI configuration to start

 - for my board added the "ncpi=0x2000" boot flag in Clover.

 - configured TSCAdjustRest.kext for my CPU

 

For bios settings:

 - all of the Hyper Threading and VTx/d settings are enabled

 - my bios has an MSR Lock Control setting  - disabled

 - Enhanced Halt State (C1E) - Enabled

 - CPU C6 report - Enabled

 - Package C-State - C6(non-retention) state

 

My system is VERY fast.  I had High Sierra installed per your guide last year, but I was having graphics issues with dual Nvidia 960 cards at the time and wanted to try a dual OS unraid build, so I switched to unraid for the last year.  I'm pretty sure the dual graphics card issue was related to having Above 4G Memory disabled now.

I was pretty happy with performance, but just wanted to get the most out of my hardware.  An upgrade to my NAS freed up some extra hardware to separate out my Windows 10 PC from my unraid build which gave me the push to go back to the bare metal Hackintosh.  I was already upgraded to Mojave and having passed a couple drives directly to my OS under Unraid, it was very easy to setup and configure my bootable drive for testing the bare metal configuration.  I think the biggest thing I missed, because it was buried deep in the advanced settings of the CPU OC settings, was the MSR Lock setting.  I scoured through everything multiple times before I came across it.  I think the GitHub page for AptioMemoryFix.efi is what got me to enable the advanced CPU settings and find it. 

 

So again, thank you for all your hardwork!  I'm loving my Hackintosh build!

 

I have sound with an OWC USB-C doc, but may try the Apple ALC Audio implementation to enable my onboard audio and I'm thinking about looking into adding a Thunderbolt 3 card.  Thunderbolt on my Macbook Pro is great and I can definitely see where I would make use of it on my desktop machine.

 

Edited by CrazyC7
fixing incorrect components

Share this post


Link to post
Share on other sites

ASUS WS X299 Sage 10G system configuration successfully added to general guidelines in the originating post of this thread (guide).

 

kgp.png.d686753632305480b1b18711c63464ca.png

Share this post


Link to post
Share on other sites

Hi.
Hope everyone's fine. 
Recently I started this hack - dual 16-core on Supermicro X11DPG-qt
Thank you KGP and thank you all for sharing your systems' development.
After over a week of working on this machine, I am finally STUCK!

Here are the full specs and below, the progress, some pics and my EFI folder

The System pictures are from the High Sierra installation but Mojave has the exact same behaviour

The EFI files and the Korey dump are attached to a link on my personal cloud as they are too big to uploaded here

For some reason, I can't upload all the bios photos, they are also attached to my link
Mainboard: Supermicro X11DPG-QT, bios revision 2 from 2017 

I cannot update to a later version as the Thunderbolt support will not be available no more.

CPUs - 2x Xeon Gold 6142 @2.4GHz engineering samples(stepping B0)
Memory - 8x 8GB Micron DDR4 ecc @ 2666MHz
GPU's - Monitors GPU - AMD RX560, processing GPUs - AMD Vega 56 and Vega 64
I am running on dual PSU - Supermicro 860W for the logic board and Corsair HX1200i for the GPUS and drives
System drives - both NVMEs -Samsung 970 EVO 2TB on the native M.2 port for Mac and 970 EVO 500GB for Windows on a PCIe adapter, 
Storage - 6X HGST 7k3000 3TB - Striped RAID
WiFi+BT - FENVI FV9801
Displays: Apple Thunderbolt Display 2K, Apple Cinema Display 23 and Dell 22"
Progress so far:
after 3 days of restarting and swiping the USB stick from my laptop to the beast and back --- I have successfully booted and installed both High Siera 10.13.6(16G45) and Mojave 10.14.3

This X11DPG-QT board has the PCIe ports ordering the opposite of any board I've seen so far, you can see on the attached picture

With High Sierra I was able to use a pretty clean EFI bootloader, I tried to respect the KGP guidance as much as I could but, the only way to boot was to use another kernel patch and the KernelPM checked in clover.

The system works almost ok but using 1 video board only. 
My goal is to have the RX560 for the monitors and the Vega GPUs for processing
so far, only the monitor GPU gets acceleration and Metal support. I swap them and doesn't matter with one is the primary, the other two will not be recognized by the system.
I installed Whatevergreen and Lilu(many versions tried) and I could have the boards recognised by the system but no acceleration and no Metal(you can see one pic from DaVinci Resolvew with only 1 GPU available)

I tried to follow some instructions for creating a SSD for each additional GPU but still no go.
I am not very advanced in doing that so, maybe someone could verify if DSDT and SSDT patching was done properly.

I had successfully booted High Sierra or Mojave with the monitor GPU in PCIe slot-9(CPU1 Slot). Any other choice it hangs at PCI configuration. beginsWindows boots ok from any slot

With these CPUs the only way to boot the installer was to use 0x0040670 as fakecpuid, droping the MATS table instead of the DMAR in Clover's ACPI, Pike's xpcm_pkg_scope kernel patch instead of xpcm_core_scope as the guide is recommending.
I configured the BIOS settings as close as I could to the original guide, I would like to say that it took me a lot of time to discover the Extended APIC in bios needs to be disabled for this board.

Still not working:
Thunderbolt GA Titan Ridge card - it was initialised in Windows, I connected a thunderbolt hard drive but macOS wouldn't even see it in the PCI branch of System Profiler, nor the IORegistryExplorer, I have way less TB options in bios than the guides

Bluetooth for the FENVI adapter not showing up.

USB 3 not working.

All of the above is happening both with High Sierra and Mojave, the only difference is that the EFI structure for Mojave is an ambiguous one, especially the config.plist that, honestly, after days of trying to boot, just matched a downloaded one from another forum.

Please let me know what other info about this build I should share.

 

https://mega.nz/#F!pR0nFaRL!QXLQESnahJ54reVL57scJQ

PHOTO-2019-03-24-22-55-39.jpg

PHOTO-2019-03-24-22-55-41.jpg

Screen Shot 2019-03-24 at 23.04.29.jpg

Screen Shot 2019-03-24 at 23.04.49.jpg

Screen Shot 2019-03-24 at 23.04.58.jpg

Screen Shot 2019-03-24 at 23.05.55.jpg

Screen Shot 2019-03-24 at 23.06.27.jpg

Screen Shot 2019-03-24 at 23.53.12.jpg

X11DPGQT MB Layout.png

2019-03-25 07.34.03.jpg

2019-03-25 07.34.20.jpg

2019-03-25 07.34.27.jpg

2019-03-25 07.34.34.jpg

2019-03-25 07.34.43.jpg

2019-03-25 07.34.52.jpg

2019-03-25 07.34.57.jpg

2019-03-25 07.35.03.jpg

2019-03-25 07.35.15.jpg

2019-03-25 07.35.24.jpg

2019-03-25 07.35.31.jpg

2019-03-25 07.35.42.jpg

2019-03-25 07.35.58.jpg

2019-03-25 07.36.12.jpg

2019-03-25 07.36.20.jpg

2019-03-25 07.36.27.jpg

2019-03-25 07.36.40.jpg

Share this post


Link to post
Share on other sites
Posted (edited)
3 hours ago, blackrunnero said:

Hi.
Hope everyone's fine. 
Recently I started this hack - dual 16-core on Supermicro X11DPG-qt
Thank you KGP and thank you all for sharing your systems' development.
After over a week of working on this machine, I am finally STUCK!

Here are the full specs and below, the progress, some pics and my EFI folder

The System pictures are from the High Sierra installation but Mojave has the exact same behaviour

The EFI files and the Korey dump are attached to a link on my personal cloud as they are too big to uploaded here

For some reason, I can't upload all the bios photos, they are also attached to my link
Mainboard: Supermicro X11DPG-QT, bios revision 2 from 2017 

I cannot update to a later version as the Thunderbolt support will not be available no more.

CPUs - 2x Xeon Gold 6142 @2.4GHz engineering samples(stepping B0)
Memory - 8x 8GB Micron DDR4 ecc @ 2666MHz
GPU's - Monitors GPU - AMD RX560, processing GPUs - AMD Vega 56 and Vega 64
I am running on dual PSU - Supermicro 860W for the logic board and Corsair HX1200i for the GPUS and drives
System drives - both NVMEs -Samsung 970 EVO 2TB on the native M.2 port for Mac and 970 EVO 500GB for Windows on a PCIe adapter, 
Storage - 6X HGST 7k3000 3TB - Striped RAID
WiFi+BT - FENVI FV9801
Displays: Apple Thunderbolt Display 2K, Apple Cinema Display 23 and Dell 22"
Progress so far:
after 3 days of restarting and swiping the USB stick from my laptop to the beast and back --- I have successfully booted and installed both High Siera 10.13.6(16G45) and Mojave 10.14.3

This X11DPG-QT board has the PCIe ports ordering the opposite of any board I've seen so far, you can see on the attached picture

With High Sierra I was able to use a pretty clean EFI bootloader, I tried to respect the KGP guidance as much as I could but, the only way to boot was to use another kernel patch and the KernelPM checked in clover.

The system works almost ok but using 1 video board only. 
My goal is to have the RX560 for the monitors and the Vega GPUs for processing
so far, only the monitor GPU gets acceleration and Metal support. I swap them and doesn't matter with one is the primary, the other two will not be recognized by the system.
I installed Whatevergreen and Lilu(many versions tried) and I could have the boards recognised by the system but no acceleration and no Metal(you can see one pic from DaVinci Resolvew with only 1 GPU available)

I tried to follow some instructions for creating a SSD for each additional GPU but still no go.
I am not very advanced in doing that so, maybe someone could verify if DSDT and SSDT patching was done properly.

I had successfully booted High Sierra or Mojave with the monitor GPU in PCIe slot-9(CPU1 Slot). Any other choice it hangs at PCI configuration. beginsWindows boots ok from any slot

With these CPUs the only way to boot the installer was to use 0x0040670 as fakecpuid, droping the MATS table instead of the DMAR in Clover's ACPI, Pike's xpcm_pkg_scope kernel patch instead of xpcm_core_scope as the guide is recommending.
I configured the BIOS settings as close as I could to the original guide, I would like to say that it took me a lot of time to discover the Extended APIC in bios needs to be disabled for this board.

Still not working:
Thunderbolt GA Titan Ridge card - it was initialised in Windows, I connected a thunderbolt hard drive but macOS wouldn't even see it in the PCI branch of System Profiler, nor the IORegistryExplorer, I have way less TB options in bios than the guides

Bluetooth for the FENVI adapter not showing up.

USB 3 not working.

All of the above is happening both with High Sierra and Mojave, the only difference is that the EFI structure for Mojave is an ambiguous one, especially the config.plist that, honestly, after days of trying to boot, just matched a downloaded one from another forum.

Please let me know what other info about this build I should share.

 

https://mega.nz/#F!pR0nFaRL!QXLQESnahJ54reVL57scJQ

PHOTO-2019-03-24-22-55-39.jpg

PHOTO-2019-03-24-22-55-41.jpg

Screen Shot 2019-03-24 at 23.04.29.jpg

Screen Shot 2019-03-24 at 23.04.49.jpg

Screen Shot 2019-03-24 at 23.04.58.jpg

Screen Shot 2019-03-24 at 23.05.55.jpg

Screen Shot 2019-03-24 at 23.06.27.jpg

Screen Shot 2019-03-24 at 23.53.12.jpg

X11DPGQT MB Layout.png

2019-03-25 07.34.03.jpg

2019-03-25 07.34.20.jpg

2019-03-25 07.34.27.jpg

2019-03-25 07.34.34.jpg

2019-03-25 07.34.43.jpg

2019-03-25 07.34.52.jpg

2019-03-25 07.34.57.jpg

2019-03-25 07.35.03.jpg

2019-03-25 07.35.15.jpg

2019-03-25 07.35.24.jpg

2019-03-25 07.35.31.jpg

2019-03-25 07.35.42.jpg

2019-03-25 07.35.58.jpg

2019-03-25 07.36.12.jpg

2019-03-25 07.36.20.jpg

2019-03-25 07.36.27.jpg

2019-03-25 07.36.40.jpg

 

Long story short questions:

1.) Is the MSR register in your BIOS locked o unlocked? If locked, you have to check "Kernel PM" and enable xpcm_core_scope. The need of xpcm_pgk_scope would imply that your CPU is not fully natively implemented by macOS. Drop Table DMAR should be fine also in your case. Also note that respective XCPM patches change from 10.13 to 10.14.

2.) You should use AppleALC.kext, Lilu.kext and WEG.kext in your EFI-Folder, otherwise neither HDAU nor HDEF will be properly implemented.

3.) Under "System Parameters" you have Nvidia Web checked although you seem not to use any Nvidia GPU.

4.) You are using USBInjectAll.kext and SSDT-1-SMCI--MB for XHCI USB. You might ask for help in the respective thread. I recommend to create and use a board specific XHC USB kext instead and even provide a dedicated guideline to do so. BTW.. what is SSDT-2-SpsNm for? And finally, I never recommended at any place do use a DSDT in /EFI/CLOVER/ACPI/patched.

5.) You do not use SSDT-DTPG.aml and you did not properly adopt SSDT-Vega64.aml to your system. The implemented SSDT-Vega64.aml is for PC02.BR2A while your ACPI table reads PC03.BR3A. I am also missing a properly adapted SSDT-RX560.aml in your EFI-Folder. The current GFX0 and GFX2 ACPI implementation of your two GPUs is solely thanks to WEG.kext and not due to any SSDT implementation. Also all other System SSDTs provided in the X299 Github library (yet to be properly adapted to your system) are be missing in your current EFI-Folder distribution.

6.) Concerning TB, I did not find any traces of any TB adapter in your IOREG.save, which rather suggests that either your TB adapter is not installed at all or at least not properly enabled in your BIOS. Once the TB adapter will be part of your ACPI table, you anyway should use a properly adapted SSDT-TB3HP.aml in /EFI/CLOVER/ACPI/patched.

For properly adapting available system SSDTs to your motherboard and particular PCIe slot population,  might be helpful in any case (standard sentence, repeated dozens of times). Else it might be beneficial to repeat reading also the main guide in your case. 

 

Else it is would be more than sufficient to post your perspective questions in one forum only. It just requires additional work at my side to respond with identical answers to identical questions in both forums at the same time.  

Good luck,

KGP

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites

Guide update to 10.14.4 (18E226) completed

 

X299-10_14.4.thumb.png.3e2cc0b90213a26101073e576c39cec5.png

 

1396919978_Screenshot2019-03-26at00_31_14.thumb.png.a93f93ca12210203e6ddee3f7c892f4a.png

 

New 10.14.4 EFI-Folder distribution EFI-X299-10.14.4-Release-iMacPro1,1-250319.zip in the X299 EFI-Folder Github repository. Clover_v2.4k_r4903 and new 10.14.4 USB port limit patch implementation. Updated FakeSMC and HWSensor distribution. One should also implement latest Lilu.kext, AppleALC.kext and Whatevergreen.kext distributions.

Still no native vanilla Radeon VII macOS implementation (still no default Radeon VII device-ID 0x66AF1002 in the vanilla AMDRadeonX5000.kext).

Also note new Xcode 10.2 and Xcode 10.2 Command Line distributions.

Enjoy and have fun,

 

kgp.png.44a100ed101de7b72dc6c8452f69bd86.png

Share this post


Link to post
Share on other sites
Posted (edited)

MacOS 10.14.4 (18E2034) - special build 

This afternoon @DSM2 advised me that yesterday Apple seems to have added a second special build of MacOS 10.14.4 (18E2034) on swcdn.apple.com, likely for new devices.

 

1009787285_Screenshot2019-03-26at23_16_16.thumb.jpg.f6b6cd91f6382a21a1afac9778830973.jpg

 

1023005410_Screenshot2019-03-26at23_28_40.thumb.png.bb058f0cf1d428c75f088586c8f1fca3.png

 

1283935623_Screenshot2019-03-26at23_19_50.thumb.png.5b31b8bd4053d50e40c6edb483061153.png

 

And here is the script for the respective Install MacOS.app creation: createInstaller-10.14.4-SB.sh.zip.

EFI-X299-10.14.4-Release-iMacPro1,1-250319.zip is also fully valid in this case. 

No native vanilla implementation of the Radeon VII also with this macOS build yet. 

Enjoy and have fun,

 

kgp.png.1b0464e3ef2894bd94de1bb1ec2fce76.png

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites

Native Radeon VII support with MacOS 10.14.5 public beta 1

 

See respective IM thread.

 

Unfortunately I am not able to confirm this by myself as I cannot implement the air flow Radeon VII in my water blocked X299 system and my X99 system with the air flow Radeon VII does not boot with 10.14.5 beta 1 as the XCPM_pkg_scope kernel patch (not required for X299) seems broken with 10.14.5 beta 1. I was not able to reach @PMheart for the necessary XCPM_core_scope kernel patch update and in 4 hours I have to leave to the airport and will not have any access to my computers for 6 days.

 

Thus, all X299 guys, enjoy Radeon VII with 10.14.5 beta 1. All necessary kext and kernel patches implemented in EFI-X299-10.14.4-Release-iMacPro1,1-250319.zip are working. I already updated to 10.14.5 beta 1 on X299 and everything is fine and working. 

 

All X99 guys should wait with the update to 10.14.5 beta 1 until an updated XCPM_pkg_scope kernel patch is available. All other kext and kernel patches implemented in EFI-X99-10.14.4-Release-iMacPro1,1-250319.zip should continue working also under 10.14.5 beta 1.

 

There are Radeon VII SSDTs in the X99 (Slot-1, ASUS X99-A II) and X299 (Slot-1, ASUS Prime X299 Deluxe; Slot-5 ASUS WS X299 Sage 10G) SSDT Github directories, which yet need to be verified and hopefully will also work with the native Radeon VII implementation after a likely necessary ACPI path and ACPI replacement adaptation depending on your motherboard and Radeon VII PCIe slot population.  

 

Also it is recommended to use the latest versions of Lilu.kext (1.3.5), AppleALC.kext (1.3.6) and Whatevergreen.kext (1.2.7). 

 

Good luck and see you in one week from now.

 

KGP

Share this post


Link to post
Share on other sites
Posted (edited)

Back from Rome, quick update to 10.14.5 Beta on X99 with Radeon VII

 

Native Radeon VII implementation, including Hardware Acceleration, Display HotPlug, multi-monitor support, DP/HDMI Audio and system sleep/wake on X99.

 

For further details, remarks and benchmark results see: 

 

 

 

EFI-X299-10.14.4-Release-iMacPro1,1-250319.zip also fully valid for 10.14.5 Betas.

There are Slot-1 and Slot-5 SSDT-X299-Radeon-VII.amls for the Deluxe and Sage 10G, respectively in the respective X299 SSDT Github repositories, yet to be successfully verified by somebody. 

Enjoy and have fun,

 

kgp.png.85fc2d2de79d30056da29b1f4329141d.png

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
Posted (edited)

New X299 10.14.5 Beta EFI-Folder distribution adding Radeon VII GPU Temp sensor information for iStatMenus. 

EFI-X299-10.14.5-Beta-iMacPro1,1-050419.zip

1.) I just modified Kozlek/Interferenc FakeSMC/HWSensor source code distribution for adding Radeon VII GPU Temp sensor information and subsequently added new FakeSMC.kext and HWSensor.kexts to /EFI/Clover/kexts/Other. The new GPU Sensor kext should now support all Vegas and also the new Radeon VII, when using iStatMenus. 

 

259842668_Screenshot2019-04-06at00_48_48.png.052112febb27b4048c3bd670e9f2eaa5.png

 

2.) Implementing Clover_v2.4k_r4918. 

Enjoy and have fun, 

 

kgp.png.ac5bb4fd0ca162d39678206c8e2749c5.png

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites

Flawless update to 10.14.5 Beta 2 (18F108f)

 

532839574_Screenshot2019-04-09at01_15_58.thumb.png.70e6ef596a334934da584394b7e627aa.png

 

No further improvements in Radeon VII performance on my X99 system so far (quite identical overall benchmark scores when compared with Beta 1) but H264 and HEVC support. 

 

1768084373_Screenshot2019-04-09at01_13_24.png.855661f421714a5570e0d44b05a314e2.png.22b756a93759ae7ae75f57795da198f8.png

 

Enjoy and have fun,

 

kgp.png.73d47fd45138f6abd649f498689cd937.png

Share this post


Link to post
Share on other sites

I've also noticed that hot plug for the USB hub in my LG UltraFine 5K display now works as expected. I can sleep/wake the machine (and have done, multiple times) and the hub comes back reliably. 

 

There were problems with the screen not waking properly in 10.14.5b1, but a simple plug/unplug of the TB3 cable into the display resolved the problem every time. Nice!

Share this post


Link to post
Share on other sites
19 hours ago, KGP-iMacPro said:

Flawless update to 10.14.5 Beta 2 (18F108f)

 

532839574_Screenshot2019-04-09at01_15_58.thumb.png.70e6ef596a334934da584394b7e627aa.png

 

No further improvements in Radeon VII performance on my X99 system so far (quite identical overall benchmark scores when compared with Beta 1) but H264 and HEVC support. 

 

1768084373_Screenshot2019-04-09at01_13_24.png.855661f421714a5570e0d44b05a314e2.png.22b756a93759ae7ae75f57795da198f8.png

 

Enjoy and have fun,

 

kgp.png.73d47fd45138f6abd649f498689cd937.png

Just to note. benchmarks for my vega frontier have dropped from around 200 000 in geekbench to 140 000...my guess is that unless its using the same driver as the VII, its a software compatibility issue? or apple really messed something up in the amd driver due to the reduction of coil whine... even with editing the powerplay table. still no real gains in performance :(

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, Wackymac said:

Just to note. benchmarks for my vega frontier have dropped from around 200 000 in geekbench to 140 000...my guess is that unless its using the same driver as the VII, its a software compatibility issue? or apple really messed something up in the amd driver due to the reduction of coil whine... even with editing the powerplay table. still no real gains in performance :(

 

Looks rather like some Apple beta driver mess in the frame of the actual VII implementation or some missing update of respective benchmark tools different than Luxmark. I can confirm a drop of 30.000 (200.00 vs 170.000) scores in Geekbench OpenGL and Metal scores with 10.14.5 Beta 2 also in case of my Nitro+ Vega 64. In contrary, Luxmark Scores slightly increased from 28.000 to 33.000.

 

Update: I now also performed a Cinebench OpenGL benchmark for my Nitro+ Vega 64 and surprisingly even there scores slightly increased from 162 fps to 166 fps.  

 

Thus in conclusion, seems we are rather missing some Geekbench update and should not blame Apple. 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
Posted (edited)
26 minutes ago, KGP-iMacPro said:

 

Looks rather like some Apple beta driver mess in the frame of the actual VII implementation or some missing update of respective benchmark tools different than Luxmark. I can confirm a drop of 30.000 (200.00 vs 170.000) scores in Geekbench OpenGL and Metal scores with 10.14.5 Beta 2 also in case of my Nitro+ Vega 64. In contrary, Luxmark Scores slightly increased from 28.000 to 33.000.

 

Update: I now also performed a Cinebench OpenGL benchmark for my Nitro+ Vega 64 and surprisingly even there scores slightly increased from 162 fps to 166 fps.  

 

Thus in conclusion, seems we are rather missing some Geekbench update and should not blame Apple. 

just saw your conclusion... well now back to beta 2. thanks for the info and your continued hard work :)

Edited by Wackymac

Share this post


Link to post
Share on other sites
Posted (edited)

Radeon VII now considered within Whatevergreen Source Code distribution

 

I just asked @VIT9696 to consider all necessary Radeon VII details within his Whatevergreen Source Code distribution and he kindly did immediately.  

 

Radeon VII is now also part of WEG and all necessary cosmetics are now also properly displayed under "About this  Mac" and "Graphics/Displays" of Apple's system report also by means of WEG and not only as up to now by means of my SSDT-X299-Radeon-VII.aml available in my Github SSDT repositories. For respective testing purposes, I removed my respective Radeon VII SSDT temporarily. 

 454410042_Screenshot2019-04-19at10_16_34.thumb.png.04b3ccbc16f0e23c7ad63462f074682c.png

 

1969095497_Screenshot2019-04-19at10_16_18.thumb.png.e8a890fc10608c5eda7b9ea7dd276916.png

 

The new version of WEG however seems to work also well in line with the actual version of my SSDT-X299-Radeon-VII.aml and the Kozlek/Interferenc FakeSMC/HWSensor kext distribution that I recently modified to properly display Radeon VII GPU Temps under iStatMenus and which is also hardwired such within my 10.14.5 EFI-Folder Github distribution.

 

1944763512_Screenshot2019-04-19at10_24_42.thumb.png.a29db47ffe52236e7a7c505b9d81f5e0.png

 

Against former claims of others, the current Radeon VII WEG consideration does not seem to have any effect on respective Geekbench scores either.

Let’s see if all the above remains valid after long term testing not only by myself but also by other users, moreover as everything related to the VII should be considered as beta in any case.

 

 

 

Enjoy and have fun,

 

kgp.png.2758904e97d4a68301d42254184a361c.png

 

 

Edit:

 

Note that the new WEG source code also seems to fix some actual or at least some former macOS inconsistencies concerning "compatible", "subvendor-ID",... GFX0 and HDAU properties. Thus anybody using my RadeonVII SSDT in addition to WEG, needs to download and implement the new modified RadeonVII-WEGVII SSDT from my respective Github libraries, after the usual adaptation to motherboard and PCI-Slot Population. I also dropped the formerly implemented load table created with VGTab (version for Vega64) but apparently not fully compatible with Radon VII, as it actually does not seem to provide major improvements and therefore rather would be confusing in the ongoing beta testing. All other above conclusion however seem still valid also after the actual changes in the RadeonVII-WEGVII SSDTs.

 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
23 minutes ago, fabiosun said:

930294686_ScreenShot2019-04-19at10_40_40AM.png.77abe414d3aec5bae0cf11c79d29f7f8.png

Hi KGP, beautiful rig and photos

I would like to ask why you do not feed in your rig EATX12V3 additional power connector you see in this grab

 

TY

 

 

Because connecting the 2x 8pin EATX connectors at the top to me seemed sufficient for usual OC purposes and because up to know I thought that one would need to connect the 3rd EATX connector only in case of special and extreme overclocking. 

 

Did you make any different experience and  observation on that? Certainly not a big deal to also connect the 3rd EATX connector if it would be really beneficial for the allover system performance.  

 

Please let me know about your appreciated opinion. 

Share this post


Link to post
Share on other sites
2 minutes ago, KGP-iMacPro said:

 

Because connecting the 2x 8pin EATX connectors at the top to me seemed sufficient for usual OC purposes and because up to know I thought that one would need to connect the 3rd EATX connector only in case of special and extreme overclocking. 

 

Did you make any different experience and  observation on that? Certainly not a big deal to also connect the 3rd EATX connector if it would be really beneficial for the allover system performance.  

 

Please let me know about your appreciated opinion. 

 

I am new with sage 10g configuration and I have had no particular problem in setting it in a basic way. I use to feed also that connector because system could benefit of it in case (as you say) of an extreme OC, but also if you populate more PCIEX slot (in my case some time with a spare GFX or thunderbolt EX card or PCIEX NVME card)

In case I would feed it (if no extra power need it is also safe to have it connected)

 

 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave 18A391:  For macOS Mojave or High Sierra, use macOS_iso_creator.tool on page 4 of thread.
      UPDATE macOS Catalina Beta DP3_19A501i:  For Catalina, @jpz4085 has made an automated batch file to create a Catalina VM in Windows with iMac 14,2 SMBIOS.  You can still use my macOS_iso_creator.tool on page 5 to make an installer ISO to attach to the VM.
       
       
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By lingaraju06
      I created Mojave installer in my vb vm and my specs are as follows.
      Asus rog rampage vi apex
      I9 7900x
      32gb 3000mhz corsair ram in all 4 slots (8gb each)
      Samsung pm961 nvme ssd
      Rtx 2080ti sli
       
      I have correct bios settings and able to boot to clover and when i start install it stops after end randomseed and on google search it appears to be ram detection issue, in config plist i set to imac 17,1 and under memory i changed the values to suit my hardware, i used notepad++ to edit plist as i dont know how to do in vmware and then it goes past end randomseed but stops at next line stating unable to do something i dont exactly remember and i have no more luck can anyone please help me, thank you. I am total noob and need a step by step guide if u dont mind, thank you once again.
    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VMware Workstation on a Windows Host
       
      I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host.  The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg
       
      Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program.
       
      Requirements
      Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X) 4GB or more RAM (2GB or more will be needed for OS X) Hard Disk with at least 40GB free for Virtual Machine VMware Workstation 12 or later VMware Unlocker 2.0.7 or later Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#41 16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg
       
      3.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes….
       
       
       
      4.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 5.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
      Updates:
      @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362.
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS 10.13+ using Apple's createinstallmedia utility.
       
      Install and Patch VMware Workstation 12 on your PC
      1.  Download and install VMWare Workstation Player 12 or later
      2.  Download and extract Unlocker 2.0.7 or later to your USB stick…
      3.  Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt.
       



       
      Create an El Capitan Virtual Machine
      1.  Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”.  Choose “I will install the operating system later” at the How will you install screen….
       

      2.  Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version.  By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder.
       


      3.  Under Specify Disk Capacity, you can leave the default 40GB or set a larger value.  I personally store the virtual disk as a single file.  Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12.
       


      4.  Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier.
       


       
      5.  To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file).  The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad).
       


       
      6.  For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine.
       

      7.  Finally click “Play virtual machine”
       

      Installation of El Capitan
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I’ve named the drive Macintosh HD but you can enter whatever you like eg El_Capitan.
       



      3.  Quit DU and choose Macintosh HD to install El Capitan on.
       

      4.  After 20-30 min (depending on how fast your system is), the installation will complete and the VM will automatically reboot…
       

      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
       


      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
       


      7.  Finally, you will arrive at the El Capitan Desktop.  You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”.  This will allow you to install VMware Tools….
       



      8.  After rebooting, the VM can now be resized or run at full screen resolution.  Audio and network/internet should also work OOB.
       

       
      SMBIOS Customization and iMessage Vars
      To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS -
      eg for an iMac 11,3 SMBIOS, you can enter the following lines....
      smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation.
       
      The critical variables for iMessage/Facetime activation are MLB & ROM.  By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk.
       
      If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0")....
      efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg
      efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to   "<=>?@A".
       
      Vanilla Mavericks and Yosemite
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Enjoy
       
      Update for macOS 10.12 Sierra
      The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13.
       
      Update for macOS 10.13 High Sierra and 10.14 Mojave
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS using Apple's createinstallmedia utility.
      Post#41 describes how to build "Install macOS ******.app" on the fly from installer files downloaded beforehand in /SharedSupport folder.
       
      Update for macOS 10.15beta Catalina
      See post Update for macOS Catalina 10.15beta
       
      CECI.zip
      CYI.tool.zip
      CMI.tool.zip
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.14 installation on MBR HFS+ partition.
       
      To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store.
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.14 HFS Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.14 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. Patch to stop auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.14.
      4. This patched MBR OSInstaller will never convert to APFS, and will always install as HFS+ partition.
      5. This patched MBR OSInstaller method works with both MBR HFS+ and GPT HFS+ partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version.

      How to make 10.14 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      How to make 10.14 installer for MBR (MBR-Automatic-Method)?
      Just use 14MBRinstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.13.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       


       
      Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_1014fullapp to download the full installer app via swscan.apple.com.
       

       
    • By fusion71au
      Patch Catalina or Mojave macOS Installer App for Unsupported Machines
       
      Often for economic reasons, Apple prevents the Installer.app for its latest macOS from installing on older machines perfectly capable of running it eg macOS 10.14 Mojave on Unsupported Macs Thread.
       

       
      In Mojave 10.14, @ASentientBot posted a method to patch the distribution file in OSInstall.mpkg to enable the Mojave installer to install on unsupported machines (with or without graphics card metal support). 
       
      In Catalina 10.15beta, the above method no longer works since Apple is checking OSInstall.mpkg for its file signature and the mandatory requirement in Catalina to install to 2 separate apfs volumes necessitates using the original Catalina macOS Base System Installer.  Fortunately, it is still possible to substitute High Sierra’s Apple Signed OSInstall.mpkg inside the Catalina or Mojave InstallESD.dmg by making it R/W.
       
      The procedure below will allow Macs or Hacks able to install High Sierra to also install Catalina or Mojave (eg SMBIOS MacPro5,1, iMac11,3, MacBook Pro7,1 which have been unsupported in macOS 10.14.x and 10.15beta) -credit to @ASentientBot's post.
       
      Prerequisites
      1. Mac or Hack capable of and running High Sierra 10.13.x
      2. An original, untouched copy of OSInstall.mpkg from High Serra InstallESD.dmg - attached OSInstall_10.13.6.mpkg.zip save to your ~/Downloads folder
      3. macOS Installer App eg for Catalina beta or Mojave downloaded to /Applications
      4. Add NVRAM boot arg (or Clover config.plist boot arg on a hack) -no_compat_check to enable system to boot to final completed Mojave or Catalina install.
       
      Procedure
      1. Open Terminal and type the following
       
      open /Applications/Install*/Contents/SharedSupport/InstallESD.dmg (assuming the Catalina or Mojave Installer App is in /Applications)  
      2. Open Disk Utility, click File|New Image|Image from ‘InstallESD”
      3. Save as read/write image, no encryption in /Applications
      4. Unmount InstallESD in DU by clicking the "eject" icon next to it
       
       
      5. Open the R/W InstallSD.dmg in /Applications and replace Catalina’s/Mojave's OSInstall.mpkg with High Sierra’s version by typing in terminal
       
      open /Applications/InstallESD.dmg cp ~/Downloads/OSInstall_10.13.6.mpkg /Volumes/InstallESD/Packages/OSInstall.mpkg  
      6. Unmount InstallESD in DU by clicking the "eject" icon next to it
      7. Replace original Catalina/Mojave InstallESD.dmg with our patched one, making a backup of the original.  In terminal, type
       
      sudo mv /Applications/Install*/Contents/SharedSupport/InstallESD.dmg /Applications/InstallESD_orig.dmg sudo mv /Applications/InstallESD.dmg /Applications/Install*/Contents/SharedSupport/  
      8.  Test the newly patched installer!…

×