Contribute
Register

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

CaseySJ said:
Adding agdpmod=pikera is sufficient. It's not necessary to change system product name. The 6900 XT is supported in Big Sur and Monterey, but not in Catalina.
Click to expand...
thank you very much,your help is much appreciated
 
Well, I received my 6900 XT today but I'm facing some issues. Basically, it won't power on neither macOS or Windows; it seems its well plug in into motherboard and power supply .
I've tried disabling iGPU in BIOS, connecting it to a different slot and nothing. It won't even start spinning the fans. Switching back to the RX 580, and everything works fine. I want to mention that I'm using BIOS 20b, and, when I tried to follow the instructions for configuration BIOS parameters, I never saw this parameter
Settings → IOPorts
  • Initial Display Output → PCIe 1 Slot (if GPU in slot 1) or IGFX (if using iGPU to display monitor)
I'd like to know if is there something else I can check in BIOS (PCI distribution, enabling PCI 3 or 4,...)
Also want to add that the card (6900 XT) is brand new so I don't thing is something wrong with it.
Sorry if this is off topic.
THANK YOU.
 
sardino said:
Well, I received my 6900 XT today but I'm facing some issues. Basically, it won't power on neither macOS or Windows; it seems its well plug in into motherboard and power supply .
I've tried disabling iGPU in BIOS, connecting it to a different slot and nothing. It won't even start spinning the fans. Switching back to the RX 580, and everything works fine. I want to mention that I'm using BIOS 20b, and, when I tried to follow the instructions for configuration BIOS parameters, I never saw this parameter
Settings → IOPorts
  • Initial Display Output → PCIe 1 Slot (if GPU in slot 1) or IGFX (if using iGPU to display monitor)
I'd like to know if is there something else I can check in BIOS (PCI distribution, enabling PCI 3 or 4,...)
Also want to add that the card (6900 XT) is brand new so I don't thing is something wrong with it.
Sorry if this is off topic.
THANK YOU.
Click to expand...
Suggestions:
  • First, with RX580 installed, perform CMOS Reset. When system starts, go to BIOS Setup and Load Optimized Defaults only. Please refer to Gigabyte owner's manual for CMOS Reset procedure.
  • Then check is CSM Support is enabled or disabled. We want it to be Disabled.
  • Save and Exit.
  • Now shutdown the computer by holding power button down until it powers off.
  • Flip power switch on PSU to OFF. Do not skip this step.
  • Physically remove RX580 and install RX 6900 XT.
  • Connect DisplayPort or HDMI cable between RX 6900 XT and monitor.
  • Flip power switch on PSU back to ON and power up the system.
  • Does Gigabyte splash screen appear on monitor?
  • If it does, enter BIOS setup and configure the rest of BIOS parameters for macOS (post 1).
 
CaseySJ said:
Suggestions:
  • First, with RX580 installed, perform CMOS Reset. When system starts, go to BIOS Setup and Load Optimized Defaults only. Please refer to Gigabyte owner's manual for CMOS Reset procedure.
  • Then check is CSM Support is enabled or disabled. We want it to be Disabled.
  • Save and Exit.
  • Now shutdown the computer by holding power button down until it powers off.
  • Flip power switch on PSU to OFF. Do not skip this step.
  • Physically remove RX580 and install RX 6900 XT.
  • Connect DisplayPort or HDMI cable between RX 6900 XT and monitor.
  • Flip power switch on PSU back to ON and power up the system.
  • Does Gigabyte splash screen appear on monitor?
  • If it does, enter BIOS setup and configure the rest of BIOS parameters for macOS (post 1).
Click to expand...
Well I followed your instructions but still no luck…I didn’t get gigabyte splash screen,cmos was reseted because I got a message saying so…still same symptoms,it is like no power goes to the card even that it seems well plugged
Any other suggestions?
Tonight I’ll try to install it in another computer but it is quite old,I don’t know if it is compatible (ga-z77x-up5 th)
THANK YOU
 
sardino said:
Well I followed your instructions but still no luck…I didn’t get gigabyte splash screen,cmos was reseted because I got a message saying so…still same symptoms,it is like no power goes to the card even that it seems well plugged
Any other suggestions?
Tonight I’ll try to install it in another computer but it is quite old,I don’t know if it is compatible (ga-z77x-up5 th)
THANK YOU
Click to expand...
I have faced similar issue with the Z490 Vision D. It really doesn't like new graphics cards! Let's try the following:
  • With RX 6900 XT installed, shutdown system, flip power switch on PSU to OFF, and short the two CMOS Reset pins with a flathead screwdriver for 5 seconds.
  • Keep DisplayPort or HDMI cable connected to RX 6900 XT and monitor, but disconnect all video cables from the motherboard rear IO panel.
  • Power the system up.
  • Do you see the Gigabyte splash screen?
  • Do GPU fans turn on briefly when computer is first powered up?
Also, which version of BIOS is installed?
 
