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

[xtddd]

the monterey bugging me is the intel i210 i bought cant work..😅

[WizeMan]

On 11/3/2021 at 4:21 AM, map002 said:

Quick Question...

 

I seem to remember that Sidecar only worked if you used the 19,1 system ID.  Is this correct?  Any answers and corrections appreciated. 🙂

 

Yes this is correct.

13 hours ago, Cipha said:

Monterey is running pretty well so far. The only thing bugging me is the slow boot up.

Did anybody achieve some improvements yet?

 

I tried all sorts of things like disabling TRIM (not recommended), doing disk first aid, nothing helped. The boot time was noticeably slower and nothing I could do about it.

[Cipha]

On 11/3/2021 at 3:41 PM, pkdesign said:

Sleep stopped working on my system after update to Monterey. I used SSDT-GPRW method with Mojave and it was fine.

 

Anyone else having this issue?

 

Have you checked Terminal?

pmset -g

 

See if anything is preventing sleep.

 

[pkdesign]

8 hours ago, Cipha said:

 

Have you checked Terminal?

pmset -g

 

See if anything is preventing sleep.

 

Ah! "sleep prevented by sharingd" seems to be the culprit. Have no idea how to fix that.

10 hours ago, WizeMan said:

I tried all sorts of things like disabling TRIM (not recommended), doing disk first aid, nothing helped. The boot time was noticeably slower and nothing I could do about it.

 

Seem like always Samsung drives. I'm sure it will need a firmware update to the drive.

[texem]

2 hours ago, pkdesign said:

 

Seem like always Samsung drives. I'm sure it will need a firmware update to the drive.

 

get rid of Samsung SSD on MacOS. i replaced my Samsung 970 EVO  for a WD Black 850. System boots ultra fast .

 

[Cipha]

You can't say that in general. It worked fine until Monterey and I also have the same drive in my other system (also with Monterey) booting just as fast as my MBP.

[hackinbot]

Hey gang, I recently got a hold of a GTX 1660 Super for Windows gaming. This is in addition to the RX580 that's been working fine for years in my Hack. Both cards work fine in Windows. However, the hack is unable boot into Big Sur when both cards are installed.

 

Here's what I've tried so far, on Big Sur, OC 71 I believe:

 

1. With RX580 in top PCIE slot, 1660 in 2nd PCIE slot = kernel panic halfway through the boot sequence

2.With RX580 in top PCIE slot, 1660 in 2nd PCIE slot and 2nd PCIE slot disabled using SSDT method (https://dortania.github.io/OpenCore-Install-Guide/extras/spoof.html) = boots a bit further, but then hangs when trying to unseal data volume (I think.. I'll have to check again in verbose boot mode) 

3.With RX580 in top PCIE slot, empty 2nd PCIE slot and 2nd PCIE slot disabled using SSDT method  = normal boot into Big Sur

 

Is there something (a bios setting, config.plist setting, etc) we need to enable/disable in our hacks when adding new hardware like a second GPU? Anybody have an AMD + NVIDIA GPU in their z390 Pro board?

[Cipha]

Have you tried the boot flag yet?

https://dortania.github.io/OpenCore-Install-Guide/extras/spoof.html#boot-flag

[hackinbot]

3 hours ago, Cipha said:

Have you tried the boot flag yet?

https://dortania.github.io/OpenCore-Install-Guide/extras/spoof.html#boot-flag

 

No, because I need the RX580 in macOS for dual monitor display. It's strange because there's lots of posts online with an RX580 (enabled) + Nvidia GPU (disabled) combo working using the spoof options above - I'm thinking I must be missing something obvious.

[texem]

19 hours ago, Cipha said:

You can't say that in general. It worked fine until Monterey and I also have the same drive in my other system (also with Monterey) booting just as fast as my MBP.

 

the problem is Trim on Samsung NVMe waiting or timeout . SATA is ok. 

 

[Ron Lemmens]

My BT/Wifi (Fenvi-T919 - BCM94360CD) is fully working without any specific kexts (e.g. BrcmPatchRAM loaded), but there is a problem after waking up from sleep. I have an Apple Magic Keyboard and Mouse and I'm able to wake my system using either the BT mouse or keyboard. However, after the system is awake, the system is not responding to the BT keyboard and mouse, and system falls asleep again.  If I wake it with a wired keyboard it fully wakes up, but still BT is not working, it takes approximately 30 seconds and then BT is working again (including unlocking with Watch)?!?

I don't have any issue with BT functionality except for the fact that it doesn't work immediately (within 30 seconds) after waking up from sleep.

This 'feature' wasn't there with Big Sur or Catalina, it just showed up after installing Monterey (12.0.1 and 12.1 Beta)?!?

 

I've already tried to find something in the syslog, but there are too many entries related to BT (can't see the forest thru the trees).

