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

[pkdesign]

Update to OC 0.7.1 was a total success. Only had to add two items to config (and of course update kexts).

 

SyncTableIDs to ACPI>Quirks and CustomKernel to Kernel>Scheme.

[mariodj]

I do my first update all done by myself and i lost icons on boot menu.

What could be a problem here ?

[letsdrink]

How to update my system after AudioGod stopped making new EFIs?

[mariodj]

11 hours ago, eSaF said:

1. First you need to insure all your kexts are the latest versions.

2. Down load OC version 0.7.1 from here - https://github.com/acidanthera/OpenCorePkg/actions.

3. Find the 64 bit EFI Folder and copy it preferably to a test USB Drive.

4. Look into the Docs Folder and copy the Sample Config.plist to the new EFI Folder.

5. Copy your new kexts to the kext Folder also your original SSDT Files to the ACPI Folder.

6. Use a good config.plist Editor like PlistEdit Pro and open both your old config.plist and the Sample one side by side and copy the entries from your old one.

7. When that is done save the settings, rename Sample to config and save.

8. Now you can see if the changes you made will boot from the test USB.

 

Yes this is a long winded way but I tried to simplified the process as much as possible. There are less convoluted methods as described here but I get the sense that you are in the dark of exactly what to do. Maybe someone else will offer an easier route to updating your EFI Folder. Good luck.

 

I make update followed your instructions but still no icons on boot menu. Any idea ?

[Anto65]

7 minutes ago, mariodj said:

 

I make update followed your instructions but still no icons on boot menu. Any idea ?

https://www.insanelymac.com/forum/topic/348064-how-to-opencore-069-070-differences/?tab=comments#comment-2760047
Have a look here "OpenCanopy image directory structure"

make sure you have updated the resources folder      https://github.com/acidanthera/OcBinaryData

[mariodj]

1 hour ago, antuneddu said:

https://www.insanelymac.com/forum/topic/348064-how-to-opencore-069-070-differences/?tab=comments#comment-2760047
Have a look here "OpenCanopy image directory structure"

make sure you have updated the resources folder      https://github.com/acidanthera/OcBinaryData

 

And the problem is solved  Thanks Antuneddu  

Like u said directory structure was changed.

[laxattack]

Has anyone updated to 11.5 yet with Opencore 0.7.1?

[juan e. jot]

24 minutes ago, laxattack said:

Has anyone updated to 11.5 yet with Opencore 0.7.1?

Yup; being sure to follow (in order) the recommendations above for prepping one's EFI for 0.7.1, it works just as 11.4 did.

[benjiolino]

I made a EFI with open core 0.71 and it works with MacOS 11.5 with my specs. Z390 Aorus Pro - Radeon VII. If anybody needs it please don't forget to put your serial numbers and reset NVRAM.

EFI.zip

[Hifi33]

I am trying to test the new OC 0.7.1 but I must be doing something wrong with he USB stick.  I drag the updated EFI folder to a newly formatted (extended journaled) USB stick, and at boot up I can select it, but its a black screen from there.  I tested it with my current working EFI and the same thing.  I'm likely doing something wrong with the formatting or something.  Any ideas where the problem could lie?  A setting in the bios?

[benjiolino]

5 hours ago, Hifi33 said:

I am trying to test the new OC 0.7.1 but I must be doing something wrong with he USB stick.  I drag the updated EFI folder to a newly formatted (extended journaled) USB stick, and at boot up I can select it, but its a black screen from there.  I tested it with my current working EFI and the same thing.  I'm likely doing something wrong with the formatting or something.  Any ideas where the problem could lie?  A setting in the bios?

But you know you have to mount the EFI partition on the stick and drop it there?

[Hifi33]

13 hours ago, benjiolino said:

But you know you have to mount the EFI partition on the stick and drop it there?

Oh right.  I must have initially formatted it wrong as there isn't an EFI partition on the stick that I can see in ESP mounter pro in FAT or hfs.  Easy to tell it's been a while since I've updated etc. and tested via USB. ha. I'm a little rusty.

 

I got it now... 🤦‍♂️  It was the formatting of the stick.  Show All Devices in Disk Utility and select GUID Partition Map on the USB.   Thanks for the heads up.  

Edited July 27, 2021 by Hifi33

[DoYouBelieveInMiracles]

On 7/26/2021 at 10:18 AM, benjiolino said:

I made a EFI with open core 0.71 and it works with MacOS 11.5 with my specs. Z390 Aorus Pro - Radeon VII. If anybody needs it please don't forget to put your serial numbers and reset NVRAM.

