Jump to content

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

AudioGod

By AudioGod,
in Installation Guides

 Share
5,966 posts in this topic

Recommended Posts

Cass67
Cass67
Posted
Posted
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.

Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted
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.

Link to comment
Share on other sites
Cass67
Cass67
Posted
Posted
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.

 

Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
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 by AudioGod
Link to comment
Share on other sites
Cass67
Cass67
Posted
Posted
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.

 

  • Like 1
Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
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. :thumbsup_anim:

Edited by AudioGod
  • Like 1
Link to comment
Share on other sites
Cass67
Cass67
Posted
Posted (edited)
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. :thumbsup_anim:

 

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 by Cass67
  • Thanks 1
Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
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. 

 

:hysterical::hysterical: 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. :hysterical: 

Edited by AudioGod
Link to comment
Share on other sites
JanRocker
JanRocker
Posted
Posted

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!

Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted
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 :thumbsup_anim:

Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted (edited)

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 by AudioGod
Link to comment
Share on other sites
JanRocker
JanRocker
Posted
Posted
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?

Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted
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.

Link to comment
Share on other sites
pkdesign
pkdesign
Posted
Posted
5 hours 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 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. :thumbsup_anim:

Wow, really? You've already switched boards? What are you using now?

Link to comment
Share on other sites
pkdesign
pkdesign
Posted
Posted (edited)

FYI: I do not use MA.efi and the only boot argument I have is darkwake=3 (based on @holyfield post) and I may remove that as well since I can't get sleep to work properly on my system no matter what I do. Probably the combination of peripherals and devices, etc, that I use. No matter, sleep is nice but not very necessary for me.

 

EDIT:
I should clarify that with darkwake=3, I do get sleep with no issue. I just have a problem with external hard drives not disconnecting properly.

 

 

I have no shiki values since I don’t care about DRM in my browsers. I am still on Mojave (no plans to update to Catallina) so that is why this may not matter.

 

So far I have a rock solid system (fingers crossed) and everything works great. BUT, to each his own and every system is different for sure. I know the reason I have such a stable system is the hard work of @AudioGod with the support  of @MaLd0n and his DSDT, and everyone else associated with getting this board up and running. :thumbsup_anim:

 

 

Edited by pkdesign
  • Like 1
  • Thanks 1
Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
47 minutes ago, JanRocker said:

One silly question. Is this installation a Vanilla one? Sorry if this is stupid xD

About as much as it can be yes it is.

 

vanilla that is not stupid :hysterical:

Edited by AudioGod
Link to comment
Share on other sites
Tiem
Tiem
Posted
Posted
5 hours ago, pkdesign said:

EDIT:
Is should clarify that with darkwake=3, I do get sleep with no issue. I just have a problem with external hard drives not disconnecting properly.

You'd likely have those on a real Mac as well. That has nothing to do with how the EFI is setup and everything to do with your external drives and how their firmware handles power loss. Most handle it like ass. Lacie, WD, they are all a hot mess.

Link to comment
Share on other sites
Cass67
Cass67
Posted
Posted
3 minutes ago, JanRocker said:

More silly questions.

 

I plan on installing two separate ssd, one for macos and the other for Windows.

 

Patching the DSDT of the MB could affect Windows in some way?

 

Thanks again!!!

If you use a custom DSDT with Clover or stock OpenCore then yes... What OS you select in the boot menu will take on the properties of what custom DSDT changes you made.  In this case if you don't want this use the UEFI boot picker you're MB provides.

 

On the other hand, with the NDK custom OpenCore release, it patches this behaviour out and you can choose (i think(it may be default behaviour)) not to have DSDT changes affect other OS's.  

 

Either way i never had an issue that i know about using Clover with a DSDT and picking Windows or Linux from the Clover boot screen or indeed nowadays since i use stock OpenCore i never have to worry about it as i use the MB UEFI boot menu to boot other OS when i need it.  I never looked very much to the custom NDK version as i prefer stock OC and im OK using the MB boot selector to boot which drive i need.

 

 

 

Link to comment
Share on other sites
Tiem
Tiem
Posted
Posted

Both Clover and OC provide a way to ignore patching anything if Windows is loaded. Please read each one's documentation on how to implement.

 

With that said, if the DSDT is set up correctly (and this is), then it won't matter. Nothing will apply to Windows. It would only affect those with an already busted build held together by duct tape.

Link to comment
Share on other sites
Alex1982
Alex1982
Posted
Posted
11 hours ago, AudioGod said:

 

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.

Hi @AudioGodCould you please clarify the meaning of "never had an EFI on it"? I just remove MemoryAllocation.efi from EFI folder and add slide=0 argument in clover boot args and system boots fine as before without BIOS reset. Should I still need to reset my F12d BIOS(MSR unlocked) to avoid any potential problems in future?

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...