Contribute
Register

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

My experience is that you can move the macOS to either M.2 slot. Just make sure when you install Windows, that you remove any other disks including SATA disks as Windows is known to overwrite the wrong EFI partitions. For the SATA disks, if you are using them, you can just disable the Drives in the BIOS without physically disconnecting them. Hope this helps.
@TinkerTenor @jb007

A subtle but noteworthy clarification: Although macOS NVMe can be installed in any M.2 slot, it should be moved to M2P if Windows is also installed in an NVMe SSD. If Windows is installed onto a SATA 2.5" SSD or onto a SATA M.2 SSD then it will operate over the SATA bus instead of PCIe bus, so it won't install its boot loader on the macOS NVMe SSD.
  • M.2 slots can accommodate either:
    • PCIe SSDs
    • SATA SSDs
  • SATA ports can only accommodate:
    • SATA SSDs
So if both M.2 slots contain PCIe SSDs (one notch on the pins) then they should be installed like this:
  • M2M slot --> Windows PCIe M.2 SSD
  • M2P slot --> macOS PCIe M.2 SSD
But if Windows will be installed on a SATA M.2 SSD (two notches on the pins) then the order does not matter:
  • Windows SATA M.2 SSD --> M2M or M2P
  • macOS PCIe SSD --> M2M or M2P
what-are-m2-drives.jpg.optimal.jpg
 
Last edited:
Hello guys! It looks now that my computer is stable and works properly and I am very happy about it, thanks to @CaseySJ! I still have emulated NVRAM running and I'm thinking to switch to the native one but honestly, I'm a little afraid to do this! There's something about modifying the firmware that makes me nervous :D
I'm curious if this procedure would affect Windows in any way since I have it dual boot.
I have both macOS and Windows with native NVRAM enabled. No issues!
 
Last edited:
.... Others reported similar issue where Thunderbolt UID would appear as all zero even when ThunderboltDROM was setup properly. For them the problem was an electrical break or disconnect between the chip's Pin 7 and the upper end of the adjacent SMD. Please have a look at this photo:

View attachment 465412

If you have a multimeter, try the following:
  • Turn on the PSU, but do not turn on the computer itself.
  • Put the Multimeter into DC Voltage mode and Auto Ranging if it has the feature.
  • Place the red probe on Pin 7 as indicated above.
  • Place the black probe on the item pointed to by the "this" arrow above.
  • What voltage do you measure?
Alright, I went out to get a multimeter and measured the DC voltages.

Between between pin 7 and the adjacent SMD you indicated, I measured 0.00V
  • Then keep red probe on Pin 7 and touch black probe to Pin 4 (GND).
  • What voltage do you measure?
  • Now, while keeping black probe on GND (Pin 4), check voltages on the other pins.
When connecting the black probe to pin 4 (GND), I measured the following voltages to the other pins:
  • 3.33V on pin 1, pin 2, pin 3 and pin 8.
  • 0.00V on pin 5, 6, and 7.
RT_08370-Winbond-small-voltages.jpg
 
Hi @CaseySJ - you've very diligently helped me with getting sleep working on this rig, however, when you have a chance, do you mind explaining what "DarkWake from Normal Sleep [CDN]" means?

I see this pop up some times on my logs, but do you also mind telling me what I should search for in the logs to differentiate a DarkWake from a Normal wake? My understanding is DarkWake is for the Mac to turn on and do things like housekeeping, notifications, check mail etc? Thanks.
 
@CaseySJ

figured I would update as to not avoid confusion for anyone else following.

1)the initial problem of just the Apple boot logo had something to do with me messing up the Bluetooth files as part of the intel setup.
2) secondary error (I was getting after restoring from backup) that I posted was in fact the CSM being relocked.(Somehow between the first error and the second, the CSM relocked)
3) the K1 keyboard does in fact Bluetooth to my BCM fenvi Bluetooth module... I just had to set the keyboard to windows/android for the hackintosh to find it - very strange but it worked
4) after reverting back to backup and then reusing the NDK EFI, I was able to make the proper changes to fix my boot & also use the true 1 key wake up (thank you to the creator for this!!)

:)
 
Alright, I went out to get a multimeter and measured the DC voltages.

Between between pin 7 and the adjacent SMD you indicated, I measured 0.00V

When connecting the black probe to pin 4 (GND), I measured the following voltages to the other pins:
  • 3.33V on pin 1, pin 2, pin 3 and pin 8.
  • 0.00V on pin 5, 6, and 7.
View attachment 465626
That looks okay since power is off (only PSU is on). If your Multimeter has a Continuity check mode, please touch Pin 7 and SMD together with PSU off. Continuity mode will tell you if the two endpoints are electrically connected.

Screen Shot 2020-04-28 at 7.02.02 AM.png
 
Hi @CaseySJ I'm not sure if you want to add this file to a post of yours or not, but let me share it anyway.

This SSDT is specifically for the Fractal Design Define R6 case including the front USB-C header, in combination with the usage of the internal Bluetooth (on the Z390 Designare MoBo) as per the bt kext which is in development on the Github page.
 

Attachments

  • SSDT-UIAC-DESIGNARE-Z390-FD-DEFINE-R6-USB2-ON-TB-V4(Internal bluetooth).aml
    883 bytes · Views: 71
Hi @CaseySJ - you've very diligently helped me with getting sleep working on this rig, however, when you have a chance, do you mind explaining what "DarkWake from Normal Sleep [CDN]" means?

I see this pop up some times on my logs, but do you also mind telling me what I should search for in the logs to differentiate a DarkWake from a Normal wake? My understanding is DarkWake is for the Mac to turn on and do things like housekeeping, notifications, check mail etc? Thanks.
Correct -- DarkWake is when the computer wakes up, but keeps the monitor turned off. Hence "dark" wake. This mode is used to perform background tasks, process scheduled events and notifications, etc. The important thing to check is whether monitor is indeed off during a DarkWake event.

DarkWakes are both normal and desirable.
 
@CaseySJ

figured I would update as to not avoid confusion for anyone else following.

1)the initial problem of just the Apple boot logo had something to do with me messing up the Bluetooth files as part of the intel setup.
2) secondary error (I was getting after restoring from backup) that I posted was in fact the CSM being relocked.(Somehow between the first error and the second, the CSM relocked)
3) the K1 keyboard does in fact Bluetooth to my BCM fenvi Bluetooth module... I just had to set the keyboard to windows/android for the hackintosh to find it - very strange but it worked
4) after reverting back to backup and then reusing the NDK EFI, I was able to make the proper changes to fix my boot & also use the true 1 key wake up (thank you to the creator for this!!)

:)
Just to correct the typo: You meant CFG was locked (not CSM). CFG-LOCK is governed by MSR 0xE2.
 
Back
Top