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

[AudioGod]

26 minutes ago, pkdesign said:

I'm guessing the new OC is just for Catalina only?

 

I think so but try it on a usb stick and see if you can boot up? (untested on anything pre 10.15)

In fairness though the new Clover updates and small changes to the plist are silky smooth too.  

Edited May 4, 2020 by AudioGod

[AudioGod]

7 minutes ago, eSaF said:

Actually AG I am able to boot Mojave with the new OC Folder without any problems.

Wow Seriously?

Now that is a unexpected turn of events.

 

@pkdesign What about you buddy? Give it a try?

[AudioGod]

3 minutes ago, eSaF said:

 

Oh Ye of little Faith 

Im shocked TBH,

The lack of SSDT-EC, SATA0 and the Real RTC are things I didn’t think Mojave would allow so for sure faith was not there at all. 
Computer Said Yes.....Wowzers!!!!!  

[AudioGod]

Just now, eSaF said:

 

Yea I ran three tests because of you reaction, just to make sure. Everything works just as in Catalina B 

That’s Awesome, Well Done G,

@pkdesign I think that’s your green light to try it yourself and confirm and give OC a try.  

[kevbo]

@AudioGod

 

I have still had no success with using your EFI on my setup. It seems to hang around the same spot during boot, even with your newest update. I am adding my own serial numbers to the EFI and I have loaded the bios profile on the newest bios update, I've got to be missing something!

 

I would continue to use my EFI build that I managed to scrape together, but it must be sloppy because I can not get Audio to work at all and it is giving me major issues with logic pro x. Before I try building another Vanilla EFI, I wanted to check here again to see if you would have any ideas. I've uploaded your EFI that I am trying to use and some poor quality photos of the verbose boot failure

EFI.zip

[measwel]

Success. I finally have a working usb mapping on my aorus z390 WIFI pro. I used a simple procedure:

 

1. Remove all kext/ssds based usb mappings. Install only the USBInjectAll.kext.

2. login, start hackintool, select all USB ports, delete, refresh.

3. plug an usb 2 device in all ports. delete all hs type ports which don't stay green.

4. delete all ss type ports which have no corresponding hs port number.

5. export to desktop. Use the generated ssdt OR kext. I use the ssdt (aml file). Remove the usbInjectAll.kext.

 

If can confirm that everything works, I will attach my clover folder.

[AudioGod]

34 minutes ago, measwel said:

Success. I finally have a working usb mapping on my aorus z390 WIFI pro. I used a simple procedure:

 

1. Remove all kext/ssds based usb mappings. Install only the USBInjectAll.kext.

2. login, start hackintool, select all USB ports, delete, refresh.

3. plug an usb 2 device in all ports. delete all hs type ports which don't stay green.

4. delete all ss type ports which have no corresponding hs port number.

5. export to desktop. Use the generated ssdt OR kext. I use the ssdt (aml file). Remove the usbInjectAll.kext.

 

If can confirm that everything works, I will attach my clover folder.

Well done but don’t attach here as my files work for most and the few that it doesn’t there’s always a reason why so while I applaud your fix i also have my doubts that it’s correct. (The thousands of users out weigh the few sorry)

well done and just enjoy.

 

if your the igpu only user then you have got missing arguments and probably the wrong framebuffers and it’s borking usb. If your not the igpu only user or even if you are then try filling in your signature so we know what your setup is with out having to ask.

 

p.s if you look on my Z390 Master Thread your find a user from today that posted the correct fix for igpu only use and he was spot on correct.

try what he did and you might find it all works for you.

 

Edited May 4, 2020 by AudioGod

[AudioGod]

@kevbo Your install looks borked to me.

can you boot into the first page of a Catalina install using my Efi and a usb Catalina thumb drive?

If you can then I would consider a fresh install.

[measwel]

 

20 minutes ago, AudioGod said:

Well done but don’t attach here as my files work for most and the few that it doesn’t there’s always a reason why so while I applaud your fix i also have my doubts that it’s correct. (The thousands of users out weigh the few sorry)

well done and just enjoy.

 

Yes, that's fine. If somebody needs it, he can ask me.

 

