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

[Project 2501]

On 1/8/2021 at 10:52 PM, Project 2501 said:

 

Quick update if anybody is out there... I reverted back to Clover r5120 but kept all the updated drivers, and it booted just fine. Not sure where to go from here, but if Clover is a dead end, I guess trying OC won't hurt.

 

 

I got Clover r5128 to work, and of course, the problem was me not fully understanding what changed between r5120 and r5128. It seems that OcQuirks.efi and OpenRuntime.efi are no longer needed. The Clover config.plist now has a Quirks section. All I had to do was use PlistEdit Pro to create a "Quirks" Dictionary in the EFI/CLOVER/config.plist and copy the key/value pairs from the old EFI/CLOVER/drivers/UEFI/OcQuirks.plist

 

[jmcm]

18 hours ago, benjiolino said:

As far as I know you should not select OpenCore in Bootmenu. You have to select the EFI partition on your USB. it should be called UEFI on drive name (sandisk or whatever)

Hi, I only have 3 options, Windows Boot Manager (my windows m.2 disk), UEFI Samsung SSD (this is the Clover EFI in m.2 Catalina disk) and OpenCore (that only exists in the usb).

 

I've changed "SecureBootModel" from j137 (or something like that) to Disabled and the system booted.

On the login screen I noticed that my usb keyboard and mouse wasn't working, but changed them to the top usb rows, and it's working again.

I just don't know if I should kept SecureBootModel disabled or if I need to do something else first.

Thanks.

[Sergey_Galan]

On 10/21/2020 at 1:14 PM, AudioGod said:

as for the wake sleep thing, I'm sorry I don't buy that response to it.

Its always worked as it should using darkwake=0 so now its broken I won't just accept it as a oh well its a hack thing, that's very defeatist of you. I would like to think that the OC Devs will get on top of that eventually as well as DRM being broken (for 19,1 etc) and have things back to normal.

On Catalina, darkwake = 0 saved from waking up with a double click.

In macOS Big Sur the key of darkwake=0 stopped being an awakening method without double clicking of the keypad.

Based on this article https://dortania.github.io/OpenCore-Post-Install/usb/misc/keyboard.html , besides darkwake = 0, there are two more ways to get rid of double-clicking when the computer wakes up, but neither the acpi-wake-type writing in DeviceProperties, nor USBWakeFixup.kext paired with SSDT-USBW.aml give a result. In SSDT-USBW I tried all USB-Devices.

log show -last boot | grep -i 'wake reason'

I saw it:

The reason was the Internal PLL Overvoltage enabled in the BIOS. After disabling this function, the computer began to wake up one click at a time without using the darkwake = 0 key and other options. True, I had to lower the memory frequency to 1600MHz.

I saw it:

 

Sorry for the bad translation)))

 

[AudioGod]

1 hour ago, Galan-od said:

On Catalina, darkwake = 0 saved from waking up with a double click.

In macOS Big Sur the key of darkwake=0 stopped being an awakening method without double clicking of the keypad.

Based on this article https://dortania.github.io/OpenCore-Post-Install/usb/misc/keyboard.html , besides darkwake = 0, there are two more ways to get rid of double-clicking when the computer wakes up, but neither the acpi-wake-type writing in DeviceProperties, nor USBWakeFixup.kext paired with SSDT-USBW.aml give a result. In SSDT-USBW I tried all USB-Devices.

log show -last boot | grep -i 'wake reason'

I saw it:

The reason was the Internal PLL Overvoltage enabled in the BIOS. After disabling this function, the computer began to wake up one click at a time without using the darkwake = 0 key and other options. True, I had to lower the memory frequency to 1600MHz.

I saw it:

 

Sorry for the bad translation)))

 

Well done buddy, that’s a good find but the problem is Internal PLL Overvoltage doesn’t exist on modern boards anymore I don’t think. I might be wrong though so I will double check that now. Let’s see

 

Also having to lower the memory is an instant dealbreaker for me. Big Nono

Edited January 10, 2021 by AudioGod

[richi_music_on]

