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

[pkdesign]

Argh. Okay So I've been testing a bunch of stuff. darkwake=0, 8, and 10 seem to allow my rig to sleep fine.

 

The scripts you mentioned actually stop sleep from working and I still get Disk Not Ejected Properly message anyway.

 

BTW, This is my Energy Saver scrren:

 

Shouldn't there be a "Computer Sleep" section?

Edited February 10, 2020 by pkdesign

[Neblogas]

8 hours ago, pkdesign said:

Argh. Okay So I've been testing a bunch of stuff. darkwake=0, 8, and 10 seem to allow my rig to sleep fine.

 

The scripts you mentioned actually stop sleep from working and I still get Disk Not Ejected Properly message anyway.

 

I also have the same error message

[Pieroman]

Just put everything together... and it's working apparently working flawlessly, thanks @AudioGod and @glasgood ! So far I'm still with MA.efi, I'll look how it progresses on here.

 

Just as a remark, there are inconsistencies between bios settings in the various pages (text in the first post of this thread VS settings file for CFG unlock VS glasgood's tutorial photos). What i did was load the CFG settings file then apply the few different things in the "BIOS SETTINGS (Bios Revision F12d)"  section of the first post.

 

EDIT : I installed MacOS on the M2 slot close to the CPU, and want dual boot windows as well. If I need to install windows (I hope that wont be necessary and that I can just transfer a disk), is there a way to deactivate a M2/NVMe drive in the BIOS so that the installer doesn't mess it up, I haven't seen it (it's kind of very hard to reach to remove it now !).

Edited February 11, 2020 by Pieroman

[AudioGod]

1 hour ago, Pieroman said:

Just put everything together... and it's working apparently working flawlessly, thanks @AudioGod and @glasgood ! So far I'm still with MA.efi, I'll look how it progresses on here.

 

Just as a remark, there are inconsistencies between bios settings in the various pages (text in the first post of this thread VS settings file for CFG unlock VS glasgood's tutorial photos). What i did was load the CFG settings file then apply the few different things in the "BIOS SETTINGS (Bios Revision F12d)"  section of the first post.

 

EDIT : I installed MacOS on the M2 slot close to the CPU, and want dual boot windows as well. If I need to install windows (I hope that wont be necessary and that I can just transfer a disk), is there a way to deactivate a M2/NVMe drive in the BIOS so that the installer doesn't mess it up, I haven't seen it (it's kind of very hard to reach to remove it now !).

Hey bud just a quick one from me, the inconsistencies are due to glasgood not updating he’s guide in a long while now as he’s a busy guy and doesn’t have the time so he’s bios settings have gone out on line with mine but my ones are the correct ones to be using with my EFI buddy. 

I’m dual booted using 2x pcie m.2 slots and I have never once removed my windows disk to install macOS, they don’t interfere with each other just remember to make your windows drive your main drive while your rebooting it up if you need to do that and your be fine.

 

11 hours ago, pkdesign said:

Argh. Okay So I've been testing a bunch of stuff. darkwake=0, 8, and 10 seem to allow my rig to sleep fine.

 

The scripts you mentioned actually stop sleep from working and I still get Disk Not Ejected Properly message anyway.

 

BTW, This is my Energy Saver scrren:

 

Shouldn't there be a "Computer Sleep" section?

I use the same script on my hack and it works for me so I’m abit baffled about that one bud.

ive got a second build at home for somebody else so il double check it again on that one.

your energy saver menu is correct and not missing anything.

 

download Jettison in that case to fix your usb issues.

if that doesn’t fix it then I’m really lost (it will work)

https://www.stclairsoft.com/Jettison/

 

Edited February 11, 2020 by AudioGod

[AudioGod]

CLOVER DRIVER UPDATE 11/02/20

 

OcQuirks Revision 14 & FwRunTimeServices Latest Versions.

 

OcQuirks R14.zip

Edited February 11, 2020 by AudioGod

[pkdesign]

7 hours ago, Pieroman said:

Just put everything together... and it's working apparently working flawlessly, thanks @AudioGod and @glasgood ! So far I'm still with MA.efi, I'll look how it progresses on here.

 

Just as a remark, there are inconsistencies between bios settings in the various pages (text in the first post of this thread VS settings file for CFG unlock VS glasgood's tutorial photos). What i did was load the CFG settings file then apply the few different things in the "BIOS SETTINGS (Bios Revision F12d)"  section of the first post.

 

EDIT : I installed MacOS on the M2 slot close to the CPU, and want dual boot windows as well. If I need to install windows (I hope that wont be necessary and that I can just transfer a disk), is there a way to deactivate a M2/NVMe drive in the BIOS so that the installer doesn't mess it up, I haven't seen it (it's kind of very hard to reach to remove it now !).

I reordered the settings for myself because it was driving me crazy every time I had to rest my BIOS or something. I have the Wifi version of this board but I think that means just one settings. This list starts from left to right and from top to bottom in order, ignoring the "Favorites" section. I hope it helps:

 

BIOS SETTINGS (Bios Revision F12c)

• Enter BIOS → Press DEL at boot screen

• Save & Exit → Load Optimized Defaults

• Tweaker -> Extreme Memory Profile (X.M.P.) -> Profile1

• Tweaker -> Advanced CPU Settings -> VT-d -> Enabled (Can be set to Enabled or Disabled, Your choice)

• Settings -> Platform Power -> Platform Power Management -> Enabled

• Settings -> Platform Power -> ErP -> Enabled

• Settings -> Platform Power -> RC6(Render Standby) -> Enabled

• Settings -> IO Ports -> Internal Display Output -> PCIe 1 Slot

• Settings -> IO Ports -> Internal Graphics -> Enabled

• Settings -> IO Ports -> Wifi -> Disabled

• Settings -> IO Ports -> Audio Controller -> Enabled

• Settings -> IO Ports -> Above 4G Decoding -> Enabled

• Settings -> IO Ports -> USB Configuration -> Legacy USB Support -> Enabled

• Settings -> IO Ports -> USB Configuration -> XHCI Hands-off -> Enabled

• Settings -> Miscellaneous -> Software Guard Extensions (SGX) -> Disabled

 

• Boot -> Windows 8/10 Features -> Win 8/10 (I like the larger logo but you can set this to Win 8/10WHQL)

• Boot -> CSM Support -> Disabled

• Save & Exit → Save & Exit Setup

After boot check to see if these are set properly:

• Settings -> IO Ports -> DVMT Pre-Allocated -> 64M

• Settings -> IO Ports -> DVMT Total GFX0-Allocated -> 256M

• Settings -> IO Ports -> Aperture Size -> 256MB

 

6 hours ago, AudioGod said:

download Jettison in that case to fix your usb issues.

if that doesn’t fix it then I’m really lost (it will work)

https://www.stclairsoft.com/Jettison/

 

Nice, I'll have to check this out.

[pkdesign]

Thanks @eSaF. This is the same tool that @AudioGod provided. Not sure why it doesn’t work.

[AudioGod]

Just now, pkdesign said:

Thanks @eSaF. This is the same tool that @AudioGod provided. Not sure why it doesn’t work.

I was gonna comment on that one too, he basically repeated my message to you 

bless!

[Cass67]

On 2/11/2020 at 4:13 PM, pkdesign said:

• Settings -> IO Ports -> DVMT Pre-Allocated -> 64M

 

Could never get my system to boot with iGPU enabled and no memoryallocation.efi driver without lowering this to 32M.  

 

[AudioGod]

7 minutes ago, Cass67 said:

 

Could never get my system to boot with iGPU enabled and no memoryallocation.efi driver without lowering this to 32M.  

 

Did you try a full bios battery reset?

[Cass67]

Just now, AudioGod said:

Did you try a full bios battery reset?

 

yeah

[AudioGod]

1 minute ago, Cass67 said:

 

yeah

The z390 pro is a tricky little board when it comes to having the igpu enabled but most people have it working fine without Ma.efi on here. 

[Cass67]

Just now, AudioGod said:

The z390 pro is a tricky little board when it comes to having the igpu enabled but most people have it working fine without Ma.efi on here. 

Yah, its proven to be a pain in the hole getting rid of ma or before that the free2000 driver.  Cant really complain though, everything else works ..  Only posted this here for others to try if all else fails for them like it did for me.

[AudioGod]

10 minutes ago, Cass67 said:

Yah, its proven to be a pain in the hole getting rid of ma or before that the free2000 driver.  Cant really complain though, everything else works ..  Only posted this here for others to try if all else fails for them like it did for me.

it’s why I haven’t updated the thread with new EFIs yet, until I find a more solid solution for you guys I’m abit stuck.

[Cass67]

Just now, AudioGod said:

it’s why I haven’t updated the thread with new EFIs yet, until I find a more solid solution for you guys I’m abit stuck.

 

Try changing the dvmt value to 32M and removing the driver

 

Im not sure how much that value is actually used these days from what i read.  From what i can tell the max allocation is what modern Windows uses and scales up to when needed and most of us probably have a dedicated GPU of sorts anyway so its probably moot whats put here for those who have a dedicated GPU.

 

I also could never figure out how to boot to efi shell (im on OC) to get the memory map to work out a proper slide value so i did not need to change this value, hacking around with various slide values never seemed to work either anyway for me with 64M in place.  32M is my sweet spot (it boots anyway multiple times) and what ill live with for now until i find issues with it down the road.

 

[AudioGod]

4 minutes ago, Cass67 said:

 

Try changing the dvmt value to 32M and removing the driver

 

Im not sure how much that value is actually used these days from what i read.  From what i can tell the max allocation is what modern Windows uses and scales up to when needed and most of us probably have a dedicated GPU of sorts anyway so its probably moot whats put here for those who have a dedicated GPU.

 

I also could never figure out how to boot to efi shell (im on OC) to get the memory map to work out a proper slide value so i did not need to change this value, hacking around with various slide values never seemed to work either anyway for me with 64M in place.  32M is my sweet spot (it boots anyway multiple times) and what ill live with for now until i find issues with it down the road.

 

if you check my z390 master thread it says to do exactly that if you can’t get it to boot or you can go with igpu disabled and change your shiki value too 144, that works perfectly too but you lose quick sync 

the master board plays very friendly with the igpu enabled so I updated that one a while ago now.

 

When you do check your custom slide value you will find that slide on the z390 pro always ends up being slide=0 

 

Edited February 13, 2020 by AudioGod

[Cass67]

5 minutes ago, AudioGod said:

if you check my z390 master thread it says to do exactly that if you can’t get it to boot or you can go with igpu disabled and change your shiki value too 144, that works perfectly too but you lose quick sync 

the master board plays very friendly with the igpu enabled so I updated that one a while ago now.

 

When you do check your custom slide value you will find that slide on the z390 pro always ends up being slide=0 

 

 

Yeah just checked the master thread and you do indeed say reduce to 32M, well that advice seems to work for this board too... iGPU enabled and 32M preallocated works for me.   Guess i need to start reading both threads consistently since the info is split between them and could be relevant for either   

 

Im not sure what your other issues are relating to this board preventing the release of the new EFI you mentioned.

 

Interesting point on the slide value, i guess i'll not bother any more trying to work out how to get to efishell .. slide=0 and above including messing with the custom slide flags seem not to work on this board in my tests.

 

[AudioGod]

25 minutes ago, Cass67 said:

 

Yeah just checked the master thread and you do indeed say reduce to 32M, well that advice seems to work for this board too... iGPU enabled and 32M preallocated works for me.   Guess i need to start reading both threads consistently since the info is split between them and could be relevant for either   

 

Im not sure what your other issues are relating to this board preventing the release of the new EFI you mentioned.

 

Interesting point on the slide value, i guess i'll not bother any more trying to work out how to get to efishell .. slide=0 and above including messing with the custom slide flags seem not to work on this board in my tests.

 

 

Il update this thread, your not meant to have to check both threads buddy that's totally my bad.

It's hard for me to maintain two threads when I no longer use the Z390 Pro myself anymore so I Lean on other people like poor @texem to test out stuff for me but he's bit fed up of doing it for me now days (and who can blame him?) so its slowed me right down on this thread.

Now that @larabee has returned and when hes feeling up for it he might help me out again with double checking it all with me.

Apologies for the delay but I will get it all sorted out and updated on here ASAP. 

Edited February 13, 2020 by AudioGod

[Cass67]

11 minutes ago, AudioGod said:

 

Il update this thread, your not meant to have to check both threads buddy that's totally my bad.

It's hard for me to maintain two threads when I no longer use the Z390 Pro myself anymore so I Lean on other people like poor @texem to test out stuff for me but he's bit fed up of doing it for me now days (and who can blame him?) so its slowed me right down on this thread.

 Now that @larabee has returned and hes feeling up for it he might help me out again with double checking it all with me.

Apologies for the delay but I will get it all sorted out and updated on here ASAP. 

 

Meh, its no hardship checking 2 places, i read a lot more threads on here so one more is no problem... Id also not be too hard on yourself about working on multiple devices, especially since you no longer have the pro board any more, we should all be happy you're still updating this given the constraints you have right now.

 

I'll look forward to what your going to release next but right now i have a practically perfect system in regards to whats working, nothing i can think of is a problem outside your favourite subject of safari and drm  Which i read will be fixed on 10.15.4.  Not sure what else needs to be updated here outside of new Opencore's or Clovers...  Maybe your fancy DSDT'less EFI would be good to look at

 

EDIT - I don't have much time outside work to help you test but if you need something and i can help if no one else is available, ping me and ill see what i can do !!

 

Cheers

Edited February 13, 2020 by Cass67

[AudioGod]

17 minutes ago, Cass67 said:

nothing i can think of is a problem outside your favourite subject of safari and drm  Which i read will be fixed on 10.15.4. 

 

 Thats the first DRM comment that's made me laugh so big up you brother...lol

I only ever got fed up about it because I always knew it was something apple needed to fix and people went that little bit too nuts about it trying to find a fix when all the time i knew there wouldn't be one until apple sorted it out.

Im over it now and don't get crazy at the mere mention of DRM anymore as long as it doesn't turn into a 10 page assay of nonsense about it.  

Edited February 13, 2020 by AudioGod

[JanRocker]

Hello, would the folder "Aorus Z390 Pro RX Polaris F12d EFI .zip" for the 12b Bios work with a installer for 10.15.3 Catalina? This is the version that I have been able to download via "software update tool".

 

If not, how may I get a 10.15.2 installer

 

Thanks!

[AudioGod]

25 minutes ago, JanRocker said:

Hello, would the folder "Aorus Z390 Pro RX Polaris F12d EFI .zip" for the 12b Bios work with a installer for 10.15.3 Catalina? This is the version that I have been able to download via "software update tool".

 

If not, how may I get a 10.15.2 installer

 

Thanks!

Yes no problems with 10.15.3 install away 

[AudioGod]

NEW Clover Major EFI, 14th February 2020 

(Use With Bios Revision F12d)

 

VERY IMPORTANT NOTICE

PLEASE NOTE IT HAS BEEN DISCOVERED THAT THE DRIVER MemoryAllocation.EFI IS MADE FROM THE SAME CODE AS THE FREE2000.EFI DRIVER AND IS POTENTIALLY HARMFUL TO YOUR SYSTEM SO I HAVE DECIDED TO DROP THE DRIVER FROM MY EFIs.

 

You will need to preform a full bios reset by removing all power to the system and then removing the motherboards internal battery for a few minutes then put it all back and load back in your bios profile and continue as normal.

 

If you find your unable to boot up with the new EFI and the IGPU enabled then you can try dropping the IGPU memory from 64mb to 32mb or if that doesn't work you can disable the IGPU and change the shiki boot argument to shikigva=144

 

The EFI and DSDT has now been updated to the my latest version.

Changes made include,

New DSDT's For bios revision F12d ONLY

MemoryAllocation.efi Removed

OcQuirks Revision 15

AppleALC-1.4.6

VirtualSMC 1.11

Clover Updated too Revision 5103

Plus other minor tweaks to the clover config

 

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

 

Z390 Pro Navi Vega Clover EFI 140220.zip - 14/02/2020 Vega, Navi (5700, 5700XT), Radeon VII DSDT EFI

Z390 Pro Polaris Clover EFI 140220.zip - 14/02/2020 RX5XX Polaris DSDT EFI

HD630 Z390 Pro F12d EFI 140220.zip - 14/02/2020 IGPU Only EFI. SMBIOS MacMini 8,1 

Edited February 14, 2020 by AudioGod

[JanRocker]

55 minutes ago, AudioGod said:

You will need to preform a full bios reset by removing all power to the system and then removing the motherboards internal battery for a few minutes then put it all back and load back in your bios profile and continue as normal.

Hello, is it necessary to perform this for a brand new z390 Pro?

[AudioGod]

5 minutes ago, JanRocker said:

Hello, is it necessary to perform this for a brand new z390 Pro?

 

If you have never had an EFI on it before then no you should be fine but if it won't boot then that's what you got to do to get it going.