cat2devnull Posted February 14, 2019 Share Posted February 14, 2019 Introduction:So this build has been very challenging as the Z390 platform is fairly new. I struggled for some days trying to get USB, power management and onboard graphics working. You need to do a bit of work customising your own plist and SSDT but if you do, your rig will not disappoint.The guide below should work for any of the ASUS Z390 boards but may require some minor SSDT changes to configure your USB ports but it’s not that hard to do as long as you are willing to read the motherboard manual and do some very basic text file editing.Hardware: Motherboard: ASUS TUF Z390M-Pro Gaming CPU: Intel Coffeelake Core i9-9900k Cooling: Be Quite Dark Rock Pro 4 RAM: G.Skill Ripjaws V 32GB 2X16GB DDR4 3200MHz CL16 Disk: Samsung 970 EVO 2TB NVMe 1.3 M.2 (2280) Ethernet: Onboard Intel I219V Wifi/BT: Broadcom BCM943602CS + PCI-e adapter (Ebay Special) Audio: Onboard Realtek ALC S1200A Graphics: Onboard Intel UHD 630 USB: Onboard Intel Z390 Chipset Working: Onboard USB, audio, ethernet, graphics Wifi and BT via the PCI-e adapter Reboot, shutdown, hibernate, sleep/wake iCloud, iMessage, FaceTime, Time Machine GPU Hardware acceleration RAM XMP (3200MHz) Not Working: USB: I’ve disabled two of the rear USB ports to keep under the 15 port limit. I tried the USB port limit patch but had no luck getting it working. Also the general consensus is that using >15 USB ports is a bad idea and can cause unexpected crashes/data-corruption. iTunes Streaming (I have not investigated this as I don’t use iTunes). Clover auto boot from OS partition (this has me stumped at the moment). Onboard HDMI port during installation (used DP instead). Not Investigated (yet): USB 3.1 Gen 2 and USB-C (I don’t have any such devices) Overclocking or exceeding the 95W TDP of the i9900k Upgrade to Mojave 10.14.3 Install Procedure:This install guide should work with any version of 10.14 but I have only tried 10.14.2 since that was the current version at the time I started this process.BIOS settings (v2.20.1271): Advanced\System Agent (SA) Configuration\VT-d - Disabled Advanced\System Agent (SA) Configuration\Above 4G - Decoding Enabled Advanced\USB Configuration\Legacy USB Support - Disabled Advanced\USB Configuration\XHCI Hand-off - Disabled What you will need: 8GB USB drive (preferably USB 2.0, see below) ASUS Motherboard manual Clover v2.4 r4871 Clover Configurator v5.4.1.1 MaciASL IORegistryExplorer Kexts (all versions are the minimum required): AppleALC v1.3.5 (needed for the Realtek ALC S1200A) IntelMausiEthernet 2.5.0 USBInjectAll from RehabMan v0.7.1 (2018-1108) VirtualSMC v1.0.2 (replaces the older FakeSMC) Lilu 1.3.1 WhateverGreen 1.2.6 This Guide is based on the amazing /r/Hackintosh Vanilla Desktop Guide and follows it with some critical additions that will fix USB, sleep/reboot/hibernate and a few other issues. It is expected that you have a basic understanding of Mac OSX, Clover, Clover Configurator and command line tools such as text editors. If not, give the below a go, and just Google when you get stuckFollow the /r/Hackintosh Vanilla Desktop Guide to do the following; Gather all your kexts as listed above. They can be downloaded and placed in /EFI/CLOVER/kexts/other/ by hand or most can be installed automatically by Clover configurator via the Kexts Installer menu. Build your USB installer. Perform your Clover setup. Update your config.plist file to include all the Coffee Lake specific configuration. Here are some specific alterations to the vanilla build that were required; Acpi I added a few extra patches which were used for USB testing and are probably not required once setup. All of which can be installed from the List Of Patches pulldown. -> change EHC1 to EH01 -> change EHC2 to EH02 -> change _OSI to XOSI Boot You should be able to remove the verbose (-v) option as hopefully it will not be required. Added slide=0 to fix various boot issues. Unfortunately I don’t remember exactly what those errors were or which forum post helped me identify the issue. Added darkwake=10 to fix issues with power nap. Kernel and Kext Patches I disabled the USB port limit patches because the didn’t work and can cause stability issues if left enabled. See the USB section below for more details. SMBIOS Set the Product Name to Macmini8,1 I found that since the Macmini8,1 is based on Coffee Lake and uses the Intel UHD 630 onboard graphics seemed to work better than when set to iMac18,1 which caused random graphical glitches. You shouldn’t need to use macserial to generate the Serial Number or board number, just hit this Generate New button and let Clover Configurator sort it for you. You will still need to verify that the serial number is safe to use with Check Coverage button. USB:By now you should have a bootable USB drive with a near working configuration. The last remaining issue is getting USB working. This is the step that most people get stuck. There are a few issues with USB on Hackintosh that cause problems; You are limited to 15 USB ports. Now this might sound like lots but each physical port usesone port if it is USB 2.0 but if it supports USB 3.1 then it counts as two ports (both a USB 2.0 and USB 3.1 in the one physical port). There are various patches out there which remove this limit but even if you can get them to work, they will probably break when you upgrade and can cause system instability. OSX has a fixed size memory array to store this data and if you have more than 15 ports it can overwrite other critical memory. All 300 series motherboards (in our case the Z390) have way more than 15 USB ports. If you don’t bother fixing this issue then on the 300 series boards you will most likely enumerate 15 USB 2.0 ports before the system ever gets a chance to find the USB 3.1 ports. As such all your USB ports will be locked to USB 2.0. This means if you install off a USB 3.x drive, it will fail part way through the install when the ports get locked to USB 2.0 and the drive can no longer be seen. So in order to fix this problem you have to build your own SSDT file to tell the system which ports to enable, where they are on the XHC bus and what version of USB they support. I used the guide from RehabMan (Creating a Custom SSDT for USBInjectAll.kext) to build mine.Now the catch will be that you probably need to boot into OSX in order to be able to map the USB port locations to create the SSDT file. If you need to do this, you must install from a USB 2.0 drive as discussed above.The other option is just try and guess the location of each port. I mapped them all out and then realised that ASUS actually named each port sensibly so I could have just worked it out if I bothered to read the manual and look at the motherboard layout diagram.So for the ASSUS ASUS TUF Z390M-Pro Gaming the port layout looks like this; Intel® Z390 Chipset : 2 x USB 3.1 Gen 2 port(s) (1 at back panel, teal blue, Type-A, 1 at mid-board) Intel® Z390 Chipset : 7 x USB 3.1 Gen 1 port(s) (4 at back panel, blue, Type-A, 1 x Type-C, 2 at mid-board) Intel® Z390 Chipset : 4 x USB 2.0/1.1 port(s) (4 at mid-board) Location/Type BIOS & Motherboard Manual Description XHC High Speed Identifier XHC Super Speed Identifier Back Panel above HDMI upper port Blue Type-A U31G1_5 HS05 SS05 Back Panel above HDMI lower port Blue Type-A U31G1_6 HS06 SS06 Back Panel USB 3.1 Gen 2 Teal Type-A U31G2_1 HS01 SS01 Back Panel USB 3.1 Type-C U31G1_C2 HS02^ SS02^ Back Panel below ethernet upper port Blue Type-A U31G1_7 HS07 SS07 Back Panel below ethernet lower port Blue Type-A U31G1_8 HS08 SS08 Onboard Connector USB 2.0 Left Header USB11 & USB12 HS11 & HS12 N/A Onboard Connector USB 2.0 Right Header USB3 & USB4 HS03 & HS04 N/A Onboard Connector USB 3.1 Header U31G1_9 & U31G1_10 HS09 & HS10 SS09 & SS10 Onboard USB 3.1 Gen2 Header U31G2_C3 HS13^ SSxx^ ^Unable to confirm as do not have any device to test on these ports.The motherboard manual and BIOS names for each port map perfectly to the XHC name so if this holds true for other ASUS 300 series motherboards (which it appears from my research that they do) then you probably can just build the .dsl file by hand.Building your own custom SSDT file as per Creating a Custom SSDT for USBInjectAll.kext; Start by grabbing SSDT-UIAC-ALL.dsl from RehabMan’s OS-X-USB-Inject-All repository. Delete all sections of the XHC configuration that do not match your XHC device-id. In this case the Z390 chipset is “8086_a36d”. You can confirm this with IORegistryExplorer. Look for /Root/Macmini8,1/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/XHC@14 then it should be listed as IOName. Now decide which ports you want to enable and which you want disabled remembering that you can only have a maximum of 15. In my case I disabled all the USB 2.0 internal ports except for one which is connected to the Broadcom BCM943602CS for BlueTooth. I also disabled a few of the USB 3.1 ports that I don’t need. Just comment out the ports you don’t need so that if in future you want to make changes it is easy. Check that the USB Connector values are correct. USB2=0, USB3=3, internal=255 Now compile the SSDT-UIAC-ALL.dsl to SSDT-UIAC.aml In MaciASLFile: Save As, format: ACPI Machine Language Binary and place it in /EFI/ACPI/patched. USBInjectAll.kext will now enable only the USB ports you have configured. My file looks like the following; // SSDT-UIAC.dsl // // This SSDT can be used as a template to build your own customization // for USBInjectAll.kext for the ASUS TUF Z390M-Pro Gaming motherboard. // It would be very easy to modify this file for any ASUS Z390 motherboard. // // Ports have comments on each to help identify their location. // You can disable ports by commenting out their configuration. // To avoid errors, this file is best edited in MaciASL. // // Note: UsbConnector: USB2 = 0, USB3 = 3, internal = 255 DefinitionBlock ("", "SSDT", 2, "hack", "_UIAC", 0) { Device(UIAC) { Name(_HID, "UIA00000") Name(RMCF, Package() { "8086_a36d", Package() { "port-count", Buffer() { 26, 0, 0, 0 }, "ports", Package() { // "HS01", Package() // U31G2_1 - Back Panel USB 3.1 Gen 2 Blue Type-A // { // "UsbConnector", 3, // "port", Buffer() { 1, 0, 0, 0 }, // }, // "HS02", Package() // U31G1_C2 - Back Panel USB 3.1 Type-C // { // "UsbConnector", 3, // "port", Buffer() { 2, 0, 0, 0 }, // }, // "HS03", Package() // USB3 - Onboard Connector USB 2.0 Right Header // { // "UsbConnector", 0, // "port", Buffer() { 3, 0, 0, 0 }, // }, "HS04", Package() // USB4 - Onboard Connector USB 2.0 Right Header { "UsbConnector", 0, "port", Buffer() { 4, 0, 0, 0 }, }, "HS05", Package() // U31G1_5 - Back Panel above HDMI upper port Blue Type-A { "UsbConnector", 3, "port", Buffer() { 5, 0, 0, 0 }, }, "HS06", Package() // U31G1_6 - Back Panel above HDMI lower port Blue Type-A { "UsbConnector", 3, "port", Buffer() { 6, 0, 0, 0 }, }, "HS07", Package() // U31G1_7 - Back Panel below ethernet upper port Blue Type-A { "UsbConnector", 3, "port", Buffer() { 7, 0, 0, 0 }, }, "HS08", Package() // U31G1_8 - Back Panel below ethernet lower port Blue Type-A { "UsbConnector", 3, "port", Buffer() { 8, 0, 0, 0 }, }, "HS09", Package() // U31G1_9 - Onboard Connector USB 3.1 Header { "UsbConnector", 3, "port", Buffer() { 9, 0, 0, 0 }, }, "HS10", Package() // U31G1_10 - Onboard Connector USB 3.1 Header { "UsbConnector", 3, "port", Buffer() { 10, 0, 0, 0 }, }, // "HS11", Package() // USB11 - Onboard Connector USB 2.0 Left Header // { // "UsbConnector", 0, // "port", Buffer() { 11, 0, 0, 0 }, // }, // "HS12", Package() // USB12 - Onboard Connector USB 2.0 Left Header // { // "UsbConnector", 0, // "port", Buffer() { 12, 0, 0, 0 }, // }, // "HS13", Package() // Unknown // { // "UsbConnector", 3, // "port", Buffer() { 13, 0, 0, 0 }, // }, // "HS14", Package() // Unknown // { // "UsbConnector", 3, // "port", Buffer() { 14, 0, 0, 0 }, // }, // "SS01", Package() // U31G2_1 - Back Panel USB 3.1 Gen 2 Teal Type-A // { // "UsbConnector", 3, // "port", Buffer() { 17, 0, 0, 0 }, // }, // "SS02", Package() // U31G1_C2 - Back Panel USB 3.1 Type-C // { // "UsbConnector", 3, // "port", Buffer() { 18, 0, 0, 0 }, // }, // "SS03", Package() // Unknown // { // "UsbConnector", 3, // "port", Buffer() { 19, 0, 0, 0 }, // }, // "SS04", Package() // Unknown // { // "UsbConnector", 3, // "port", Buffer() { 20, 0, 0, 0 }, // }, "SS05", Package() // U31G1_5 - Back Panel above HDMI upper port Blue Type-A { "UsbConnector", 3, "port", Buffer() { 21, 0, 0, 0 }, }, "SS06", Package() // U31G1_6 - Back Panel above HDMI lower port Blue Type-A { "UsbConnector", 3, "port", Buffer() { 22, 0, 0, 0 }, }, "SS07", Package() // U31G1_7 - Back Panel below ethernet upper port Blue Type-A { "UsbConnector", 3, "port", Buffer() { 23, 0, 0, 0 }, }, "SS08", Package() // U31G1_8 - Back Panel below ethernet lower port Blue Type-A { "UsbConnector", 3, "port", Buffer() { 24, 0, 0, 0 }, }, "SS09", Package() // U31G1_9 - Onboard Connector USB 3.1 Header { "UsbConnector", 3, "port", Buffer() { 25, 0, 0, 0 }, }, "SS10", Package() // U31G1_10 - Onboard Connector USB 3.1 Header { "UsbConnector", 3, "port", Buffer() { 26, 0, 0, 0 }, }, // "USR1", Package() // { // "UsbConnector", 255, // "port", Buffer() { 15, 0, 0, 0 }, // }, // "USR2", Package() // { // "UsbConnector", 255, // "port", Buffer() { 16, 0, 0, 0 }, // }, }, }, }) } } //EOF Now you should be able to perform a successful install of Mojave. Once you are up and running, copy the EFI folder from your USB to the EFI partition on your SSD/HDD and you should be good to go.iMessage, iCloud and FaceTime:If you get errors enabling these services, you can try this simple repair guide from Hackintosher to get up and running.Files:If it helps I have uploaded all my config files to Dropbox so you can see what I did.If you copy my config.plist file, be aware that I have removed the following keys; SerialNumer SmUUI BoardSerialNumber Memory You will need to generate these keys for yourself. Good Luck! 5 2 Link to comment Share on other sites More sharing options...
RandomTech Posted February 14, 2019 Share Posted February 14, 2019 Very nice and detailed guide, I actually don't have this configs but it still encourages me to upgrade to i9 from 8700K Link to comment Share on other sites More sharing options...
MaLd0n Posted February 14, 2019 Share Posted February 14, 2019 some extra fine tunning here https://olarila.com/forum/viewtopic.php?f=45&t=8730 nice hardware Link to comment Share on other sites More sharing options...
zac840 Posted May 21, 2019 Share Posted May 21, 2019 (edited) Hi, This is my first post on this forum. I found the original post here very helpful thanks cat2devnull, so figured I should give back. I am also using an Asus TUF Z390M PRO (non WI-FI) motherboard and just the iGPU (i5 9600k). Currently running the latest kexts mentioned by the OP (excluding the Light and Battery ones) and the latest clover bootloader seems to be working fine with the latest Mojave 10.14.5 from the light testing I've done so far. Here are a few issues and solutions I ran into. 1. Kernel Panic trying to boot from USB to install. Fixed by DVMT Pre-Allocated from 32M to 64M in the bios 2. I stupidly updated the BIOS to the latest (Version 2401) before doing any research and it results in an uninitialised variable in Device(RTC) that makes OSX DSDT parser freak out. Fixed using a patch I found for an Asrock Motherboard worked fine on the Asus board. <dict> <key>Comment</key> <string>Fix AsRock and Asus Z390 BIOS DSDT Device(RTC) bug</string> <key>Disabled</key> <false/> <key>Find</key> <data> oAqTU1RBUwE= </data> <key>Replace</key> <data> oAqRCv8L//8= </data> </dict> Credit to 'pupin' in this thread: https://www.tonymacx86.com/threads/mojave-on-asrock-z390-phantom-gaming-itx-ac.265245/ 3. Trying to use the HDMI port results in a black screen once the installer initialises. Fixed using this frame buffer patch for (ASUS Prime Z390-A etc) I don't think it's perfect because it lists 3 ports and my motherboard only has 2 (DP and HDMI) but I haven't tried creating my own patch yet. <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,ig-platform-id</key> <data> BwCbPg== </data> <key>device-id</key> <data> mz4AAA== </data> <key>framebuffer-con0-busid</key> <data> AgAAAA== </data> <key>framebuffer-con0-enable</key> <data> AQAAAA== </data> <key>framebuffer-con0-flags</key> <data> xwMAAA== </data> <key>framebuffer-con0-index</key> <data> AgAAAA== </data> <key>framebuffer-con0-pipe</key> <data> CgAAAA== </data> <key>framebuffer-con0-type</key> <data> AAgAAA== </data> <key>framebuffer-con1-busid</key> <data> BAAAAA== </data> <key>framebuffer-con1-enable</key> <data> AQAAAA== </data> <key>framebuffer-con1-flags</key> <data> xwMAAA== </data> <key>framebuffer-con1-index</key> <data> AwAAAA== </data> <key>framebuffer-con1-pipe</key> <data> CAAAAA== </data> <key>framebuffer-con1-type</key> <data> AAgAAA== </data> <key>framebuffer-con2-busid</key> <data> AQAAAA== </data> <key>framebuffer-con2-enable</key> <data> AQAAAA== </data> <key>framebuffer-con2-flags</key> <data> xwMAAA== </data> <key>framebuffer-con2-index</key> <data> AQAAAA== </data> <key>framebuffer-con2-pipe</key> <data> CQAAAA== </data> <key>framebuffer-con2-type</key> <data> AAQAAA== </data> <key>framebuffer-patch-enable</key> <data> AQAAAA== </data> </dict> </dict> Credit here https://www.tonymacx86.com/threads/guide-general-framebuffer-patching-guide-hdmi-black-screen-problem.269149/ 4. AppleALC I set the layout-id (inject) to 3 instead of 1 as my motherboard only has the 3 audio ports and not 5/6 like I think layout 1 is meant for. I could be wrong on this one but the green port on the back seems to be working great. As well as the HDMI audio. I can post my config.plist if there is any interest. Cheers, zac Edited May 26, 2019 by zac840 Link to comment Share on other sites More sharing options...
jbesclapez Posted May 25, 2019 Share Posted May 25, 2019 Hi Zac, can you please put your full EFI folder. Delete your SMBIOS before . Thanks Link to comment Share on other sites More sharing options...
zac840 Posted May 25, 2019 Share Posted May 25, 2019 Hi jbesclapez, You are going to have to wait a week or so I'm on holidays away from my machine. Link to comment Share on other sites More sharing options...
zac840 Posted June 12, 2019 Share Posted June 12, 2019 Hi, I don't really see the point in posting my whole EFI folder it's basically the same as the OPs just with newer versions of the Clover bootloader and kext files. I'd just grab the latest versions and do it again if I were you. Here is what I used: Clover: v2.4k_r4928 Kexts: AppleALC.kext => Identifier: as.vit9696.AppleALC | Version: 1.3.7 IntelMausiEthernet.kext => Identifier: com.insanelymac.IntelMausiEthernet | Version: 2.5.0d0 Lilu.kext => Identifier: as.vit9696.Lilu | Version: 1.3.5 SMCProcessor.kext => Identifier: as.vit9696.SMCProcessor | Version: 1.0.3 SMCSuperIO.kext => Identifier: ru.joedm.SMCSuperIO | Version: 1.0.3 USBInjectAll.kext => Identifier: com.rehabman.driver.USBInjectAll | Version: 0.7.1 | Other infos: 0.7.1 Copyright © 2015 RehabMan. All rights reserved. VirtualSMC.kext => Identifier: as.vit9696.VirtualSMC | Version: 1.0.3 WhateverGreen.kext => Identifier: as.vit9696.WhateverGreen | Version: 1.2.8 I made some slight tweaks to the OPs SSDT-UIAC-ALL.dsl because I'm only using a T9E wireless card (I disabled all the internal USB2 headers and enabled the USB 3 ports on the back instead) but that is pretty minor. I've attached it but you will have to compile it (follow OPs guide above). I can't attach the compiled version here. I've attached my config.plist (minus) the SMBIOS stuff as that is where all the work is IMO. I hope this helps. config.plist SSDT-UIAC.dsl Link to comment Share on other sites More sharing options...
cmaster Posted August 10, 2019 Share Posted August 10, 2019 I just wanted to thank everyone in this thread for providing such great info -- I'll provide my config.plist and SSDT to give back and hopefully help someone else who was in my situation. This was my first Vanilla Hackintosh -- I'm using a dGPU instead of the iGPU given above, therefore, I had to change the intel framebuffer patch in clover configurator. I'm running a dual boot Win10 / Mojave 10.14.5 build. Any critiques are also welcome. Model: iMac18,3 Hardware: Motherboard: ASUS TUF Z390M-Pro Gaming (Wi-Fi) CPU: Intel Coffeelake Core i5-9600k Case: NZXT H400i RAM: Corsair Vengeance 32GB 2X16GB DDR4 2667MHz Disk: HP EX950 NVMe M.2 Ethernet: Onboard Intel I219V Wifi/BT: Broadcom BCM943602CD Audio: Onboard Realtek ALC S1200A Graphics: RX 570 USB: Onboard Intel Z390 Chipset Working: Onboard USB, audio, ethernet, graphics Wifi and BT via the PCI-e adapter Reboot, shutdown, hibernate, sleep/wake iCloud, iMessage, FaceTime, Time Machine, AirPlay (HomePod), AirDrop GPU Hardware acceleration JPEG Photos I disabled the USB 2.0 ports for the Type C and 3.1 connectors, kept an additional USB 2.0 port for the Broadcom card, and also disabled the USB header connected to the NZXT Fan and light controller. You will have to compile the SSDT yourself, which is super easy to do with MaciASL. SSDT-UIAC-FINAL.dsl config.plist 1 Link to comment Share on other sites More sharing options...
pscaught Posted September 3, 2019 Share Posted September 3, 2019 tl;dr: Installing your Clover boot disk on the "M.2_1" may give you a black BIOS issue. Move it to "M.2_2" and things should work. Hi, This post was hugely helpful for my new build using an ASUS TUF Z390-Pro Gaming and i7-9700K. Thanks! I wanted to share an issue I ran into in case it might help someone who finds this post in the future. My rig was able to install Debian Buster and Windows 10 without any issues. I was able to enter the EFI Bios settings without any issue by pressing either the F2 or Del key during boot. This changed once I inserted a boot disk with Clover on it. Suddenly when I tried to reach the BIOS, I was only getting a black screen. (Clover boot loader worked as expected, only BIOS was inaccessible). I spent a while trying the usual stuff: Clearing CMOS, trying iGPU video ports vs. my PCI GPU. Nothing worked. This issue was present even if I ONLY had Clover on a USB connected (no other boot drives). It persisted after I had Clover/macOS on an m.2 NVME Samsung EVO 970 connected to the "M.2_1" socket, without the USB connected. I finally tried my m.2 NVME drive with Clover/macOS in the "M.2_2" socket and everything started to behave as expected. Super weird, but hopefully this will save someone some time in the future. My guess is something in my Clover setup + a quirk of this board is the issue. If someone has any insight on this, that would be appreciated. Thanks, Scott Link to comment Share on other sites More sharing options...
safehans Posted October 1, 2019 Share Posted October 1, 2019 Thanks to this guide. I have my Hackintosh setup mostly. Need to debug sleep and iGPU issue. Tested so far: iCloud, iMessage, Bluetooth, WiFi, USB ports after Custom SSDT. @cmaster Does your iGPU show up and work fine? Here's my hardware: Motherboard: ASUS TUF Z390M-Pro mATXCPU: Intel Core i9-9900K 3.6 GHz 8-Core ProcessorRAM: Crucial Ballistix Sport LT 32 GB (2 x 16 GB) DDR4-3200 MemorySSD: Samsung 970 Evo 1 TB M.2-2280 NVME Solid State DriveGPU: Sapphire Radeon Pulse RX 580 8GB GDDR5 Wifi/BT: fenvi T919 3x3 MIMO cardCase: Thermaltake Core V21 MicroATX Mini Tower CasePSU: Corsair RMi 650 W 80+ Gold Certified Fully Modular ATX Power SupplyCPU cooler: Corsair H100i PRO 75 CFM Liquid CPU Cooler Link to comment Share on other sites More sharing options...
safehans Posted October 1, 2019 Share Posted October 1, 2019 (edited) Hey @pscaught I have the same issue with Samsung 970 NVME installed in M.2_2 socket. I'll try moving to the other one just see if changes anything On 9/2/2019 at 9:46 PM, pscaught said: tl;dr: Installing your Clover boot disk on the "M.2_1" may give you a black BIOS issue. Move it to "M.2_2" and things should work. Hi, This post was hugely helpful for my new build using an ASUS TUF Z390-Pro Gaming and i7-9700K. Thanks! I wanted to share an issue I ran into in case it might help someone who finds this post in the future. My rig was able to install Debian Buster and Windows 10 without any issues. I was able to enter the EFI Bios settings without any issue by pressing either the F2 or Del key during boot. This changed once I inserted a boot disk with Clover on it. Suddenly when I tried to reach the BIOS, I was only getting a black screen. (Clover boot loader worked as expected, only BIOS was inaccessible). I spent a while trying the usual stuff: Clearing CMOS, trying iGPU video ports vs. my PCI GPU. Nothing worked. This issue was present even if I ONLY had Clover on a USB connected (no other boot drives). It persisted after I had Clover/macOS on an m.2 NVME Samsung EVO 970 connected to the "M.2_1" socket, without the USB connected. I finally tried my m.2 NVME drive with Clover/macOS in the "M.2_2" socket and everything started to behave as expected. Super weird, but hopefully this will save someone some time in the future. My guess is something in my Clover setup + a quirk of this board is the issue. If someone has any insight on this, that would be appreciated. Thanks, Scott Edited October 1, 2019 by safehans Link to comment Share on other sites More sharing options...
codecowboy Posted November 12, 2019 Share Posted November 12, 2019 Has anyone tried Catalina on this board? I only just got the board so wondering whether to go straight to Catalina. Link to comment Share on other sites More sharing options...
zac840 Posted February 25, 2020 Share Posted February 25, 2020 @codecowboy yes Catalina runs fine on this board. I'm currently running latest 10.15.3 I recently just switched bootloaders from Clover over to OpenCore, that wasn't beginner friendly though. But if you are interested I just followed this awesome guide here: https://khronokernel.github.io/Opencore-Vanilla-Desktop-Guide/ Link to comment Share on other sites More sharing options...
MorenoAv Posted April 24, 2020 Share Posted April 24, 2020 Hi all, I have a TUF Z390M Pro Gaming motherboard I can't install or boot anything than windows 10. I have tried install macOS 10.15.3 with clover, OpenCore and it don't install after the first reboot the screen turns black an stays there. Today I have an 10.15.3 ssd with OpenCore installed and functioning it boots but after the first reboot black screen and stays that way. My question is possible the motherboard is bad? If the motherboard is bad how can I return it when it works only with windows... Sorry for the lengthy post, and for the rant, but I don't know what to do... Link to comment Share on other sites More sharing options...
Recommended Posts