Recently Browsing 0 members
No registered users viewing this page.
MOJAVE HACKINTOSH GUIDE
**FOR** GIGABYTE Z390 AORUS PRO
CREDITS & THANKS
His help with EFI configuration and DSDT
Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, rehabman, Download-Fritz, Zenit432, cecekpawon Et al
autumnrain, slice2009, zenith432
ESP PRO MOUNTER
Hackintosh Vanilla Desktop Guide
/r/Hackintosh - corpnewt
JoniVR & theOneyouseek
• Intel I7 8700
• Gigabyte Z390 AORUS PRO
• Gigabyte AORUS RADEON RX 580 8GB ( connected to monitor with DisplayPort )
• Corsair Vengeance LPX 16GB ( 2 x 8GB ) 2666MHz – CMK16GX4M2A2666C16 In this build, both memory modules are installed in memory slots DDR4_A1 and DDR4_B1
• Corsair RM650x 80 Plus Gold Power Supply Unit
• Corsair H100i V2 AIO Hydro/Water RGB LED CPU Cooler
• Samsung EVO 500GB SSD (2.5) macOS Mojave
• Samsung EVO 250 GB SSD (2.5) Windows 10 Pro
• NZXT H500 Mid Tower ATX Case
• RECOMMENDED WIFI CARD → ABWB 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E) BCM943602CS
• WIFI and Bluetooth with BCM94331CD with PCI-e adapter (but will require AirportBrcmFixup.kext for AirDrop.. )
** Avoid Samsung EVO 970 PLUS as Hackintosh has problem with that device **
• HDMI Port on AMD RX580 / 590 ( Ensure you disable BIOS CSM if using HDMI on RX580 / RX590 )
• HDMI Port on Aorus Z390 Motherboard ( Ensure you have correct BIOS settings as per this guide for Intel only)
• Ethernet Port
• SSD Trim
• USB 3.0 & 2.0
• Hardware Acceleration
PREAMBLE - BEFORE YOU START
Here detailed, is all the steps towards building a successful and stable Aorus Pro Z390 Hackintosh, if you are a first time Hackintosher, this guide will have you quickly up and running with the Aorus Pro Z390 Hackintosh. To rule out any problems from the go,
only have the disc that you plan to install macOS Mojave connected to the Aorus Pro, disconnect any other Windows / Linux or data drives, external drives from your Aorus Pro. Windows / Linux and data drives can be connected after successful installation of macOS Mojave
If you have more than 16 GB of memory, then install macOS Mojave with just 16GB, you can later add any additional memory. Install memory modules in slots DDR4_A1 and DDR4_B1. This build has the Wi-Fi combo PCI-e adapter card installed in slot PCIEX1_3.
The WiFi/Bluetooth PCI-e Combo card used in this Aorus Pro guide has it's 9 pin USB cable attached to motherboard header F_USB2 and is enabled in SSDT-UIAC.aml ( USB ports fix ).
Do install macOS Mojave on its own physical drive, so do not try and install macOS Mojave onto a free partition on a disc that contains Windows.
Remove any Thunderbolt cards, Thunderbolt card can be reinserted after installation. Double check your BIOS settings are the same as this guide.
Following are unsupported / problematic
• Intel Optane ( if you have this, remove it before installation of macOS Mojave )
• Samsung EVO Plus drives ( firmware problem with macOS )
• XFX Radeon RX 580
• NVIDIA GTX / RTX not supported in macOS Mojave
• Fenvi T919 Wireless Card, it seems Bluetooth is not working out of box for some users ( Maybe the USB port attached to Fenvi bluetooth is wrongly configured, or the SSDT-UIAC.aml port connector was not configured as Internal, or maybe some other reason )
Save yourself a headache ---> RECOMMENDED WIFI CARD WORKING OUT OF BOX (OOB) is ---> ABWB 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E) BCM943602CS
Q - WILL THIS GUIDE WORK WITH MY NON AORUS Z390 MOTHERBOARD ?
A - Possibly may work with other Z390 chipset motherboards, but you will have to remove SSDT-UIAC.aml from Clover / ACPI / patched from the PRE-INSTALL EFI and enable the ports limit patch.
Q - I notice you have the Aorus Pro Z390 version, will this guide work with Aorus Pro Z390 WiFi version ?
A - Yes, but onboard Intel / Intel CNVi WIFII /Bluetooth will not work with macOS and you will have to disable HS14 for Bluetooth to function properly on BCM943602CS or BCM94331CD WiFi/Bluetooth Combo cards ( more info at bottom of guide) .
PART 1 - DOWNLOAD
Download the following:
• PRE-INSTALL Aorus Pro Z390 EFI - RX580.zip
• POST-INSTALL Aorus Pro Z390 EFI - RX580.zip
// INTEL UHD 630 EFI Aorus Pro Z390 EFI's below. For those who do not have a Graphics Card Installed in PCIe Slot, requires Initial Display Output BIOS setting to be changed to IGFX spoiler below!
• PRE-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip
• POST-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip
• ESP MOUNTER PRO v1.9
• macOS MOJAVE
• CLOVER CONFIGURATOR
• EmuVariableUefi-64.efi ( Used only to initialise iMessages. It then must be removed from Clover drivers64UEFI folder as will cause intermittent memory allocation errors on boot, explained in guide)
• Native Display Brightness with MonitorControl
// Not really needed but IF no sound on Wake from Sleep then use SSDT-ALC1220 and CodecCommander
• SSDT-ALC1220.aml ( Resolves Audio Sound on Wake, place in Clover / ACPI / Patched )
• CodecCommander.kext.zip ( Resolves Audio Sound on Wake, place in Clover / Kexts / Other )
PART 2 - BIOS SETTINGS (version F9 )
Here is a list of the BIOS settings that I have used ( Screenshots in spoiler below )
• Enter BIOS → Press F12 → Enter Setup
• Save & Exit → Load Optimized Defaults
• BIOS → Windows 8/10 Features → Other OS
• BIOS → CSM Support → Enabled
• Peripherals → Initial Display Output → PCIe 1 Slot
• Peripherals → Trusted Computing → Security Device Support → Disable
• Peripherals → Intel(R)Bios Guard → Intel BIOS Guard Support → Disable
• Peripherals → USB Configuration → Legacy USB Support → Enabled
• Peripherals → USB Configuration → XHCI Hand-off → Enabled
• Peripherals → Network Stack Configuration → Network Stack → Disabled
• Peripherals → SATA And RST Configuration → SATA Mode Selection → AHCI
• Chipset → Vt-d → Enabled
• Chipset → Internal Graphics → Enabled
• Chipset → DVMT Pre-Allocated → 256M
• Chipset → DVMT Total Gfx Mem → MAX
• Chipset → Audio Controller → Enabled
• Chipset → Above 4G Decoding → Disabled
• Power → ErP → Disabled
• Power → RC6 (Render Standby) → Disabled
// IF USING CORSAIR H100i V2 AIO CPU WATER COOLER
• MIT → Smart Fan 5 Settings → CPU Fan Control mode → PWM
• Save & Exit → Save & Exit Setup
SCREEN DUMP SPOILERS
PART 3 – CREATE A MOJAVE USB FLASH INSTALLER
Prepare USB Installer for Mojave ( Video below )
• Insert USB drive
• Launch /Applications/Utilities/Disk Utility
• Disk Utility → View → Show All Devices
• On Left-hand panel → External →(Identify your USB device in left hand panel)
• Click and highlight your USB device in the left-hand panel.
• Click erase button.
• Name: USB
• Format: Mac OS Extended (Journaled )
• Scheme: GUID Partition Map
• Click Erase button.
• Place the downloaded MacOS Mojave app into Applications folder.
• Open Terminal copy and paste:
sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USB --nointeraction && say Mojave Drive Created • Enter
PART 4 – INSTALL CLOVER ON THE MOJAVE USB INSTALLER
Make Mojave USB flash drive installer bootable.( Video below )
• Launch Clover application, double click.
• Click Continue → Continue → Continue
• Click Change Install Location button.
• Click Install macOSMojave USB installer → Continue
• Click Customise button
Clover for UEFI booting only Install Clover in the ESP Themes UEFI Drivers • Click Install button
• Installation Complete!
PART 5 – CUSTOMIZE MOJAVE USB INSTALLER FOR AORUS Z390 PRO
Replace Clover EFI folder with PRE-INSTALL Aorus Pro Z390 EFI - RX580.zip OR if NO graphics card installed in PCIe slot, then use PRE-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip( Video below )
• Install ESP Mounter Pro v1.9
• Using ESP Mounter Pro, Mount ESP on disk2s1 ( Your disk name may be different )
• Open mounted EFI partition found on desktop
• Copy all the contents from Aorus 390 Pro EFI folder
• Replace USB EFI folder with all the contents inside the Aorus 390 Pro EFI folder.
PART 6 – INSTALL MAC OS MOJAVE ON INTERNAL DRIVE
ENSURE BIOS: Above 4G Decoding is set to Disabled
if Above 4G decoding is set to enabled then macOS Mojave install will freeze at 2 mins remaining and will not shut down properly!!!!
Please be patient during install, so when install gets to 2 or 3 mins remaining then it may take extra time. Be ready to boot from UEFI USB installer by pressing F12 when install initiates restarts.
• INSERT USB INSTALLER INTO THE USB 2.0 PORT
Here is a walkthrough of the full process using the macOS Mojave USB Installer on the Aorus Z390 Pro.
• Power on PC and press F12• Choose bootable USB drive from boot menu.
• Install macOS Mojave to internal solid state or hard drive.
When system returns to the Clover boot menu choose:
• Boot macOS Install from Macintosh
At next restart, press F12 and boot from external UEFI USB device and choose:
• Boot macOS Install from Macintosh
Proceed with macOS Mojave install
macOS Mojave is now installed, but it can only boot at this moment thanks to FakeSMC and Clover on the Mojave USB flash drive installer.
PART 7 – MAKE AORUS Z390 PRO INTERNAL DRIVE BOOTABLE
Make internal drive bootable ( Video below )
So far, the Aorus Pro can only boot the internal system drive with the aid of the Mojave USB Installer.
To boot from the internal system drive without the installer:
Download and install Clover with RC Scripts on target volume.
If your Aorus Pro Z390 has AMD RX 580 then copy the EFI folder from inside POST-INSTALL Aorus Pro Z390 EFI - RX580.zip folder and paste it inside the the System Drive EFI partition. OR
If your Aorus Pro Z390 has no graphics card installed in PCIe slot, then copy the EFI folder from inside POST-INSTALL Aorus Pro Z390 EFI - Intel UHD630.zip folder and paste it inside the the System Drive EFI partition.
• Remove USB Mojave installer and shut down and restart.
Aorus Hackintosh should now be able to boot to macOS Mojave, Done, well almost !
PART 8 – ENABLE IMESSAGES & FACETIME
// UPDATE 21st MAY 2019
Past experience suggests Clover Configurator now automatically populates correct values for working iMessages when you select an SMBIOS.
After selecting SMBIOS, example iMac19,1 for Aorus Pro with RX580 ( image above ) then go to Apple and ensure you have the "serial number is not valid " message. Done!
If you still have problems connecting to iMessage, test and ensure that AirDrop is working, then follow instructions inside spoiler.
• Mount internal drive EFI/ESP partition
• Go to folder CLOVER → drivers64UEFI
• Place both EMUVariableUefi-64.efi inside → drivers64UEFI
Using Clover Configurator, add the following argument to config.plist using Clover Configurator.
• Slide = 0
Shutdown and then press power on button on PC.
• You should now be able to Log into iCloud, iMessages and FaceTime
• NOW delete EMUVariableUefi-64.efi from CLOVER → drivers64UEFI Folder
• Shutdown and restart Aorus Pro hackintosh. iMessages etc is now operational without EMUVariableUefi-64.efi ( EMUVariableUefi-64.efi only needed to initialise iMessages )
// UPDATE 22nd May 2019
• It seems that there are no "Couldn't allocate runtime area" errors when continuing to use EMUVariableUefi-64.efi since updating to macOS Mojave 10.14.5 and using Clover version r4920.
• It is important to delete EMUVariableUefi-64.efi, this will avoid very intermittent boot errors such as: “Couldn’t allocate runtime area” post errors.
PART 9 – ENABLE TRIM for Solid State Flash Drives
Open Terminal and enter the following command:
sudo trimforce enable
DEFAULT SSDT – USB PORTS FIX CONFIGURATION WITH FRONT USB-C - SSDT ALREADY INSIDE AORUS Z390 EFI FOLDER – Provided by @AudioGod
If you have USBC on Computer Chassis / Case, then SS01 and SS02 is mapped to that USB C port
------------ GUIDE FINISHED YOU SHOULD NOW HAVE WORKING AORUS Z390 PRO HACKINTOSH WITH SSDT USB FIX ------------
OPTIONAL: Set Wi-Fi Country Code
OPTIONAL: System Information - PCI
OPTIONAL: Enable HDMI Audio on RX580
OPTIONAL: Native Display Brightness - with MonitorControl
OPTIONAL: Dual Boot macOS Mojave & Windows 10
OPTIONAL: Replace the default "About This Mac" Apple Logo with RED AORUS APPLE
OPTIONAL - ALTERNATIVE SSDT 1 – SSDT Ports configuration below - replace SSDT inside Clover /ACPI/PATCHED folder
OPTIONAL - ALTERNATIVE SSDT 2 - SSDT Ports configuration below - replace SSDT inside Clover /ACPI/PATCHED folder
OPTIONAL - ALTERNATIVE SSDT 3 – Create your own SSDT
FRAMEBUFFER PATCHING – For working Intel UHD 630 Graphics, working HDMI Port, working HDMI Audio on Aorus Z390 Pro
AORUS PRO Z390 WIFI version with Intel CNVi – Disable Bluetooth on HS14
Resolve bluetooth issue reported by @eSaF
CLOVER – Updating / Upgrade Clover boot loader
RECOMMENDED READING – Excellent Hackintosh Vanilla guide created by CorpNewt with in depth tutorial on Clover.
FOR MORE HACKINTOSH INFORMATION SUCH AS USB PORTS FIX, CLOVER CONFIGURATOR, HACKINTOSH BACKUP WITH CARBON COPY CLONER ..... THEN SEE MY PREVIOUS GUIDE FOR ASUS Z370-G Strix
GigaByte Z390 M Gaming
Intel Core i9-9900K
CoolerMaster MasterLiquid ML120R RGB
Corsair Dominator Platinum 16GB (2 x 8GB)
Sapphiretech Radeon RX 590 8 GB GDDR5
Samsung 970 EVO NVMe M2 Flash Drive
EVGA 750 N1, 750W
TP-Link Archer T9E
Thermaltake View 21 Tempered Glass Edition
-FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE 10 ID -DMAC -REMOVE 22K LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM / REAL TIME CLOCK -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -MIKEY -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -OPERATION REGION GPIO -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES
--USB-C-- test with SanDisk Ultra USB-STICK 128gb
-Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
We're all here to have fun and learn from each other!
I'm new here and French.
I success to hack my Asus X751LJ and pass it to High Sierra 10.13.6, not easily, and everything works except the keyboard and the touchpad.
I tried VoodooPS2Controller, ApplePS2SmartTouchpad, even VoodooI2C, but nothing works...
Could someone help me? Is there a DSDT problem? Witch kext should I use?
I post my ACPI and Kexts folders and my IOReg.
Please... Help me. I'm desperate...
MacBook Pro de Candrahm.ioreg
This project is dedicated to the memory of Mausi, the cat I loved more than anybody else.
A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports:
82578LM 82578LC 82578DM 82578DC 6 and 7 Series
82579LM 82579V 8 and 9 Series
I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series (since V2.1.0d0)
I219LM I219V 200 Series (since V2.3.0d0)
I219LM I219V 300 Series (since V2.4.0d0)
Key Features of the Driver
Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled due to hardware bugs). Fully optimized for Sierra (64bit architecture) but should work with older 64bit versions of macOS too, provided you build from source with the appropriate SDK for the target OS. Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2.
The driver has been tested successfully with I217V, I218V and 82579V under 10.9.5 and above. The attached archive includes source code as well as a prebuilt binary (debug version) for Mavericks and newer versions of macOS. Known Issues
There seem to be problems while using VMware with version 1.x.x of the driver. In case you are affected use version 2.0.0 or newer.
Could you add support of for...? Well, you are probably asking me to add support for one of the older NICs like the 82571/2/3/4L or 82583 and the answer will be no as I dropped support for these chips intentionally. They are broken and I lost more than 2 weeks trying to make it work on the 82574L without success. I was asked to add support for I210, I211 and I350 but as these chips have a completely different architecture, which isn't supported by the underlying Linux driver, this is impossible, sorry. Does it work with Snow Leopard or 32 bit kernels? No and I have no plans to make a version for 32 bit kernels or anything older than Lion. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5.
Goto /S/L/E and delete AppleIntelE1000e.kext. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface.
Help - I'm getting kernel panics!
Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.
Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me. Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any AppleIntelE1000e.kext from your system because it could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000. In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable. Changelog
Version 2.4.0 (2018-04-14) Added support for 300 series versions of I219LM and I219V. Updated underlying Linux source code. Version 2.3.0 (2017-06-20) Added support for 200 series versions of I219LM and I219V. Version 2.2.0 (2016-09-23) Disabled TSO to work around a hardware bug. Version 2.1.0 (2016-05-24) Added support for I219LM and I219V Version 2.0.0 (2015-04-22) First official release which is identical to 2.0.0d2 (only the version number has been changed). Version 2.0.0d2 (2015-04-04) Changed the tx descriptor write back policy for 82579, I217 and I218 to prevent random tx deadlocks. Version 2.0.0d1 (2015-03-14) Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ Solves the VMware issue. Version 1.0.0d6 (2015-03-04) Reworked TSO6 support to avoid problems with VMware. Wake-on-LAN now working. Version 1.0.0d5 (2015-02-27) Reworked TSO4 support to eliminate the bug of 1.0.0d4. Added some debug code in order to collect information about the VMware related issue. Version 1.0.0d4 (2015-02-25) Set total length field of the IP-header to zero for TSO4 operations. Report EEE activation state in kernel log message when the link has been established. Version 1.0.0d3 (2015-02-11) Reworked media selection and EEE support (EEE is now activated when both link partners support it. It can be disabled selecting the medium manually). Duplex setting for 10/100 MBit connections is now reported correctly. The number of tx descriptors has been reduced from 2048 to 1024. The code has been cleaned up and obsolete files have been removed. Version 1.0.0d2 (2015-01-31) First development release. Getting the Driver
The source code can be found on GitHub: https://github.com/Mieze/IntelMausiEthernet There is also a prebuilt binary for 10.11 and above in the download section: http://www.insanelymac.com/forum/files/file/396-intelmausiethernet/ Build from Source for 10.8
Register as a developer on Apple's developer website. A free membership is sufficient. Download a copy of Xcode 5.1.1 and install it on your machine. In the project select 10.8 as the "Base SDK" and the "Deployment Target". Call "Archive" from the menu "Product" and save the built driver. Credits
Thanks to RehabMan and Yung Raj for running tests and pointing me in the right direction while I was trying to fix TSO. Special thanks to Yung Raj for motivating me when I was about to give up.
DSDT Request - random restarts, shutdown fix, glitches caused by GPU or memory (X99, i7 5820k, 1060)By Gorec
I apologize in advance if I didn't post in the right category and if my title and description aren't specific enough :c
My config in a nutshell:
CPU: i7 5820k GPU: MSI GTX 1060 3GB RAM: 16 GB MOBO: MSI X99 SLI PLUS I attached RunMe output with all the details of my built.
I have my Hackintosh for about half a year. That time I managed to make it works and fix major issues, but some of them left unresolved since then and I ignored them until now.
I use my Hackintosh for Adobe projects (PR, AE, PS, IL, AU and a lot more) - most of them connected with video editing of course browsing with Chrome and other small tasks.
Random restarts - this is the biggest one. I'm starting to work on bigger and bigger projects and at this time I think I can't allow this to happen that often. In the past, they happened like once a day or a couple of times a week. However, now it's just frustrating when it happens even 5 or more times a day. I've tried to observe and find out what can be the cause but I haven't managed to find any connections. I thought it happens when Premiere or another app is using GPU, but I haven't seen increased usage when it restarts. I think that it can be connected with GPU, memory or PSU or... meh, anything else. I don't have resources to check if it'll work with other components. There should be some fix for this. I will really appreciate any help with this :c Restart instead of shutdown & sleep doesn't work. I've tried to look through some Google results for this and tried many solutions (as you can see in attached Clover folder), but I think the right one for many of these issues is to make my own DSDT. Glitches, freezes and other things while encoding a video. It happens very often when I try to do this. Maybe it is an issue with GPU or (hopefully) only with GPU drivers which can be fixed with some patch. Today my headphones stopped working. I have a multi-output device configured in the Audio MIDI Setup app which includes my headphones (HyperX Cloud via USB) and Soundflowerbed virtual audio device for capturing system audio. Today while I was trying (like 15 times) to encode a video in Media Encoder in the background and watch video on YouTube I stopped hearing anything from my system. Of course, it restarted a couple of times as always, but even this didn't solve this. If I plug them directly with mini jack (not via USB Soundcard which was in the box and which I always used) in the front IO or the back I only hear some loud noise It takes EX-Fat formatted volumes a few minutes to mount after each restart. I found a workaround to format it with NTFS since I have Tuxera installed and I will reformat these volumes when I will find time for this, but maybe there is some fix for this. GPU is a little bit hot. HW Monitor shows it is only 45-55 degrees, but for my hand is a little bit hot, idk. Also related to GPU - glitch after POST but before entering Clover boot menu. It is a black screen with little white squared glitches for a few seconds. Maybe it indicates the GPU drivers are loading, but maybe it shouldn't be like this. And if I can ask about that - I can't make all applications hide on startup. I, obviously, have "Hide" checkbox checked on every login item in settings, but it doesn't work, none of the apps is hidden in the dock. Is there a way to fix this? Also a small but annoying problem - I can't turn off permanently Mojave update notification (since I tried to install it, and I had to reverse to High Sierra because I had a black screen and I didn't have time for repairing all of them. Tags are not working in Finder - every time I tag a file or folder and make a change in it (for example save a text file) the tag disappears.
So, with knowing all of that, is there a way to make a proper DSDT file for my Hackintosh? I tried to look through some guides on how to make it but I think I reached my abilities to understand how Mac OS works and what all of these things are, so I'm asking you guys politely, would someone like to help me? At least with these random restarts? :/
I really begin to think that I'm a newbie in configuring all of that Clover things - even after what I managed to do with my PC. Help me, pleease... :c
If you have any questions post it below, I will really appreciate any help <3
Send me MBP-Gorec.home.zip