Anyone any ideas where to look for?

 

 

 

Edited November 7, 2021 by Ron Lemmens

[texem]

19 hours ago, eSaF said:

I have the same card and there is a slight lag on mine as well but my time is much lower at 10 seconds with a Logitech MX keyboard and a MX Master 3 Mac Mouse.

 

Issue here as well. But my BT doesn't recover without restarting the Bluetooth-Daemon (bluetoothd) after wake from sleep.

If i press the power button, i don't have to press any other key but BT is dead as well.

 

With USB kbd a double klick is rqrd, BT dead.

 

AFAIK this happens with Apple devices. Third-party devices ( mouse, kbd .. )  seems to behave different.

 

btw: anyone here with successful showing the BT device under Monterey  ? Picture is from BigSur , with Monterey the blue line is empty ...

 

Edited November 8, 2021 by texem

[Ron Lemmens]

8 hours ago, eSaF said:

@texem Hi Bro - I have no problem with B/Tooth after wake apart from the 10 seconds delay, keyboard and mouse are responsive after Sleep.

 

Yes this is how it is on mine as well, I think you'll find everyone has this problem on their hacks with empty BT data in Hackintool but is ok with previous OS X versions.

 

Same here, empty in Hackintool with Monterey.

 

Update: my problem with the delayed BT activation after sleep has been resolved. Apparently, for some strange reason my Fibaro CO Sensor (also BT)  was connecting first to my Hackintosh (as HID device) and thereby blocking my regular HID devices (mouse / keyboard). I've removed this Fibaro CO Sensor from the BT auto connect list (not sure how it got there in the first place), and now everything works like a charm again 🙂

 

Update #2: and we are back to square #1 - BT delay after wake is back. I've also noticed that the BT Preference plane is not available during this delay (> 30 secs). I've tried to find the com.apple.Bluetooth.plist but in order to delete it (remove all connected BT devices), but the file is non-existing?!? Where does Monterey keep track of it's BT devices, is this somewhere in the iCloud?!?

Edited November 8, 2021 by Ron Lemmens
Problem still not solved

[dsynos80]

Is anyone using IntelBluetooth on Monterey?

Airport kext is working but i cannot load the system with the bluetooth kexts. Tried the last working versions, tried with the latest ones, also with and without BluetoothFixup kext. Any ideas?

[pkdesign]

Same empty, but working, Bluetooth area in Hackintool. Same for DPCI Manager.

[dsynos80]

Solution!!

1.Use latest BluetoothFixup

2.Use Previous IntelBluetoothFirmware ( I used 1.1.3 from my Catalina folder)

3.Shutdown

4.Cold boot

5.Enjoy!

 

P.S. DO NOT use BluetoothInjector kext

Edited November 8, 2021 by dsynos80

[pkdesign]

On 11/5/2021 at 3:01 PM, eSaF said:

Hi - Try deselecting everything here (see attached) and test sleep again.

Yup, tried that. Now I get "sleep prevented by mds_stores, mds, powerd, mdsync" as the reason for no sleep.

 

New OS, new problems!

[Cipha]

disabling spotlight should fix it

sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist 

[texem]

On 11/8/2021 at 11:07 PM, dsynos80 said:

Solution!!

1.Use latest BluetoothFixup

2.Use Previous IntelBluetoothFirmware ( I used 1.1.3 from my Catalina folder)

3.Shutdown

4.Cold boot

5.Enjoy!

 

P.S. DO NOT use BluetoothInjector kext

 

This is for the Z390-Wifi board.

Issues here using the "normal" Pro with a natively supported BroadCom BT-Adapter .

fixup kext is a nogo

 

 

[dsynos80]

3 hours ago, texem said:

 

This is for the Z390-Wifi board.

Issues here using the "normal" Pro with a natively supported BroadCom BT-Adapter .

fixup kext is a nogo

 

 

Correct it is for the WiFi version.

Sorry i did not mention it.

[Ron Lemmens]

I noticed the following when looking at 'pmset -g log | grep -i "wake from"':

Apparently, by clicking the BT mouse my BT adapter causes only a darkwake through the xDCI controller and doesn't trigger a full wake?!

When I subsequently (after 17 seconds) hit a button on my USB connected keyboard, it goes to full wake (due to HID activity).

 

2021-11-11 15:54:25 +0100 DarkWake            DarkWake from Normal Sleep [CDNP] : due to XDCI CNVW/ Using AC (Charge:0%) 17 secs   

2021-11-11 15:54:42 +0100 Wake                DarkWake to FullWake from Normal Sleep [CDNVA] : due to HID Activity Using AC (Charge:0%)

[texem]

yes i can confirm this behaviour .  

BT wakes the system but then all BT (Apple) devices are not working anymore until restarting the bluetoothd (as root user - via sleepwatcher automates this).

The second click for a full wake is only possible via USB kbd or mouse.

FullWake from sleep w/o need for double klick via power button, but BT still dead until restarting the BT-daemon.

 

For my taste it has something to do with system speed or clocking.

I own a second machine with same mainboard but slower CPU (8700) and slower RAM .

Any other component is identical.

 

Bam ..  no BT issues..  what the hell is going on ?

 

[Ron Lemmens]

21 minutes ago, texem said:

yes i can confirm this behaviour .  

BT wakes the system but then all BT (Apple) devices are not working anymore until restarting the bluetoothd (as root user - via sleepwatcher automates this).

The second click for a full wake is only possible via USB kbd or mouse.

FullWake from sleep w/o need for double klick via power button, but BT still dead until restarting the BT-daemon.

 

For my taste it has something to do with system speed or clocking.

I own a second machine with same mainboard but slower CPU (8700) and slower RAM .

Any other component is identical.

 

Bam ..  no BT issues..  what the hell is going on ?

 

 

I have the same with an older GA-Z97X-UDH5 MB with Core i5 CPU, also running MacOS 12.0.1/12.1 Beta no issues with waking up from BT devices, showing the following (different device tree):

2021-11-11 16:10:38 +0100 Wake                Wake from Normal Sleep [CDNVA] : due to GLAN EHC1 EHC2 XHC HDEF/UserActivity Assertion Using AC (Charge:0%)

[texem]

with my i9-9900KS  i modified memory timing from XMP-3200 to manual 2666 .

 

all BT - issues are gone the same moment 

 

Uhhhhh … timing problems on z390pro … whats going wrong ? 

 

 

[Project 2501]

On 11/8/2021 at 2:07 PM, dsynos80 said:

Solution!!

1.Use latest BluetoothFixup

2.Use Previous IntelBluetoothFirmware ( I used 1.1.3 from my Catalina folder)

3.Shutdown

4.Cold boot

5.Enjoy!

 

P.S. DO NOT use BluetoothInjector kext

 

I didn't know there was a solution for the onboard BT for the Intel CNVi WiFi/BT board. I found IntelBluetoothFirmware on GitHub, but I couldn't find BluetoothFixup (I'd like to know where I can find it please). Since I am still running 10.14, does that mean the current IntelBluetoothFirmware will work for me without using your workaround for Monterey?

 

I assume that Intel CNVi WiFi is still not supported.