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

[markl18]

18 hours ago, eSaF said:

@scotty pro - Hi without changing anything else, please re-enter your personal data to the config.plist and try this EFI Folder on a test USB Drive. I have updated all files to the latest OC 0.7.8 as they were some outdated files, don't forget to clean the NVRAM before booting from the USB Drive. If your using p/c speakers you might need to reduce the volume slightly as I have enabled Startup Boot Chime. If the revised folder is to your satisfaction, then you can copy the entire folder to the EFI Partition of your main drive. Good luck.

OC.zip 6.3 MB · 3 downloads

all of the sudden after I looked at your EFI file I solved all of my problems except "unsupported image"

 

Edited February 17, 2022 by markl18

[scotty pro]

I do not have a front USB-C port just the back one that is what the phone is plugged into, might have a dodgy back port but I have nothing else to connect to it.

 

Just tried the front usb 2.0 standard port and that seems to work OK

[pkdesign]

On 2/16/2022 at 10:34 AM, scotty pro said:

@eSaF

 

I have used your updated OC Efi folder a couple of pages back (0.7.7) as I was still on Audiogods original version running Mojave.

 

Just plugged my new iPhone 13 into the back USB C port and the Mac does not see it, is there any reason why I cannot see the iPhone, is the back Type C port disabled in your USB kext.

 

Any suggestions would be gratefully appreciated to get it working as I have just ordered an Apple Watch 7 and I think the only way to connect that is with the Type C port.

Well. This has sent me down a rabbit hole. I didn’t even notice that my phone was not showing up in the side bar. I normally just plug it in anywhere to transfer but tried the USB C port in the back and nothing.

 

I have been using the SSDT-6 and config edits since @eSaF first mentioned it months ago.

 

If I plug my USB 3.1 10Gbs external hard drive into that port, it shows right up as SS06 TypeC+Sw in Hackintool.

 

What gives?

 

EDIT:

Dang it!! I never had CDs, DVDs, and iOS devices ticked in Finder Preferences. Doh.

Edited February 17, 2022 by pkdesign

[scotty pro]

19 hours ago, eSaF said:

The attached pic shows where the connection is on mine and it is exactly in the same location as on your board, just have a look and see if a case cable leading from a USB-C plug-in point is attached to where the arrow is pointing in the pic.

  Hide contents

 

I do not have a cable where you have indicated, I am using the port on the rear as indicated by the blue circle.

 

 

 

 

[panosru]

I wonder why if I set ResizeAppleGpuBars to -1 I'm stuck on the apple boot logo + empty loading bar screen, but that is only visually since the OS boots normally I can even ssh into it and connect to it via the remote screen. If I set it to 0 then it boots normally. (It was because I had Resize Bar enabled in BIOS)

 

I also haven't quite figured out the benefit of that quirk... Almost the same question has been asked before and also AudioGod mentioned that "If you are not using a 6800, 6800 XT or 6900 XT then it’s totally pointless using the feature.", since I'm not using one of these GPU, does it mean that I should disable Resize GPU Bars from BIOS and then set the quirk to -1 and see how it goes?

 

Thanks!

Edited February 21, 2022 by panosru

[panosru]

@eSaF, yeah I figured it out but I still wonder if it provides any performance benefit for those who have compatible GPUs as AudioGod stated

[BoomR]

On 2/8/2022 at 3:55 PM, eSaF said:

If Clover is your usual Boot loader and you're trying OC, you must clean the NVRAM before booting from OC.

Want to update the OC/EFI folder on a build I did. Used the EFI/OC version AG used in the OP (Catalina) to the 0.7.8 EFIs you just shared (iMac19,1 version). The machine I'm working on is one I built for my music partner (& still on Catalina).  Need to get him up to at least Big Sur (if not Monterey). In theory (and my current plan), is to put the new EFI on a USB thumb drive and try booting his existing Catalina build with 0.7.8. 

• Would you recommend also clearing NVRAM before trying to boot from the thumb drive's newer OC? 
• I've gone into the config.plist included in your zip and plugged in all his current Platform Info details (Sys SN, UUID, etc.).  Anything else I'm missing?

 

THANKS!!

--B

[MaLd0n]

--Some Updates--

EFI folders with OpenCore_NO_ACPI fork with 0.7.9 version

EFI iMacPro1,1 AMD GPU.zip

EFI iMac19,1 IGPU.zip