Hello Can I use this EFI and OpenCore 0.6.5 of this update in Mojave 10.14.6 with the same computer, formatting and installing? I don't understand much, but I can copy and paste and change MLB, SystemSerialNumber and SistemUUID and delete boot-args=agdpmod=pikera  I'm right? Or do I have to change some more parameters? Thank you

IntelCore i9 9900k

Aorus Pro z390 F12K

Sapphire Radeon rx580 8GB

Corsair Vengeance lpx 3200

 

Edited January 11, 2021 by RichardCk

[AudioGod]

8 minutes ago, RichardCk said:

Hello Can I use this EFI and OpenCore 0.6.5 of this update in Mojave 10.14.6 with the same computer, formatting and installing? I don't understand much, but I can copy and paste and change MLB, SystemSerialNumber and SistemUUID and delete boot-args=agdpmod=pikera  I'm right? Or do I have to change some more parameters? Thank you

IntelCore i9 9900k

Aorus Pro z390 F12K

Sapphire Radeon rx580 8GB

Corsair Vengeance lpx 3200

 

Yes you can use Mojave no problems there and yes you got it with the changes needed to the config.plist.

also one other thing to change is put your Mac address where the rom field is and don’t forget to remove the : between the digits. 

[richi_music_on]

Ok! very very thanx!

You are f**ng boss!

Saludos desde España!

[Blesh]

@AudioGod In order to disable SIP (temporarily) I have to change the "csr-active-config" argument from "<67000000>" to "FF0F0000" right??

But what does "67000000" mean, did you set this? (I mean your config.plist)

Edited January 11, 2021 by Blesh

[AudioGod]

1 hour ago, Blesh said:

@AudioGod In order to disable SIP (temporarily) I have to change the "csr-active-config" argument from "<67000000>" to "FF0F0000" right??

But what does "67000000" mean, did you set this? (I mean your config.plist)

Good spot bro,

They are the old config settings that used togo

00000000 - SIP completely enabled
30000000 - Allow unsigned kexts and writing to protected system file locations
67000000 - SIP completely disabled

 

FF0F0000 is correct for sip to be disabled.

it will be defaulting to sip enabled with it set to 67 as it will bypass it.

il correct that one, Thank you bud 

[Blesh]

5 minutes ago, AudioGod said:

Good spot bro,

They are the old config settings that used togo

00000000 - SIP completely enabled
30000000 - Allow unsigned kexts and writing to protected system file locations
67000000 - SIP completely disabled

 

FF0F0000 is correct for sip to be disabled.

it will be defaulting to sip enabled with it set to 67 as it will bypass it.

il correct that one, Thank you bud 

ahhhh... hehe

 

So I changed to FF0F0000 but "csrutil status" says that:

 

System Integrity Protection status: unknown (Custom Configuration).

 

Configuration:

Apple Internal: disabled

Kext Signing: disabled

Filesystem Protections: disabled

Debugging Restrictions: disabled

DTrace Restrictions: disabled

NVRAM Protections: disabled

BaseSystem Verification: enabled

[richi_music_on]

Hello again!

My problem now is with my FENVI T919 BCM94360CD network card and my apple magic mouse and keyboard, bought in 2010, I also bought a Bluetooth extender antenna but it works just as badly, I have looked in forums, I have reinstalled the Bluetooth with alt + shift ... I don't know what else to do, could someone help me?

By the way, both work perfectly in my 2017 MBAir without any problem.

Thanks a lot!

[AudioGod]

1 hour ago, RichardCk said:

Hello again!

My problem now is with my FENVI T919 BCM94360CD network card and my apple magic mouse and keyboard, bought in 2010, I also bought a Bluetooth extender antenna but it works just as badly, I have looked in forums, I have reinstalled the Bluetooth with alt + shift ... I don't know what else to do, could someone help me?

By the way, both work perfectly in my 2017 MBAir without any problem.

Thanks a lot!

Have you tried using AirportBrcmFixup and or BrcmPatchRAM with your T919?

Im scratching my head somewhat as how can you use a T919 on a 2017 MBAir?????? 

Do you have a pcie to thunderbolt converter or does your MacBookAir have special morphing powers to grow pcie slots or something?

 

