Contribute
Register

Gigabyte X299X - Catalina Support

Joined
Mar 6, 2013
Messages
231
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
Vega 64
Mobile Phone
  1. Android
Currently running Mesh at 30, Core at 48, with a voltage of 1.19 and VCCIN of 2.0. LLC is Medium, so everything's quite close to what you've been experimenting with as well.
I briefly tried going 49, but I think that may require me to increase my LLC, which I currently don't want to do. Maybe something to check later.
Nice, 4.8 at 1.19 is pretty good. Above average anyway, from what I've been told.

Out of interest, what's your concern regarding increasing LLC? Heat? I've not yet really got my head around the interactions of VCCIN and LLC with main vcore and its effect on overclock. Interesting that you're as high as 2.0 on VCCIN - did you try lower VCCINs and found 2.0 gave better results? I've not gone above 1.92 yet. There's one expert on overclock.net who sets his VCCIN to 1.74 - underclocking it - and uses minimal or no LLC, because he says some voltage droop is good. Then I found a guide on another site that set VCCIN to 3.0!

I have experimented with various VCCINs, but haven't yet spotted any clear pattern. High VCCINs didn't seem to enable lower VCore, which was the main thing I was hoping for, though I haven't yet tried as high as 2.0. And of course I'm quite limited until I get proper cooling; I've stopped experimenting with new overclock settings until I do.

I'm going to order the MO-RA3 radiator soon, maybe today. I'll likely get that TechN block as well, despite the lack of reviews, as I don't think I want to pay the high delivery prices that an Optimus would involve. It's working well for you so that's a good sign :)

Yeah, I'm seeing the same behavior as you, entering without "Save and Exit" or resetting leads to an OpenCore boot failure. Seems like the SMBIOS does not affect this particular behavior.
OK thanks. I'm thinking there must be some OpenCore setting that affects this.

Today I learned two three new things regarding this issue:

1. It happens the same when I boot Windows from OpenCore. Exactly the same: if I launch OpenCore having been in the BIOS, I get a shutdown and restart very early in the Windows boot process, and when it comes back up CPU and RAM are at stock. So it's definitely OpenCore in general and not macOS specifically.

2. It's not, as I thought before, specific to overclocking. I prepared a BIOS profile with all CPU and RAM frequencies and voltages at Auto, and it happened just the same. It wasn't a complete stock setup, eg I still had my power and current overrides in place, and a couple of other non-default settings in the Advanced CPU Options menu.

3. It even happens when I use the F12 Boot menu. So it's not specific to having accessed the BIOS. It happens in any scenario except normal straight-through booting.

I'm going to keep investigating it as it's a bit of a pain when testing other OpenCore settings using a USB stick. In that scenario it's very convenient to be able to just select the USB from the Boot Override or F12 menu rather than messing around with boot orders, and this reset issue rather gets in the way of that.
 
Last edited:
Joined
Mar 6, 2013
Messages
231
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
Vega 64
Mobile Phone
  1. Android
I think I'm starting to understand the parameters of this boot-from-BIOS problem, though sadly I'm no closer to finding a solution.

Firstly, to establish some terms: by "straight through" booting I mean any boot in which the user does not enter the BIOS and does not access the F12 boot menu. The system is powered up or restarted, and then the user leaves it to automatically boot the first entry in the boot order.

I have established that:
  1. Booting OpenCore will fail in any boot that is not a straight-through boot. However having failed, subsequent non-straight-through boots will succeed, until the next time BIOS settings are applied with F10.
  2. It happens with all BIOS settings I have tested, including when the BIOS has been reset to "Optimized Defaults".
  3. Putting OpenCore into debug mode shows that there are no errors or other indicative messages printed by OpenCore at or before the reboot. So far as I can understand, the OpenCore debug logs are identical between a boot that triggers the problem and one that does not. The only things that change are a few hex values related to partition IDs and the like, but I think these change on every boot.
  4. It appears to be based on a timer / timeout. Therefore it can happen at any stage of booting, including when sitting idle at the OpenCore/OpenCanopy boot menu (this is easily triggered if you increase the Timeout value in config.plist)
  5. I timed multiple instances of boot-from-BIOS, timing how long it took from the moment I hit Enter on the Boot Override screen before the system rebooted. It was almost exactly 10 seconds every time. The stopwatch read eg 10.14 and 10.25, but this includes my reaction time to hit the button.
  6. Therefore I believe it is the BIOS that is triggering the shutdown and reboot.
  7. This feels to me like a BIOS-initiated shutdown after a timeout period has elapsed. This suggests to me that the BIOS is not seeing something it expects on the boot, so it aborts it after 10 seconds because it thinks it's a boot failure.
  8. This could very well explain why the CPU and RAM frequencies are reset at the same time: thinking it's a boot failure, it resets settings to try to achieve a successful boot next time.
