Jump to content

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

AudioGod

By AudioGod,
in Installation Guides

 Share
5539 posts in this topic

Recommended Posts

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?

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

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.

 

 

 

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.

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?

AudioGod
AudioGod
Posted
  • Author
Posted (edited)
3 hours ago, AlexeyNikitin said:

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?


the driver MA.EFI leaves traces of itself in the reserved memory allocation layer and the only way to truly clear it out for good is to do a battery bios reset or reflash the bios. Anything else won’t fully clear it out properly and could cause problems X amount of time later.

 

Edited by AudioGod
Alex1982
Alex1982
Posted
Posted (edited)

Thanks a lot for your clarification @AudioGod. Could you please clarify some more questions:

1. In your original post you mentioned that NVRAM emulation is no more required, so I removed EmuVariable.efi and Clover RC scripts. I see that NVRAM still working(Clover remember last selected boot drive, opened application windows are restored after reboot/shutdown etc). The question is: where it stores NVRAM now? In the reserved memory allocation layer you mentioned? Also I observe some strange issue: if I check/uncheck "restore windows" checkbox before shutdown the system reboots instead of shutdown and during first boot I got message that system was recovered from error. All subsequent reboot/shutdown operations are fine until I again trigger "restore windows" checkbox. Also with unchecked "restore windows" checkbox some times system still restores opened windows after reboot. May be it is related somehow with MA.EFI? I don't tried to reflash the BIOS yet.

2. In your latest EFI I see KernelPM fix is enabled. Does it still needed even with unlocked MSR? I tried to set KernelPM fix back to disabled and system boots fine.

3. After updating to F12d BIOS I got very low resolution(1024x768 or even 800x600, don't quite sure but it is really very low) in Clover boot screen and macOS early boot screen. I have CSM support disabled in BIOS(I know that enabled CSM support can cause such issue) as you suggested. Also tried to set screen resolution in Clover config but it don't give any effect. Do you know how to fix this issue?

 

Thanks a lot in advance!

Edited by AlexeyNikitin
texem
texem
Posted
Posted
9 minutes ago, AlexeyNikitin said:

3. After updating to F12d BIOS I got very low resolution(1024x768 or even 800x600, don't quite sure but it is really very low) in Clover boot screen and macOS early boot screen. I hame CSM support disabled in BIOS(I know that enabled CSM support can cause such issue) as you suggested. Also tried to set screen resolution in Clover config but it don't give any effect. Do you know how to fix this issue?

 

BIOS Boot -> Windows8/10WHQ

 

  • Like 1
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
14 minutes ago, texem said:

 

BIOS Boot -> Windows8/10WHQ

 

@AlexeyNikitin do exactly as @texem just said but more importantly goto page one of my thread and every question you have just asked has a Answer in my guide tips. 
But to answer to your questions anyway bud,

1. NVram is stored natively like it should be
2. I set kernal PM to true because some people don’t want to unlock there MSR And this way somebody with a locked MSR will be able to boot in with no trouble and the people with a unlocked MSR can just uncheck it again with no trouble,

3. Do what Texem Said to do :thumbsup_anim:

 

10 hours ago, Tiem said:

Too fast my friend, v15 just dropped :hysterical:


That’s exactly what your GF said to me last night the dirty girl :hysterical::hysterical: (jokes)

 

FFS a new one in a few days..ok ok il do a silent little update to R15

Edited by AudioGod
pkdesign
pkdesign
Posted
Posted
15 hours ago, Tiem said:

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.

Yes this is what I've come to discover. This is a universal issue.

AudioGod
AudioGod
Posted
  • Author
Posted (edited)
19 minutes ago, lanparty35 said:

Do you have plans for update HD630 EFI without external GPU?

Have a look on page one bud, there’s a Efi already for that just remove the driver MemoryAllocation.efi from the UEFI folder before you use it,

 

I will update it later though but there’s not much else to do other then the above and a few minor driver updates.

Edited by AudioGod
AudioGod
AudioGod
Posted
  • Author
Posted

@lanparty35 Here you go Pal, All updated and now using smbios MacMini 8,1 but feel free to change it over to the Smbios of your choice. :)

 

HD630 Z390 Pro F12d EFI 140220.zip  Use with Bios revision F12d Only (14/02/2020 IGPU Only EFI) SMBIOS MacMini 8,1 

AudioGod
AudioGod
Posted
  • Author
Posted

CLOVER DRIVER UPDATE 14/02/2020

 

OcQuirks Revision 15 & FwRunTimeServices Latest Versions.

 

OcQuirks R15.zip

 

(Already Included in the latest Clover EFIs 14/02/20)

stavidawg
stavidawg
Posted
Posted

Does the new EFI still support iMessage? I was under the impression some type of memory efi is needed for it to work?

 

Also I figured out why your EFI folder wasn't working.. I vertically mounted my GPU and had it plugged into the bottom PCI port, not realizing the two bottom ports are NOT PCIx16 lanes... So plugging it into the top one did the trick immediately. 

 

  • Like 1
AudioGod
AudioGod
Posted
  • Author
Posted
1 minute ago, stavidawg said:

Does the new EFI still support iMessage? I was under the impression some type of memory efi is needed for it to work?

 

Also I figured out why your EFI folder wasn't working.. I vertically mounted my GPU and had it plugged into the bottom PCI port, not realizing the two bottom ports are NOT PCIx16 lanes... So plugging it into the top one did the trick immediately. 

 

Yup everything works as per normal including all iCloud services.

  • Like 1
Tiem
Tiem
Posted
Posted
3 hours ago, pkdesign said:

Yes this is what I've come to discover. This is a universal issue.

Play with pmset disksleep. Man pmset for details. But setting disksleep will prevent external drives from sleeping.

stavidawg
stavidawg
Posted
Posted (edited)

EDIT: After a few restarts it's all working now!

 

Awesome! 

Everything seems to be up and running great with the exception of continuity? Handoff works but fine but air play, side car and if right click on the desktop and click import do not work. For both the latter, I will eventually get an error that that says the "device timed out".  I saw that you had side car working from the front page and was just wondering if there was anything in particular you had to finagle, or a thread I could look through.

Edited by stavidawg
 Share
Go to topic listing
×
×
  • Create New...