Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[CaseySJ]

@CaseySJ My magic trackpad is preventing my Hackintosh from falling sleep, and after I updated to Mac OS Monterey the preventing Bluetooth device wake Mac option is disappear. Is there any solution to that? Thanks!

We can disable wake from USB (Bluetooth operates over USB) by enabling:

• SSDT-GPRW.aml from ACPI section
• GPRW patch from ACPI —> Patch section

After this, only power button will wake up the computer.

 

[emistral]

Does anybody know what type of WiFi 6 chipset the new Macbook with M1 pro/max have by any chance?

 

[CaseySJ]

Does anybody know what type of WiFi 6 chipset the new Macbook with M1 pro/max have by any chance?

The actual model name is not apparent from IOReg, but it is a Broadcom device judging by "BCM" in the driver name. It's a WiFi 6 module with 80MHz max channel bandwidth on 5GHz band, and 2x2 MIMO instead of 3x3. It's the same chip as on M1 MacBook Pro from 2020.

Details:

MacBook Pro Wi-Fi specification details

Learn about MacBook Pro Wi-Fi specification details.

support.apple.com

IOReg from my 14" MacBook Pro. No clear device ID anywhere that I could find. Might be in one of the hex dumps.

 

[CaseySJ]

You need to disable AppleVTD in order to dual boots Windows and Mac OS.

This problem affects some users, but not all. I have not needed to disable AppleVTD in order to boot Windows 10 or Windows 11 through OpenCore. We haven't determined what specifically causes this problem for some users.

 

[yurid]

There are several factors that affect sleep/wake, but most of them are related to USB devices (including Bluetooth, which operates over USB). Other lessor factors involve smart power supplies and other devices that connect to internal USB 2.0 hub on motherboard.

If you believe OpenCore itself is the issue, please try going back to OpenCore 0.7.4 to recheck sleep/wake. If sleep/wake is still broken in OpenCore 0.7.4, then we know the problem lies elsewhere.

Thank you for the prompt answer CaseySJ. Nothing has changed besides the Opencore update; well, I connected the Bluetooth BluMe HD at the same time, but even when the Bluetooth connection is removed, it doesn't go to sleep. So, I assume it is the update. Do you think I need to reset NVRAM after going back to 0.7.4?

 

[CaseySJ]

Thank you for the prompt answer CaseySJ. Nothing has changed besides the Opencore update; well, I connected the Bluetooth BluMe HD at the same time, but even when the Bluetooth connection is removed, it doesn't go to sleep. So, I assume it is the update. Do you think I need to reset NVRAM after going back to 0.7.4?

Because OpenCore updates historically have not affected sleep/wake, here are some things to try:

• Reset NVRAM is always a good idea. It will also change the default startup disk if there is more than one boot disk in the system.
• As mentioned before, you may go back to previous version of OpenCore to recheck sleep/wake. This may be very important to do. It will tell us more definitively whether OpenCore 0.7.6 is really the culprit. If it is, then we can try disabling some kernel extensions in 0.7.6 such as BrcmFirmwareData and BrcmPatchRAM3.

 

[Fabrizzioa04]

Hi, @CaseySJ,
I'm sorry to bother you ... I just get rid of my RX 580 and started to work with the iGPU. But I can't connect a second screen with an USB type c to HDMI adapter.

 

[yurid]

Because OpenCore updates historically have not affected sleep/wake, here are some things to try:

• Reset NVRAM is always a good idea. It will also change the default startup disk if there is more than one boot disk in the system.
• As mentioned before, you may go back to previous version of OpenCore to recheck sleep/wake. This may be very important to do. It will tell us more definitively whether OpenCore 0.7.6 is really the culprit. If it is, then we can try disabling some kernel extensions in 0.7.6 such as BrcmFirmwareData and BrcmPatchRAM3.

It was changed back to 0.7.4 with the same result - no sleep. I am puzzled. What could trigger this change? My question to you, CaseySJ, what would my next step be to fix the problem?
Another observation is that my Monterey is stuck at 12.0.1 and stating it is up to date. I have heard about that problem, but only about M1-based Macs.

 

[CaseySJ]

It was changed back to 0.7.4 with the same result - no sleep. I am puzzled. What could trigger this change? My question to you, CaseySJ, what would my next step be to fix the problem?
Another observation is that my Monterey is stuck at 12.0.1 and stating it is up to date. I have heard about that problem, but only about M1-based Macs.

Let's tackle the second issue first, as follows:

• Software Update is not giving you the option to upgrade to Monterey 12.1.
• This can be fixed as follows:
  • Change SecureBootModel in Misc --> Security to Disabled (not Default)
  • Reboot and log back in
  • Now try System Preferences --> Software Update again. You should have the upgrade option now.
  • Proceed with the full upgrade.
• When 12.1 is fully installed, you may either keep SecureBootModel set to Disabled or you may change it back to Default.

 

[yurid]

Let's tackle the second issue first, as follows:

• Software Update is not giving you the option to upgrade to Monterey 12.1.
• This can be fixed as follows:
  • Change SecureBootModel in Misc --> Security to Disabled (not Default)
  • Reboot and log back in
  • Now try System Preferences --> Software Update again. You should have the upgrade option now.
  • Proceed with the full upgrade.
• When 12.1 is fully installed, you may either keep SecureBootModel set to Disabled or you may change it back to Default.

Thank you, CaseySJ, very much. I will do it, but only in 2 weeks. I am on my two weeks hitch in Alaska. Happy New Year to you.