What remains a mystery to me is why, after one such boot failure, it will then work following the shutdown/reboot. This implies that whatever the BIOS resets also works to fix this problem. It will continue to work until the next time BIOS settings are applied with F10, at which point it'll then fail on the next non straight-through boot.

I've tried testing various OpenCore quirks related to booting, but nothing so far has made any difference.

This seems like a rather strange issue that definitely needs to be asked of the OpenCore devs, and I'll try and do that soon.

Unfortunately it seems quite possible that this is a BIOS bug unique to our motherboard, so whether there will be any resolution I don't know.

In the meantime, if you never boot OpenCore except with a straight-through boot it should work fine using the 0.6.3 EFI I posted earlier.
 
Last edited:
Joined
Mar 28, 2019
Messages
84
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
Quick update from my end:

I can confirm the 10 second "non-straight-boot" issue exactly as you are describing. I tried a ton of different RTC-related stuff, including the RtcMemoryFixup approach, but no dice. Earlier in the thread it was mentioned that this did not succeed for another person either, so I guess we're following in the footsteps of those who came before us. So far I was unable to turn up anything usable that would remedy this reset issue.

While digging through the config file I did notice that native power management was unavailable because SSDT-PLUG-DRTNIA.aml was disabled. Enabling it also enables native power management and fixes that issue.
Originally I was looking at that section because I was trying to get sleep to work, which thus far I've been unsuccessful with.

I did manage to do a fresh install of Big Sur though, which works well, without any extra issues, which was a nice surprise.

The three items that now remain on my list are:
- Get sleep working (currently not working at all)
- Get ethernet working
- Fix the BIOS reset bug

For the second one I noticed that whether the ethernet ports worked largely came down to whether a butterfly was active in china at a given time or not, so I moved them to /Library/Extensions, which made my Catalina install extremely unstable. I'm probably going to stick with a Fenvi WiFi card and not bother with the Ethernet ports unless a better solution comes along for now.

In better news though, I got the Bluetooth portion of the integrated AX200 card to work and now have my Magic Keyboard and Trackpad connected wirelessly, which works well. WiFi is very iffy with that card on Big Sur though, so that's a no-go at the moment.

I'm gonna try figure out the sleep issues next, though currently I'm at a bit of a loss as to what's causing the inability to go to sleep.
 
Joined
Mar 6, 2013
Messages
231
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
Vega 64
Mobile Phone
  1. Android
While digging through the config file I did notice that native power management was unavailable because SSDT-PLUG-DRTNIA.aml was disabled. Enabling it also enables native power management and fixes that issue.
Originally I was looking at that section because I was trying to get sleep to work, which thus far I've been unsuccessful with.
OK interesting. Can you describe what you mean by "native power management unavailable", because I'm quite confused about how exactly we know if PM is working?

I had PLUG-DRTNIA disabled for two reasons:

1. Enabling it gave me a panic on boot when I tested it recently. Though I ran it in addition to SSDT-X299X-DESIGNARE10G-PR00 which I believe does the same thing.

2. I was pretty sure that enabling PM was already being done by dolgarrenan's SSDT-X299X-DESIGNARE10G-PR00. Basically, as I understand it, the purpose of PLUG-DRTANIA is to set plugin-type 1 on the first CPU, which enables native power management, and that's exactly what SSDT-X299X-DESIGNARE10G-PR00 is doing.

However, when I looked at Dortania's guide on power management, they showed a way to confirm if PM was working was to look at IoReg and check if X86PlatformPlugin was connected to the CPU. And for me, it was not.

But then on the other hand, I see my cores scaling in frequency from 1200Mhz up to 4600Mhz, and I see my package power going up and down, and I hear my fans spinning faster and slower. So if I don't have PM working, I'm not sure what would actually change if I did?

What actually is the definition of 'power management working'? Can you describe what you saw was missing that made you want to enable PLUG-DRTANIA, and what you noticed to be different afterwards?

Of course you're now on iMacPro 1,1 so this could be affecting it. As I understand it, dolgarrenan has set configuration to rename components (eg CPUs) to match a real Mac Pro. So if you're not emulating a Mac Pro, you may need different config. Though maybe CPUs are named the same on both systems, as they do both use the Intel Xeon W.

