Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

Correct for the most part.

We need to add boot argument agdpmod=pikera

The 6650 and 6950 will need a SSDT to spoof device ID.

Thank you very much. Looks like I've got a few busy weekends ahead of me!
 
Have been having a few random restart lately. Below if the macOS report and my Config.plist.

Any help would be greatly appreciated! :thumbup:

Code:
panic(cpu 14 caller 0xffffff80036d3941): userspace watchdog timeout: no successful checkins from WindowServer in 120 seconds
WindowServer has not exited since first loaded
service: logd, total successful checkins in 65901 seconds: 6590, last successful checkin: 0 seconds ago
service: WindowServer, total successful checkins in 65861 seconds: 6574, last successful checkin: 120 seconds ago
service: opendirectoryd, total successful checkins in 65901 seconds: 6589, last successful checkin: 0 seconds ago
service: configd, total successful checkins in 65901 seconds: 6589, last successful checkin: 0 seconds ago

Panicked task 0xffffff8bba590218: 3 threads: pid 127: watchdogd
Backtrace (CPU 14), panicked thread: 0xffffff8bba6840c8, Frame : Return Address
0xffffffffc06a3590 : 0xffffff80003edf9d mach_kernel : _handle_debugger_trap + 0x4ad
0xffffffffc06a35e0 : 0xffffff800055b786 mach_kernel : _kdp_i386_trap + 0x116
0xffffffffc06a3620 : 0xffffff800054aa10 mach_kernel : _kernel_trap + 0x3e0
0xffffffffc06a3670 : 0xffffff8000388951 mach_kernel : _return_from_trap + 0xc1
0xffffffffc06a3690 : 0xffffff80003ee27d mach_kernel : _DebuggerTrapWithState + 0x5d
0xffffffffc06a3780 : 0xffffff80003ed929 mach_kernel : _panic_trap_to_debugger + 0x1a9
0xffffffffc06a37e0 : 0xffffff8000be0f93 mach_kernel : _panic_with_options + 0x89
0xffffffffc06a38d0 : 0xffffff80036d3941 com.apple.driver.watchdog : __ZN10IOWatchdog14userspacePanicEP8OSObjectPvP25IOExternalMethodArguments.cold.1 + 0x27
0xffffffffc06a38e0 : 0xffffff80036d35e0 com.apple.driver.watchdog : __ZN10IOWatchdog35userspaceDisableUserspaceMonitoringEP8OSObjectPvP25IOExternalMethodArguments
0xffffffffc06a3900 : 0xffffff80036d26cd com.apple.driver.watchdog : __ZN20IOWatchdogUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x7f
0xffffffffc06a3a30 : 0xffffff8000b544ca mach_kernel : _is_io_connect_method + 0x37a
0xffffffffc06a3b90 : 0xffffff8000502319 mach_kernel : _iokit_server_routine + 0x38c9
0xffffffffc06a3ca0 : 0xffffff80003c5999 mach_kernel : _ipc_kmsg_send + 0x569
0xffffffffc06a3d50 : 0xffffff80003de892 mach_kernel : _mach_msg_overwrite_trap + 0x4a2
0xffffffffc06a3dc0 : 0xffffff80003def9a mach_kernel : _mach_msg2_trap + 0x3ba
0xffffffffc06a3ef0 : 0xffffff800052d02a mach_kernel : _mach_call_munger64 + 0x1ea
0xffffffffc06a3fa0 : 0xffffff8000388db6 mach_kernel : _hndl_mach_scall64 + 0x16
      Kernel Extensions in backtrace:
         com.apple.driver.watchdog(1.0)[A71DE745-044D-37DB-B730-8F8FFB66B24A]@0xffffff80036d1000->0xffffff80036d3fff

Process name corresponding to current thread (0xffffff8bba6840c8): watchdogd
Boot args: keepsyms=1 debug=0x100 alcid=11 shikigva=80 igfxfw=2 agdpmod=pikera

Mac OS version:
22A380

Kernel version:
Darwin Kernel Version 22.1.0: Sun Oct  9 20:14:54 PDT 2022; root:xnu-8792.41.9~2/RELEASE_X86_64
Kernel UUID: BF7C9676-EF23-3E8D-A2E2-25DAC63091B6
roots installed: 0
KernelCache slide: 0x0000000000000000
KernelCache base:  0xffffff8000200000
Kernel slide:      0x00000000000dc000
Kernel text base:  0xffffff80002dc000
__HIB  text base: 0xffffff8000100000
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: 65901694001455
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00003befef0fa5ca
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x00000013f7b8714a 0x0000000000000000
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 1 swapfiles and OK swap space
Zone info:
  Zone map: 0xffffff8082ad7000 - 0xffffffa082ad7000
  . PGZ   : 0xffffff8082ad7000 - 0xffffff808aad8000
  . VM    : 0xffffff808aad8000 - 0xffffff8556471000
  . RO    : 0xffffff8556471000 - 0xffffff86ef7a4000
  . GEN0  : 0xffffff86ef7a4000 - 0xffffff8bbb13d000
  . GEN1  : 0xffffff8bbb13d000 - 0xffffff9086ad6000
  . GEN2  : 0xffffff9086ad6000 - 0xffffff955246f000
  . GEN3  : 0xffffff955246f000 - 0xffffff9a1de09000
  . DATA  : 0xffffff9a1de09000 - 0xffffffa082ad7000
  Metadata: 0xffffffffc7fee000 - 0xffffffffe7fee000
  Bitmaps : 0xffffffffe7fee000 - 0xfffffffffffee000
 

