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

WizeMan
WizeMan
Posted
Posted
17 minutes ago, AudioGod said:

No no buddy it’s setup_var_3 you should be doing it with.

Hm I haven’t had any issues until now but I’ll be keeping an eye then, if I notice anything going wrong I’ll redo with setup_var_3. 

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

So the other thread about the Aorus Master was updated about the fact that MemoryAllocation.efi is the same as free2000 and thus not recommended. Any updates for the Aorus Pro? 

From my understanding Z390 boards need some kind of memory fix .efi with sometimes a custom slide value, but @AudioGod seems to recommend not putting any other memory fix .efi, I'm confused... EDIT : reading around it looks like it's hard to have the Aorus Pro with the iGPU enabled, which is required for 19,1 SMBIOS.

Edited by Pieroman
Link to comment
Share on other sites
WizeMan
WizeMan
Posted
Posted
6 minutes ago, Pieroman said:

So the other thread about the Aorus Master was updated about the fact that MemoryAllocation.efi is the same as free2000 and thus not recommended. Any updates for the Aorus Pro? 

From my understanding Z390 boards need some kind of memory fix .efi with sometimes a custom slide value, but @AudioGod seems to recommend not putting any other memory fix .efi, I'm confused... EDIT : reading around it looks like it's hard to have the Aorus Pro with the iGPU enabled, which is required for 19,1 SMBIOS.


I removed MemoryAllocation.efi this morning. Cleared NVRAM and my iMac19,1 setup works fine. About mid-day I switched back from Vega 56 to Polaris RX 580 and it is also working. So I’d say at least with my setup there is no issue removing the MemoryAllocation.efi from the EFI.

 

PS: if you’ll be using OpenCore be sure to remove the entry from the Drivers section as well.

  • Thanks 1
Link to comment
Share on other sites
Tiem
Tiem
Posted
Posted (edited)
2 hours ago, pkdesign said:

The only difference in that guide is that @Tiem says to use setup_var_3

Correct. Both setup_var and setup_var_3 will return the same error. But the latter will actually apply the variable and unlock your board. Using setup_var will just error out and your board will still be locked.

 

If you're not sure whether the CFG unlock offset was applied, you need to use UEFITool and IFR-Extractor to ensure the offset changed from 0x1 (locked) to 0x00 (unlocked). Relying on the fact your system can boot isn't really ideal.

 

If you have the WIFI variant of the Pro, you need to apply the patch via the modified grub shell (or hack your own firmware file). If you have a regular Pro, then AG has linked an actual unlocked BIOS firmware, which is the ideal way to remove the CFG Lock. Just flash your board with it and you're good to go.

Edited by Tiem
Link to comment
Share on other sites
WizeMan
WizeMan
Posted
Posted (edited)
15 minutes ago, Tiem said:

Correct. Both setup_var and setup_var_3 will return the same error. But the latter will actually apply the variable and unlock your board. Using setup_var will just error out and your board will still be locked. 


Not correct. If setup_var was unsuccessful and left my board’s CFG Lock enabled, it wouldn’t be able to boot after setting


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

 

I do not disagree with your statement that setup_var_3 works (heck, it might work better than setup_var) but using setup_var DID disable the CFG Lock

Edited by WizeMan
Link to comment
Share on other sites
Neek
Neek
Posted
Posted
1 hour ago, WizeMan said:


I removed MemoryAllocation.efi this morning. Cleared NVRAM and my iMac19,1 setup works fine. About mid-day I switched back from Vega 56 to Polaris RX 580 and it is also working. So I’d say at least with my setup there is no issue removing the MemoryAllocation.efi from the EFI.

 

PS: if you’ll be using OpenCore be sure to remove the entry from the Drivers section as well.

Can confirm that clearing NVRAM/CMOS and re-doing BIOS setting as in the guide allowed me to remove MemoryAllocation.efi.

 

When I was lazy and didn't pull the battery and reset CMOS pins I needed the extra. All is well now.

  • Like 1
Link to comment
Share on other sites
Neek
Neek
Posted
Posted
23 minutes ago, pkdesign said:

I hate to sound lazy...but, can i just remove MemoryAllocation.efi and not clear NVRAM or reset my BIOS? Such a pain in the ass to do.

Boot off a backup USB w/your EFI (a version that has MA.efi removed) and see if it'll work.

 

Chances are it won't, but you may get lucky.

 

Do NOT modify your main EFI without trial booting off of an external backup that includes your proposed changes.

Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
29 minutes ago, pkdesign said:

Well, I was lazy. I just removed MemoryAllocation.efi and off I went. No issues rebooting after that.

For now you mean. Wait for it!!!!!!

 

clear out your nvram via clover or OC at the very least bud

Edited by AudioGod
  • Thanks 1
  • Haha 1
Link to comment
Share on other sites
Tiem
Tiem
Posted
Posted

Clearing NVRAM is fine for 99% of things. And you really should do it every time you make any change to your EFI. It's basically a reboot. Not that big of a deal.

 

You really don't need to reset your BIOS for these things.

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