Joking aside and to be totally honest with you, I can not stand that stupid combo card and personally think it’s a load of rubbish so hearing story’s about it not working never ever surprise me as it’s built like a load of horse {censored}...lol....sorry but that’s how I feel about them combo cards.

Edited January 18, 2021 by AudioGod

[richi_music_on]

hahaha sorry i mean i use apple mouse and keyboard without any problem on my MBA xd

I use exactly one copy of your EFI on my computer so I only have AirportBrcmFixup installed, Will I try using BrcmPatchRAM?

I bought this card because I thought it was the most compatible ... simply ... but the one you have is out of print, although I found the adapter on eBay at this link but I don't know which exact chip could be compatible...

Thanks a lot!

Edited January 18, 2021 by RichardCk

[AudioGod]

27 minutes ago, RichardCk said:

hahaha sorry i mean i use apple mouse and keyboard without any problem on my MBA xd

I use exactly one copy of your EFI on my computer so I only have AirportBrcmFixup installed, Will I try using BrcmPatchRAM?

I bought this card because I thought it was the most compatible ... simply ... but the one you have is out of print, although I found the adapter on eBay at this link but I don't know which exact chip could be compatible...

Thanks a lot!

LOL Ok I get you now buddy.

Here you go, A note from the devs about your problem 

Please pay attention

In 11 (Big Sur) class AirPortBrcm4360 has been completely removed. Using of injector kext with such class name and matched vendor-id:device-id blocks loading of original airport kext. To address this issue and keep compatibility with older systems injectors for AirPortBrcm4360 and AirPortBrcmNIC were removed from main Info.plist file. Instead, the two new kext injectors are deployed in PlugIns folder: AirPortBrcm4360_Injector.kext and AirPortBrcmNIC_Injector.kext. You have to block (or remove) AirPortBrcm4360_Injector.kext in BigSur. In OpenCore you can specify MaxKernel 19.9.9 for AirPortBrcm4360_Injector.kext. In Clover you can have two different AirportBrcmFixup.kext, but in kext folder with version name 11 AirportBrcmFixup.kext must not contain AirPortBrcm4360_Injector.kext. You don't need these injectors at all if your vendor-id:device-id is natively supported by AirPortBrcmNIC or AirPortBrcm4360 (your device-id is included into Info.plist in these kexts).

https://github.com/acidanthera/AirportBrcmFixup

 

 

[pkdesign]

Check this forum out as well. I had to do this when I had my old card: 

 

[pkdesign]

I've got an odd question. I was looking at my USB ports and noticed this:

Spoiler

I am using @AudioGod USBPortMap. Why would something show up as HS01 and HS02 when they are plugged into the HS13 ports on the back of my computer?

Edited January 18, 2021 by pkdesign

[deeveedee]

3 hours ago, pkdesign said:

I've got an odd question. I was looking at my USB ports and noticed this:

I am using @AudioGod USBPortMap. Why would something show up as HS01 and HS02 when they are plugged into the HS13 ports on the back of my computer?

Is the device you're plugging into HS13 a USB3 device?  If so, I just observed something not exactly like this, but similar to it on my rig.  I figured out it was because I was inserting a USB3 device into a USB3 port, but I didn't have the correct associated SSxx port in my map.  I wouild recommend "starting over" with your USB port patching: change your USB kext to USBInjectAll.kext, enable your USB port limit patch and make sure no other USB kexts/patches are installed/enabled.  Then plug your device into HS13 and see what happens.  If your situation is like mine, you'll discover a SSxx port that you didn't include in your map.

Edited January 19, 2021 by tonyx86

[pkdesign]

4 hours ago, eSaF said:

@pkdesign I am not sure but maybe you have in the config.plist to push past the 15 port limit which you can or don't have to with AG's new USB port mapping.

Nope. I have XchiPortLimit set to False. Even if I didn't, how would lit get a HS01 and HS02 designation if it were not in the USBPort Map?

 

2 hours ago, tonyx86 said:

Is the device you're plugging into HS13 a USB3 device?  If so, I just observed something not exactly like this, but similar to it on my rig.  I figured out it was because I was inserting a USB3 device into a USB3 port, but I didn't have the correct associated SSxx port in my map.  I wouild recommend "starting over" with your USB port patching: change your USB kext to USBInjectAll.kext, enable your USB port limit patch and make sure no other USB kexts/patches are installed/enabled.  Then plug your device into HS13 and see what happens.  If your situation is like mine, you'll discover a SSxx port that you didn't include in your map.

No. It is a KVM switch, a scanner and a camera. All USB 2.0. The USBPortMap should not be wrong. I am directly using AudioGod's map which has been configured for this Mobo.

[deeveedee]

11 hours ago, pkdesign said:

The USBPortMap should not be wrong.

Agree that the operative word is "should".  A USB port map takes 5-minutes to create.  Might be worth the experiment.

[pkdesign]

1 hour ago, tonyx86 said:

Agree that the operative word is "should".  A USB port map takes 5-minutes to create.  Might be worth the experiment.

I have made several USBPortMaps in the past. None of the USB maps have HS01 or HS02 configured. Yet still, these show up.

Edited January 19, 2021 by pkdesign

[AudioGod]

1 hour ago, tonyx86 said:

Agree that the operative word is "should".  A USB port map takes 5-minutes to create.  Might be worth the experiment.

Remember that this is a thread For a specific board so If you map it again yourself of use mine it’s all the same if you do it right...

@pkdesign Ive not seen that before but have you done the usual stuff like clear your cache and rebuild your permissions, clear nvram etc etc?

 

Edited January 19, 2021 by AudioGod

[deeveedee]

@AudioGod - my comment wasn't meant to criticize or question your work.  You've done a fantastic job.

[pkdesign]

1 hour ago, AudioGod said:

 

@pkdesign Ive not seen that before but have you done the usual stuff like clear your cache and rebuild your permissions, clear nvram etc etc?

 

I've cleared NVRAM and rebuilt kext cache but not rebuild permissions. I mean everything works but I think it is so odd!

 

Should port count be 15?

 

EDIT:

I've gone back though to see what is happening. When I plug anything into the HS13 ports whether they are USB2 thumb drive or USB3 (the four USB 2 ports at the top of the mobo) Hackintool shows HS01, HS04, HS03, and HS02 turn on (in that order left to right.) HS13 is always on as "USB2.0 Hub." 

 

I did rebuild kext cache, permissions and cleaned NVAM.

Edited January 19, 2021 by pkdesign

[deeveedee]

On 1/19/2021 at 12:59 PM, pkdesign said:

EDIT:

I've gone back though to see what is happening. When I plug anything into the HS13 ports whether they are USB2 thumb drive or USB3 (the four USB 2 ports at the top of the mobo) Hackintool shows HS01, HS04, HS03, and HS02 turn on (in that order left to right.) HS13 is always on as "USB2.0 Hub." 

 

I think you've discovered that HS13 is just an internal USB 2.0 hub with downstream ports HS01, HS02, HS03 and HS04.  You can't physically insert devices into an internal hub, so what you've observed makes sense.  If that's true, then the only confusing part is that its connector name is HSxx (just cosmetic).  If desired, just give the hub a different name (e.g. HUBx).

 

EDIT: I haven't experienced this before, so I'm just thinking out loud... What happens if you remove HS13 from the port map?  Do HS01, HS02, HS03 and HS04 still work as before?  Does this now free up a logical port that you can use while remaining within your 15-port limit?

 

EDIT2: @pkdesign Recent Hackintool commits have involved USB.  It might be worth it to make sure that you are using the latest Hackintool and then to retest (just to be sure that Hackintool wasn't giving you any false readings).

Edited January 22, 2021 by tonyx86

[jmcm]

Is it possible to boot to LastBootedVolume in OpenCore like it was in Clover?

I reinstalled my hackintosh drive with a fresh OpenCore \ BigSur and used TimeMachine to reinstall all the apps \ files and the system is working fine, then I tested the Windows drive and it's also working as before, but I noticed that on boot it defaults to Mac drive, and that is not really a problem when I'm sitting in front of the pc but when working from remote location that option was great so I'm missing that last booted option.