CaseySJ said:
I have faced similar issue with the Z490 Vision D. It really doesn't like new graphics cards! Let's try the following:
  • With RX 6900 XT installed, shutdown system, flip power switch on PSU to OFF, and short the two CMOS Reset pins with a flathead screwdriver for 5 seconds.
  • Keep DisplayPort or HDMI cable connected to RX 6900 XT and monitor, but disconnect all video cables from the motherboard rear IO panel.
  • Power the system up.
  • Do you see the Gigabyte splash screen?
  • Do GPU fans turn on briefly when computer is first powered up?
Also, which version of BIOS is installed?
Click to expand...
I just found what the problem was..First, thank you again for your help, and then I am sorry to make you loose your time. The problem was the new PCI cable connector which I had to use because this card takes 8+8+6...I was checking that everything was properly connected to the power supply and the card but the problem was in the actual cable.
Thanks again for your time.
 
thegubatoshchamp said:
@CaseySJ is there any way to create a custom SSDT to remove a particular NVMe SSD drive from OpenCore being able to pick it up basically exclude from boot. I have a Windows OS installed on a Samsung Pro NVMe SSD on Z490 Vision D on slot m2m_sb. Scan policy in OpenCore would be a option.But changing the scan policy number may do more harm than good because, if another drive is connected after boot by a user imputing a USB that was formatted in NTFS Windows format, then scan policy in OpenCore would not pick it up. I have disabled the "untitled" Windows drive from editing VIFS setting the UUID to none auto.

The main objective is to possibly create a custom SSDT that will block Windows NVMe M.2 from showing in OpenCore boot picker and not be picked up as a recognizable drive on boot login. If a scan policy number that will be convenient to allow NTFS partitions to connect after boot such as user USB input to be picked up that would be ideal also which ever is easier or less of a hassle.
Click to expand...
Hi, thegubatoshchamp.

You can do that by following this guide. See below to find your Windows EFI Partition, and then in OpenCore Configurator in Misc Entries (see pic below), don't tick Enabled - leave it blank that would do the trick not showing Windows in OpenCore boot menu.

The guide:
kextcache.com

[GUIDE] Opencore Dualboot/ Multiboot Guide | Kextcache

The Hottest Bootloader is now Dropped Opencore 0.5.8 and you wanted to Dualboot Your System with macOS Catalina, Windows 10 & Linux but don't know how
kextcache.com kextcache.com


2022-03-03 14:48:47.png
 
Last edited:
Build :1
GA-Z97M-D3H |  i5 4570 |  GeForce GTX 760
Hi, after I have upgraded to Monterey, the Hackintosh suddenly freezes and restart -- the pointer can still be moved, but there is no response wherever I clicked on the dock or the app that I am using.
It happened three times on this day.
The first time, the screensaver is on, after I went out and came back, it had restarted, I logged on and received a bug report.
The second time, I was browsing with Chrome. And it froze.
The third time, I was using Google Meet with Chrome.
Does anyone know what is going on?:crazy:


panic(cpu 6 caller 0xffffff800c5049ad): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
service: logd, total successful checkins since load (1770 seconds ago): 178, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins since load (1740 seconds ago): 162, last successful checkin: 120 seconds ago
service: opendirectoryd, total successful checkins since load (1770 seconds ago): 177, last successful checkin: 0 seconds ago

Panicked task 0xffffff94f61466a0: 3 threads: pid 112: watchdogd
Backtrace (CPU 6), panicked thread: 0xffffff99c25fdaa0, Frame : Return Address
0xffffffd0c89a36c0 : 0xffffff8009085ffd mach_kernel : _handle_debugger_trap + 0x41d
0xffffffd0c89a3710 : 0xffffff80091e6035 mach_kernel : _kdp_i386_trap + 0x145
0xffffffd0c89a3750 : 0xffffff80091d5803 mach_kernel : _kernel_trap + 0x533
0xffffffd0c89a37a0 : 0xffffff8009025a60 mach_kernel : _return_from_trap + 0xe0
0xffffffd0c89a37c0 : 0xffffff80090863cd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffd0c89a38e0 : 0xffffff8009085b86 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffd0c89a3940 : 0xffffff80099164a6 mach_kernel : _panic_with_options + 0x5c
0xffffffd0c89a39b0 : 0xffffff800c5049ad com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xffffffd0c89a39c0 : 0xffffff800c504600 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments
0xffffffd0c89a39e0 : 0xffffff800988a33d mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1dd
0xffffffd0c89a3a30 : 0xffffff800c5039bb com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7f
0xffffffd0c89a3b60 : 0xffffff800989460c mach_kernel : _is_io_connect_method + 0x3cc
0xffffffd0c89a3cc0 : 0xffffff800918d0b4 mach_kernel : _iokit_server_routine + 0x4e94
0xffffffd0c89a3dd0 : 0xffffff8009061048 mach_kernel : _ipc_kmsg_send + 0x468
0xffffffd0c89a3e60 : 0xffffff8009077a8d mach_kernel : _mach_msg_overwrite_trap + 0x2bd
0xffffffd0c89a3ef0 : 0xffffff80091b8f7e mach_kernel : _mach_call_munger64 + 0x22e
0xffffffd0c89a3fa0 : 0xffffff8009026246 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[0E41330C-797B-3F73-A333-04EFB1F20DAC]@0xffffff800c502000->0xffffff800c504fff

