Jump to content
AudioGod

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

3,819 posts in this topic

Recommended Posts

Advertisement
2 minutes ago, pkdesign said:

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

 

I did not read that particular guide, setup_var worked fine though

Share this post


Link to post
Share on other sites
18 minutes ago, WizeMan said:

 

I did not read that particular guide, setup_var worked fine though

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

Share this post


Link to post
Share on other sites
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. 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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?

Share this post


Link to post
Share on other sites
30 minutes ago, AudioGod said:

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


I do not recall seeing a darkwake argument on the NVRAM Boot Arguments section, mate.

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites
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.

 

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By Donw35
      09192020 - Big Sur Beta 7 update, no issues.
      09042020 - Big Sur Beta 6 update, no issues.
       
      I have moved on with this and do not use my HP G2 for Hackintosh, its mainly used for Kali Linux for Packet analysis these days, with that said I am using the HP 840 G3 for Hackintosh. I transitioned to OpenCore and Big Sur for this laptop but feel free to continue to ask questions. 
       
      My G3 has the BCM84360CS2 mod, I got the module from eBay for $10 and the adapter for $10 off amazon.
       
      Big Sur Beta 5 is working using the below EFI folder. OpenCore 6.1.0 and latest kexts
       
      Method: USB Big Sur installation
      Create an Big Sur Beta5 or Catalina USB installer (google is your friend here, plenty of tutorials there) Mount the EFI partition of your USB installer using Clover Configurator Copy the EFI file attached here. Boot your laptop using F9 and choose the USB installer and follow the prompts  
       
       
      Catalina and old method in the Spoiler
       
       
      Credits go to Jake Lo for creating this EFI file. I did make some changes to his, this one is Open Core 6.1.0 and latest Lilu.kext and WhatEverGreen.kext
      HP_840_G3_BSB5.zip
    • By mridhulofficial
      Hi team,
      Please advice me for the issue. Already gone through other posts.
      My spec Ryzen 9 3900x and Gigabyte B550 Aorus Pro AC motherboard.
      I installed Cataliana on my system .. everything looking perfect exept ethernet. Installed LucyRTL8125Ethernet.kext and ethernet is showing on network window but no internet connection. Adjusted hardware settings in network as Manually/100baseTX/full-duplex, flow-control but issue not fixed.
      Please help me.
       
      Thanks is advance.
    • By MaLd0n
      -OpenCore Vanilla TUTORIAL-
       
       
      -USB Port Mapping TUTORIAL-
       
        1 -Create a USB bootable
       
      Create your usb installer, use this tool and download Catalina or Big Sur from Apple servers
       
      Catalina
      installScript_allfullapp.zip
       
      Big Sur
      installScript_1016fullapp.zip
       
      Credits: crazybirdy
       
      Copy Catalina / Big Sur installer to Applications folder, open terminal and run
       
      Catalina
       
       
      Big Sur
       
       
      If you want check one step by step, check here
       
      -Opencore Vanilla Tutorial
      https://tinyurl.com/ycvcnp8h
       
      2- EFI folder USB installation
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition in your USB STICK
      https://tinyurl.com/yxsw7d3t
       
      3- EFI folder SSD
       
      -EFI OpenCore Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD 
      https://tinyurl.com/ybwr9kq3
       
      -EFI Clover Folder Desktop 10th Intel Processors
      Paste this EFI folder in EFI partition SSD
      https://tinyurl.com/yxsw7d3t
       
      4- Start Fine Tune
       
      Run this app and post full dump here for full ACPI solution
       
      RunMe.app
      https://tinyurl.com/y9562hz7
       
       
      If you like a SSDT way, here we go
      SSDT-OLARILA.aml.zip
       
      5- USB Solution
       
      Use these kexts, enable XHCI port limit patch
       
      USB INTEL SERIE 400.zip
       
      and follow this tutorial for remap USB ports
       
       
      --DSDT PATCHES--
       
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE ID -DMAC -REMOVE LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM -REAL TIME CLOCK -SLPB -DARWIN / WINDOWS -XHCI -PLUGIN TYPE -HDEF -ARTC -IPIC -TIMR -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -kUSBCompanionIndex -io-device-location -IMEI -EC -PNLF -ARPT -GFX0 -NVME -ACPI-WAKE-GPE -DTGP -HDMI / HDAU  
      --SCREENSHOTS--































      -If you want to buy me a beer - Donations with PayPal
      https://tinyurl.com/r2bvzm7
       
      Big Thanks to XLR and your Badass Motherboard, Ultrafast CPU, Coolest Heatsink, Huge Graphics Card, Tonnes of RAM,
      Gigantic Hard Drive, Lightspeed Disk Burner, Professional Sound Card, Massive LCD Display.
       
       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad and many, many, many others!

      We're all here to have fun and learn from each other!
    • By asheenlevrai
      Hi
       
      I recently built my 1st ryzentosh.
      I also used Opencore (0.6.1) for the 1st time and followed the install guides on Dortania.
       
      Now I need to map my USB ports and apparently it's not achieved the same way on AMD platforms compared to what I was "used to" on Intel platforms.
       
      The guide on Dortania is a bit confusing to me since there is information that is not clearly labelled as "for Intel" or "for AMD" and I thus don't understand very well what I should and shouldn't do.
       
      Can anyone give me advice or point towards as comprehensive tutorial intended for AMD-based builds.
       
      Thank you very much in advance for your help.
       
      Best,
      -a-
    • By tonyx86
      **********************************************************************************
      In this thread, I have fully documented the installation of macOS Catalina on my HP EliteDesk 800 G4 Mini. It is a PERFECT HackMini8,1 and is running very well for me without any issues. I hope this documentation helps you to install macOS on your hack. Please leave feedback if you think there is anything I can improve and let me know if you have any questions.
      **********************************************************************************
       
      Background
      This is my first "modern" hack supporting UEFI and my first hack using Clover "on-the-fly" patches.  My previous hacks
      Laptop: Thinkpad T61 / Nvidia NVS 140m Laptop: Dell Latitude E6410 / Nvidia G3100m Desktop: Gigabyte G31 / GeForce 9600 Desktop: Biostar TH55HD / Sapphire Pulse RX580 (Google "Catalina Biostar TH55HD" and look for user name deeveedee)  
      are all perfectly running Catalina and I patched them all "manually" - all DSDT patches applied with MaciSL with virtually no Clover on-the-fly patching and all booted Legacy Clover.  This UEFI hack was MUCH easier and took about 20 hours vs. a combined hundreds of hours for the old hacks.  I wanted a hack that was a little more future proof and I think this is it.  I hope you enjoy this as much as I am enjoying it.  It is a perfect MacMini8,1.
       

       
      My system specs
      HP EliteDesk 800 G4 Mini (I7-8700T / UHD 630 / Q370 Chipset / 32GB DDR4 RAM) 3 x DP Ports (connected to monitors using DP -> DVI adapters) 6 x USB 3.1 1 x USB Type-C 3.1 2 x NVMe SSD (M.2 PCIe x4 2280/2230 combo ports) 1 x SATA6 SSD 1 x Intel Ethernet RJ-45 Conexant CX20632 Audio Codec Unsupported M.2 PCIe x1 2230 Intel Wi-Fi.  A possible solution is here, but I am NOT offering any support for this.  
      macOS Installation 
      Important: You MUST BE LOGGED-IN to download attachments from this forum
      See macOS installation steps here See Known Issues here for additional installation steps that may not yet be included in my attached config files See CLOVER (UEFI) installation later in this first post
      See BIOS configuration in attached BIOS configuration PDF document
      See EFI and /L/E kexts in attached EliteDesk.zip archive See how I developed my installation methodology here See references here See instructions here for installing two M.2 2280 NVMe SSDs and one SATA HD / SSD  
      What is not working
      Microphone port  
      What is not tested
      USB c 3.1 port (I have partially tested the USB 3 functionality of the port and it seems to be working fine with the SSDT-UIAC.aml in the attached EliteDesk800.zip archive) Wi-Fi / Bluetooth (intentional since I have not yet replaced my Intel card). A possible solution is here, but I am not offering any support for this.
       
      What is working
      Everything not mentioned above Sleep / Wake Multiple displays with IGPU graphics acceleration, hot pluggable display ports and DP->DVI adapters USB 3.1 ports Audio (internal speaker and headphone jack) Ethernet Auto-sensing headphone jack automatically switches to internal speaker when headphones removed  
      Known Issues and their solutions - see here
       
      BIOS Version / Configuration
      Version: 02.11.01 Rev.A or 02.12.00 Rev.A See attached BIOS configuration in PDF document "HP EliteDesk 800 G4 Mini BIOS Configuration.pdf" Intel ME must be enabled for proper sleep / wake of UHD 630
       
      Clover Configuration
      Clover for UEFI booting only Install Clover in the ESP UEFI Drivers Recommended drivers DataHubDxe FSInject SMCHelper File System drivers ApfsDriverLoader VBoxHfs Memory fix drivers OcQuirks (replaces AptioMemoryFix) Additional drivers NvmExpressDxe Install RC scripts on target volume Themes Choose your desired theme Install Clover Preference Pane (option not available when installing on USB thumb drive)  
      UHD 630 Framebuffer Patching
      See here to understand my graphics properties for use with WhateverGreen.kext Read this to see my attempt at graphics patching without WhateverGreen.kext (WEG) to get a better understanding of what WEG is doing
       
      Current Versions
      Catalina 10.15.6 Clover (UEFI) r5122 Lilu.kext 1.4.7 WhateverGreen.kext 1.4.2 AppleALC.kext 1.5.2 IntelMausi.kext 1.0.3 (acidanthera version, not IntelMausiEthernet) NVMeFix.kext 1.0.3 EFIChecikDisabler.kext 0.5  
      Credits To be provided
       
      ScreenShots
       
       
      HP EliteDesk 800 G4 Mini BIOS Configuration.pdf
      EliteDesk800 G4 Mini - Rev 1.2.zip
×