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

[juan e. jot]

Thanks, AG! Sorry to be so long-winded. Lost in the bulk of my text is that I did both clear NVRAM & unseat the CMOS battery, and yet the OpenCore boot option persisted in UEFI.

 

Anyway, whenever you and/or others have time to read my meandering tome… thanks again!

[MorenoAv]

Hi all,

Today I created an EFI and installed a new OpenCore 0.5.9, and accidentally deleted my EFI 0.5.9 N-D-K fork, and now I want to know how can I use OpenCanopy to see how it works. Is someone able to help me or point me in the right direction?

Thanks

Edited June 3, 2020 by MorenoAv

[AudioGod]

2 minutes ago, MorenoAv said:

Hi all,

Today I created and installed a new OpenCore 0.5.9, and accidentally deleted my 0.5.9 N-D-K fork, and now I want to know how can I use Opencanopy to see how it works. Is someone able to help me or point me in the right direction?

Thanks

download my Oc Efi buddy and copy my OpenCanopy settings across from the plist and my resources folder too.

i have OpenCanopy enabled as standard now. 

[MorenoAv]

That works, thanks @AudioGod ...

[texem]

1 hour ago, juan e. jot said:

 

• Any possible correlation with video artifacting (in all OSes) that eventually killed two Sapphire Pulse RX580s (luckily, RMA worked, twice, and the current one has been stable for a couple of months)? It may easily NOT be related at all, but the timing of them starting to artifact is merely concurrent with OpenCore being installed at the bootloader. At the time, I had MSR locked, but have since unlocked it (thanks for the 12c file!). Whether locked or not, I did and always have continued to set kernel PM appropriately to the current lock status while using Clover, or set AppleCpuPpuPmCfgLock & AppleXpcmCfgLock appropriately to the current lock status while using Opencore. I have also always removed any " agdpmod=pikera" boot args for

 

OC killing Polaris is (sorry) nonsense nor any correlation with MSR . There might be other reasons .

I would go for a clean install , take care you only have one EFI (preferable on the macOS drive) and no somewhere else.

 

Have a look here.

 

[juan e. jot]

Thanks @texem & @AudioGod, good to hear there's no possible correlation with OpenCore for the GPUs having fried; just bad cards & I'm glad both that my software choices didn't cause it & that RMA stepped up.

 

It looks like the OpenCore Desktop Guide has some info on Setting up Bootstrap.efi that may be of some use with my second and third bulleted points, above. I'll check it out; thanks!  In the meantime, do I understand you correctly @texem,  that there should only be one EFI partition on the entire two-boot-drive system?  If so, what (if anything) should get copied over from the Win/Linux drive's EFI partition to the macOS drive's EFI partition, before wiping the former EFI partition?

 

I could while running OpenCore just hit F12 on system startup to bypass the bootloader and select Linux, but it just seems like something the bootloader was intended to do (and Clover does, on my system as currently set up).

 

In any event, thanks for your insights so far. Now that I've read up, I'll try mt hand at configuring Bootstrap.efi once the system isn't otherwise busy, but feel free to keep sharing any more that occur to you!

[Filmluver]

I'm interested in going OpenCore since it's the future. I'm currently running the previous Clover EFI from AudioGod. Is jumping to OC as easy as replacing the Clover EFI with OC EFI, shut down, pull battery, turn on, load MSR Unlock bios preset, save, reboot.. and that's it?

 

Also in the part where I write in my system info in the new OC config plist, I understand I use the same SystemSerial# and UUID I already generated from current Clover build, but what is the MLB? In the instructions it says enter MLB, but I don't see MLB in old Clover SMBIOS section. Thanks in advance.

[ctguru]

Dumb question, I want to patch my DSDT myself. I can’t seem to find the motherboard model number? Can’t find it on the board with all the stuff on it.
Any idea what model number the gigabyte aorus pro is? My windows boot is having trouble installing, so I can’t boot into windows and look.

Cheers


Sent from my iPhone using Tapatalk

Dumb question, I want to patch my DSDT myself. I can’t seem to find the motherboard model number? Can’t find it on the board with all the stuff on it.
Any idea what model number the gigabyte aorus pro is? My windows boot is having trouble installing, so I can’t boot into windows and look.

Cheers


Sent from my iPhone using Tapatalk

[WizeMan]

1 hour ago, Filmluver said:

I'm interested in going OpenCore since it's the future. I'm currently running the previous Clover EFI from AudioGod. Is jumping to OC as easy as replacing the Clover EFI with OC EFI, shut down, pull battery, turn on, load MSR Unlock bios preset, save, reboot.. and that's it?

 

Also in the part where I write in my system info in the new OC config plist, I understand I use the same SystemSerial# and UUID I already generated from current Clover build, but what is the MLB? In the instructions it says enter MLB, but I don't see MLB in old Clover SMBIOS section. Thanks in advance.