EFI iMac19,1 AMD GPU.zip

 

Link

https://gitee.com/btwise/OpenCore_NO_ACPI

 

Features

- ACPI patches and Booter Quirks are optional for non macOS with setting ACPI

- SMBIOS and Device Properties patches will only applied to macOS

https://www.olarila.com/topic/24542-opencore_no_acpi-opencore-with-additional-featureschanges-implemented-how-to-use-this-fork/

 

Credits: Acidanthera Team, Clover Team, n-d-k, btwise and many others

[map002]

2 hours ago, MaLd0n said:

--Some Updates--

EFI folders with OpenCore_NO_ACPI fork with 0.7.9 version...

 

 

Any chance of a 19,1 with AMD GPU?

[MaLd0n]

4 hours ago, map002 said:

Any chance of a 19,1 with AMD GPU?

post above is updated

let me know if work good

[markl18]

On 2/15/2022 at 7:19 AM, eSaF said:

Read my post above - Bro I don't know or understand what your system is about. If you're using the Debug OC or the SampleCustom.plist, these are only for special cases and since I have never used any of the two, I can't help you on the subject. Sorry.

hi I really need your expertise the bless file is found yet it discards it for some reason

Adding bless entry on disk - PciRoot(0x0)/Pci(0x14,0x0)/USB(0x1,0x0)/HD(1,GPT,43B59A14-97DA-4D04-B0FE-0D37651B00FB,0x800,0x1D1CFDF)
243:589 00:433 OCBP: Predefined <nil> PciPciRoot(0x0)/Pci(0x14,0x0)/USB(0x1,0x0)/HD(1,GPT,43B59A14-97DA-4D04-B0FE-0D37651B00FB,0x800,0x1D1CFDF)/\EFI\BOOT\BOOTX64.EFIRoot(0x0)/Pci(0x14,0x0)/USB(0x1,0x0)/HD(1,GPT,43B59A14-97DA-4D04-B0FE-0D37651B00FB,0x800,0x1D1CFDF) is missing - Invalid Parameter
244:442 00:852 OCBP: Blessed file is missing
244:872 00:430 OCBP: Blessed folder is missing
246:162 01:290 OCBP: Predefined <nil> \System\Library\CoreServices\boot.efi is missing - Not Found
246:593 00:430 OCBP: Predefined <nil> \EFI\Microsoft\Boot\bootmgfw.efi is missing - Not Found
247:444 00:850 OCBP: Predefined <nil> \EFI\BOOT\BOOTX64.EFI was found
248:315 00:870 OCB: Adding entry type (T:1|F:0|G:1) - PciRoot(0x0)/Pci(0x14,0x0)/USB(0x1,0x0)/HD(1,GPT,43B59A14-97DA-4D04-B0FE-0D37651B00FB,0x800,0x1D1CFDF)/\EFI\BOOT\BOOTX64.EFI
249:171 00:856 OCB: Discarding discovered OpenCore bootloader
249:608 00:436 OCB: Not adding hidden auxiliary entry ControlMsrE2.efi (tool|B:0) -> ControlMsrE2.efi
250:899 01:291 OCB: Showing menu... (polling hotkeys)

 

 

config.plist

[freakermonguer]

My build has been solid booting for a couple of years. Still on Big Sur

 

Suddenly it stopped booting. This is what I get on verbose boot

 

I've done no changes at all in the computer

 

Tried reset NVRAM already a couple of times to no avail

 

 

Edited March 2, 2022 by freakermonguer
add more info

[MaLd0n]

On 2/28/2022 at 7:33 PM, eSaF said:

Hi @MaLd0n - I noticed you seem to always use the Custom Config.plist in your EFI Folders contrary to the advice to using the Sample Config.plist, is there any particular reason you opt to choose the Custom one?

i don't like

generic things. no high level acpi, etc. not good  

7 minutes ago, freakermonguer said:

My build has been solid booting for a couple of years. Still on Big Sur

Check here some updates

https://www.insanelymac.com/forum/topic/339980-audiogods-aorus-z390-pro-patched-dsdt-mini-guide-and-discussion/?do=findComment&comment=2777476

 

[freakermonguer]

1 hour ago, MaLd0n said:

 

Check here some updates

https://www.insanelymac.com/forum/topic/339980-audiogods-aorus-z390-pro-patched-dsdt-mini-guide-and-discussion/?do=findComment&comment=2777476

 

