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

[DoYouBelieveInMiracles]

Hello everyone. I used OCAT to update to OC 0.77 and I got the following errors for my plist.

Can anyone help?

 

 

[panosru]

Hey guys, I wonder if any one is facing issues with runningboardd process being cranked up to 100%+, eventually the apps are starting to be slow and the system overall needs reboot, it started happening since Monterey and I can't find any way to fix it, I try to avoid a fresh install but I kind of having the feeling that I might end up re-installing everything from scratch! 😫

 

Killing the process isn't solving the issue, the apps start to work again but soon it reaches 100% again...

 

[DoYouBelieveInMiracles]

Hey @panosru, how is the 970 Evo Plus performing with your Hackintosh?

I am looking into replacing my Samsung 860 with an M2 SSD and was wondering how the M2 change is performance-wise?

[panosru]

@unknownharris is F!@ed UP! (ΓΑΜΙΕΤΑΙ!) I will get an M.2 PCIe controller and I'll stick the 970 evo plus pro there and I'll use it as the drive where my final cut library is for all my videography process since it is fast, but I'll be buying a 2TB WD M.2 NVMe drive for my main. I was about to do that change now but after the power shortages here in Athens, both my UPS are fried and I will be replacing them

[pkdesign]

3 hours ago, unknownharris said:

Hello everyone. I used OCAT to update to OC 0.77 and I got the following errors for my plist.

Can anyone help?

 

 

Go back through and update but follow directions very closely. OCAT should have corretced these missing items in your config plist. You must have missed a step.

 

Either that or open your old and new config next to each other using PlistEdit Pro (or similar) and see what is missing from your new config.

[panosru]

@pkdesign I'm getting exactly the same messages, I checked my config.plist, it is valid and I also compared it with other configs, so I'm just ignoring those messages on boot... but, I'm also interested to know more about it!

[Anto65]

Simply have not updated the plist, on the right 0.7.7 with the new keys highlighted in green to be inserted in the plist 0.7.6 always on the left the items in red are to be deleted

If you use OCAT just open and save the plist ... follow here  https://github.com/5T33Z0/OC-Little-Translated/blob/main/D_Updating_OpenCore/README.md  it will be updated automatically 

 

Manually, open your config  (plisteditorpro ...) and add the new keys from the sample.plist of release 0.7.7 (those in green) remove those in red from the config 

 

Edited January 28, 2022 by antuneddu

[panosru]

@antuneddu for my case at least, I'm using OCAT and I double checked with plist editor to make sure that the new properties are in place, which they are, but the messages appear nonetheless.

[Anto65]

7 minutes ago, panosru said:

@antuneddu for my case at least, I'm using OCAT and I double checked with plist editor to make sure that the new properties are in place, which they are, but the messages appear nonetheless.

If you have done everything in order as @eSaF says (I have attached the guide x OCAT) You should be ok then .. if you checked with ocvalidate (0.7.7) and it gives no errors, you just have to reset the nvram 🤔

[panosru]

Well, I believe that I'm doing it correctly but in any case, I might missed something.

 

For what is worth, this is the OC validate output:

 

I do ALWAYS reset NVRAM after any modification I do in my config, and I'm also attaching here my config with serials removed.

config.plist

[cabal2000]

13 hours ago, panosru said:

Well, I believe that I'm doing it correctly but in any case, I might missed something.

 

For what is worth, this is the OC validate output:

 

I do ALWAYS reset NVRAM after any modification I do in my config, and I'm also attaching here my config with serials removed.

config.plist 39.48 kB · 5 downloads

 

Could you upload the full EFI folder? Thanks

[MaLd0n]

1 hour ago, cabal2000 said:

Could you upload the full EFI folder? Thanks

Just use EFI folder from here. Generate your smbios with serial

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

Hot to update Opencore easy and fast

https://www.olarila.com/topic/14268-how-to-update-opencore-bootloader-on-hackintosh-easy-and-fast-way/

[richi_music_on]

Hi!

Here I leave my EFI-077 folder, in case someone is interested.

EFI077-definitiva.zip

[existation]

Hello. Thank you all for this topic. All works good. I have Aorus Z390 Pro WIFI mobo and running 10.14.6 Mojave.

I have only one question. Is it safe to update bios from F12k to F12? Here is change log for F12:

1. Checksum : D53B
2. Major vulnerabilities updates, customers are strongly encouraged to update to this release at the earliest.
   Credits to 'Assaf Carlsbad and Itai Liba from SentinelOne'
   
3. Introduce capsule BIOS support starting this version.
   Customers will NOT be able to reverse to previous BIOS version due to major vulnerabilities concerns.

I am confused by last line.

Any suggestions....

[Cipha]

Yes it’s s save. Since you have an Aorus Pro there’s a Backup BIOS on the board anyway. So nothing to worry about. 

[panosru]

@eSaF well it seems that I'm not getting the message anymore, tbh I'm not sure why, I guess maybe after I upgrade to v0.7.7 I might indeed forget something, I also had a USB plugged in the back of my PC and I forgot about it, it also has an EFI backup, maybe that was to blame, in any case, it seems to be ok now (it was and before though). @MaLd0n nice guides! You put a lot of effort and attention, very valuable for the whole community, thank you!

 

