Contribute
Register

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

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
17,342
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
Hello Casey,
I have 10900f, Z490 vision G, RX 5600 XT Asus Dual Evo, Samsung 970 Evo Plus
Cooler Master liquid Cooler 240, 750w power supply

I'm using your EFI folder for G not D version 0.7.4 woks prefect including Shutdown and restart

But i have a problem with sleep
when i choose sleep, the PC goes to sleep for less than 1 second and wakes again
the display is still in sleep until I click a button
but the fans, liquid cooler and GFX Card back to work and light.

* i tried different bios version, different sleep setting in macos system preferences and different hackintool power settings

Can you tell me what is my problem please
Hello @menanegm,

Couple of things to check first:
  • System Preferences --> Energy Saver --> Wake for Network Access must be unchecked.
  • What USB devices are connected to both (a) internal and (b) external USB ports?
    • Is there a Fenvi FV-T919 WiFi/BT card that is connecting to the internal USB Header?
Most sleep issues are caused by USB devices so we start by disconnecting all of them except for a simple USB keyboard and mouse, then we check if sleep works. If it does, we reconnect USB devices one by one while checking sleep after each reconnection.
 
Last edited:
Joined
Mar 11, 2017
Messages
39
Motherboard
Gigabyte 490 Vision G
CPU
i9-1080k
Graphics
Sapphire Nitro+ RX 570
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
If you are not using Thunderbolt devices, it may be best to disable AppleVTD as described in the bottom half of this post:
That should eliminate the boot-time warning.

Also note that some folks are experiencing random crashes with latest versions of Gigabyte BIOS. So it might be worth downgrading the BIOS to (a) F8c and/or (b) F6.
Thanks for your continued assistance with this. I very much appreciate it :thumbup:

I've downgraded to F6 as recommended, completed a fresh install of Big Sur, and created a new backup as outlined in the first post. This included a fresh OC install (fresh config.plist). Will slowly add the apps I need, monitor for freezes, and take notes to find patterns.
 
Joined
Jul 13, 2013
Messages
104
Motherboard
Gigabyte Z490 Vision D
CPU
i7-10700K
Graphics
AMD RX 580
Mac
  1. MacBook Pro
  2. Mac mini
Classic Mac
  1. Centris
  2. Power Mac
  3. Quadra
Mobile Phone
  1. iOS
Intel PTT on F5 (Vision D) works just fine to enable the onboard intel TPM firmware. It’s just not on by default.

I’ve been running win 11 on BIOS F5 on the z490 since the summer after enabling PTT, and there has been no problems at all (with the exception of a couple of dev builds in the 224xx series that were incompatible with the Samsung T7’s firmware and was causing crashes as soon as a T7 was attached to the bus, but that quirk has since been fixed).

Thanks, @dehjomz! Because of your post I was able to determine that I hadn't quite gotten my BIOS change correct. I missed the PTT setting...I went straight to Settings > Trusted Computing and enabled things there. I missed the Platform Trust Technology entry entirely. That's now fixed, which I greatly appreciate.

Now to find the post that reminds me how to pair my Magic Keyboard and Magic Trackpad on the macOS side and then copy the pairing keys into Windows Registry...<sigh>
 

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
17,342
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
** macOS Monterey will be released on Monday, October 25 **

OpenCore 0.7.4 is Necessary
Screen Shot 2021-10-18 at 4.44.01 PM.png
 
Joined
Feb 1, 2011
Messages
123
Motherboard
Gigabyte Z490 Vision D rev 1.1
CPU
i7-10700
Graphics
RX 570
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
After updating from OpenCore 0.6.0 to current, and installing Big Sur, OpenCore fails to boot my Win10 drive. I replaced the config.plist with a fresh one. Anybody care to speculate on the first thing to look at? The furthest I get is Windows trying to start self repair and hanging. I was dual booting no problem before.

Side note: it appears Windows 11 may require Secure Boot enabled. Is this going to be an issue for OpenCore?
 
Joined
Jun 2, 2020
Messages
39
Motherboard
GIGABYTE Z490 Aorus Master
CPU
i9-10900K
Graphics
RX 580
Windows 11 doesn't require Secure Boot enabled. I think, the problem with booting Windows is related to Apple-VTD. You can try my SSDT-DMAR.aml or disable Apple-VTD, if my file doesn't work either.
 

Attachments

  • SSDT-DMAR.aml
    80 bytes · Views: 6
Joined
Nov 24, 2020
Messages
19
Motherboard
Gigabyte Z490 Vision D
CPU
Intel 8 Core i7-10700K
Graphics
Sapphire Pulse RX 5700XT
Alas this has also been addressed numerous times in this thread. Simply visit the OpenCore 0.7.3 mini-guide and there’s a link to a post that states how AppleVTD can be disabled. Simply disable it and you should be okay to boot Windows through OpenCore.
Hey Casey,

Circling back to this one. Recently I notice my computer would get a kernel panic crash following wake up and 2-3 minutes of work. Any chance it may have something to do with the (improper) deactivation of AppleVTD? Or does it have another explanation?

As always, very much appreciated!

Here is the latest crash report:
anic(cpu 2 caller 0xffffff8013bfea25): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since wake (290 seconds ago): 30, last successful checkin: 0 seconds ago
service: com.apple.WindowServer, total successful checkins since wake (290 seconds ago): 18, last successful checkin: 120 seconds ago