There is still a problem with sleep. If i click before the fans stop running, the mac wakes up, but the display does not (remains black, no hdmi signal). If I manually switch inputs on my monitor, I can bring it back. This could be a general catalina bug as I read similar reports from regular users. Its annoying but bearable. I will get a new gfx card in a few weeks so I will try another setup then.

 

A bigger problem is; when I wait for the fans to stop spinning (true sleep) and then click the mouse, the mac reboots instead of awakening. Now this is the last big problem remaining. Can you please help me solve it? 

 

 

PS How can I check if my nvram is working correctly?

Edited May 4, 2020 by measwel

[AudioGod]

3 minutes ago, measwel said:

 

 

Yes, that's fine. If somebody needs it, he can ask me.

 

There is still a problem with sleep. If i click before the fans stop running, the mac wakes up, but the display does not (remains black, no hdmi signal). If I manually switch inputs on my monitor, I can bring it back. This could be a general catalina bug as I read similar reports from regular users. Its annoying but bearable. I will get a new gfx card in a few weeks so I will try another setup then.

 

A bigger problem is; when I wait for the fans to stop spinning (true sleep) and then click the mouse, the mac seems to be restarting. I can't really tell as the display stays black for a long time. 

 

 

PS How can I check if my nvram is working correctly?

Mate I’ve already told you.

your sleep isn’t working for the same reason your usb wasn’t working.

All you have done is put a plaster over a booboo, nothing has been fixed on your end and you need to do more research to understand why Im telling you it’s wrong.

 

again the correct fix is up on my Z390 Master thread. 
 

Edited May 4, 2020 by AudioGod

[measwel]

Just now, AudioGod said:

Mate I’ve already told you.

your sleep isn’t working for the same reason your usb wasn’t working.

All you have done is put a plaster over a booboo, nothing has been fixed on your end and you need to do more research to understand why Im telling it’s wrong.

 

again the correct fix is up on my Z390 Master thread. 
 

 

I don't remember you telling me the reason. If you are referring to the bios profile, I have read it in.

 

[AudioGod]

2 minutes ago, measwel said:

 

I don't remember you telling me the reason. If you are referring to the bios profile, I have read it in.

 

Read the post before the one I just posted before this one (3 posts back from me I think)

its all there pal

Edited May 4, 2020 by AudioGod

[measwel]

2 minutes ago, AudioGod said:

Read the post before the one I just posted before this 9one (3 posts back from me I think)

its all there pal

 

Sorry AudioGod, somehow I totally missed your iGPU comment. Yes, that's me. The guy who wants it all to work on his built in uhd 630.

[AudioGod]

4 minutes ago, measwel said:

 

Sorry AudioGod, somehow I totally missed your iGPU comment. Yes, that's me. The guy who wants it all to work on his built in uhd 630.

Jump over to my Z390 Master thread and look though today’s or late last nights comments and your find a guy with all the same problems you had and he fixed it the correct way and posted how he did it.

 

everything you need to know is there and the fix so just do what he says with a fresh Efi download from today’s bunch.

 

good luck.

Edited May 4, 2020 by AudioGod

[pkdesign]

3 hours ago, AudioGod said:

Wow Seriously?

Now that is a unexpected turn of events.

 

@pkdesign What about you buddy? Give it a try?

I definitely will give it a go! Will let you know how it goes.

[kevbo]

I can't believe I didn't think to try a fresh install...  

 

I must have been subconsciously holding onto my original install since it took so long to hack it together with my igpu. I didn't even think to do a fresh install since installing the 5500xt, but that did it. Everything seems to be working better than ever now and I can finally chill out a bit haha. Thank you for all your work @AudioGod

[AudioGod]

2 minutes ago, kevbo said:

I can't believe I didn't think to try a fresh install...  

 

I must have been subconsciously holding onto my original install since it took so long to hack it together with my igpu. I didn't even think to do a fresh install since installing the 5500xt, but that did it. Everything seems to be working better than ever now and I can finally chill out a bit haha. Thank you for all your work @AudioGod

No worries my friend and I’m glad your up and running now.

if you never of posted the screen shots I never would of noticed something like that so good on you sport that’s awesome. 