MLB is the board serial number.

[WizeMan]

1 hour ago, Filmluver said:

I'm interested in going OpenCore since it's the future. I'm currently running the previous Clover EFI from AudioGod. Is jumping to OC as easy as replacing the Clover EFI with OC EFI, shut down, pull battery, turn on, load MSR Unlock bios preset, save, reboot.. and that's it?

 

Also in the part where I write in my system info in the new OC config plist, I understand I use the same SystemSerial# and UUID I already generated from current Clover build, but what is the MLB? In the instructions it says enter MLB, but I don't see MLB in old Clover SMBIOS section. Thanks in advance.

MLB is the board serial number.

[Tiem]

So after some fiddling, the correct way to set up DeviceProperties:

 

 

[AudioGod]

3 minutes ago, Tiem said:

So after some fiddling, the correct way to set up DeviceProperties:

 

 

 yup for sure that would work. I’m always saying that page is purely cosmetic unless your using an igpu or doing audio via it. Otherwise it’s all pointless but looks nice...hahahaha

Im with you there.

[pkdesign]

I've updated to Clover 5119 and updated kexts:

AppleALC.kext 1.5.0
IntelMausi.kext 1.0.2
Lilu.kext 1.4.5
WhateverGreen.kext 1.4.0

VirtualSMC.kext 1.1.4

SMCProcessor.kext 1.1.4
SMCSuperIO.kext 1.1.4

 

So far so good!

[Crispymac]

@AudioGod. just swapped the board and everything, same issue, I probably ain't got a hardware defect or a defect either in the RAM or the CPU. Tried windows install with the onboard GPU in first try same issue. so if its the hardware its the case and its cables or the CPU or the RAM.
I appended the logs from the old mainboard and the new one, Could not understand the issue it fired but maybe you or someone here can hopefully.
Sad to have fully PC and you can't install It...

BTW I used today the front panel USB 3.0
yesterday the back and on June 2 the back 3.0 on the old board

 

always f12c and your BIOS profile without ANY changes, the RGB went blue/white after using your profile the standard is yellow so I was pretty sure it worked. without your profile the installer would not even boot. so that is not the issue its somewhere hidden :/

 

Installer Log 5-Jun-2020 new board.txt

Installer Log 2-Jun-2020.txt

Installer Log 4-Jun-2020.txt

[Tiem]

Upgraded my CPU 

 

Also check out that Metal support 

 

[cabal2000]

Hi guys. BIOS versions. At present I am running Z390 I AORUS PRO WIFI. I am guessing its completely different from z390 Aorus pro WIFI?!?!

[Tiem]

4 hours ago, cabal2000 said:

Hi guys. BIOS versions. At present I am running Z390 I AORUS PRO WIFI. I am guessing its completely different from z390 Aorus pro WIFI?!?!

YEEUUUPPPP

[AudioGod]

12 hours ago, Tiem said:

Upgraded my CPU 

 

Also check out that Metal support 

 

 

Metel Support????

Your system must of had some problems if you didn't have support in the past....

 

 

Also I wouldn't personally class a Xeon W as an upgrade, Sidegrade maybe yes.

Are you spoofing you’re 9700k or Is that what you really got or is there a cometlake in there now?

 

Edited June 6, 2020 by AudioGod

[Tiem]

7 hours ago, AudioGod said:

 

Metel Support????

Your system must of had some problems if you didn't have support in the past....

 

 

Also I wouldn't personally class a Xeon W as an upgrade, Sidegrade maybe yes.

Are you spoofing you’re 9700k or Is that what you really got or is there a cometlake in there now?

 

No mine just says "supported" like a real Mac

 

Changed the AppleSystemInfo.strings for my CPU. Just cosmetic. 

 

Also I brought up this issue on the red apple forums in the AMD Navi chipset thread. Look at your display's listed resolution. It says 5k (so does mine). But your display isn't 5K (neither is mine). I'm going to do some digging but that could be an issue. If you take a screenshot of your desktop, no matter what your currently resolution it'll kick out a 5K png. So something is wrong as macOS should always return the res for the physical display (something it reports properly in the display tab of the About this Mac).

[smintel]

