Jump to content
KGP-iMacPro

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

142 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 ludufre
      Installing macOS Mojave on Lenovo ThinkPad L440

       
      New Catalina Installation Guide: 
       
       
      There are two version of this laptop:
      - 20AS = Chipset QM87, without Express Card (mine).
      - 20AT = Chipset HM86, with Express Card.
      I strong believe is the same thing...
       

      Changelog:
       
      10/20/2019 20:00h GMT-0
      - Added info about update 10.14.16.
      - Added link do Catalina guide. 
       
      07/30/2019 14:56h GMT-0
      - Fixed typo in credits. Thanks @"Sniki"
       
      06/09/2019 14:16h GMT-0
      - Added missing parts in the post-install step. 
       
      06/04/2019 17:19h GMT-0
      - Updated Clover link. 
       
      06/02/2019 18:08h GMT-0
      - Added info about update 10.14.5. 
       
      03/13/2019 13:15h GMT-0
      - Updated info about touchpad replacement and CPU and 4G LTE modem.
       
      02/05/2019 18:47h GMT-0
      - Updated info about CPU replacement and 4G LTE modem.
       
      02/04/2019 15:24h GMT-0
      - Sometimes the VoodooHDA.kext doesn't work.
      - Added AppleHDADisabler.kext to fix that (attached bellow).
       
      01/24/2019 14:42h GMT-0
      - Added more adjustments to use of VoodooHDA.
      - Updated VoodooHDA links to 2.9.1 official (without installer).
      - Changed PCM volume from 90 to 180 in Info.plist (attached modified VoodooHDA.kext bellow)
      - Updated SSDT-L440.aml (Removed HDEF and HDAU, not needed).
      - Updated config.plist (Changed to user Audio layout to 1).
       
      01/22/2019 20:47h GMT-0
      - I gave up on the AppleALC.
      - Headset does not work.
      - Now with VoodooHDA is perfect and the sound even louder.
       
      01/22/2019 14:37h GMT-0
      - Added info about update 10.14.3. 
       
      01/22/2019 13:46h GMT-0
      - Added link to BIOS reassing guide.
       
      01/20/2019 11:49h GMT-0
      - First version.
       
      What works and what does not
       
      - Processor: Intel Core i5-4300M ->  Work. All SpeedStep stages.
      - Video Card: Intel HD4600 ->  Work. QE/CI and Metal.
      - Chipset: Intel QM87 ->  Work.
      - Mini DisplayPort ->  Work. But no audio, yet.
      - VGA ->  Not work. Normal.
      - Audio: ALC292 ->  Work.
      - WiFi/Bluetooth: Intel AC 7260 ->  Not work. Replaced with DW1560 (need whitelist removal).
      - Ethernet: Intel I217-LM ->  Work.
      - Card Reader: Realtek RTS5227 ->  Not work.
      - Keyboard and Touchpad ->  Work.
      - Webcam ->  Work.
      - Fingerprint Reader ->  Not work. Normal.
      - USB3.0 ->  Work.
      - Sleep ->  Work.
      - Airdrop, Handoff, Instant Hotspot and Continuity ->  Work after replaced wireless.
       
       
      Extras
       
      - FullHD 1920x1080 display upgrade: 
      Replaced with AU Optronics B140HAN01.1 30pin eDP (B140HAN01.2 and B140HAN01.3 also compatible).
      Apparently same screen as Dell Latitude E6440, E7440, Lenovo Ideapad U430 and E129.
       
      - CPU upgrade:
      Replaced the stock Intel Core i5 4300M 2.6Ghz (3.3Ghz turbo) 6M cache with Intel Core i7 4700MQ 2.4Ghz (3.4Ghz turbo) 6MB.
      I initially had problems with overheating. The processor ran at full load above 90 degrees.
      After using a quality thermal paste I can work between 70 and 80 degrees.
      Acceptable taking into consideration that the new processor has 47TDP versus 37TDP which is recommended.
      I also had no problem consuming the battery while charging. The original 65W source seems to have figured out.
       
      - Touchpad upgrade:
      Replaced the stock with T460 touchpad.
      This is serious: you have to do it! It should be stock. Touchpad with precision and absurd quality!
      Just do it!
       
      - RAM upgrade:
      No mistery here. Just upgade.
       
       
      Todo
       
      - Make DP audio work.
      - Make Card Reader work.
      - Upgrade CPU to i7-4712MQ (Ordered. It's on the way) Done, but received i7-4700MQ (47w TDP, with good paste I have no overheating)
      - Replace touchpad with T460 model (Ordered. It's on the way) Done. Sensitivity and perception of quality much better. I recommend 100%!
      - Sierra Gobi5000 4G LTE modem EM7355 (Ordered. It's on the way. I hope works. ) Done, but not work. Recognize but not connect. I already gave up...
      - Upgrade to 16GB RAM Done
      - Make trackpad appear in System Preferences
       
       
      What you need to install

      - Running install of macOS
      - One USB flash drive of 8GB or bigger
      - macOS Mojave install app
      - Clover EFI
      - Clover Configurator
      - Some KEXTs and SSDT patches


      How create create the install flash drive
       
      Prepare install flash drive

      Format the flash drive with GUID partition mapping and name it "Install".

      - Open Disk Utility.
      - Click in View, then "Show All Devices".
      - Select the destination flash drive, then Erase.
      - Name: Install, Format: Mac OS Extended (Journaled) and Scheme: GUID Partition Map
       
      Create install flash drive

      Open terminal and run this command:
      sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/Install --nointeraction This will take about 30 minutes.
       


      Install bootloader

      Download the CloverEFI from SourceForge (used 4934) and install with this options on "Install macOS Mojave":
       
      - Install for UEFI booting only
      - Install Clover in the ESP
      - UEFI Drivers - ApfsDriverLoader-64
      - UEFI Drivers - AptioMemoryFix-64


       
       
      Make things works

      Will be created a partition named EFI and mounted in Desktop.
      - Replace the /Volumes/EFI/CLOVER/config.plist with mine attached below
                    If you have modded BIOS with Advanced Menu and enabled 128MB DRAM-prealloc use 128MB_DRAM-prealloc_config.plist.zip
                    If no, then use 32MB_DRAM-prealloc_config.plist.zip
      - Put SSDT-L440.aml attached below in /Volumes/EFI/CLOVER/ACPI/patched/
       
      Generate your Serial, MLB and SmUUID
       
      - Open the replaced config.plist with Clover Configurator (used 5.3.2.0)
      - Go to SMBIOS, click few times in "Generate New" in Serial Number and SmUUID.
       
      Download those Kexts and put in /EFI/CLOVER/kexts/Other/
       
      - Download the HWSensors 3 from here. I used the FakeSMC.kext, ACPIMonitor.kext and IntelCPUMonitor.kext inside of DMG version r196.
      - Download the VoodooPS2Controller.kext from here. I used version 2018-1008.
      - Download the IntelMausiEthernet.kext from here. I used the version 2018-1031.
      - Download the Lilu.kext from here. I used the version 1.3.6.
      - Download the VoodooHDA from here. I used the version 2.9.1 and patched the sound volume (attached below).
      - Download the WhateverGreen.kext from here. I used the version 1.2.9.
      - Download the AppleBacklightFixup.kext from here. I used the version 2018-1013.
      - Download the USBInjectAll.kext from here. I used the version 2018-1108.
      - Download the ACPIBatteryManager.kext from here. I used the version 2018-1005.
       
      - Download the VirtualSMC.kext from here. I used version 1.0.2. Replaced with FakeSMC of the HWSensors 3 r196 package.
      - Download the FakeSMC.kext from here. I used the version 2018-0915. Replaced with VirtualSMC.kext due 10.14.4 issues on update.
      - Download the AppleALC.kext from here. I used the version 1.3.4. Replaced with VoodooHDA.kext due mic not working.
       
       
      Wifi and Bluetooth (DW1560 / BCM94352Z)
       
      Unfortunately, some notebook manufacturers are currently blocking the replacement of wireless cards. They want you to only use the models sold by them. And of course, none of them from Lenovo for this notebook model is compatible with MacOS.
       
      If you try to start with an unauthorized wifi card for them, you will receive a screen error:
      1802: Unauthorized network card is plugged in - Power off and remove the network card. Since this check is done directly in the BIOS, the only solution is to modify it.
      But since nothing is easy in this life, there is one small big problem:
      - The BIOS update procedure does not allow you to use modded files as it used to be.
      - You will need to physically reach your BIOS on the motherboard and make use of a USB BIOS reader/writer.
       
      So what you need to do:
      1. Disassembly your laptop;
      2. Dump your BIOS with an USB BIOS reader with SOIC8 clip (to not desolder from the motherboard);
      3. Patch it (In addition to removing the whitelist, add the advanced menu);
      4. Fix RSA signature;
      5. Reflash BIOS;
      6. Replace wireless card;
      7. Remount your laptop;
      8. Done.
       
      Soon, I'll provide step by step in this process. Probably until end of this week.
      In the meantime, if you need to, send me your dump that I do steps 3 and 4 for you.
      I also add the Advanced Menu so you can increase to 128MB the DRAM-prealloc.
       
      To fix a Modded BIOS to remove the 5 beeps on boot, you need this guide: https://www.insanelymac.com/forum/topic/337333-guide-fix-insyde-h2o-bios-signature-5-beeps-on-lenovo (traduzido: pt-BR)
       
       
      After replaced the wireless card. Download those Kexts and put in /EFI/CLOVER/kexts/Other/
       
      - Download the AirportBrcmFixup.kext from here. I used the version 2.0.0.
      - Download the BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext from here. I used the version 2018-0505.
      - Download the BT4LEContinuityFixup.kext from here. I used the version 1.1.2.
       
       
      Now you can start the instalation without problem (I guess).
       
       
      How install
       
      UEFI Setup Configuration and Installation

      UEFI configuration
       
      My BIOS is the latest: 1.93 (J4ET93WW) 

      - Shutdown and insert the flash drive.
      - Power on with F1 pressed to enter BIOS setup.
      - Change value: Config - Intel(R) AMT - Intel(R) AMT Control to DISABLED
      - Change value: Security - Security Chip to DISABLED
      - Change value: Security - Anti-Theft - Intel(R) AT Module Activation to DISABLED
      - Change value: Security - Anti-Theft - Computrace to DISABLED
      - Change value: Security - Secure Boot to DISABLED
      - Change value: Startup - UEFI/Legacy Boot to BOTH, Legacy First and CSM Support = Yes
      - Save & Exit Setup (F10)
       
      - Now, hold the F12
      - In the list, select your flash drive.
       
      The installer will start. 
      
      Format destination disk

      Format the disk with GUID partition mapping and name it "Macintosh".

      - Select Disk Utility in the list, then press Continue.
      - Click in View, then "Show All Devices".
      - Select the destination Disk, then Erase.
      - Name: HD, Format: APFS and Scheme: GUID Partition Map

      Close Disk Utility.
      
      Select "Install macOS", then Continue.
      Follow instructions in screen.

      After install

      After first part install the system will reboot. Maybe you have to press F12 again and select the flash drive.
      
      The second part of the installation will begin. This will take 16 minutes.
       

      Post installation

      Install bootloader
       
      When the second part of install finish, the system will reboot again.

      After performing the user initial setup and go to the desktop, you need to install Clover on internal disk.

      Open the Clover installer inside flash drive that you copied before.

      Use same options above but choose the system partition this time.

      Now you need to replace the EFI folder inside your destination disk EFI parittion, with EFI folder inside flash card EFI partition.

      If the flash drive EFI partition of your destination disk or flash drive is unmounted:
      Mount with terminal "sudo diskutil mount /dev/rdiskXs1". To know what X is, use "diskutil list", most likely is 0 for destination disk and 1 for flash drive.
       
      Then, eject the flash drive.
       
      Last step
       
      Move all Kexts from EFI partition to /Library/Extensions, with those commands in Terminal:
      sudo mv -R /Volumes/EFI/EFI/CLOVER/kexts/Other/* /Library/Extensions/ sudo chmod -R 755 /Library/Extensions sudo chown -R root:wheel /Library/Extensions sudo kextcache -i / Restart the system.
       
       
      It's done!
       
       
      Updates
       
      System update 10.14.3
       
      - Updated with success;
      - Everything works perfectly after reboot;
       

       
       
      System update 10.14.4
       
      - Updated Clover to 4910.
      - Updated Lilu.kext to 1.3.5 and WhateverGreen to 1.2.7.
      - After first reboot the update progress stoped with:
      GTrace synchronization point 4 Unsupported CPU Unsupported PCH hmm.. mismatch sizes: 3100 vs 20 It was still possible to start the previous installation, selecting "Macintosh" as opposed to "macOS Install" in Clover.
      So I created a flash drive with Clover 4910 and put only my config.xml, SSDT-L440.aml, the updated Lilu.kext and WhateverGreen.kext. And I decided to test VirtualSMC instead of FakeSMC.kext.
      With this I was able to install update 10.14.4. After installation I can boot normally, even with FakeSMC.kext that already in /Library/Extensions.
      I do not know what exactly happened, but now works everything like was previously.
       


       
       
      System update 10.14.5
       
      - Updated Clover to 4934.
      - Updated Lilu.kext to 1.3.6 and WhateverGreen to 1.2.9.
      - After first reboot the update progress stoped again (like 10.14.4 update) with:
      GTrace synchronization point 4 Unsupported CPU Unsupported PCH hmm.. mismatch sizes: 3100 vs 20 It was still possible to start the previous installation, selecting "Macintosh" as opposed to "macOS Install" in Clover.
      I decided to rollback to FakeSMC.kext but this time with the version of HWSensors 3. Link above.
      With this I was able to install update 10.14.5. After installation I can boot normally.
       

       
       
       
      System update 10.14.6
       
      - Updated Clover to 5097.
      - Updated Lilu.kext to 1.3.8 and WhateverGreen to 1.3.3.
      - Make system update.
       
       

      And last but not least

      I would like to thank the following community members, by making these dream possible:
      @crushers, @snatch, @apianti, @blackosx, @blusseau, @dmazar, @slice2009, @autumnrain, @phpdev32, @EMlyDinEsH, @RehabMan, @Scellow, @mitch_de, @Shailua, @Andy Vandijck, @maxfierke, @ArturXXX, @LexHimself, @brumas, @"Sniki" and all others members involved directly or indirectly.
       
       
      Attachments
      32MB_DRAM-prealloc_config.plist.zip
      128MB_DRAM-prealloc_config.plist.zip
      SSDT-L440.aml
      VoodooHDA.kext.zip
      AppleHDADisabler.kext.zip
    • By brerackl
      Good evening,
       
      I used to mess around with iATKOS back in 2011, I since have been out of the loop and have gone through several different PC's.
      Now I have built a new PC and would like to install High Sierra to my external SSD.
      I have gotten as far as installing clover and the .raw image to my USB stick but I am getting stuck on the +++++++++++ then reboot problem.
      I realize a LOT has changed and I am having a bit of trouble figuring it out. 
       
      My PC's specs are as follows:
       
      CPU:
                  Intel Core i7 7820X
       
      RAM:
                  32GB Ballistix RGB Tactical Tracer (by Micron)
       
      Motherboard:
                  EVGA X299 FTW K
       
      Graphics:
                  NVIDIA RTX 2070 (EVGA)
       
      Storage:
                  4TB Western Digital HDD
                  1TB Samsung SSD 970 EVO 1TB
                  480GB Micron SSD
       
      If someone can help point me in the right direction that would be amazing, I have tried using some of the efi files for different x299 setups and such but no luck same results, played with different boot flags and options but everything is so much different I don't really know what does what. 
      I would very greatly appreciate if anyone can point me to some reading or a specific set of files to get me past this error as I haven't the slightest why it is even doing this. Mind you the last time I played around with this was back in 2011 with iATKOS and CD's, I have no CD drive in this build and need to do this via USB and as I understand this is 100% possible I just need the right boot setup and settings.
       
      Thank you in advance,
      Brett
    • By ludufre
      Installing macOS Mojave 10.14.6 on Gigabyte Z370N WIFI + i7 8700K + UHD 630



      Changelog:
       
      09/01/2019 15:57h GMT-0
      - Updated to 10.14.6.
       
      06/10/2019 00:44h GMT-0
      - Completely rewritten.
       
      10/17/2018 08:12h GMT-0
      - Fix Kexts permissions commands adjusted.
      - Removed FrameBuffer patch that is not needed.
      - Added audio solution and HDMI.
      - Unfortunately DisplayPort does not work.
      - Replaced Wifi/BT with DW1560 (BCM94352Z)
       
      10/11/2018 04:15h GMT-0
      - Added USB 3.0 patch.
      - Adjusted some steps.
      - Changed text formatting.
       
      10/11/2018 03:42h GMT-0
      - Added missing UEFI configuration.
       
      10/07/2018 00:36h GMT-0
      - First version.
       
      What works and what does not
       
      - Processor: Intel Core i7-8700K ->  Work. All SpeedStep stages.
      - Video Card: Intel UHD 630 ->  Work. QE/CI and Metal.
      - Chipset: Intel Z370 ->  Work.
      - HDMI 2.0 (1st) ->  Work.
      - HDMI (2nd) ->  Work.
      - DP ->  Not tested yet.
      - Audio: ALC1220 ->  Work.
      - HDMI Audio ->  Work.
      - WiFi/Bluetooth ->  Not work. Replaced with BCM94360CS2.
      - Ethernet (1st) ->  Work.
      - Ethernet (2nd) ->  Work.
      - USB3.0 ->  Work.
      - Sleep ->  Work.
      - Airdrop, Handoff, Instant Hotspot and Continuity ->  Work after replaced wireless.
       
       
      Todo
       
      - Make audio work.
      - Make HDMI audio work.
      - Test DisplayPort.
      - Make second ethernet work.
      - Replace Wifi/Bluetooth.
      - Test DP.
       
      What you need to install

      - Running install of macOS
      - One USB flash drive of 8GB or bigger
      - macOS Mojave install app
      - Clover Configurator
      - Clover EFI
      - Clover Configurator
      - Some KEXTs and SSDT patches


      How create create the install flash drive
       
      Prepare install flash drive

      Format the flash drive with GUID partition mapping and name it "Install".

      - Open Disk Utility.
      - Click in View, then "Show All Devices".
      - Select the destination flash drive, then Erase.
      - Name: Install, Format: Mac OS Extended (Journaled) and Scheme: GUID Partition Map
       
      Create install flash drive

      Open terminal and run this command:
      sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/Install --nointeraction This will take about 30 minutes. / 8 minutes with USB 3.0
       
       

      Install bootloader

      Download the CloverEFI (used 5058, from Automated Clover Builds) and install with this options on "Install macOS Mojave":
       
      - Install for UEFI booting only
      - Install Clover in the ESP
      - UEFI Drivers - Recommended drivers (check all)
      - UEFI Drivers - Human Interface Devices (check all)
      - UEFI Drivers - FileVault 2 UEFI Drivers (check all, If you are going to use FileVault)
      - UEFI Drivers - Additional drivers - NvmExpressDxe (if you are going to use NVMe)


       
       
      Make things works
       
      We'll make a full working flash drive, so follow these instructions:
       
      Will be mounted the EFI partition of the flash drive.
       
      Open the the /Volumes/EFI/CLOVER/config.plist inside this new partition with Clover Configurator (used 5.5.0.0)
       
      Important modifications
       
      config.plist
       
      ACPI Page
       
      - Check: SSDT - PluginType
       
      BOOT Page
       
      - Add: Arguments - darkwake=2
      - Check: Legacy - XMPDetection=Yes
       
      KERNEL AND KEXT PATCHES Page
       
      - Check: KernelPm
       
      RT VARIABLES Page
       
      - Change: CsrActiveConfig - 0x3E7
       
      SMBIOS Page
       
      - Change: Macmini8,1 - Mac mini (Late 2018) | Intel Core i7-8700B @ 3.20 GHz

       
      - Click: Generate New (few times in the two buttons)

       
       
      Need some Kexts in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the HWSensors 3 from here. I used the FakeSMC.kext, ACPIMonitor.kext, ITEIT87x.kext and IntelCPUMonitor.kext inside of DMG version r240.
      - Download the Lilu.kext from here. I used the version 1.3.8.

       
      Intel UHD 630
       
      ACPI Page
      - Uncheck: Fixes - AddHDMI
      - Uncheck: Fixes - FixDisplay
      - Uncheck: Fixes - FixHDA
       
      GUI Page
      - Change: Screen Resolution - 3840x2160 (My monitor is 4K)

      Need a Kext in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the WhateverGreen.kext from here. I used the version 1.3.1.

       
      Audio ALC 1220 and HDMI audio

      BOOT Page
      - Add: Arguments - alcid=11

      DEVICES Page
      - Change: Audio - Inject - 11
      - Uncheck: Audio - AFGLowPowerState
      - Uncheck: Audio - ResetHDA

      Need a Kext in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the AppleALC.kext from here. I used the version 1.4.0.

       
      All USBs (2.0, 3.0, Type-C, internal)
       
      KERNEL AND KEXT PATCHES Page - KextsToPatch
       
      - Name*: com.apple.iokit.IOUSBHostFamily
      - Find* [HEX]: 83FB0F0F
      - Replace* [HEX]: 83FB3F0F
      - Comment: USB Port Limit Patch 1 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      - Name*: com.apple.iokit.IOUSBHostFamily
      - Find* [HEX]: 83FB0F0F
      - Replace* [HEX]: 83FB3F0F
      - Comment: USB Port Limit Patch 2 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      - Name*: com.apple.driver.usb.AppleUSBXHCI
      - Find* [HEX]: 83FB0F0F
      - Replace* [HEX]: 83FB3F0F
      - Comment: USB Port Limit Patch 3 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      - Name*: com.apple.driver.usb.AppleUSBXHCI
      - Find* [HEX]: 83FF0F0F
      - Replace* [HEX]: 83FF3F0F
      - Comment: USB Port Limit Patch 4 PMHeart/DalianSky
      - MatchOS: 10.14.x
       
      Need a Kext in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the USBInjectAll.kext from here. I used the version 2018-1108.
       
      Need SSDT patch in the folder /EFI/CLOVER/ACPI/patched/
       
      - Download the SSDT-EC.aml, SSDT-UIAC.aml and SSDT-USBX attached bellow.
       
      Wifi and Bluetooth (BCM94360CS)
       
      Works out of box (plug 'n' play).
       
       
      LAN Cards
       
      Need a Kext for feach card in the folder /EFI/CLOVER/kexts/Other/
       
      - Download the IntelMausiEthrenet.kext from here. I used the version 2018-1031.
      - Download the SmallTreeIntel82576.kext attached bellow. I do not remember where I found it.

       
      Now you can start the instalation without problem (I guess).
       
       
      How install
       
      UEFI Setup Configuration and Installation

      UEFI configuration
       
      - Shutdown and insert the flash.
      - Power on with DEL pressed to enter BIOS setup.
      - Change value: Periphelrals - Initial Display to IGP
      - Change value: Periphelrals - USB Configuration - XHCI Hand-off to ENABLE
      - Change value: Chipset - VT-d to DISABLE
      - Change value: Chipset - Internal Graphics to ENABLE
      - Change value: Chipset - DVMT Pre-Allocated to 128M
      - Save & Exit Setup
       
      - Now, hold the F12
      - In the list, select your flash drive.
      - It will show twice. One with UEFI prefix and another without.
      - Select with UEFI prefix. Ie.: "UEFI: Sandisk Cruzer"
       
      The installer will start. 
      
      Format destination disk

      Format the disk with GUID partition mapping and name it "HD".

      - Select Disk Utility in the list, then press Continue.
      - Click in View, then "Show All Devices".
      - Select the destination Disk, then Erase.
      - Name: HD, Format: APFS and Scheme: GUID Partition Map

      Close Disk Utility.
      
      Select "Install macOS", then Continue.
      Follow instructions in screen.

      After install

      After first part install the system will reboot.
      
      The second part of the installation will begin. This will take 16 minutes.
       

      Post installation

      Install bootloader
       
      When the second part of install finish, the system will reboot again.

      After performing the user initial setup and go to the desktop, you need to install Clover on internal disk.

      Open the Clover installer inside flash drive that you copied before.

      Use same options above but choose the system partition this time.

      Now you need to replace the EFI folder inside your destination disk EFI parittion, with EFI folder inside flash card EFI partition.

      If the flash drive EFI partition of your destination disk or flash drive is unmounted:
      Mount with terminal "sudo diskutil mount /dev/rdiskXs1". To know what X is, use "diskutil list", most likely is 0 for destination disk and 1 for flash drive.
       
      Then, eject the flash drive.
       
      Last step
       
      Move all Kexts from EFI partition to /Library/Extensions, with those commands in Terminal:
      sudo cp -R /Volumes/EFI/EFI/CLOVER/kexts/10.14/* /Library/Extensions/ sudo chmod -R 755 /Library/Extensions sudo chown -R root:wheel /Library/Extensions sudo kextcache -i / Restart the system.
       
       
      It's done!
       
       
      Updates
       
      System update 10.14.6
       
      - Download and open latest CloverConfigurator
      - Open Mount EFI and click in Mount Partition in EFI Partitions list
      - Click in Open Partition that appears
      - Go to EFI -> CLOVER
      - Backup config.plist and ACPI folder to desktop
      - Go back and delete CLOVER folder
      (If you restart now you can't boot in macOS - DON'T RESTART)
      - Download latest Clover and install (link and config above)
      - Replace config.plist and ACPI folder from your desktop
       
      - Update Lilu.kext, AppleALC.kext, WhateverGreen.kext, HWSensors kexts (FakeSMC, ACPIMonitor, IntelCPUMonitor, ITEIT87x) in /Library/Extensions/
      - Run:
       
      sudo chmod -R 755 /Library/Extensions sudo chown -R root:wheel /Library/Extensions sudo kextcache -i /  
       
      - Install macOS Update 10.14.6 and restart
       

       
      And last but not least
       
      I would like to thank the following community members, by making these dream possible:
      @crushers, @snatch, @apianti, @blackosx, @blusseau, @dmazar, @slice2009, @autumnrain, @phpdev32, @EMlyDinEsH, @RehabMan, @Scellow, @mitch_de, @Shailua, @Andy Vandijck, @maxfierke, @ArturXXX, @LexHimself, @brumas and all others members involved directly or indirectly.
       
       
       
      Z370N-WIFI v2.zip
    • By arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app, using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issue DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.

       
      With that being said, I'll just move on to the actual tutorial.
       
      New (probably better) method.
       
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
       
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
       
      Alternatively, you can also try one of the MacPro SMBIOSes, such as MacPro5,1 or MacPro6,1. It was tested multiple times and it showed good results. 
      Keep in mind that choosing these will most likely not show you an iGPU in System Report, since those machines generally (probably all of them) use Xeon CPUs with no iGPUs either.
       
      /!\NOTE: There have been reports saying that using this method (switching SMBIOS to a MacPro one) with newer versions of MacOS may cause iTunes to crash.
      So...keep that in mind and better try some of the other methods mentioned here.
       
      A simple Lilu plugin
       
      Thanks to vulgo for the plugin and @Matgen84 for sharing and testing it, we now have yet another possible solution to this issue. It's a Lilu plugin (which means that it requires Lilu.kext in order to work) it's called NoVPAJpeg, and it can be downloaded from here.
      You use it as a regular kext, alongside Lilu. I prefer (and recommend) using it within the EFI folder, in Clover/kexts/Other. But if you want to use it in S/L/E, that should work just fine.
       
      More info can be found in this post here.
       
      UPDATE:
       
      According to Vulgo, NoVPAJpeg.kext is now deprecated.
      In case its functionality is needed, use WhateverGreen.kext and add the following boot arguments:
      shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94 In case you wanna try alternative medicine  ...
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.
       
      For ATI GPUs (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id)  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
       
       
      For NVIDIA GPUs (tested on my old MSi GTX 650)
       
      This is what I needed for my NVIDIA GPU and the MSI motherboard in the signature (*since then, I upgraded my GPU to my current RX 580). Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
         For MSi motherboads (check out my motherboard details in the signature)
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
         For Gigabyte motherboards
       
         Set:
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext (now included into WhateverGreen.kext) in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      Another way to activate the iGPU while having the dGPU set as primary is by going into BIOS/SAG/Graphics Configuration/iGPU and setting Multi-Monitor to [Enabled], all the rest remains on [Auto], and set Inject/Intel to [True] in Clover config.*.
       
      Thanks to @gjw for the tip.
       
      *Motherboard dependent. But the multi-monitor option might be the same regardless of manufacturer.
       
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from dGPU to iGPU and vice-versa.
       
      Cheers!
    • By gengik84
      Ciro82==>>Thanks
      Uno dei tre Requisiti:
      Hack funzionante Mac vero Macchina virtuale Impostazioni Bios per il boot:
      Cercate una voce  del tipo “Sata Mode”e settatela  in AHCI
      Secure Boot: disabilitare o altri sistemi operativi
      CSM: UEFI o LEGACY, oppure a secondo del tipo di installazione
      VT-x / VT-d disable
      *Nota: Secure boot e csm valido solo per bios UEFI
      Materiale Occorrente 
      "OS X (Versione App.Store)”
      USB 8GB  *nota: nel caso di usb superiori dovrà essere partizionata, in modo da avere una partizione su cui "lavoreremo,di questa dimensione
      ShowAllfiles 
      kext Wizard 
      Bootloader Clover_2.3k_r xxx:                   http: //sourceforge.n.../cloverefiboot/
      Clover Configurator:                                    http: //mackie100proj...a.org/download/
      FakeSmc.kext:                                            https://github.com/kozlek/HWSensors/releases
      In allegato,a fondo pagina troverete un "pacchetto" contenente : ShowAllfiles, Kext Wizard, FakeSmc.kext: 
      App alternative:
      ESP Mounter Pro: per montare la partizione EFI
      Vi illustrerò tre metodi per creare la usb, ma sono ben distinti… quindi usatene soltanto uno
      Metodo 1: “Install Mac_OS_X.command” Metodo 2: “Create Install Media di Apple” Metodo 3:  Metodo Manuale Alla fine delle preparazione dell’installer, tutti i metodi necessitano l’installazione del Bootloader Clover sulla a vostra USB.
      “CONDIZIONI OBBLIGATORIE”
      PUNTO 1: che la vostra usb sia stata preventivamente nominata USB (caratteri maiuscoli) Tabella di partizione GUID e la formattazione in  Mac esteso Journaled.
      PUNTO 2: che l’installer di OSX si trovi in Applicazioni
      Utility Disco 
      Selezionate la pendrive, andate su “partizione”, selezionate “1 partizione”, impostate Mac OS esteso journaled e date il nome USB, poi in basso cliccate su opzioni e scegliete Tabella partizione (GUID), poi “applica”.
      Immagine 
      Riporto nuovamente l’operazione sopra citata adoperando dal nuovo Utility Disco introdotto su El Capitan.
      Rimane ovviamente invariato nome della usb in ==>> USB (maiuscolo), la formattazione in Mac esteso Journaled e sia la mappa partizione in GUID
      Da utility disco selezionate la usb, cliccate su inizializza.
      dal menù a tendina scegliete la relative impostazioni
      Immagine  
      Procedura effettua da High Sierra è la stessa della precedente, l'unica attenzione e operazione da aggiungere in primis  è cliccare nel menù a tendina in alto sulla sinistra di utility disco e selezionare "mostra tutti i dispositivi"
      Immagine 
       
      =====================
        METODO 1: "Install_Mac_OS_X.Command" Lo script che trovate allegato in fondo alla guida permette la creazione dell’installer in maniera automatica
      Include la possibilità di scelta di tre versioni di osx
      Yosemite El Capitan Sierra Il risultato finale è come quello del metodo "manuale" descritto nella guida, per cui l'installazione avverrà in un solo passaggio, non in due come con il metodo createinstallmedia. 
      Offre inoltre la possibilità di inserire un kernel patchato, utile, per esempio, per chi usa AMD.
      Rimane invariato il nome dato alla usb in USB, mappa partizione e tipo di formattazione
      Se la vostra usb non sarà rinominata nel modo corretto, verrete avvisati dal terminale, quindi non dovrete far altro che apportare la relativa modifica e rilanciare nuovamente lo script
      Esempio
      ===========================
      Metodo 2 
      L'intento è quello di usare la procedura fornitaci direttamente da Apple, "createinstallmedia", introdotta  con Mavericks. 
      Tale metodo prevede l’uso del terminale che via via se ne sta perdendo il “valore e l’uso”
      Inizialmente per i neofiti potrà sembrare problematico ma alla fine non è così.
      Durante il post installazione alcune operazioni ne richiedono l’ uso.
      Perciò mi sono chiesto perchè, qualora uno volesse, non far conoscere da subito un po’ questo “strumento”???
      Per favorirvi vi ho allegato i comandi già  “pronti”, i quali li potrete copiare ed incollare sul terminale.
      A questo punto aprite il terminale, copiate ed incollate il comando sottostante e premete invio, digitate la vostra password e premete nuovamente invio.
      Comando per creare USB con Yosemite:
      sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction  
      Comando per creare USB con El Capitan
      sudo /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ OS\ X\ El\ Capitan.app --nointeraction Comando per creare USB con Sierra 
      sudo /Applications/Install\ macOS\ Sierra.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --applicationpath /Applications/Install\ macOS\ Sierra.app/ --nointeraction Per creare USB con Hight Sierra o Mojave usate --> C_I_M (aggiornato per 10.14)
       
      Funziona con il drag & drop sul terminale, in questo caso non vi è necessità che la usb sia nominata in un determinato modo ed essendo basato su create install media ovviamente funziona da 10.9 a 10.14.... 
      BENE…IL PROCESSO DI CREAZIONE E’ INIZIATO…
      AVREMO CIRCA 20/30 MINUTI DI TEMPO LIBERO A CUI DEDICARSI A CIO’ CHE VOGLIAMO………………………………………..  
      COLGO L’OCCASIONE PER FARVI NOTARE LA VELOCITA’ E LA SICUREZZA DI QUESTO METODO
      CONFRONTATE QUESTO CON IL TERZO METODO E NOTERETE CHE CON UN SOLO PASSAGGIO, OSSIA IL COMANDO DATO AL TERMINALE, FACCIAMO IN UNA SINGOLA OPERAZIONE TUTTI I VARI STEP DESCRITTI SULL’ ALTRO METODO.
      DETTO QUESTO, MOLTO IMPORTANTE E’ SOTTOLINEARE CHE COSI’ FACENDO EVITEREMO ERRORI  DI DISTRAZIONE RIGUARDO AI PASSAGGI O FRAINTENDIMENTI.
      Immagine 
      Potete adesso passare ad installare il bootloader Clover sulla vostra usb.
      *NOTA*:
      Avendo usato questo metodo l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      =========================
      METODO "MANUALE"....  (lascio per futura memoria-Compatibile fino a 10.12)
      ==========================
      Bootloader
      **Nota:** Installazione in UEFI  dipenderà dalla scheda madre in vostro possesso, quindi se non supporta tale opzione , il bootloader dovrà essere installato in  modalità Legacy.
       Vi invito, qualora non sapeste questa informazione, a recarvi nel sito ufficiale del produttore e controllare le informazioni a riguardo
      Fatto questo dobbiamo installare  Clover sulla usb.
      A seconda del tipo di Bios o al tipo di installazione che vogliamo fare UEFI o Legacy avremo ovviamente configurazioni diverse in questa fase.
      Lanciate il pkg.
      Immagine 

       
      Cambiate la destinazione di installazione ad USB oppure Install Mac_OS_X (a secondo del tipo di creazione eseguita)
      Successivamente clicchiamo su "Ad Hoc"
      Per Installazione UEFI
      Mettete i flag   : Installazione solo per avvio UEFI
                               : installare Clover nella ESP
                               : Driver64UEFI  AptioMemory --> (consigliato) ->  Link download
       Può essere solo aggiunto manualmente scaricando dal link sopra e collocandolo nella rispettiva cartella
       NOTA: in questo caso non selezionare nessun OsxAptioFixDRV durante l'installazione di clover oppure rimuovetelo                        successivamente. 
                               : Driver64UEFI  ApfsDriverLoader --> (consigliato) --> sostituisce l'uso del driver apfs.efi
                               : Selezionate l'altri driver come da successiva immagine,
       
      *Nota: Altri driver che si possono usare  al suo posto  sono:
       informazioni 
       
      Proseguite con l’installazione.
      Immagine 
      ** Ricordate che avrete accesso a questa cartella dopo aver montato la partizione EFI**
      ===========================
      Per installazione Legacy
      Immagine 
      ===========================
      Impostazione per config.plist:
      Con clover configurator “montate” la partizione EFI della usb.
      1) Per fare questo nel menù di sinistra, cliccate su “Mount EFI”
      2) individuate la partizione relativa alla vostra usb, a questo punto montiamo la relativa partizione EFI  selezionando l’apposito pulsante “Mount Partition”
      Immagine 
      3) Successivamente cliccate su “Open Partition”.. recatevi in EFI/Clover ed aprite il config.plist
      4) Sezione ACPI: Disabilitate tutti i fix sia del menù 1 che del menù 2
      Immagine 
      5) Sezione BOOT: Sole se si sta installando Yosemite mettete il flag su kext-dev-mode=1
      Immagine 
      6) Sezione RT Variables: Se si sta installando El Capitan oppure Sierra, aggiungere i valori: BooterConfig= 0x28, CsrActiveConfig= 0x67
      Immagine 
      7) Sezione System Parameters: Su inject kext mettete YES
      Immagine 
      ===========================
      Nota: Su El Capitan, è stato introdotto SIP (System Integrity Protection)
      Info:
      ===========================
      Recatevi in EFI/Clover/kext/10.x 
      X= alla versione di osx che state installando. Per esempio se installerete Yosemite dovrete recarvi nella cartella 10.10, con El Capitan in 10.11….ecc
      Se non ci fosse tale cartella, createla e nominatela voi a “modo”.
      Copiatevi all’interno FakeSmc.kext
      *Nota se venite già da altre vostre configurazioni, oltre kext sopra citato ,potete mettere gli altri necessari per il vostro hardware
      Stessa cosa se avete DSDT e/o SSDT potete copiarli in EFI/Clover/Acpi/Patched
      Immagine 
      
      Per High Sierra:
      Scaricare il driver apfs.efi a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
       
      Per chi volesse continuare ad usare HFS vi rimando a questo post:
        Come installare High Sierra in HFS direttamente dalla usb  
      Utenti Laptop:  Nel 99% è obbligatorio disattivare la grafica discreta Nvidia/Amd per installare questo nuovo osx
                                     Quindi aggiungete --> SSDT-Disable_DGPU.aml.zip
                                     in EFI/Clover/acpi/Patched della usb
      --------------------------------------------------------------------
      Per Mojave:
      Scaricare il driver apfs.efi per 10.14 a fine guida, collocarlo:
          --> EFI/clover/Driver64UEFI se stiamo usando UEFI
      --> EFI/Clover/Driver64 se stiamo usando Legacy
      Versione di clover non antecedente a V_4015
      Volete usare HFS?
      E' possibile fare un installazione diretta su altro disco o partizione, nel caso può essere usato anche per effettuare aggiornamenti...
      nel caso guardate...
       Mojave in HFS 
       Oppure direttamente da usb  
       
      Fatto questo avrete la vostra USB bootable per installare OSX.
      ………Non scordatevi Fakesmc.kext da mettere nella relativa cartella…. senza il quale non farete mai il Boot......
      *NOTA: se usato il terminale per la creazione della usb, l'installazione si dividerà in due fasi, perciò dopo il primo riavvio e necessario far partire nuovamente l'installer, selezionare lo stesso disco senza formattarlo.
      Finita questa ulteriore fase , l'installazione sarà terminata
      **NOTA** Se avete processori Broadwell,Skylake o Kabylake...usate FakeSmc.kext e relativi sensors che trovate all'interno del secondo pacchetto.. (potete usarlo anche sui precedenti senza problemi, essendo una versione più aggiornata ha ulteriore supporto per le cpu più recenti)
      Update: Fakesmc e sensors versione 6.26
      Post installazione... post #2           
       Buon Hack….. 
      Aggiornamento:Install_Mac_OS_X.command.zip (compatibile da 10.10 a 10.12)
      le info le trovate a questo post
      Ringrazio @Ciro82 che mi ha aiutato nel preparare questa guida.
      Pacchetto.zip
      Pacchetto-2.zip
      Pacchetto-Fake+Sensors 6.26.1440.zip
      C_I_M.zip
       
       
       
       
       
       
       
       
       
       
       
       
       
×