You want me to use that OpenCore instead the oneI have?

Are there any special requirements or changes to be done?

 

At this moment I have an old version of opencore, the one that was used to install Big Sur. Don't know how to get the version from the EFI files

 

Also want to mention that the "Install Macos BigSur" boot drive doesn't work neither. (it was working before). It's as if something got messed up in the bios, but I've restored the bios to the unlocked mode reloading the default I saved when I built this machine. 

 

PS: Apart of my question, I've been on the hackintosh scene a long time. It amazes me that you have helped me a couple of times with this and my previous build. I truly want to thank you for your dedication.

Edited March 2, 2022 by freakermonguer
add more info

[freakermonguer]

35 minutes ago, eSaF said:

Yes you need to furnish your machine's original data i.e SmUUID, S/N, MLB and ROM to the config.plist and save the settings.

 

Ok, did it all, put my UUD / SN MLB and ROM

 

Same result.

Doesn't boot. 

 

Neither the installation mac os big sur drive works. 

 

Any thoughts? could it be a hardware problem?

 

 

[freakermonguer]

6 minutes ago, eSaF said:

If you're referring to one of @MaLd0n EFI Folders, you need to use all the files in his Folder that corresponds to you previous working EFI Folder, you cannot use old files (i.e drivers, kexts etc) from your previous EFI Folder as they will inevitably need updating, also clean the NVRAM before booting.

Sorry

 

a bit confused in what you mean.

 

What I did was to unzip the files. Move my non-working EFI to another directory and copy the new files to the EFI directory.

Then I edited the plist copying my Serial number, etc, from the non working EFI plist. Only those values. The rest of the folders were untouched as they came out of the zip.

 

Also cleaned ram. To no avail

 

I've also in the meantime since I last wrote, removed the ram and checked both slots. Ram seems to be ok as I get the same issue by switching ram... so for the moment I think it's not a wonky ram issue.

 

Now I'm going to disconnect all the drives except the one that I need to boot.

 

Getting out of ideas here....

[freakermonguer]

OK, removed all drives. Same issue...

 

I also took the old usb that I had for catalina that was working on this computer, and I get the same results...

 

let's see... Im clearing the nvram using OpenCanopy option. Once it boots, I press space and then I choose "cleanNvram". But maybe nvram is not clearing at all or some values remain... is there a way from the bios to clean the nvram?

 

I'm thinking on updating the bios. At this moment I have F12d version.

By updating it I guess that all nvram values will be erased for sure.... if that's the issue

 

 

 

[freakermonguer]

10 minutes ago, eSaF said:

There is a possibility your BIOS is too old or the BIOS settings needs looking at again.

 

 

 

but why if I've done no changes on the system, neither updated opencore, nothing, the whole build suddenly doesn't boot any more? I was working with it, suddenly a crash and then it boots - I noticed that the booting drive wasn't selected as if the nvram option was deleted. I move over the booting drive, and nothing. no boot. And not only that, the installing image of the macos doesn't boot neither.

 

WTF...

 

 

[MaLd0n]

1 hour ago, eSaF said:

Hi @MaLd0n - I tried your EFI iMac 19.1 IGPU Folder, it boots but a little slower to my current boot time,  also my iPhone was not recognised when plugged into my C-Port as before plus my BIOS clock stopped working which I had to reset, I am guessing that is something to do with the RTC setting in the config.plist that stopped the clock.

try disable DisableRtcChecksum in kernel tab

ur usb-c port have a usb2 connection remmaped in this kext from this topic? iPhone use usb-c but usb2 connection and not 3. check it

13 minutes ago, freakermonguer said:

but why if I've done no changes on the system, neither updated opencore, nothing, the whole build suddenly doesn't boot any more? I was working with it, suddenly a crash and then it boots - I noticed that the booting drive wasn't selected as if the nvram option was deleted. I move over the booting drive, and nothing. no boot. And not only that, the installing image of the macos doesn't boot neither.

use load optmized default and stay bios/uefi in default settings just disable csm if used amd gpu

u can use folder from this topic and put ur serial

https://www.olarila.com/topic/5676-hackintosh-efi-folders-for-all-chipsets-clover-and-opencore/

[freakermonguer]

12 hours ago, MaLd0n said:

 

use load optmized default and stay bios/uefi in default settings just disable csm if used amd gpu

u can use folder from this topic and put ur serial