Could you share your EFI sometime so I can compare and contrast what you're doing?

The three items that now remain on my list are:
- Get sleep working (currently not working at all)

Yeah I have no sleep either. I can't recall anyone who has/had sleep working in this thread, except dolgarrenan himself. The two things I know he had different to most of us is that he flashed his Thunderbolt firmware, and he was using n-d-k's fork of OpenCore. Or in fact he was using Clover in the earliest pages.

I don't have sleep working even with TB3 disabled so it seems unlikely it's that, though I haven't gone as far as also removing all the TB3-related config (there's an SSDT, plus some config.plist entries related to TB3).

I've done USB port mapping which apparently can help with sleep, but it's not made any difference.

- Get ethernet working

Ethernet is working fine for me with SmallTree in /L/E. Two ports, stable. Not sure why this is different for you, unless it's iMacPro 1,1. Or because you're now on Big Sur?

Are you only testing Big Sur from now on, or do you have two installs?

In better news though, I got the Bluetooth portion of the integrated AX200 card to work and now have my Magic Keyboard and Trackpad connected wirelessly, which works well.

Yeah Bluetooth is working fine for me. No WiFi and I've not yet made any efforts to get it, eg iwltm. I might at some point but I've never used WiFi on my desktops as I have cabled 1G and 10GBe. So I'll only pursue WiFi to increase closeness to a real Mac Pro, in case any apps look for / expect a working WiFi adapter.

Actually that might be another thing that was different for dolgarrenan - he had working WiFi. I suppose it's possible that the system tries to interface with WiFi during sleep, and if it can't find a WiFi adapter it breaks sleep?

Then again @Walterfilms has working fenvi WiFi and he didn't have sleep working either.
 
Last edited:
Joined
Mar 28, 2019
Messages
84
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
What actually is the definition of 'power management working'? Can you describe what you saw was missing that made you want to enable PLUG-DRTANIA, and what you noticed to be different afterwards?
It was largely the section you linked. If I see something that is misconfigured, I fix it if I can, and this was one of the things that was easily fixable. I haven't noticed much in terms of change, but I'm a firm believer in doing it properly when possible, so might as well. Initially I thought this may have been related to sleep, but so far no progress on that front.
I can't recall anyone who has/had sleep working in this thread, except dolgarrenan himself.
This person does seem to have managed, however they were on an X299X Aorus Master, but I'm hoping there's some stuff that translates to the Designare. Will investigate his EFI to compare and contrast.
Ethernet is working fine for me with SmallTree in /L/E. Two ports, stable. Not sure why this is different for you, unless it's iMacPro 1,1. Or because you're now on Big Sur?

Are you only testing Big Sur from now on, or do you have two installs?
It was unstable on Catalina already, which is one of the reasons I attempted the Big Sur install. The install became very unstable and it was very difficult to get it back to normal, even after uninstalling the kext. I don't like having /L/E kexts because that can shoot you in the foot with a 12 gauge shotgun real quick, so I'd rather avoid a solution such as this.
I will likely be going forward with Big Sur for now as everything else seems to work the same on it, as far as I was able to test up 'til now.

My plan for now is to do the following:
- Compare my EFI with the one guy who claimed to have sleep working
- Tweak my EFI according to the Dortania guide to see if I missed anything obvious
- Create an EFI from scratch using the Dortania guide, in case all else fails. Maybe that'll reveal an oversight or a hint as to what I'm currently missing
- Trawl OpenCore's GitHub for hints regarding sleep and bios resets

Will share my EFI over the weekend once I do a bit more testing.
 
Joined
Oct 28, 2017
Messages
50
Motherboard
Gigabyte x299x Designare 10G
CPU
i9 10940x
Graphics
Radeon VII
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
1)
dolgarrenan's WIFI is a Dell model, I know that because I purchased the same model and replaced with the one that comes in the motherboard.

BCM94350ZAE DW1820A 802.11AC 867Mbps M.2

2)
The ethernet from first page:
Section 3.2: No need to use multiple kext to load the two Intel X550T 10GbE ports! Please find in attachments a modified version of the latest SmallTreeIntel8259x.kext to work with our cards :). Remove all other kexts from C/K/O and install the modified version under /L/E using KextBeast or Hackintool, then rebuild kext cache with terminal command, KextUtility or Hackintool.

Slightly better results with SmallTree kext in correct location.