Attachments

  • config.plist
    35.3 KB · Views: 29
Hi @CaseySJ
I have upgraded BIOS firmware with last CPU Microcodes.

On this new BIOS firmware based on F9i version, I have included last CPU Microcodes version 0xF0 (11/15/2021) and CPU Microcodes version 0xF4 (07/31/2022).

Microcodes has been found on last Apple iMac19,1 firmware included on macOS Ventura 13.2 update.

I haven't tested this update because I'am on another hack based on MSI Z490.

@CaseySJ, if you can, Could you verify it and post it ?

Thanks :)

Hey Elias!
Just tried your custom BIOS, but get a "invalid BIOS image" error pop-up within QFlash when trying to upgrade.

I am on the official F9i firmware from gigabyte, downloaded from this post:

/EDIT1
Tried the other custom F9i versions found in this thread as well but all give the same error. Guess I'm doing something wrong..
Upgraded to the official F9 version now, no way back so hope it works without any problems ;)
 
Last edited:
Hey Elias!
Just tried your custom BIOS, but get a "invalid BIOS image" error pop-up within QFlash when trying to upgrade.

I am on the official F9i firmware from gigabyte, downloaded from this post:

/EDIT1
Tried the other custom F9i versions found in this thread as well but all give the same error. Guess I'm doing something wrong..
Upgraded to the official F9 version now, no way back so hope it works without any problems ;)
Strange, it « should » work fine as it’s still a F9i BIOS…
 
Have been having a few random restart lately. Below if the macOS report and my Config.plist.

Any help would be greatly appreciated! :thumbup:
There's insufficient information about the problem.
  • You're running Ventura 13.1, but latest version is 13.2. Would be good to upgrade.
  • Which version of BIOS?
  • What changes were made recently?
  • Have you tried to narrow the problem? What troubleshooting steps have you already taken?
  • Does the crash happen in any particular application or randomly anywhere, anytime?
  • Is the system running under high load when the crash occurs?
  • Are there any new software applications installed?
  • Any new hardware installed?
 
Thanks for all the great info! I just installed and ran HackinDROM. I have OC 0.7.8 and system is running well, although I do find it a bit slower than I expected with Sabrent Rocket NVMe 2.0 drives and 64GB RAM.
When I run the updater it shows this error screen. I have a backup copy of the existing config.plist ...do I just go for it? Some of these errors I just have no clue.
 

Attachments

  • Screen Shot .png
    Screen Shot .png
    145.7 KB · Views: 44
Thanks for all the great info! I just installed and ran HackinDROM. I have OC 0.7.8 and system is running well, although I do find it a bit slower than I expected with Sabrent Rocket NVMe 2.0 drives and 64GB RAM.
When I run the updater it shows this error screen. I have a backup copy of the existing config.plist ...do I just go for it? Some of these errors I just have no clue.
The error message provides all the hints we need. Let's look at the first one:
  • HfsPlus.efi at UEFI->Drivers[0] must have LoadEarly set to FALSE!
This means:
  • We go to UEFI->Drivers section in config.plist
  • We see a list of drivers, one per row
  • Row numbers start at 0
  • Hence UEFI->Drivers[0] is referring to the first row
  • And if we look at the first column of that row, we see it's HfsPlus.efi
  • And if we look at the remaining columns of that row, we see a column called LoadEarly
  • All we have to do now is uncheck that checkbox to set it to FALSE
This should help:
Screen Shot 2023-02-16 at 8.33.43 AM.png
 
Thanks for the reply!

When I load my existing config.plist from my active (working) efi none of those are checked. Is it possible it's just a version conflict from OC 0.7.2 to 0.8.9?
I think you can ignore those warnings. HackinDROM will make a backup of your EFI folder in any case. So I would suggest updating to 0.8.9 and rebooting. If you see these warnings during boot (just before OpenCore boot picker appears) then please report it here.
 
Thank you very much. Looks like I've got a few busy weekends ahead of me!
Of course, upgrading GPU means you won't be able to go back to Catalina. RX 6800/6900 requires Big Sur; RX 6600, Monterey (or later).
 
Back
Top