AudioGod's Aorus Z390 Pro Patched DSDT Mini Guide and Discussion

[Cameron Nicholson]

7 minutes ago, AudioGod said:

Using my latest EFI no it’s not normal.

you shouldn't need to give an allocation to the nvram like that anymore. 
use me latest EFI in vanilla form other then the Broadcom fix I sent you with the latest bios F12d and my bios settings and you should be golden.

 

hint....read the little tips I put on the main mini guide page to get everything going correctly.
 

one more thing, don’t use the MSR unlocked profile with your combo card, we have found it works better keeping your MSR locked. This only apples to the FV-T919 though.

 

Thank you, I'll investigate. What do you mean MSR Locked?

[AudioGod]

14 minutes ago, Cameron Nicholson said:

Thank you, I'll investigate. What do you mean MSR Locked?

Check the main guide/EFI post for all the info you need buddy.  

[Cameron Nicholson]

2 minutes ago, AudioGod said:

Check the main guide/EFI post for all the info you need buddy.  

Yeah I saw, sorry,

 

I just updated to your EFI, the issue is worse, internet is slower and mouse is laggy when pulling any kind of data

[WizeMan]

39 minutes ago, Cameron Nicholson said:

Hi Ladies and Gents

 

Wonder if anyone can help me help. I'm having an issue with my hackintosh, sometimes on boot my bluetooth Magic keyboard doesn't connect, I am using a FV-T919 - BCM94360CD, If when it boots it doesn't connect I can leave it for a few minutes and it'll connect but it unusable due to lag the keyboard is fine in the BIOS and installer, I reformatted at put my USB EFI on my internal EFI, same issue, restarting no sometimes helps, any ideas?

Specs:
CPU: i9 9900K 8c/16t
Motherboard: Gigabyte Aorus z390 Pro
GPU: Asus Vega 64gb OC 8gb
Ram: Corsair Vengeance 32gb 3000MHz
SSD (MacOS): Corsair MP150 NVMe SSD

Thanks

 

I do have the same CPU and Fenvi card and was having many issues with the unlocked MSR.

 

Make sure that:

If you are using Clover, go to Clover Configurator -> Kernel and Kext Patches -> KernelPM is checked

If you are using OpenCore make these changes:

 

<key>AppleCpuPmCfgLock</key>
<false/>
<key>AppleXcpmCfgLock</key>
<false/>

 

to

 

<key>AppleCpuPmCfgLock</key>
<true/>
<key>AppleXcpmCfgLock</key>
<true/>

[Cameron Nicholson]

8 minutes ago, WizeMan said:

 

I do have the same CPU and Fenvi card and was having many issues with the unlocked MSR.

 

Make sure that:

If you are using Clover, go to Clover Configurator -> Kernel and Kext Patches -> KernelPM is checked

If you are using OpenCore make these changes:

 

<key>AppleCpuPmCfgLock</key>
<false/>
<key>AppleXcpmCfgLock</key>
<false/>

 

to

 

<key>AppleCpuPmCfgLock</key>
<true/>
<key>AppleXcpmCfgLock</key>
<true/>

Thanks, Kernal PM iS checked 

 

[AudioGod]

10 minutes ago, Cameron Nicholson said:

Thanks, Kernal PM iS checked 

 

Did you try with and without the Broadcom fix I sent you?

[WizeMan]

 

16 minutes ago, Cameron Nicholson said:

Thanks, Kernal PM iS checked 

 

 

Also try to reset the bluetooth module:

 

Shift - Alt - Click the bluetooth icon -> Debug 

 

Edited January 21, 2020 by WizeMan

[AudioGod]

Just now, WizeMan said:

 

 

Also try to reset the bluetooth module:

 

Shift - Alt - Click the bluetooth icon -> Debug 

 

@WizeMan could you open your usb  page in hardware info and take a screen shot of your devices in it mainly your Broadcom connection and show me please?

[WizeMan]

2 minutes ago, AudioGod said:

@WizeMan could you open your usb  page in hardware info and take a screen shot of your devices in it mainly your Broadcom connection and show me please?

[AudioGod]

2 minutes ago, WizeMan said:

yeah that’s what I thought I wuould see, it’s wrong buddy. Add the Broadcom fix kexts I sent a few posts back and check again and send  Me screenshots please?

Edited January 21, 2020 by AudioGod

[WizeMan]

3 minutes ago, AudioGod said:

yeah that’s what I thought I wuould see, it’s wrong buddy. Add the Broadcom fix kexts I sent a few posts back and check again and send  Me screenshots please?

 

I think you might have misunderstood me for @Cameron Nicholson I am not facing any bluetooth issues whatsoever  

[AudioGod]

2 minutes ago, WizeMan said:

 