3)
There is some people that has Sleep working in this thread, I think that is related to the graphics card or USB devices. I have been with macOS Big Sur all the betas in a Macbook Pro 16" and I can verify that Sleep has been a nightmare, most of the betas didn't work, only the external monitor goes to sleep (my issue) but not the computer, the usb keyboard, tablet or de usb-c device. As now, with the macOS Big Sur Release Candidate, Version: 11.0.1 is working perfectly.
 
Joined
Mar 6, 2013
Messages
231
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
Vega 64
Mobile Phone
  1. Android
It was largely the section you linked. If I see something that is misconfigured, I fix it if I can, and this was one of the things that was easily fixable. I haven't noticed much in terms of change, but I'm a firm believer in doing it properly when possible, so might as well. Initially I thought this may have been related to sleep, but so far no progress on that front.
OK I've figured this out now. In order to get PM working as per the definition on the Dortania guide - ie that X86PlatformPlugin shows in IORegistryExplorer - I needed to (relative to dolgarrenan's config and the EFI I posted the other day):

1. Remove all of the CPU renames that dolgarrenan added, renaming CPxx to PRxx

2. Enable SSDT-PLUG_DRTANIA

I also disabled SSDT-X299X-DESIGNARE10G-PR00, which is dolgarrenan's SSDT intended to enable PM. Clearly it wasn't working for some reason.

Like you I've not actually noticed any major difference. My Cinebench scores are not improved, in fact first benchmark was down 150 points. I need to test that some more.

It's possible there's a bit more variance in the per-core frequencies; when I last checked this, using HWMonitorSMC2, I noticed that it seemed like some cores were 'sticking' to certain frequencies for a while. Like Core 27 or whatever might show it was at 4.2Ghz for many seconds, even a minute. Now they seem to all be bouncing around a lot more.

Anyway, according to the Dortania guide it's now configured right, so as you say that is likely a good thing.

I'm still trying to figure out exactly why dolgarrenan renamed the CPUs and various other ACPI components in config.plist using ACPI patches. I'm unclear whether he thought it was necessary, or if it was just to get the system more closely resembling a Mac Pro, or what.

I do know that having all those ACPI patches could be a major hurdle to dual-booting Windows using OpenCore, as OpenCore will apply them to all operating systems equally. That's why dolgarrenan used n-d-k's fork which has changes that make it only apply ACPI to macOS. But that fork is still on version 0.5.8 and hasn't been updated in months, so I have no interest in using it.

like having /L/E kexts because that can shoot you in the foot with a 12 gauge shotgun real quick, so I'd rather avoid a solution such as this.
I agree completely with regard to Hackintosh tools like Lilu, WEG, etc. But 'real' drivers I like to put where they're designed to go. If the hardware isn't found they won't load.

Have you tested installing them in /L/E and then updating kextcache? Because as I say ethernet is solid for me. And it sounds like our only differences are kext location and SMBIOS.

Interesting re sleep on the Aorus. That MB doesn't have TB3. Another possible scrap of evidence indicating thunderbolt could be the root of this issue.

I might give the TB3 flashing a go this weekend, which would put me on the same setup as dolgerrenan.
 
Joined
Mar 6, 2013
Messages
231
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
Vega 64
Mobile Phone
  1. Android
I've done some investigation on sleep, and I just got my first ever sleep!

It was still a failure, because on attempting to wake it rebooted instead. But it points to the general area of the problems: SSDTs.

Firstly I checked the logs after a failed sleep and found messages indicating the failure to sleep could be CPU related, or related to PCI devices; I suspected the latter more:

Code:
kernel: PMRD: sleep reason Software Sleep
kernel: PMRD: SleepWake UUID queued: 24191C6E-B4AB-4BF5-86A3-5769DFDB43BC
kernel: PMRD: tellChangeDown::userActivityAtSleep 0
kernel: PMRD: prevent idle sleep list: IODisplayWrangler- (0)
kernel: PMRD: tellChangeDown::userActivityAtSleep 0
kernel: PMRD: System sleep prevented by kPMCPUAssertion
kernel: (AppleACPIPlatform) System sleep prevented by SBUS
kernel: (AppleACPIPlatform) System sleep prevented by SBUS
kernel: PMRD: System sleep prevented by kPMPCIUnsupported
kernel: PMRD: display wrangler tickled1 1 lastSleepReason 103
kernel: PMRD: display wrangler tickled1 2 lastSleepReason 103
kernel: PMRD: prevent idle sleep list: IODisplayWrangler+ (1)
kernel: PMRD: idle sleep timer disabled
kernel: PMRD: display wrangler tickled1 3 lastSleepReason 103