Backtrace (CPU 2), Frame : Return Address
0xffffffa0bf68b670 : 0xffffff801088e04d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa0bf68b6c0 : 0xffffff80109d4e13 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa0bf68b700 : 0xffffff80109c540a mach_kernel : _kernel_trap + 0x55a
0xffffffa0bf68b750 : 0xffffff8010832a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0bf68b770 : 0xffffff801088d86d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa0bf68b890 : 0xffffff801088db63 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa0bf68b900 : 0xffffff801109dc74 mach_kernel : _panic_with_thread_context
0xffffffa0bf68b970 : 0xffffff8013bfea25 com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xffffffa0bf68b980 : 0xffffff8013bfe660 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments
0xffffffa0bf68b9a0 : 0xffffff801101e4be mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1de
0xffffffa0bf68b9f0 : 0xffffff8013bfda34 com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7c
0xffffffa0bf68bb20 : 0xffffff801102876b mach_kernel : _is_io_connect_method + 0x35b
0xffffffa0bf68bc80 : 0xffffff8010980841 mach_kernel : _iokit_server_routine + 0x4dd1
0xffffffa0bf68bd90 : 0xffffff80108936cd mach_kernel : _ipc_kobject_server + 0x2fd
0xffffffa0bf68be00 : 0xffffff8010869cf5 mach_kernel : _ipc_kmsg_send + 0x115
0xffffffa0bf68be60 : 0xffffff8010881252 mach_kernel : _mach_msg_overwrite_trap + 0x2d2
0xffffffa0bf68bef0 : 0xffffff80109a970d mach_kernel : _mach_call_munger64 + 0x29d
0xffffffa0bf68bfa0 : 0xffffff8010833216 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[5E977058-687E-36A0-9AED-3BDE47B80C97]@0xffffff8013bfc000->0xffffff8013bfefff

Process name corresponding to current thread: watchdogd
Boot args: keepsyms=1 dart=0 debug=0x100 agdpmod=pikera alcid=11 shikigva=80

Mac OS version:
20G80

Kernel version:
Darwin Kernel Version 20.6.0: Wed Jun 23 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64
Kernel UUID:xx
KernelCache slide: 0x0000000010600000
KernelCache base: 0xffffff8010800000
Kernel slide: 0x0000000010610000
Kernel text base: 0xffffff8010810000
__HIB text base: 0xffffff8010700000
System model name: iMacPro1,1 (Mac-xxxx)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 10423061784632
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000097acee52aea
Sleep : 0x00000934b38e8beb 0x00000001889e175c 0x0000091ff387638a
Wake : 0x00000935044e5397 0x00000001891044c6 0x00000934fe1ccc35
 

CaseySJ

Moderator
Joined
Nov 11, 2018
Messages
17,342
Motherboard
Gigabyte Z490 Vision D
CPU
i5-10400
Graphics
RX 580
Mac
  1. MacBook Air
  2. MacBook Pro
  3. Mac Pro
Classic Mac
  1. Quadra
Mobile Phone
  1. iOS
Hey Casey,

Circling back to this one. Recently I notice my computer would get a kernel panic crash following wake up and 2-3 minutes of work. Any chance it may have something to do with the (improper) deactivation of AppleVTD? Or does it have another explanation?

As always, very much appreciated!

Here is the latest crash report:
...
We added CpuTscSync.kext starting with OpenCore 0.7.3 so the first thing would be to disable this kext. If the problem persists after that, then it's necessary to characterize the problem by describing (a) when it first started, (b) whether there's any pattern to it, (c) what troubleshooting steps have already been undertaken, (d) does it occur on a fresh install of macOS on a spare SSD, (e) etc.
 

ffk

Joined
Aug 3, 2011
Messages
152
Motherboard
Gigabyte Z390 Designare
CPU
i9-9900K
Graphics
UHD 630
Classic Mac
  1. Power Mac
Mobile Phone
  1. iOS
** macOS Monterey will be released on Monday, October 25 **

OpenCore 0.7.4 is Necessary

I don't think there is a great answer to this question, but... If my build is not one listed on the hackindrom list of builds...

Updating the OS is going to involve an opencore update and drag and drop doesn't seem to be a working option with the opencore update as the config file from 0.6.5 will most definitely not play well with 0.7.4.

  1. Is there? or What is? ...the easiest way to update the EFI folder to 0.7.4 on a hack that has been running OC 0.6.5 well on 10.14.x and then 10.15.x?
  2. Do I have to build a port map for all builds using 11.3 and up? Will the configs that use USBInjectAll.kext continue to work?
My findings all seem to point to the opencore config compare for the config files, plist editor pro, and opencore configurator, and alot of back and forth comparisons...
 
Last edited:
Joined
Oct 24, 2013
Messages
797
Motherboard
Gigabyte Z590 Vision D
CPU
i7-11700K OC @ 5.2GHz
Graphics
RX 6800 XT
Mac
  1. iMac
  2. MacBook
  3. MacBook Pro
Mobile Phone
  1. iOS
** macOS Monterey will be released on Monday, October 25 **

OpenCore 0.7.4 is Necessary
View attachment 531258
I like Monterey. Especially the airplay receiver feature. I turned my MacBook into an Apple TV essentially and was airplaying content to it when I went on vacation earlier this year. Hooked it up to a tv via hdmi and was playing content back from my iPhone.

I do have some ideas for how Apple could update macOS airplay however. They need allow airplay content to run in windowed mode (that can be resized) rather than taking up the whole screen. And even worse, with a dual screen setup, the current iteration displays content on one monitor in full screen mode, and the other monitor is black, and can’t be used for other tasks like web browsing and so forth. Unintuitive in my opinion.
 
Top