Contribute
Register

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

If there are multiple EFI partitions, the system may be booting from the wrong one. Good to check BIOS —> BOOT and/or press F12 at boot splash screen.
Hi Casey, yes that's definitely the case, I was just experimenting along those lines as you replied.

I'm a bit bamboozled however (as usual). My boot options from BIOS show a couple of UEFI partitions, my Windows Boot Manager and one called 'OpenCore'. I was under the impression that we just used the one called 'OpenCore' now as of a few versions ago but booting with my Mac HD UEFI seems to have loaded up on 0.6.9 with no issues.

What am I missing here... what's the difference between booting from UEFI and booting 'OpenCore'?

Thanks again :)
 
Hi Casey, yes that's definitely the case, I was just experimenting along those lines as you replied.

I'm a bit bamboozled however (as usual). My boot options from BIOS show a couple of UEFI partitions, my Windows Boot Manager and one called 'OpenCore'. I was under the impression that we just used the one called 'OpenCore' now as of a few versions ago but booting with my Mac HD UEFI seems to have loaded up on 0.6.9 with no issues.

What am I missing here... what's the difference between booting from UEFI and booting 'OpenCore'?

Thanks again :)
So booting using the UEFI one once, and now booting using the OpenCore one seems to have fixed the issue.
 
Somewhere along the road from Clover to OC my Z170X-UD5 TH lost the Thunderbolt.. it works in Windows, shows up in the BIOS but not in macOS. Does anyone with this MB have a ACPI SSDt to enable TB? Don't care about bus, etc., just want to be able to use it from cold boot for disks and audio devices. TIA
 
Ah, the ever trusty NVM 33 from Designare Z390!
I'm using the AORUS Extreme version of that firmware and getting great results. When I tried the Designare version (originally) I had several issues with 1 port not working. Is there a difference? Maybe my config is more stable now with OC and that is the difference, not sure. I was making a lot of changes back then so it's really hard to know for sure.
 
@CaseySJ , I only have Titan Ridge 1.0 on Aorus Master. The Designware don't have this card, and I'm using the Thunderbolt on board.

Just flashed the stock firmware of Titan Ridge to NVM 50. Will this be any different?
Please try the attached OC.zip for the Z390 AORUS Master.
  • Copy serial numbers into PlatformInfo before use.
Changes made:
  • Replaced OpenHfsPlus.efi with HfsPlus.efi. At this time we should not use OpenHfsPlus.efi.
  • Disabled SIP by setting it to FF0F0000. You may change this back to 00000000 if the system is stable.
Question:
  • Why does OC folder contain the file BOOTx64.efi? This file should be in EFI/BOOT folder.
 

Attachments

  • OC.zip
    2.6 MB · Views: 76
Hi Casey, need you help sir. I tried to update to 0.6.9 OpenCore (used your broadcom EFI folder) but boot is stuck at Apple logo. However OpenCore 0.6.8 can boot without any issues. I have attached both my EFIs, can you please take a look and let me know what I did wrong? Your help would be much appreciated

Intel i9-9900K
Gigabyte Z390 Designare
XFX RX590
Fenvi T919 WiFi
ASUS XG-C100C 10G
 

Attachments

  • April EFI.zip
    4.2 MB · Views: 83
  • May EFI.zip
    4.2 MB · Views: 85
...
Re the 'csr-active-config' changes - in layman's terms what am I actually doing? Enabling/disable System Integrity Protection? Is running with 67000000 leaving me exposed in any way?
...
From the Apple open source page for Big Sur 11.2 (file csr.h), the bit flags for SIP are as follows:
C:
/* CSR configuration flags */
#define CSR_ALLOW_UNTRUSTED_KEXTS               (1 << 0)
#define CSR_ALLOW_UNRESTRICTED_FS               (1 << 1)
#define CSR_ALLOW_TASK_FOR_PID                  (1 << 2)
#define CSR_ALLOW_KERNEL_DEBUGGER               (1 << 3)
#define CSR_ALLOW_APPLE_INTERNAL                (1 << 4)
#define CSR_ALLOW_DESTRUCTIVE_DTRACE                    (1 << 5) /* name deprecated */
#define CSR_ALLOW_UNRESTRICTED_DTRACE                   (1 << 5)
#define CSR_ALLOW_UNRESTRICTED_NVRAM                    (1 << 6)
#define CSR_ALLOW_DEVICE_CONFIGURATION                  (1 << 7)
#define CSR_ALLOW_ANY_RECOVERY_OS                       (1 << 8)
#define CSR_ALLOW_UNAPPROVED_KEXTS                      (1 << 9)
#define CSR_ALLOW_EXECUTABLE_POLICY_OVERRIDE    (1 << 10)
#define CSR_ALLOW_UNAUTHENTICATED_ROOT                  (1 << 11)