Will the Clover EFIs work for Z390 Pro wifi (there doesn't appear to be a 12d bios for it, but there is a 12c - is 12c on the pro wifi same as 12d on Z390 pro)? 

 

I have wake issues where my current setup wakes 30 seconds after being put to sleep - I'm hoping updating might fix this. 

[dsynos80]

1 hour ago, eSaF said:

Use Hackintool for a possible fix, you sleep image should look something like this example.

Yes, this is the sleep solution. Use 12c for ProWifi and load  the unlocked f12c msr unlock profile from 1st post.

[juan e. jot]

Hi folks.  Just reporting what I found with regard to adding Linux to the boot menu for AG & texem's OpenCore EFI: adding a child to the BlessOverride array of config.plist with a string representing the path to the location on the drive of Linux's grubx64.efi (with Windows-style forward backslashes, not Linux/macOS/http-style forward slashes) replaces the Windows boot option (if you've installed it) next to the macOS boot option as presented by the OpenCanopy bootpicker screen.  If you have a functioning grub installation (as I do) and you then select Windows to boot from within grub, OpenCanopy remembers the selection and presents Windows (with a Windows disk icon) alongside macOS and the EFI selection leading to Linux, upon the next boot. Note that clearing NVRAM will clear that Windows icon as an option to boot, but going to grub & booting to Windows from it again, restores the Windows icon (and Windows-booting behavior) to OpenCanopy.

 

As always, your mileage may vary.  This is not a recommendation, but is as well as I've gotten it to function so far, in my case.  Read up, back up, and be ready for the pain of restoring (and whatever re-indexing macOS deems necessary after that, which may take several days) before trying anything that deviates from what AG & texem have already presented in this thread.

 

Issues (not AG or texem's, but OpenCanopy's):

• It doesn't look wonderful, as in OpenCanopy the Linux boot option just names itself the same name as whatever that drive's EFI partition is called & uses a generic icon. (Come to think of it, the macOS drive gets a generic icon too, but that's a separate issue that will take continuing to read & interpret OpenCore's Configuration.pdf.)
• Even if you set your macOS drive as what you want to default boot to in the Startup Disk pane under System Preferences (which is supposed to work under OC, even if it doesn't under Clover), OC still seems to boot up in whatever was most recently selected.
• Worse, somehow even with "OpenCore" set in UEFI BIOS as the primary boot option, bootmgfw.efi (I assume) intermittently bypasses OpenCore entirely & the machine boots straight into Windows without showing the OpenCanopy picker.  This behavior happened (again, intermittently) with version 1909; I haven't tried it* since upgrading to 2004.

* By "haven't tried it" I mean that I didn't love the cosmetics of the first point, and the lack of "set it and forget it" control of the second two points made me return, for now, to Clover.  I'll keep watching OC, and look forward to trying AG & texem's 0.6.0 EFI when it's out! Maybe acidanthera will have addressed or made the ways for users to deal with the above, simpler in OpenCanopy by then… or later.

[Crispymac]

On 6/5/2020 at 9:09 PM, Crispymac said:

@AudioGod. just swapped the board and everything, same issue, I probably ain't got a hardware defect or a defect either in the RAM or the CPU. Tried windows install with the onboard GPU in first try same issue. so if its the hardware its the case and its cables or the CPU or the RAM.
I appended the logs from the old mainboard and the new one, Could not understand the issue it fired but maybe you or someone here can hopefully.
Sad to have fully PC and you can't install It...

BTW I used today the front panel USB 3.0
yesterday the back and on June 2 the back 3.0 on the old board

 

always f12c and your BIOS profile without ANY changes, the RGB went blue/white after using your profile the standard is yellow so I was pretty sure it worked. without your profile the installer would not even boot. so that is not the issue its somewhere hidden :/

 

Installer Log 5-Jun-2020 new board.txt

Installer Log 2-Jun-2020.txt

Installer Log 4-Jun-2020.txt

Just got windows 10 install to work!
created the installer USB with parrallels and rufus instead of straigth through Mac and terminal or Unetbootin.

I am reinstalling now my Macbook Pro and create the hackintosh drive installer from the clean one, that might fix it aswell. 
Crash was allways at 2 minutes remaining, but maybe someone else in here got a tip left.
I used clover, f12c and your exact Bios profile.

[karmasuture]

Hey all, 

 

I'm up and running with the latest Clover EFI and Bios 12d - it updated to Catalina 10.5.5 latest security update with no issues. Thanks for all your hard work on this.

 

I was worried about problems with my Samsung 970 Evo Plus NVME, but it shipped with the latest firmware and I didn't even have to update - everything just worked. 

 

I started out to do this with OC but had a couple problems with the install, so I'll read through the documentation again and try loading the EFI from a separate card. 

 

For anyone specifically thinking of using this hardware for a music workstation, so far it's performing great under Logic Pro X with an Audient ID22 and Audient ASP880. 

 

____

 

Gigabyte Z390 Aorus Pro, I59600k, XFX Radeon 580, Samsung 970 Evo Plus NVME, unlocked BIOS 12d, Audiogod Clover profile, Catalina 10.5.5

Edited June 7, 2020 by karmasuture
redundant

[nikosvr]

Hi, is there a way to enable hardware encoding on RX 580?