The two lines that I think are most relevant are:
Code:
kernel: PMRD: System sleep prevented by kPMCPUAssertion
kernel: PMRD: System sleep prevented by kPMPCIUnsupported

And the latter feels more important to me, because it's last, and because we now think we have the CPU set up correctly.

Then I went through the dolgarrenan SSDTs and disabled a bunch of them. First I tried disabling the USB and Thunderbolt related SSDTs, but that didn't help. Then I disabled several more, including SBUS and X550T.

And then I got my first ever sleep on this system. Sadly my attempt to wake it up rebooted instead. But at least this is moving in the right direction.

I think it's time for me to go through these SSDTs - and the ACPI rename patches - one by one and try to understand exactly what they're intended to do, and whether they're doing that properly.

I have a feeling some of them are just cosmetic, eg ensuring that About This Mac shows the right entries under PCI.

Anyway, this is some progress at least. Next I'll try to narrow it down to which exact SSDTs are blocking sleep. And of course see if I can get it to actually wake up.
 
Joined
Mar 6, 2013
Messages
231
Motherboard
Gigabyte X299X Designare 10G
CPU
i9-10980XE
Graphics
Vega 64
Mobile Phone
  1. Android
OK, so as predicted by this log line (that I forgot to highlight in previous post):
Code:
kernel: (AppleACPIPlatform) System sleep prevented by SBUS

It is the SBUS SSDT that is preventing sleep. Disabling this SSDT alone will allow sleep.

It then kernel panics when it attempts to wake. The kernel panic is in AppleACPIPlatform. Once again pointing to ACPI as the cause of this (and maybe other) problems.

At the end of the post is the full text of the kernel panic, which might be useful for Google research.

Anyway I think this is definitely good news. We have some idea where to look and experiment.

Code:
panic(cpu 0 caller 0xffffff800d4469aa): Kernel trap at 0xffffff800d462d27, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0xffffff8e0f8f1000, CR3: 0x0000000012cbc000, CR4: 0x00000000003626e0
RAX: 0x000000007e008003, RBX: 0xffffff800dc5dc40, RCX: 0x00000000000000e2, RDX: 0x0000000000000000
RSP: 0xffffff8e254abbb0, RBP: 0xffffff8e254abbe0, RSI: 0x0000000000000003, RDI: 0xffffff800dc5dbe0
R8:  0x0000000000000020, R9:  0xffffff80116e506c, R10: 0x0000000000000003, R11: 0x0000000000000000
R12: 0xffffff800db2f33d, R13: 0x0000000000000001, R14: 0x0000000000000000, R15: 0xffffff800db2f323
RFL: 0x0000000000010046, RIP: 0xffffff800d462d27, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0xffffff8e0f8f1000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 0