https://www.olarila.com/topic/5676-hackintosh-efi-folders-for-all-chipsets-clover-and-opencore/

 

SOLVED!!! READ BELOW

 

 

This is all what I've tried till now

- Changed the usb booting stick to another one to see if it was a bad usb

- Update BIOS to the recommended version of the thread and applied the optimized settings

- Clear nv ram all the time using opencanopy option

- Downloaded the EFI build from the first post of this topic

- Added my serial and personal info

 

As this was not letting me boot

 

- Removed wifi card

- Removed all drives except booting one (It's a M1)

- Removed all memory except one slot (tried with both and same results)

- Removed Graphic card (Sappire pulse RX580)

- Booted using iGPU

 

I tried to boot on any step change from the last things

 

I always get the same error

 

SOLVED!!!!

 

By using your booting Opencore I noticed something. I've used your boots for debugging stuff and so on in the past. And when booting from your files I noticed that the icons were pretty basic. And I knew you like to change opencanopy graphics...

 

entered in the bios and noticed that the booting options had been reset. Changed the booting sequence (i boot from usb) and kaboom!

 

What I think it has happened:

 

I got a computer hang. A bad one. Even a normal mac would hav hanged. Chrome with nearle a hundred tabs, around 2 weeks no reboot, photoshop with huge files, etc.

But the computer crash affected the bios configuration. Then the booting drives changed. And as my hard drive has an OLD Opencore boot that looks quite similar to the actual opencore I didn't notice I was always booting from the drive - a bad opencore - and not the ones I was updating all the time on the usb. 

 

I know, a very stupid error... but sometimes I'm stupid... now I have the build running and proceeding to set up the things I disconnected

 

Thank you a lot for all your help.

 

 

 

 

 

 

Edited March 3, 2022 by freakermonguer

[MaLd0n]

8 hours ago, eSaF said:

@MaLd0n - Thanks will do that and give it another shot. Although I think my machine is rock solid in it's present state, I like to try different ideas or recommendations specially from people far more knowledgeable than myself, plus I do like to tinker now and again to keep the old brain cells from dying. 

but is far away from one real mac. no high level acpi, no apple devices, many devices trashes for windows, etc

the big problem is about high level acpi and uefi things, after that some extra problems appears but we need fight this war

Use this efi folder. dont need change nothing, reboot and extract one full dump with ioreg

EFI 01.zip

 

Post one Full Dump
https://www.olarila.com/topic/10301-olarila-runme-dumper/
https://olarila.com/files/Utils/RunMe.app.zip
https://youtu.be/DH5vRhE1P7U

and one Ioreg
https://olarila.com/files/Utils/IORegistryExplorer.app.zip

 

-If you need edit config.plist use OpenCore Configurator last version and change Fork to MOD and Configuration Properties to last Development Version.
https://tinyurl.com/52tjt85m

-This OpenCore fork have good additional feature and we can boot into Windows with no problems with full ACPI solution.
 

[MaLd0n]

1 hour ago, eSaF said:

Thank you very much for your support, much appreciated. Files attached exactly as you requested.

Here

EFI eSaF.zip

Test sleep. I remember with AudioGod this mobo have some problems with Real Time Clock after sleep and other things

[gabe.p]

@MaLd0n @eSaF can we use this on the non wifi model just change the serial/rom/mlb?

 

 

[MaLd0n]

26 minutes ago, gabe.p said:

@MaLd0n @eSaF can we use this on the non wifi model just change the serial/rom/mlb?

Use this efi folder and post one full dump

EFI gabe.p.zip

Post one Full Dump
https://www.olarila.com/topic/10301-olarila-runme-dumper/
https://olarila.com/files/Utils/RunMe.app.zip
https://youtu.be/DH5vRhE1P7U

 

and one Ioreg
https://olarila.com/files/Utils/IORegistryExplorer.app.zip

 

-If you need edit config.plist use OpenCore Configurator last version and change Fork to MOD and Configuration Properties to last Development Version.
https://tinyurl.com/52tjt85m

-This OpenCore fork have good additional feature and we can boot into Windows with no problems with full ACPI solution.

[rob1980]

Hi @MaLd0n  Can I just test your EFI 1.1 folder that you posted with my serial etc in, or is a custom DSDT or similar created for each individual?

 

Could you explain for us less technical people the advantage over what we're currently using?

 

Thanks