Process name corresponding to current thread (0xffffff99c25fdaa0): watchdogd
Boot args: keepsyms=1 debug=0x100 agdpmod=pikera alcid=11 shikigva=80 dk.e1000=0

Mac OS version:
21D62

Kernel version:
Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64
Kernel UUID: 93729D02-FE6F-355B-BA76-BA930AA7103F
KernelCache slide: 0x0000000008e00000
KernelCache base: 0xffffff8009000000
Kernel slide: 0x0000000008e10000
Kernel text base: 0xffffff8009010000
__HIB text base: 0xffffff8008f00000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 1780189304058
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000019e7b8d1a08
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000000182013fba8 0x0000000000000000
Zone info:
Foreign : 0xffffff80106b9000 - 0xffffff80106c6000
Native : 0xffffff802959c000 - 0xffffffa02959c000
Readonly : 0xffffff84f6268000 - 0xffffff868fbfc000
Metadata : 0xffffffd34195b000 - 0xffffffd361aea000
Bitmaps : 0xffffffd361aea000 - 0xffffffd367aea000


panic(cpu 6 caller 0xffffff800c5049ad): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
service: logd, total successful checkins since load (1770 seconds ago): 178, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins since load (1740 seconds ago): 162, last successful checkin: 120 seconds ago
service: opendirectoryd, total successful checkins since load (1770 seconds ago): 177, last successful checkin: 0 seconds ago

Panicked task 0xffffff94f61466a0: 3 threads: pid 112: watchdogd
Backtrace (CPU 6), panicked thread: 0xffffff99c25fdaa0, Frame : Return Address
0xffffffd0c89a36c0 : 0xffffff8009085ffd mach_kernel : _handle_debugger_trap + 0x41d
0xffffffd0c89a3710 : 0xffffff80091e6035 mach_kernel : _kdp_i386_trap + 0x145
0xffffffd0c89a3750 : 0xffffff80091d5803 mach_kernel : _kernel_trap + 0x533
0xffffffd0c89a37a0 : 0xffffff8009025a60 mach_kernel : _return_from_trap + 0xe0
0xffffffd0c89a37c0 : 0xffffff80090863cd mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffd0c89a38e0 : 0xffffff8009085b86 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xffffffd0c89a3940 : 0xffffff80099164a6 mach_kernel : _panic_with_options + 0x5c
0xffffffd0c89a39b0 : 0xffffff800c5049ad com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xffffffd0c89a39c0 : 0xffffff800c504600 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments
0xffffffd0c89a39e0 : 0xffffff800988a33d mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1dd
0xffffffd0c89a3a30 : 0xffffff800c5039bb com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7f
0xffffffd0c89a3b60 : 0xffffff800989460c mach_kernel : _is_io_connect_method + 0x3cc
0xffffffd0c89a3cc0 : 0xffffff800918d0b4 mach_kernel : _iokit_server_routine + 0x4e94
0xffffffd0c89a3dd0 : 0xffffff8009061048 mach_kernel : _ipc_kmsg_send + 0x468
0xffffffd0c89a3e60 : 0xffffff8009077a8d mach_kernel : _mach_msg_overwrite_trap + 0x2bd
0xffffffd0c89a3ef0 : 0xffffff80091b8f7e mach_kernel : _mach_call_munger64 + 0x22e
0xffffffd0c89a3fa0 : 0xffffff8009026246 mach_kernel : _hndl_mach_scall64 + 0x16
Kernel Extensions in backtrace:
com.apple.driver.watchdog(1.0)[0E41330C-797B-3F73-A333-04EFB1F20DAC]@0xffffff800c502000->0xffffff800c504fff

Process name corresponding to current thread (0xffffff99c25fdaa0): watchdogd
Boot args: keepsyms=1 debug=0x100 agdpmod=pikera alcid=11 shikigva=80 dk.e1000=0

Mac OS version:
21D62

Kernel version:
Darwin Kernel Version 21.3.0: Wed Jan 5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64
Kernel UUID: 93729D02-FE6F-355B-BA76-BA930AA7103F
KernelCache slide: 0x0000000008e00000
KernelCache base: 0xffffff8009000000
Kernel slide: 0x0000000008e10000
Kernel text base: 0xffffff8009010000
__HIB text base: 0xffffff8008f00000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 1780189304058
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0000019e7b8d1a08
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000000182013fba8 0x0000000000000000
Zone info:
Foreign : 0xffffff80106b9000 - 0xffffff80106c6000
Native : 0xffffff802959c000 - 0xffffffa02959c000
Readonly : 0xffffff84f6268000 - 0xffffff868fbfc000
Metadata : 0xffffffd34195b000 - 0xffffffd361aea000
Bitmaps : 0xffffffd361aea000 - 0xffffffd367aea000
Click to expand...
 

Attachments

  • config.plist
    35.8 KB · Views: 27
Last edited:
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top