Backtrace (CPU 0), Frame : Return Address
0xffffff800d151220 : 0xffffff800d31a65d mach_kernel : _handle_debugger_trap + 0x49d
0xffffff800d151270 : 0xffffff800d454a75 mach_kernel : _kdp_i386_trap + 0x155
0xffffff800d1512b0 : 0xffffff800d4465fe mach_kernel : _kernel_trap + 0x4ee
0xffffff800d151300 : 0xffffff800d2c0a40 mach_kernel : _return_from_trap + 0xe0
0xffffff800d151320 : 0xffffff800d319d27 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff800d151420 : 0xffffff800d31a117 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff800d151470 : 0xffffff800dac1a6c mach_kernel : _panic + 0x54
0xffffff800d1514e0 : 0xffffff800d4469aa mach_kernel : _sync_iss_to_iks + 0x2aa
0xffffff800d151660 : 0xffffff800d4466a8 mach_kernel : _kernel_trap + 0x598
0xffffff800d1516b0 : 0xffffff800d2c0a40 mach_kernel : _return_from_trap + 0xe0
0xffffff800d1516d0 : 0xffffff800d462d27 mach_kernel : _xcpm_perf_bias_set + 0x1c7
0xffffff8e254abbe0 : 0xffffff800d462fbb mach_kernel : _xcpm_init + 0xab
0xffffff8e254abc00 : 0xffffff800d452f91 mach_kernel : _acpi_sleep_kernel + 0x441
0xffffff8e254abc70 : 0xffffff7f8e591c2a com.apple.driver.AppleACPIPlatform : __ZN23AppleACPIPlatformExpert13sleepPlatformEv + 0x204
0xffffff8e254abcc0 : 0xffffff7f8e595eab com.apple.driver.AppleACPIPlatform : __ZN12AppleACPICPU7haltCPUEv + 0x75
0xffffff8e254abce0 : 0xffffff800da4bb20 mach_kernel : __Z16IOCPUSleepKernelv + 0x290
0xffffff8e254abd40 : 0xffffff800da850d5 mach_kernel : __ZN14IOPMrootDomain15powerChangeDoneEm + 0xac5
0xffffff8e254abde0 : 0xffffff800da162a7 mach_kernel : __ZN9IOService8all_doneEv + 0x767
0xffffff8e254abe50 : 0xffffff800da1303c mach_kernel : __ZN9IOService23actionPMWorkQueueInvokeEP11IOPMRequestP13IOPMWorkQueue + 0x86c
0xffffff8e254abea0 : 0xffffff800da106d0 mach_kernel : __ZN13IOPMWorkQueue17checkRequestQueueEP11queue_entryPb + 0xa0
0xffffff8e254abef0 : 0xffffff800da10569 mach_kernel : __ZN13IOPMWorkQueue12checkForWorkEv + 0xc9
0xffffff8e254abf30 : 0xffffff800da2bdce mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x11e
0xffffff8e254abf70 : 0xffffff800da2b3c6 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x36
0xffffff8e254abfa0 : 0xffffff800d2c013e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.driver.AppleACPIPlatform(6.1)[0EF10B66-B44B-32BB-9CE3-5434F4D40FE1]com.apple.0xffffff7f8e586000-com.apple.driver.0xffffff7f8e620fff
            dependency: com.apple.iokit.IOACPIFamily(1.4)[2956198D-24F2-3790-A9B2-1EAB9434B906]com.apple.0xffffff7f8dd09000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[44472E6F-8DA0-3B46-ADEF-AFF76EC6C6DB]com.apple.0xffffff7f8dd12000
            dependency: com.apple.driver.AppleSMC(3.1.9)[D2F0B610-83F8-3B84-B0BD-D9D0CC95A697]com.apple.0xffffff7f8dda9000

BSD process name corresponding to current thread: kernel_task
Boot args: -v keepsyms=1 darkwake=0 brcmfx-country=#a alcid=7 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19H2