The operations (1 << x) mean start with binary 1 and shift it to the left x times. Therefore, if we use a single 8-bit byte we get:
  • 1 << 0 = 0000 0001 (decimal 1, hex 0x01)
  • 1 << 1 = 0000 0010 (decimal 2, hex 0x02)
  • 1 << 2 = 0000 0100 (decimal 4, hex 0x04)
  • 1 << 3 = 0000 1000 (decimal 8, hex 0x08)
  • 1 << 4 = 0001 0000 (decimal 16, hex 0x10)
  • 1 << 5 = 0010 0000 (decimal 32, hex 0x20)
These are simply powers of 2, or 2 raised to the power x.

The command csrutil disable properly disables SIP. It does so by setting the following flags:
C:
/* Flags set by `csrutil disable`. */
#define CSR_DISABLE_FLAGS (CSR_ALLOW_UNTRUSTED_KEXTS | \
                       CSR_ALLOW_UNRESTRICTED_FS | \
                       CSR_ALLOW_TASK_FOR_PID | \
                       CSR_ALLOW_KERNEL_DEBUGGER | \
                       CSR_ALLOW_APPLE_INTERNAL | \
                       CSR_ALLOW_UNRESTRICTED_DTRACE | \
                       CSR_ALLOW_UNRESTRICTED_NVRAM)

This equates to binary 0000 0000 0111 1111 or hex 0x007F. In reverse byte order (needed for OpenCore) this is 7F00. But two additional flags are always enforced:
C:
#define CSR_ALWAYS_ENFORCED_FLAGS (CSR_ALLOW_DEVICE_CONFIGURATION | CSR_ALLOW_ANY_RECOVERY_OS)

If we add the bit flags for these, the SIP value becomes binary 0000 0001 1111 1111 or hex 0x01FF. In reverse byte order this is FF01.

But if we want to go beyond Apple's csrutil disable and disable everything, then we can specify binary 0000 1111 1111 1111 or hex 0x0FFF. In reverse byte order this is FF0F.

Now let's look at 67000000. We ignore the last 4 bytes and examine only 6700, which we know is in reverse byte order because we're getting this value from OpenCore config.plist. Switching the bytes we get 0x0067 or binary 0000 0000 0110 0111. We can decode this as follows:
C:
#define CSR_ALLOW_UNTRUSTED_KEXTS               (1 << 0)
#define CSR_ALLOW_UNRESTRICTED_FS               (1 << 1)
#define CSR_ALLOW_TASK_FOR_PID                  (1 << 2)
...
#define CSR_ALLOW_UNRESTRICTED_DTRACE                   (1 << 5)
#define CSR_ALLOW_UNRESTRICTED_NVRAM                    (1 << 6)
Happy now? :) Bottom line: Do not worry about it. We've been running with SIP completely disabled for years.
 
Last edited:
...shows up in the BIOS but not in macOS. Does anyone with this MB have a ACPI SSDt to enable TB?

...under macOS the TB bus is not visible on this board. Is your audio device working in macOS?
 
Hi Casey, need you help sir. I tried to update to 0.6.9 OpenCore (used your broadcom EFI folder) but boot is stuck at Apple logo. However OpenCore 0.6.8 can boot without any issues. I have attached both my EFIs, can you please take a look and let me know what I did wrong? Your help would be much appreciated

Intel i9-9900K
Gigabyte Z390 Designare
XFX RX590
Fenvi T919 WiFi
ASUS XG-C100C 10G
Everything looks fine in the May EFI folder. Please try this:
  • Boot using OpenCore 0.6.9 (May EFI)
  • At the OpenCanopy GUI press and release CMD-V to enable Verbose
  • Then boot macOS
  • When the boot process hangs grab a photo and then:
    • Remove EXIF location info from the photo
    • Resize it so that file is no larger than about 512KB to 768KB
    • Post the photo
 
Back
Top