EFI.zip 8.93 MB · 29 downloads

 

Hello there, would this EFI work for me? (I have i9-9900K, Z390 Aorus Pro and Radeon 5700XT.)

Also can someone clarify if AG is out of the scene, meaning he will never make EFI for this build again?

Thank you in advance.

[AudioGod]

Out of the scene, Not at all but maintaining my old Intel Threads and keeping the EFIs up to date I have indeed stopped doing.

Im now fully invested in the AMD side of Hackintoshing and that’s where my energy goes now.

 

The OpenCore EFI that’s still available to download will work fine for you with all OS up to Monterey.

Edited August 5, 2021 by AudioGod

[WizeMan]

1 hour ago, AudioGod said:

Out fo the scene, Not at all but maintaining my old Intel Threads and keeping the EFIs up to date I have indeed stopped doing.

Im now fully invested in the AMD side of Hackintoshing and that’s where my energy goes now.

 

The OpenCore EFI that’s still available to download will work fine for you with all OS up to Monterey.

 

The influence M0rg0n4ut has on you is obvious, brotha!  

[benjiolino]

On 8/5/2021 at 1:55 PM, unknownharris said:

 

Hello there, would this EFI work for me? (I have i9-9900K, Z390 Aorus Pro and Radeon 5700XT.)

Also can someone clarify if AG is out of the scene, meaning he will never make EFI for this build again?

Thank you in advance.

It would work if you add: "agdpmod=pikera" to the boot args.

Edited August 7, 2021 by benjiolino

[panosru]

Hi all! I updated my OC to the latest version, The changes I made are the following:

 

I added UEFI -> AppleInput -> GraphicsInputMirroring (boolean set to True)

Modified Misc -> Security -> SecureBootModel (string set to Default, previous value was j137), as far as I'm aware, j137 won't work with Monterey on machines without T2 chip, but don't take my word for it.

 

The sample config has many differences, therefore I'm not sure if I missed anything important.

 

UPDATE:

for Misc -> Security -> SecureBootModel I'm not sure if I have to set Default or x86legacy, also, for APFS MinDate and MinVersion, currently I have it set to zero, but I think that -1 should be the better option.

 

UPDATE2:

I set it to x86legaxy and set the Min Date and Version to -1, on 11.15.1 it works like a charm, I'm not sure if the changes will work on lower than 11.0.1 version.

Edited August 11, 2021 by panosru

[pkdesign]

I've updated as well. Added three things:

Misc > Security > SecureBootModel =Disabled

UEFI > AppleInput > GraphicsInputMirroring (boolean) = True (or yes)

UEFI > APFS = Set to Mojave setting from below.

 

I have always had to have SecureBootModel set to Disabled. It may be that I am on Mojave.
 

UEFI>APFS: Increased default APFS MinDate and MinVersion to macOS Big Sur for better security. These keys are the minimal allowed APFS driver date and version to be loaded. Examples:
    - MinDate and MinVersion 0 is default (currently Big Sur), leave this value if you are using Big Sur or Monterey
    - MinDate=20210508 and MinVersion=1677120009000000 is for Big Sur 11.4 (20F71)
    - MinDate=20200306 and MinVersion=1412101001000000 is for Catalina 10.15.4 (19E287)
    - MinDate=20190820 and MinVersion=945275007000000 is for Mojave 10.14.6 (18G103)
    - MinDate and MinVersion -1 is disabled (not recommended).
It's required to change MinDate and MinVersion in the APFS section for macOS versions older than Big Sur.

[MetalSoul666]

Hello

 

Guys, i'm facing problem while install (freash) on my machine

 

the problem happens duting installation and here is the errors, i got during install process

 

stuck on this during install

 

 

than i got this error

 

 

BTW, it's was installed on my machine same EFI but i was tring to format and got this problem

 

my hardware

 

CPU: i9 9900k

Motherboard: Aorus z390 Pro

GPU: Radeon VII

 

 

any idea about this problem?

 

best regards
 

[MetalSoul666]

4 hours ago, eSaF said:

Hi a few questions - Updating from what version OS X to which, are all your kexts the very latest and is OC the latest version?

 

hello

 

thank you for reply

 

currently i want fresh install of 11.5.2 and my all kexts latest update and my opencore version is 0.7.2

 

in my config System Product is iMac19,1 

 

btw was everything working, i was just want format and re-install after fail into update to latest version

 

best regards

[MetalSoul666]

7 hours ago, eSaF said:

@jrkman - Hi compress your EFI Folder and upload it here and we'll take a look and see what the problem may be.

Hello

This is my EFI folder

 