I'm also attaching my EFI folder here, if someone wants to look into it, feel free to do so, a second pair of eyes won't hurt! Normally I'm not using nvmefix but after Monterey, I'm trying everything I can to maybe solve the issue with Samsung EVO 970 pro drives, but it seems that I'll have to get a new WD drive for my main. For USB I'm using the SSDT aml approach instead of kext. Otherwise my EFI I think is pretty standard.

 

What I wasn't able to make it work is the chime sound on boot, I guess maybe it requires a mobo speaker in order to work and won't work with my soundbar or monitor's speakers (via display port).

 

PS: Updated to v12.2, so far so good.

EFI.zip

[panosru]

Thank you for your time @eSaF! I replaced my drivers with the ones in your zip folder, how could you tell that mine were outdated? I got them from the latest 0.7.7 OpenCore zip and mine had the same size as yours (I didn't check md5), did you get yours from the v0.7.8?

 

About the chime I was never able to make it work, from Dortania guide also states that chime via HDMI/DisplayPort is a hit or miss operation. I'm still not very sure what should I put in AudioDevice and AudioOutMask, for now, my AudioOutMask has a value of -1 which actually should broadcast the sound to all devices, and the audio device, instead of being empty and picking the first available audio device, I set it to my HDEF device, should I set my GPU as an audio device instead (which doesn't make much sense)?

 

I'm also attaching my OC debug log just in case (lines 149-163):

 

11:057 00:005 OC: Changed console mode to 0x0 (max: 1) from Max - Success
11:065 00:008 OCAU: System amp gain -31 dB, saved raw gain 0x0, system audio mute (for chime) 0  - Not Found/Success
11:075 00:010 OCAU: OcAudioInstallProtocols (0, 0)
11:082 00:006 OCAU: 4B228577-6274-4A48-82AE-0713A1171987 protocol - Success
11:090 00:008 OCAU: C32332DF-FC56-4FE1-9358-BA0D529B24CD protocol - Success
11:098 00:008 OCAU: F4CB0B78-243B-11E7-A524-B8E8562CBAFA protocol - Success
11:107 00:008 OCAU: 3224B169-EC34-46D2-B779-E1B1687F525F protocol - Not Found
11:115 00:008 OCAU: Matching PciRoot(0x0)/Pci(0x1F,0x3)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000)...
11:126 00:010 OCAU: Incorrect audio I/O protocol revision 3 != 2
11:133 00:007 OCAU: 1/3 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000) (0 outputs) - Unsupported
11:146 00:012 OCAU: Incorrect audio I/O protocol revision 3 != 2
11:153 00:007 OCAU: 2/3 PciRoot(0x0)/Pci(0x1F,0x3)/VenMsg(A9003FEB-D806-41DB-A491-5405FEEF46C3,00000000) (0 outputs) - Unsupported
11:165 00:011 OCAU: Incorrect audio I/O protocol revision 3 != 2
11:173 00:007 OCAU: Cannot find specified audio device - Unsupported
11:180 00:007 OC: Audio connection failed - Unsupported

 

 

 

opencore-2022-01-31-105838.txt

Edited January 31, 2022 by panosru

[panosru]

My OCAT is for v0.7.7 maybe that’s why you are getting the update and I'm not, I will install v0.7.8 later today. My monitor is also connected via Display Port but since I have 5 monitors I tried both DP and HDMI, when I reach Desktop the sound is working from all my audio sources either 3.5" jack, usb, hdmi, display port, you name it, but on boot the chime sound isn't coming from anywhere, which, ok, isn't much of a deal, I'm just checking maybe someone knows an easy fix

 

Nice one about the SSD controller, mine is stock and shows generic controller

Edited January 31, 2022 by panosru

[miliuco]

@panosru

 

As @eSaF says, it's purely cosmetic, SSD and NVMe disks are going to work the same as generic.

 

But if you want to try the NVMe.kext fix, it's easy to get Apple SSD Controller in System Profiler:

• Get NVMe.kext (I am not able to find it in the network now so it's attached)
• Right click >> Show package contents >> open Info.plist
• Inside IOKitPersonalities >> AppleNVMe there is the IOPCIPrimaryMatch key, here you must type device id of your NVMe disk.

How type the device id? Open Hackintool >> PCIe tab and look for vendor and device of the storage controller. E.g. if vendor is 15b7 and device is 5006 you must type in IOPCIPrimaryMatch the value 0x500615b7 replacing current value.

Reboot and try.

 

Remember to add the kext into Kexts folder and in config.plist.

 

 

 

NVMe.kext.zip

Edited February 1, 2022 by miliuco

[Project 2501]

After much procrastination, I'm actually giving OC a try, but already I've run into a problem. Any help will be greatly appreciated.

What I did:

1. I started with @Audiogod's latest EFI based on OC 0.7.4.

2. Updated to OC 0.7.7 manually by copying over the new files from OpenCore-0.7.7-RELEASE.zip.

3. Updated the other KEXTs and drivers not included with the OC release from my Clover EFI.

4. Since I'm not using a NAVI based GPU, removed agdpmod=pikera from NVRAM > Add ... > boot-args.

5. Dropped the SSDT for the Titan Ridge Thunderbolt 3 card into the ACPI folder and registered in config.plist.

6. Config.plist validated using OCAuxiliaryTools v20220106-OC0.7.7. First pass through validator listed 16 issues (missing keys), so I saved it and ran it through the validator again and it passed.

7. Changed the boot picker theme to Blackosx/BsxDarkFenceLightGrey1. I followed the instructions on how to modify my config.plist in the readme.md file.


However, I didn't want to replace the EFI without testing it, so I copied the EFI to a flash drive I use to test my Clover EFIs. I then rebooted and pressed F12 to select my boot device. I selected "OpenCore" and it brought me to the GUI boot picker as expected, but it only showed a Windows and an EFI icon, no Apple icon to be seen. So I went ahead and selected the "EFI" icon and it loaded the Clover boot picker installed in the EFI partition of the OSX drive (Samsung 970 EVO NVMe M.2), but Clover only shows the Windows icon. I was able to reboot normally with Clover, so whatever happened doesn't seem persistent.

I'm not sure what I did wrong.

[miliuco]

@Project 2501

I think you are booting Mojave, right? If yes, there is 2 keys UEFi >> APFS >> MinDate and MinVersion, for Mojave and Catalina both must be -1 or a specific value:

• MinDate=20200306 and MinVersion=1412101001000000 for Catalina
• MinDate=20190820 and MinVersion=945275007000000 for Mojave.

[Project 2501]

21 hours ago, miliuco said:

@Project 2501

I think you are booting Mojave, right? If yes, there is 2 keys UEFi >> APFS >> MinDate and MinVersion, for Mojave and Catalina both must be -1 or a specific value:

• MinDate=20200306 and MinVersion=1412101001000000 for Catalina
• MinDate=20190820 and MinVersion=945275007000000 for Mojave.

 

Thanks for the tip. The Apple icon showed up after I entered the specific values for Mojave. However, my EFI still not quite there yet...

 

After I selected the Apple icon, the motherboard speaker beeps again (I installed a piezoelectric buzzer so I can hear it POST, mostly for nostalgia). Eventually the booting stops to show me an animated graphic instructing me to turn on my mouse or trackpad. I am using a bluetooth dongle instead of a PCI card; I do have an Fenvi FV-T919 WiFi Card, but I'm not using the bluetooth function, since I don't have an available USB header.

 

At @eSaF's suggestion, I'm attaching my EFI, minus the serial numbers and UUID.

 

EFI-OC077-Project2501.zip

[Project 2501]

11 minutes ago, eSaF said:

Normally this shows up when the machine cannot find the Mouse or Track Pad or Port they are attached to. I looked at your EFI Folder and checked it with OC validate and it is error free so I think something else is amiss. I noticed a USBMap.kext in the kext folder but you still have this in boot-args (see attached) is this necessary? Surely that should have been catered for in the kext.

Try removing that boot-arg, clean the NVRAM, reboot and see what result you get apart from that, I am out of ideas, maybe someone else can offered up something else. Good luck.

 

I'll try removing that boot-arg and clearing the NVRAM. That boot-arg is a holdover from my early attempts at setting up Clover, before using @AudioGod's EFI. Put it in there to exclude the built-in CNVi card which is useless to MacOS; not sure if it is needed, but since it didn't cause any problems in Clover, I left it alone. That USBMap.kext is not present in my Clover EFI. Don't have time to play with it now... need to get some rest 

[Project 2501]

Okay... I tried deleting the uia_exclude=HS14 boot-arg from my config.plist. Unfortunately it did not solve the problem.

 

However, after a good night's rest, I was able to see the obvious solution when that animated graphic telling me to turn on my pointing device popped up. I simply plugged in my old school trackball. It worked, but instead of getting to the log in screen, I found myself in recovery mode. Instead of booting from my regular OSX partition, it booted the recovery partition instead. I believe that the Startup Disc info is stored in NVRAM, so maybe resetting it will do the trick.

 

But I will have to procrastinate some more and do that later. I get nervous when I have to do something that can't be undone, so I make sure I have a full backup (aside from time machine) and block out enough time to recover if something goes horribly wrong. In the past, I have had many "routine" fixes, upgrades, maintenance cause me to spend hours repairing the damage. Anyway, are there any risks I should be aware of when resetting NVRAM? As long as I can fall back to my current Clover EFI, I'll be satisfied.

[miliuco]

11 minutes ago, Project 2501 said:

... However, after a good night's rest, I was able to see the obvious solution when that animated graphic telling me to turn on my pointing device popped up. I simply plugged in my old school trackball. It worked, but instead of getting to the log in screen, I found myself in recovery mode. Instead of booting from my regular OSX partition, it booted the recovery partition instead. I believe that the Startup Disc info is stored in NVRAM, so maybe resetting it will do the trick...

Yes, you can clean NVRAM (press ResetNVRAM in the picker) without damage, but I think you must also go into BIOS menu and remove any OpenCore entry in the devices boot order section.