Kernel version:
Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1/RELEASE_X86_64
Kernel UUID: 05D51A3D-3A87-3FF0-98C3-9CF3827A3EDD
Kernel slide:     0x000000000d000000
Kernel text base: 0xffffff800d200000
__HIB  text base: 0xffffff800d100000
System model name: MacPro7,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 98866706487
last loaded kext at 35700150014: com.apple.driver.AppleUpstreamUserClient    3.6.8 (addr 0xffffff7f94518000, size 28672)
loaded kexts:
com.disc-soft.DAEMONTools.VirtualSCSIBus    1.0.2
net.telestream.driver.TelestreamAudio    1.1.1
at.obdev.nke.LittleSnitch    5474
com.intel.driver.EnergyDriver    3.7.0
com.SmallTree.driver.SmallTreeIntel8259x    3.5.0
ru.joedm.SMCSuperIO    1.1.8
hu.interferenc.TSCAdjustReset    1.1
as.vit9696.SMCProcessor    1.1.8
as.vit9696.VirtualSMC    1.1.8
org.acidanthera.NVMeFix    1.0.4
meow.IOIIIO.MacProMemoryNotificationDisabler    1.0.0
as.vit9696.WhateverGreen    1.4.4
as.vit9696.Lilu    1.4.9
com.apple.driver.AppleUpstreamUserClient    3.6.8
com.apple.driver.AppleMCCSControl    1.14
com.apple.kext.AMDFramebuffer    3.1.0
com.apple.fileutil    20.036.15
com.apple.kext.AMDRadeonX5000    3.1.0
com.apple.kext.AMDRadeonServiceManager    3.1.0
com.apple.driver.AudioAUUC    1.70
com.apple.driver.AppleGraphicsDevicePolicy    5.2.6
com.apple.AGDCPluginDisplayMetrics    5.2.6
com.apple.filesystems.autofs    3.0
com.apple.driver.AppleHV    1
com.apple.iokit.IOUserEthernet    1.0.1
com.apple.iokit.IOBluetoothSerialManager    7.0.6f7
com.apple.driver.pmtelemetry    1
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AGPM    111.4.4
com.apple.driver.ApplePlatformEnabler    2.7.0d0
com.apple.driver.X86PlatformShim    1.0.0
com.apple.kext.AMD10000Controller    3.1.0
com.apple.driver.ACPI_SMC_PlatformPlugin    1.0.0
com.apple.driver.AppleGFXHDA    100.1.429
com.apple.driver.AppleSMCLMU    212
com.apple.driver.AppleFIVRDriver    4.1.0
com.apple.driver.AppleIntelMCEReporter    115
com.apple.driver.AppleIntelPCHPMC    2.0.1
com.apple.driver.AppleIntelSlowAdaptiveClocking    4.0.0
com.apple.private.KextAudit    1.0
com.apple.driver.AppleFileSystemDriver    3.0.1
com.apple.filesystems.hfs.kext    522.100.5
com.apple.BootCache    40
com.apple.filesystems.apfs    1412.141.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0
com.apple.driver.AppleVirtIO    1.0
com.apple.driver.AirPort.Brcm4360    1400.1.1
com.apple.driver.AppleAHCIPort    341.140.1
com.apple.driver.AppleRTC    2.0
com.apple.driver.AppleHPET    1.8
com.apple.driver.AppleACPIButtons    6.1
com.apple.driver.AppleSMBIOS    2.1
com.apple.driver.AppleAPIC    1.7
com.apple.security.AppleImage4    1
com.apple.nke.applicationfirewall    303
com.apple.security.TMSafetyNet    8
com.apple.AppleSystemPolicy    2.0.0
com.apple.iokit.EndpointSecurity    1
com.apple.driver.AppleSMBusController    1.0.18d1
com.apple.iokit.IOSMBusFamily    1.1
com.apple.iokit.IOAVBFamily    850.1
com.apple.plugin.IOgPTPPlugin    840.3
com.apple.iokit.IOEthernetAVBController    1.1.0
com.apple.kext.AMDRadeonX5000HWLibs    1.0
com.apple.iokit.IOAcceleratorFamily2    438.7.3
com.apple.kext.AMDRadeonX5000HWServices    3.1.0
com.apple.driver.AppleGraphicsControl    5.2.6
com.apple.kext.triggers    1.0
com.apple.AppleGPUWrangler    5.2.6
com.apple.driver.IOPlatformPluginLegacy    1.0.0
com.apple.driver.AppleHDAController    283.15
com.apple.iokit.IOHDAFamily    283.15
com.apple.iokit.IONDRVSupport    576.1
com.apple.driver.AppleSMBusPCI    1.0.14d1
com.apple.kext.AMDSupport    3.1.0
com.apple.AppleGraphicsDeviceControl    5.2.6
com.apple.iokit.IOGraphicsFamily    576.1
com.apple.iokit.IOSlowAdaptiveClockingFamily    1.0.0
com.apple.driver.X86PlatformPlugin    1.0.0
com.apple.driver.IOPlatformPluginFamily    6.0.0d8
com.apple.driver.usb.AppleUSBHub    1.2
com.apple.driver.usb.IOUSBHostHIDDevice    1.2
com.apple.driver.usb.cdc    5.0.0
com.apple.driver.usb.networking    5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice    1.2
com.apple.driver.AppleUSBMergeNub    900.4.2
com.apple.iokit.IOSurface    269.11
com.apple.driver.AppleXsanScheme    3
com.apple.filesystems.hfs.encodings.kext    1
com.apple.iokit.IOAudioFamily    300.2
com.apple.vecLib.kext    1.2.0
com.apple.iokit.IOSerialFamily    11
com.apple.driver.AppleThunderboltNHI    5.8.6
com.apple.iokit.IOThunderboltFamily    7.6.1
com.apple.iokit.IONVMeFamily    2.1.0
com.apple.iokit.IO80211Family    1200.12.2b1
com.apple.iokit.IOSkywalkFamily    1
com.apple.driver.mDNSOffloadUserClient    1.0.1b8
com.apple.driver.corecapture    1.0.4
com.apple.iokit.IOAHCIFamily    290.0.1
com.apple.driver.usb.AppleUSBXHCIPCI    1.2
com.apple.driver.usb.AppleUSBXHCI    1.2
com.apple.driver.usb.AppleUSBHostPacketFilter    1.0
com.apple.iokit.IOUSBFamily    900.4.2
com.apple.driver.AppleEFINVRAM    2.1
com.apple.driver.AppleEFIRuntime    2.1
com.apple.driver.AppleSMCRTC    1.0
com.apple.iokit.IOHIDFamily    2.0.0
com.apple.security.quarantine    4
com.apple.security.sandbox    300.0
com.apple.kext.AppleMatch    1.0.0d1
com.apple.driver.AppleKeyStore    2
com.apple.driver.AppleUSBTDM    489.120.1
com.apple.iokit.IOSCSIBlockCommandsDevice    422.120.3
com.apple.driver.AppleCredentialManager    1.0
com.apple.driver.AppleFDEKeyStore    28.30
com.apple.driver.AppleEffaceableStorage    1.0
com.apple.driver.AppleMobileFileIntegrity    1.0.5
com.apple.kext.CoreTrust    1
com.apple.iokit.CoreAnalyticsFamily    1
com.apple.iokit.IOTimeSyncFamily    840.3
com.apple.iokit.IONetworkingFamily    3.4
com.apple.driver.DiskImages    493.0.0
com.apple.iokit.IOBluetoothFamily    7.0.6f7
com.apple.iokit.IOBluetoothPacketLogger    7.0.6f7
com.apple.driver.AppleSSE    1.0
com.apple.driver.KernelRelayHost    1
com.apple.driver.AppleSEPManager    1.0.1
com.apple.driver.IOSlaveProcessor    1
com.apple.iokit.IOUSBMassStorageDriver    157.140.1
com.apple.iokit.IOSCSIArchitectureModelFamily    422.120.3
com.apple.iokit.IOStorageFamily    2.1
com.apple.iokit.IOUSBHostFamily    1.2
com.apple.driver.usb.AppleUSBCommon    1.0
com.apple.driver.AppleUSBHostMergeProperties    1.2
com.apple.driver.AppleBusPowerController    1.0
com.apple.iokit.IOReportFamily    47
com.apple.driver.AppleACPIPlatform    6.1
com.apple.driver.AppleSMC    3.1.9
com.apple.driver.watchdog    1
com.apple.iokit.IOPCIFamily    2.9
com.apple.iokit.IOACPIFamily    1.4
com.apple.kec.pthread    1
com.apple.kec.corecrypto    1.0
com.apple.kec.Libm    1
 