[Alex1982]

Hi @AudioGod, in your OC config.plist I see that you added your Wi-Fi adaptor in DeviceProperties section:

            <key>PciRoot(0x0)/Pci(0x1c,0x7)/Pci(0x0,0x0)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Slot 4</string>
                <key>device_type</key>
                <string>Network controller</string>
                <key>model</key>
                <string>BCM4360 802.11ac Wireless Network Adapter</string>
            </dict>

 

I have different Wi-Fi adaptor TP-LINK Archer T9E inserted in PCIEX1_3 slot on my Aorus Z390 Pro board. I just removed your Wi-Fi adaptor from DeviceProperties in OC config.plist (don't add mine instead so far). I don't observe any Wi-Fi related issues and all Wi-Fi related stuff seems to be working fine.

 

Could you please clarify, should I still add my TP-LINK Archer T9E adaptor into OC config.plist to avoid any possible issues in future or it is not necessary and just cosmetic(to be able observe Wi-Fi device in PCI section of macOS SystemReport)?

[Tiem]

7 minutes ago, AlexeyNikitin said:

Hi @AudioGod, in your OC config.plist I see that you added your Wi-Fi adaptor in DeviceProperties section:

            <key>PciRoot(0x0)/Pci(0x1c,0x7)/Pci(0x0,0x0)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Slot 4</string>
                <key>device_type</key>
                <string>Network controller</string>
                <key>model</key>
                <string>BCM4360 802.11ac Wireless Network Adapter</string>
            </dict>

 

I have different Wi-Fi adaptor TP-LINK Archer T9E inserted in PCIEX1_3 slot on my Aorus Z390 Pro board. I just removed your Wi-Fi adaptor from DeviceProperties in OC config.plist (don't add mine instead so far). I don't observe any Wi-Fi related issues and all Wi-Fi related stuff seems to be working fine.

 

Could you please clarify, should I still add my TP-LINK Archer T9E adaptor into OC config.plist to avoid any possible issues in future or it is not necessary and just cosmetic(to be able observe Wi-Fi device in PCI section of macOS SystemReport)?

It’s being handled by airportbcrmfixup kext. Just leave it. You don’t technically need both. Either the kext or the raw entry in OC. But having things mapped in OC is the cleanest. Unless OC itself is known to not handle it.

[AudioGod]

16 minutes ago, AlexeyNikitin said:

Hi @AudioGod, in your OC config.plist I see that you added your Wi-Fi adaptor in DeviceProperties section:

            <key>PciRoot(0x0)/Pci(0x1c,0x7)/Pci(0x0,0x0)</key>
            <dict>
                <key>AAPL,slot-name</key>
                <string>Slot 4</string>
                <key>device_type</key>
                <string>Network controller</string>
                <key>model</key>
                <string>BCM4360 802.11ac Wireless Network Adapter</string>
            </dict>

 

I have different Wi-Fi adaptor TP-LINK Archer T9E inserted in PCIEX1_3 slot on my Aorus Z390 Pro board. I just removed your Wi-Fi adaptor from DeviceProperties in OC config.plist (don't add mine instead so far). I don't observe any Wi-Fi related issues and all Wi-Fi related stuff seems to be working fine.

 

Could you please clarify, should I still add my TP-LINK Archer T9E adaptor into OC config.plist to avoid any possible issues in future or it is not necessary and just cosmetic(to be able observe Wi-Fi device in PCI section of macOS SystemReport)?

@Tiem is right and that device property is purely cosmetic and I leave it in there as a lot of people use the WiFi card.  Go ahead and remove it and any other unwanted entires in device properties with the exception of the igpu.

[AudioGod]

Clover & OpenCore EFI Updates (10.15.5 Ready), 4th MAY 2020 

(Use With Bios Revision F12d)

 

 

The EFIs and DSDTs have now been updated to the my latest versions.

Changes made include,

 

AppleALC 1.4.9

Lilu 1.4.4

WhateverGreen 1.3.9

VirtualSMC 1.1.3

AirportBrcmFixup 2.0.7

OcQuirks Revision 22 (I have made some changes to the plist that should make it play a lot more friendly now with the IGPU enabled) (Clover)

Clover Updated to Revision 5115

OpenCore Updated to Revision 0.5.8

Plus other major tweaks and changes to all of the configs

 

 

Clover EFI Update - 04/05/2020 - Use with Bios revision F12d Only or Replace with the older F11 DSDT if you don't want to update the bios

 

Clover Z390 Pro Navi Vega EFI 040520.zip - Vega, Navi (5700, 5700XT etc), Radeon VII DSDT EFI

Clover Z390 Pro Polaris EFI 040520.zip - RX500 Polaris Series (RX590, 580, 570 etc) DSDT EFI

Please Note - I have now set KernelPM to No as standard so if you don’t have a unlocked MSR or not using my MSR Unlocked Bios Profile then go into the Clover Config.plist and set KernelPM to Yes or you won’t be able to boot up. An even better fix would be to unlock your MSR using my profile method.

 

Note - If your not using a 5700 XT or any other Navi GPU then remove agdpmod=pikera from the boot arguments.

 

 

OpenCore EFI Update - 04/05/2020

Myself and @texem have now created a OpenCore EFI done the way the OpenCore Devs intended it to be made, There is no DSDT in use so you can use this EFI on any supported GPU and the SSDTs have been made so they will not be used in any other Operating System apart from MacOS.

 

OpenCore 058 Z390 Pro 19,1 040520.zip  - OpenCore v0.5.8, SMBios iMac19,1

OpenCore 058 Z390 Pro 1,1 040520.zip  - OpenCore v0.5.8, SMBios iMacPro1,1 (IGPU Disabled)

 

Note - If your not using a 5700 XT or any other Navi GPU then remove agdpmod=pikera from the boot arguments.

 

 

 

For OpenCore Using PlistEdit Pro add your details by modifying the following 



 

PLEASE NOTE - These EFIs are setup to be used with your msr Unlocked so make sure you use the F12d Unlocked Profile but if for any reason you can not unlock MSR then just modify following in the OpenCore config.plist :



 

 

Additional Downloads

mb_bios_z390-aorus-pro_f12d.zip - Aorus Z390 Master Bios F12d 

PlistEdit Pro.zip - PlistEdit Pro (use to edit OpenCore)

 

CFG Unlock (MSR) F12d (F12c Pro WIFI) BIOS Profile - The Easy Way 

I have made this bios profile for you all to use that will unlock CFG on your motherboard making it play alot more friendly with the NVRam.

It also has all the bios settings listed on this guide pre done and saved onto the profile.



F12d_UNLOCK.zip - Use with Z390 Pro Bios Revision F12d ONLY

F12c Unlock.zip - Use with Z390 Pro WIFI Bios Revision F12c ONLY

 

1 - Download the profile and save it to a USB Key

2 - Go into the bios,

3 - Load the profile, 

4 - Save and exit

5 - Go straight back into the bios and save your bios to a new profile and name it Default CFG Unlocked or something like that.

6 - Boot back into Catalina go into your clover config and under Kernal and Kext Patches Uncheck KernalPM 

7 - Save the changes and then restart and your done, your motherboard will now be CFG (MSR) Unlocked

 

    PLEASE NOTE - If you reset the bios or load bios defaults it will clear the Unlock making CFG Locked again. 

 

 

Default USB Setup For All OpenCore EFIs

 



 

 

 

MAY THE FORTH BE WITH YOU ALWAYS!!!!

 

Edited May 5, 2020 by AudioGod

[pkdesign]

Ooo, a new EFI already? Or is this a repost?

[AudioGod]

Just now, pkdesign said:

Ooo, a new EFI already? Or is this a repost?

Repost for the lazy crew out there.

[pkdesign]

1 minute ago, AudioGod said:

Repost for the lazy crew out there.

Seriously, one page back?

[AudioGod]

1 minute ago, pkdesign said:

Seriously, one page back?

You don’t need to tell me buddy...lol 

 

ive been asked 4 times today if I’m going to update the Oc EFI to 0.5.8 so I thought I better repost it even though it’s all on page one. 

Edited May 5, 2020 by AudioGod