https://drive.google.com/file/d/1Y8QgrMNZ6GoByScV8Wdd0F4BSGMKz__q/view

 

😀

[texem]

Hi all, still alive 😇

 

fiddling with 12.0 beta 6 and now i have issues with bluetooth after wake from sleep. I have to disable/enable BT getting mouse and kbd re-connected.

Seems the driver behaves different now. Never had any issue(s) with BT since using my BCM PCIe card which is natively supported but now ...

 

Couldn't find a kext fixing this, always tried some promising tweaks.

 

For my taste it has something to do with power-management, possibly the card is now fully offline cos wake via BT doesn't work as well.

 

Anyone ?

 

Cheers

 

 

[pkdesign]

I've updated to OC 0.7.3 with no issues. Just had to add one quirk and redo "Drivers" section to match new formatting.

 

UEFI>ForceOcWriteFlash = NO

 

Sample of new Drivers section. You can have all drivers present (in OC>Drivers) now, just change key to "Disabled" is you don't use. I keep mine clean and only have what I need:

			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>Path</key>
				<string>HfsPlus.efi</string>
			</dict>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>Path</key>
				<string>OpenRuntime.efi</string>
			</dict>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>Path</key>
				<string>OpenCanopy.efi</string>
			</dict>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>Path</key>
				<string>AudioDxe.efi</string>
			</dict>

 

[juan e. jot]

56 minutes ago, pkdesign said:

I've updated to OC 0.7.3 with no issues. Just had to add one quirk and redo "Drivers" section to match new formatting.

 

UEFI>ForceOcWriteFlash = NO

 

Sample of new Drivers section. You can have all drivers present (in OC>Drivers) now, just change key to "Disabled" is you don't use. I keep mine clean and only have what I need:

			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>Path</key>
				<string>HfsPlus.efi</string>
			</dict>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>Path</key>
				<string>OpenRuntime.efi</string>
			</dict>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>Path</key>
				<string>OpenCanopy.efi</string>
			</dict>
			<dict>
				<key>Arguments</key>
				<string></string>
				<key>Enabled</key>
				<true/>
				<key>Path</key>
				<string>AudioDxe.efi</string>
			</dict>

 

This is a great start! Linux multi-booters, read on for a warning!

 

Unfortunately, these steps haven't worked for me yet, as I triple-boot with one of the options being Linux.  Since acidenathera have just overhauled how GRUB & systemd-boot* are expected to work with OpenCore (and it looks like it's an offshoot of acidenathera's expectation to use efibootmgr from within Linux rather than the older BlessOverride entry in config.plist; but we as yet have no corroboration from Dortania, whose guide still covers 0.7.2), I have some more tinkering to do.

 

In fact, trying the method above while retaining my BlessOverride entry in config.plist & NOT yet installing or referencing the new OpenLinuxBoot.efi under Drivers as you have other drivers above, the OpenCanopy boot graphics go away (though I have yet to see an update to Resources from OcBinaryData), and any mention of my macOS boot drive by name goes away, too; I'm left with "Windows" and two "NO NAME" entries (one probably being macOS & the other probably being Linux, but who knows which is which), and I can't seem to space out of there to reset NVRAM.

 

In any event, I'll try to post whatever was successful, once it is!

 

*Weird point for Linux users & acidanthera, if they see it: Differences.pdf for 0.7.3 asserts that if your Linux distro uses systemd-boot, it's likely Arch. Um, not so; I recognize the irony of saying "BTW, I don't run Arch…," but various non-Arch distros I've tried & in fact run on various machines, use systemd-boot. Even across bases, the boot manager differs; among Ubuntu-based distributions, for example, elementary OS (currently) uses GRUB by default, but Pop!_OS (currently) uses systemd-boot by default. So getting one or another BootLoaderSpec/[ByDefault] way of booting to Linux consistently, with either consistency or a clear delineation between GRUB & systemd-boot in the instructions, will be great, moving forward. Thanks for reading this far!

[DoYouBelieveInMiracles]

Hello there folks and hope you are all well 😇

I was wondering if someone could provide an update as to what will happen from Monterrey and further.

I mean I am trying to piece together how to set-up a successful EFI now that AG has departed and zip is provided but cannot really comprehend how because you are talking in a higher expert level.

Will someone be able to compress EFIs for us less simple-minded on the subject of Hackintoshing that carry the same AG original build moving forward?

 

P.S: Don't take this as a hostile post or anything, just noting that there might be other people here as well that might be new to Hackintoshing (like me) and cannot successfuly make it work on their own as the macOS moves forward so we might need a boilerplate.