I think you might have misunderstood me for @Cameron Nicholson I am not facing any bluetooth issues whatsoever  

I known your not and yes I’m talking to you bud,

I’ve been doing a lot of homework on Broadcom cards and I can see your firmware and it’s wrong and listing the usb incorrectly,
the files I’m Suggesting will correct it. 
 

it would also explain why you have to do things differently to get it all going.

Edited January 21, 2020 by AudioGod

[WizeMan]

Just now, AudioGod said:

I known your not and yes I’m talking to you bud,

I’ve been doing a lot of homework on Broadcom cards and I can see your firmware and it’s wrong and listing the usb incorrectly,
the files I’m Suggesting will correct it. 

 

Hm... OK I'll add the kexts to the kexts folder and to OC config.plist and report back... let's hope that this is not a revenge plot to destroy my Apple Watch unlock

[AudioGod]

Just now, WizeMan said:

 

Hm... OK I'll add the kexts to the kexts folder and to OC config.plist and report back... let's hope that this is not a revenge plot to destroy my Apple Watch unlock

It sure is...

hahahaha

nooooooo I just want things to be perfect for you that’s all bud.

i have A bad case of OCD that goes beyond my own hack 

 

[WizeMan]

Just now, AudioGod said:

It sure is...

hahahaha

nooooooo I just want things to be perfect for you that’s all bud.

i have A bad case of OCD that goes beyond my own hack 

 

 

I feel you, brotha. I'm preparing the OC config.plist and rebooting, will report back in a couple of mins.

[AudioGod]

Just now, WizeMan said:

 

I feel you, brotha. I'm preparing the OC config.plist and rebooting, will report back in a couple of mins.

Good luck 

[WizeMan]

5 minutes ago, AudioGod said:

Good luck 

 

 So I did that and I see no changes in the USB information (the screens I uploaded earlier)

[AudioGod]

Just now, WizeMan said:

 

 So I did that and I see no changes in the USB information (the screens I uploaded earlier)

Really?

when I’m back at home il send you pictures of what should happen.

i have the same card sitting at home at the moment and it worked for me.

did you attach the kexts inside the oc config?

[WizeMan]

12 minutes ago, AudioGod said:

Really?

when I’m back at home il send you pictures of what should happen.

i have the same card sitting at home at the moment and it worked for me.

did you attach the kexts inside the oc config?

 

Weird thing. I am sure I saved config plist but now I opened it and the entries are nowhere to be found. I'll do it again and report back.

 

Indeed, tried that again and nothing changes in the USB section:

 

YES I DID BOOT OFF THE TESTING STICK

 

Edited January 21, 2020 by WizeMan

[AudioGod]

15 minutes ago, WizeMan said:

 

Weird thing. I am sure I saved config plist but now I opened it and the entries are nowhere to be found. I'll do it again and report back.

 

Indeed, tried that again and nothing changes in the USB section:

 

YES I DID BOOT OFF THE TESTING STICK

 

oh {censored} sorry it’s the wrong batchram kext.

il send you the right one in abit.

 

[Cameron Nicholson]

6 hours ago, AudioGod said:

Did you try with and without the Broadcom fix I sent you?

Sorry, had to go to bed. 

 

I have tried with all different combinations of the kext's you gave me. Still slow internet, laggy mouse when doing a upload test, jittery mouse in normal use.

 

 

[WizeMan]

21 minutes ago, Cameron Nicholson said:

Sorry, had to go to bed. 

 

I have tried with all different combinations of the kext's you gave me. Still slow internet, laggy mouse when doing a upload test, jittery mouse in normal use.

 

 

Make sure you have your Fenvi card on the last slot of your motherboard and the header cable on the F_USB2 connector 

[Tiem]

6 hours ago, WizeMan said:

 

Weird thing. I am sure I saved config plist but now I opened it and the entries are nowhere to be found. I'll do it again and report back.

 

Indeed, tried that again and nothing changes in the USB section:

YES I DID BOOT OFF THE TESTING STICK

 

If I can chime in. You definitely don't need all those kexts. I have the same card and it is recognized and works perfectly.

 

These are the only kexts you need (if you have a pretty vanilla system without a bunch of other hardware or peripherals attached):

 

 

While I know you want the problem fixed, but just arbitrarily chucking kexts at it isn't really the best way to go about it. What FENVI card do you have? I know MQUPIN sells them as well (which is what I have): https://www.amazon.ca/gp/product/B07Z3MN5XM/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8&psc=1

 

The native card is a BCM94360CD but you have BCRM20702 listed, so it's not being identified properly:

 

 

I have nearly an identical system. I say start over. Or just run the EFI (after adding in your SMBIOS details) off a Catalina USB installer. That's a pretty clean way of testing hardware without having to deal with caching or NVRAM or anything else.

 