Joined
Apr 17, 2020
Messages
26
Motherboard
Gigabyte Designare x299x
CPU
10980xe
Graphics
Radeon VII
I posted about that on Monday, here and here. Short answer is that I don't get that BIOS failure message and I am able to boot both macOS and Windows successfully. I don't yet have a working OpenCore-based dual-boot, which I believe is down to the fact that the SSDTs need to be edited to only run for macOS, as OpenCore will inject SSDTs regardless of OS (unlike Clover).

I looked at your EFI partition you posted a while back when I was researching my own. I noticed you seemed to be missing a lot of the SSDTs from the OP, and in some cases using generic versions instead (eg using SSDT-PLUG-DRTNIA instead of dolgarrenan's SSDT-X299X-DESIGNARE10G-PR00 and SSDT-AWAC instead of his SSDT-X299X-DESIGNARE10G-RTC0).


My recommendation would be to try the OpenCore 0.6.3 EFI I posted yesterday and see how you get on with that as a base. Copy your PlatformInfo details into it and then try booting with it to see if it makes those boot failures go away. Also, like byteminer said, don't use OpenConfigurator.

I'd definitely try clearing your NVRAM before first booting with my (or anyone else's) EFI. If it still fails, it can't hurt to do a CMOS reset and re-configure the BIOS, in case anything has got setup wrong there. I can post a BIOS config file if that helps.
@TheBloke thank you for your detailed response and linking me to those posts. it's good to know my error message has been seen before although it is no longer being experienced. I was taking the "if it aint broke" approach so I haven't updated to the newest version of opencore yet, but will be giving it a shot.

Please note that I am on mojave as i use my hackintosh for music production and catalina is finicky. Also please note that i did not do any of the disassembly of my motherboard for thunderbolt as indicated in the first post. I do not know if this prevents things from working the same way it does for you guys, but when I tested a few of the efi's on this thread, my computer would get stuck on the apple logo and never load the progress bar. It did not do this with the generic SSDT's, so that's why I was using those instead. i'd love to get it working like most here though. I have yet to test yours on opencore 0.6.3, and will do so tonight.

Could you please save and upload your bios config settings file as well for me as well (preferably without overclocks if possible)? It would be greatly appreciated.

@byteminer thanks. I'll stick to my fenvi chip for wifi then :)
 
Last edited:
Top