Contribute
Register

[SUCCESS] jbarnette's Build - ASUS TUF Z390 M Gaming + i9-9900K + Sapphire RX Vega 64 8GB + 32GB RAM + MacOS 10.14.3 w/ USB3 working!

Status
Not open for further replies.
Are you aware that the build in this threat is based on the Gigabyte Z390 M Gaming, not the Aorus pro wifi?
You should have seen my signature, is that 1 week ago I was deciding which parts I would use to mount my Hackintosh, and I would be informed.
But during that week, I decided to change to this one, and I do not have any of those parts, because it is a long-term project, because here in Brazil the value is doubled or triple that of the USA.
 
Okay, I'm really not sure if that's irony... Does it work? My first research said no.

Everything I've read indicates no. I tried for a few minutes and my Wi-Fi/Bluetooth card was not detected in macOS at all. Even Bluetooth wasn't detected. However, to be fair, I didn't try very hard. I just plugged it in to see if it was detected. It wasn't and I stopped there.

The card I tried was a DW1830 which I had previously used with my Z370 motherboard without issues.
 
This build is now fully functional and really everything works (sleep/wake; BT handoff/continuity; sound; wifi etc.)

@CaseySJ

I might have spoken too quickly for the sleep / wake functions. The computer wakes up immediately after going into sleep. I think it is related to the BT card because when I disable the HS10 port (internal F_USB1 header) in the customized SSDT the computer stays on sleep.
May I ask you a favor? Could you please look into my SSDT file? I have followed the instruction from Rehabman's guide but I might (must) have made some silly mistakes...
I am uploading also the scheme with the USB port mapping for this motherboard.

Thank you very much!
 

Attachments

  • USBLayoutv05.png
    USBLayoutv05.png
    784.7 KB · Views: 97
  • SSDT_USB_Z390M_Gaming_MMairav05.dsl
    4.5 KB · Views: 79
Last edited:
@CaseySJ

I might have spoken too quickly for the sleep / wake functions. The computer wakes up immediately after going into sleep. I think it is related to the BT card because when I disable the HS10 port (internal F_USB1 header) in the customized SSDT the computer stays on sleep.
May I ask you a favor? Could you please look into my SSDT file? I have followed the instruction from Rehaman's guide but I might (must) have made some silly mistakes...
I am uploading also the scheme with the USB port mapping for this motherboard.

Thank you very much!

According to the guide, "For a Motherboard USB 2.0 port used for a BlueTooth card we need: “UsbConnector”, 255, - this is to stop the BT device waking your PC from sleep unnecessarily."

I can see you did that with HS10, what happens if you do the same to HS09 just in case?
 
@CaseySJ

I might have spoken too quickly for the sleep / wake functions. The computer wakes up immediately after going into sleep. I think it is related to the BT card because when I disable the HS10 port (internal F_USB1 header) in the customized SSDT the computer stays on sleep.
May I ask you a favor? Could you please look into my SSDT file? I have followed the instruction from Rehaman's guide but I might (must) have made some silly mistakes...
I am uploading also the scheme with the USB port mapping for this motherboard.

Thank you very much!
I must say I'm impressed by the thoroughness of the port diagram and the extensive comments in the DSL file! Some suggestions:
  • Each of your USB 2 headers supports two USB ports. On F_USB1 you have already deactivated HS09 because you know that the Fenvi is attached to HS10. And you've set the type to 255 (Internal). All of this is good.
  • On F_USB2, however, if the only connected device is the Titan Ridge card, I would suggest looking at IORegistryExplorer --> XHC to determine whether the Titan Ridge is attached to HS11 or HS12.
  • Then I would suggest removing the unused port and setting the used-port to type Internal (255) as well. You'll free up one port in the process, which you can reallocate to a different USB port.
Let's start with this and see how it goes.
 
@joanareis below you will find a snippet of what I am talking about from @CaseySJs thread. If you get a moment you should drop in on that thread as there is a wealth of knowledge there.

Injecting Audio and Enabling On-Board HDMI
In order to keep the build procedure simple, we took the liberty of maximizing point-and-click options in Clover Configurator. But now that the installation is complete, everyone is encouraged to apply the following procedure to inject audio properly and to enable onboard HDMI port. If you plan to run the system in headless mode where the iGPU will not be driving any displays, then you should only make the change for audio injection.

Inject Audio Layout 16 only
For audio injection only, the procedure is:
  • Start by mounting the EFI partition on the Mojave internal SSD and run Clover Configurator. In Clover Configurator, open your config.plist and set Devices --> Audio --> Inject = NO.
  • Then copy-paste the indicated lines directly into config.plist, just after <key>properties</key>.
XML:
<key>Properties</key>
<dict>
// 1. Copy the lines shown below
// 2. Paste them into your config.plist under <key>Properties</key>
<key>PciRoot(0x0)/Pci(0x1f,0x3)</key>
<dict>
<key>AAPL,slot-name</key>
<string>Built In</string>
<key>device_type</key>
<string>Audio Controller</string>
<key>layout-id</key>
<data>
EAAAAA==
</data>
<key>model</key>
<string>Realtek ALC1220-VB</string>
</dict>

@gyrene2083, after upgrading to 10.14.4, I cannot make audio work, which is fine on 10.14.2. Can you post your EFI for reference as I am using Z390 M GAMING, too.
 
I have the same board and I am using default BIOS settings just IGPU enabled everything works for me without any problem.
 
@gyrene2083, after upgrading to 10.14.4, I cannot make audio work, which is fine on 10.14.2. Can you post your EFI for reference as I am using Z390 M GAMING, too.

I'm not home right now but you should take a look at the OPs EFI and compare it to yours if you haven't done so already. You should also post your config.plist and your EFI too. Maybe someone with more experience can take a quick look and see what's going on.

Good Luck.
 
Status
Not open for further replies.
Back
Top