Another option is to toss it into a PC running Windows and ensure it's actually working correctly. You could have just got a bad card.

 

As for unlocking your MSR, you have the Pro (not WIFI), so just download and flash the unlocked BIOS that AG has linked in his guide. If you don't want to do that, you can do it using https://github.com/datasone/grub-mod-setup_var/releases. The offset is 0x5C1. (Make sure you use setup_var_3, it will still throw an error but will patch your board.

 

But I assure you, you don't need any BT kexts. It works OOB, that's why the card is so popular.

 

Lastly, ordering in OC matters. Just FYI. 

[WizeMan]

25 minutes ago, Tiem said:

If I can chime in. You definitely don't need all those kexts. I have the same card and it is recognized and works perfectly.

 

These are the only kexts you need (if you have a pretty vanilla system without a bunch of other hardware or peripherals attached):

 

 

While I know you want the problem fixed, but just arbitrarily chucking kexts at it isn't really the best way to go about it. What FENVI card do you have? I know MQUPIN sells them as well (which is what I have): https://www.amazon.ca/gp/product/B07Z3MN5XM/ref=ppx_yo_dt_b_asin_title_o08_s00?ie=UTF8&psc=1

 

The native card is a BCM94360CD but you have BCRM20702 listed, so it's not being identified properly:

 

 

I have nearly an identical system. I say start over. Or just run the EFI (after adding in your SMBIOS details) off a Catalina USB installer. That's a pretty clean way of testing hardware without having to deal with caching or NVRAM or anything else.

 

Another option is to toss it into a PC running Windows and ensure it's actually working correctly. You could have just got a bad card.

 

As for unlocking your MSR, you have the Pro (not WIFI), so just download and flash the unlocked BIOS that AG has linked in his guide. If you don't want to do that, you can do it using https://github.com/datasone/grub-mod-setup_var/releases. The offset is 0x5C1. (Make sure you use setup_var_3, it will still throw an error but will patch your board.

 

But I assure you, you don't need any BT kexts. It works OOB, that's why the card is so popular.

 

Lastly, ordering in OC matters. Just FYI. 

I do have the MQUPIN and I am not facing any issues. Actually I do also have unlock with Apple Watch working pretty solid as well. I am normally using the provided EFI same Kexts as yours, I just tried these additional Kexts upon @AudioGod’s request. I don’t normally use them.

 

Is your card identified correctly in your setup? 
 

Regarding the MSR unlock, Bluetooth is junky and devices disconnect upon boot when I uncheck kernelPM OR when I disable the lock flags on the OC config.plist (after having loaded the unlock profile of course). Maybe the fault is that my card is not recognized properly? And I’m curious as to why this is happening as this is how it is recognized with the stock EFI kexts as well.

Edited January 21, 2020 by WizeMan

[Tiem]

Ya my card works OOB. And I have the same MQUPIN. So just to be clear, it's your BT that's not working properly? But your WIFI is fine? The card has 4 antennas, one of which is dedicated for BT (not sure which one that is, but would love to know). The rest all drive WIFI. It could be that the signal is being attenuated. I have the WIFI variant of this board so I used the antenna from Gigabyte which is better quality and has quite a bit of length to the cables so it's not buried in the back of your PC.

 

IMO, you got a bad card. I would pull it or try it in another OS. It works great in Windows with the appropriate drivers. First ensure the card is actually working as it should before you toss kexts at it. Because I can tell you that macOS does indeed support the card OOB. No fiddling, nothing.

 

If the card is indeed working, maybe pick up some better antennas. I have been thinking about these: https://www.amazon.ca/COVVY-Dual-Band-Connector-Wireless-Extender/dp/B07TQ4Y47D/ref=pd_sbs_147_12?_encoding=UTF8&pd_rd_i=B07TQ4Y47D&pd_rd_r=633adfd9-9eb9-4404-a720-b82f1327d6dc&pd_rd_w=oVTIx&pd_rd_wg=lHBxQ&pf_rd_p=dbebb38c-0e3d-4a67-ac15-432d7c7a2789&pf_rd_r=CWFFRSGN6RDH4R9TNZ6W&psc=1&refRID=CWFFRSGN6RDH4R9TNZ6W

 

You could just grab 2, just to boost the BT.

 

EDIT: Actually how does the BT work when you're in post (or the BIOS)? I find the card is a bit twitchy, where sometimes it picks up the BT device (I have a wireless Apple Keyboard I'm using) fast enough for me to hit F12 to get the boot options and other times, it lags behind to where OC/Clover has already loaded before it connects.

 

The card works but it isn't the greatest. I'm still hunting for something that has better performance and reliability.

Edited January 22, 2020 by Tiem