Hi, i just fix my problem of my radeon VII by disabling audio and used a DAC, ( https://www.tonymacx86.com/threads/radeon-vii-repeated-kps-10-14-6.281254/ ) ( https://www.tonymacx86.com/threads/radeon-vii-and-new-amd-gpus-compatibility.269128/page-45 )
In my log than i posted forward yesterday there is one line about AppleGFXHDA but this kext is not present in my S/L/E. As they said on tony topics to remove it, I tryed to put the AppleHDADisabler.kext to to fix my problem. It seems to be working. No more KP. 
I had ordered two Radeon VII to find the best overclock ( https://docs.google.com/spreadsheets/d/1Iim9e_ejX3nkgxLIZ3vLu1seQ1m0lDTKUhClJpAO-Gk/edit?usp=sharing ). My first one radeon has no problem, but the new gave me the Kp and UC undercontrol. the radeon isn't still overclocked, i am waiting a stable macos. It depends of the radeon VII I suppose. 
Can you tell me if I need to patch SDST my Watercooling using usb for working well  ?

Edited by hansik
Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted (edited)
9 hours ago, Tiem said:

Clearing NVRAM is fine for 99% of things. And you really should do it every time you make any change to your EFI. It's basically a reboot. Not that big of a deal.

 

You really don't need to reset your BIOS for these things.

When it comes to dropping MA.EFI your completely wrong bud and 9 it of 10 times your going to need to pull the battery or short the pins to bring it too life. Anybody that does it without doing that and gets away with it will down the line get boot failures but nine out of ten times it just won’t boot at all.

this is why I say to do it and I stick to my guns about it.

 

To explain abit more to why without getting all technical about it, MA.EFI and free2000 unlock a section of memory that is reserved and not meant to be used and when you drop the driver again you leave a pile of mess in that reserved area of memory. F11 via clover or a NVRam reset via OC doesn’t clean out the reserved area of memory, there is only two ways to do that properly. 1 is to pull the battery from the mortherboard or 2 is to reflash the bios. Anything else doesn’t clean that area of memory out.

I hope that clears up why I am so instant on the process and makes sense to everybody as to why it need to be done. :) 

Edited by AudioGod
  • Like 3
Link to comment
Share on other sites
WizeMan
WizeMan
Posted
Posted (edited)

Has anybody else noticed with the latest OpenCore EFI that it needs two mouse clicks and more time to fully wake up? It used to wake with one mouse click and almost instantly.

 

I am using a Magic Mouse 2.

 

While the beast is sleeping I click the mouse once. The motherboard LEDs, fans and CPU AIO start working but monitor does not wake.

 

If I wait and don’t click the mouse again, it will sleep again. If I click again and mouse the mouse, unlock with watch kicks in, unlocks the hack and the monitor wakes.

 

Anyone else experiencing this?

 

(I’ll try the latest Clover EFI on Monday to see if I can replicate the same behavior)

Edited by WizeMan
Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted
2 minutes ago, WizeMan said:

Has anybody else noticed with the latest OpenCore EFI that it needs two mouse clicks and more time to fully wake up? It used to wake with one mouse click and almost instantly.

 

I am using a Magic Mouse 2.

 

While the beast is sleeping I click the mouse once. The motherboard LEDs, fans and CPU AIO start working but monitor does not wake.

 

If I wait and don’t click the mouse again, it will sleep again. If I click again and mouse the mouse, unlock with watch kicks in, unlocks the hack and the monitor wakes.

 

Anyone else experiencing this?

 

(I’ll try the latest Clover EFI on Monday to see if I can replicate the same behavior)

Have you got darkwake=8 or 0 missing from your boot arguments by any chance bro?

Link to comment
Share on other sites
WizeMan
WizeMan
Posted
Posted (edited)
8 minutes ago, AudioGod said:

Add one mate darkwake=8 

Thanks. Will do and post results tomorrow morning or Monday morning.

 

PS shouldn’t this be on the EFI by default? I remember the Clover variants did actually have it.

Edited by WizeMan
  • Like 1
Link to comment
Share on other sites
c1ru
c1ru
Posted
Posted
2 hours ago, AudioGod said:

Have you got darkwake=8 or 0 missing from your boot arguments by any chance bro?

sorry for quote this msg with my off topic, but looking for any configuration where you can get working a thunderbolt with video setup in this forum, and I don't know if I need thunderbolt in the motherboard or the graphic card.

Link to comment
Share on other sites
AudioGod
AudioGod
Posted
  • Author
Posted
13 minutes ago, c1ru said:

sorry for quote this msg with my off topic, but looking for any configuration where you can get working a thunderbolt with video setup in this forum, and I don't know if I need thunderbolt in the motherboard or the graphic card.

 

  • Thanks 1
Link to comment
Share on other sites
WizeMan
WizeMan
Posted
Posted
14 hours ago, WizeMan said:

Has anybody else noticed with the latest OpenCore EFI that it needs two mouse clicks and more time to fully wake up? It used to wake with one mouse click and almost instantly.

 

I am using a Magic Mouse 2.

 

While the beast is sleeping I click the mouse once. The motherboard LEDs, fans and CPU AIO start working but monitor does not wake.

 

If I wait and don’t click the mouse again, it will sleep again. If I click again and mouse the mouse, unlock with watch kicks in, unlocks the hack and the monitor wakes.

 

Anyone else experiencing this?

 

(I’ll try the latest Clover EFI on Monday to see if I can replicate the same behavior)

 

13 hours ago, AudioGod said:

Add one mate darkwake=8 

 

I added darkwave=8 and it seems to have fixed the issue. Thank you @AudioGod

Proposal: Since this boot argument is by default on the Clover variant I think we should add it by default on the OpenCore one as well.

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