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

[CaseySJ]

Right now its plugged into the HS11 hub, I don't want to unplug it because I use it in windows. Do I just disable it for now so computer can sleep? If so, how do i create the SSDT to do this, for just this device not the entire HS11 hub, cause other devices are plugged in to it. In IORegistryExplorer I have a locationID: 0x14840000. Can I just disable this somehow?

Which USB SSDT are you using? It will be in CLOVER/ACPI/patched folder with a name that starts with SSDT-UIAC-...

Generally we just have to set HS11 to Type 255 (0xFF). Based on the SSDT you're using, I can check whether or not this has been done.

 

[CaseySJ]

Hi guys !

My install process stop at Phase 2.
No evolution of progress bar after 30 mins waiting.

My conf :

- Gigabyte Designare Z390
- MSI Radeon RX 580
- 16G (2x8) Ballistix sport LT DDR4 3000
- I7-9700 3.6
- Samsung SSD OCZ Vertex 2
- Old usb 2.0 key

I bought a Samsung 970 EVO Plus NVMe m.2 but the install process stop with a kernel panic before Phase 2 and now i try to use my old Samsung sata ssd.

Any ideas to help me ?

Thanks a lot.

Hello @milouse,

Please note that the Samsung 970 EVO Plus must be updated to the latest firmware before it will work with macOS. To update the firmware, you must install this drive on a Windows system and use Samsung's "Magician" software.

But the OCZ Vertex 2 SSD should be okay. Please try the attached config.plist as follows:

• Insert your USB install disk on the Mac.
• Mount the EFI partition using EFI Mounter v3 or Clover Configurator or Hackintool.
• Rename the attached file to config.plist and copy it the EFI/CLOVER folder.

 

[CaseySJ]

Greetings from Spain. Thanks a lot for your efforts.

I am trying to install High Sierra on this mobo (I'm stuck with a nVidia 9800Ti), but no success. If I boot from Clover on pendrive, it seems to work, but nVidia WebDrivers not load (High Sierra stays in MacOS standar driver, not saving the "use nVidia driver" option).

I I boot from MB SSD, I obtain a forbidden sign at boot. Followed estrictely your guide (in the possible).

Any clue?

Thanks

Hello @Manu1001,

• Have you already finished installing High Sierra, but now you are trying to enable the Nvidia graphics driver?
• Or are you having a problem trying to install High Sierra?

 

[CaseySJ]

Hi I got this:

There is no USB device attached to HS12, which is good because it means that port will be used for external USB devices. Therefore the USB SSDT in my previous reply should be sufficient.

Is your system is still waking suddenly from sleep?

 

[wickett]

There is no USB device attached to HS12, which is good because it means that port will be used for external USB devices. Therefore the USB SSDT in my previous reply should be sufficient.

Is your system is still waking suddenly from sleep?

Ok thanks. Yes it is still waking from sleep. Also the no video at startup is happening

 

[CaseySJ]

Ok thanks. Yes it is still waking from sleep. Also the no video at startup is happening

Sleep Issue:

• Have you isolated the device that prevents sleep through the process of elimination?
• After attempting another sleep operation, type this command in Terminalwhen the system wakes right up: pmset -g log | tail -50 > ~/Documents/sleep_problem.txt
  • This will create a file called sleep_problem.txt in your Documents folder.
  • Upload this file.

No Video at Startup:

• Does this happen even after correcting the "PCIRoot" typo to "PciRoot" and setting platform ID to 0x3E980003 in reverse byte order?
• If so, please upload your config.plist (remove serial numbers from SMBIOS).

 

[Manu1001]

Hello @Manu1001,

• Have you already finished installing High Sierra, but now you are trying to enable the Nvidia graphics driver?
• Or are you having a problem trying to install High Sierra?

Hi, @CaseySJ...

Yes, I've finished the basic installation, and it boots from install pendrive (choosing the High Sierra partition on the SSD, or course). But when I choose nVidia web drivers in pref panel, it request a reboot, but... remains in MacOS driver (slooooowwwwww and low resolution).

If I try to boot from SSD Clover (modified plist.ini and post-installation files copied), does not boot and shows a forbidden sign.

I'm trying to make another configuration copying the CLOVER folder from pendrive to SSD and restarting the process... But, ¿there is any incompatibility with High Sierra in any place? Thanks in advance.

 

[CaseySJ]

Hi, @CaseySJ...

Yes, I've finished the basic installation, and it boots from install pendrive (choosing the High Sierra partition on the SSD, or course). But when I choose nVidia web drivers in pref panel, it request a reboot, but... remains in MacOS driver (slooooowwwwww and low resolution).

If I try to boot from SSD Clover (modified plist.ini and post-installation files copied), does not boot and shows a forbidden sign.

I'm trying to make another configuration copying the CLOVER folder from pendrive to SSD and restarting the process... But, ¿there is any incompatibility with High Sierra in any place? Thanks in advance.

The instructions in this build guide may not apply 100% to High Sierra. Some modifications may be needed. If you like, you can compress and upload the CLOVER folder from EFI partition of your High Sierra SSD (remove serial numbers from SMBIOS section of config.plist).

 

[cubed3d]

We can safely ignore "No drivers are loaded" from the Thunderbolt section of System Information! It should say the same even if you boot from the SATA drive.

Let's see if I have this right:

• You cloned a SATA drive containing High Sierra to an NVMe M.2 drive using Carbon Copy Cloner.
• Both drives contain High Sierra, so the purpose of this is probably to gain the extra speed that comes with NVMe.

Therefore:

• Before cloning the SATA drive, did you use Disk Utility to format the NVMe SSD?
  • If so, do you remember whether you selected the parent name of the NVMe SSD and chose "GUID Partition Table" as the formatting Scheme?
  • It is necessary to format the NVMe with the GUID Partition Table scheme. This will create both the HFS+ (or APFS) partition and the crucial EFI partition.
• After running CCC,it is necessary to manually copy the EFI folder from the EFI partition of the SATA drive to the EFI partition of the NVMe drive.
  • The EFIClone-v2 script does this for us, but it's pretty easy to do it manually.
  • Just mount EFI partitions of both drives.
  • Use Finder to drag-and-drop the EFI folder from one to the other.

Yea I did everything except the EFIClone-v2 script. I just copied the EFI data over manually. Regarding the Thunderbolt section, I feel like it used to show me some information regarding the interface I had attached but maybe not. I have formatted my SATA drive that I had so I can't boot back into it to check unfortunately. I just find it very strange that it would behave like this unless it is influenced by the fact that its now using different system resources than the SATA drive was but even so, with the NVMe connected and the SATA (before I formatted it) I was able to get the sound working when I booted into the SATA drive. I didn't realize it was a problem with the NVMe until after I had formatted the SATA thinking everything was good.

 

[CaseySJ]

Yea I did everything except the EFIClone-v2 script. I just copied the EFI data over manually. Regarding the Thunderbolt section, I feel like it used to show me some information regarding the interface I had attached but maybe not. I have formatted my SATA drive that I had so I can't boot back into it to check unfortunately. I just find it very strange that it would behave like this unless it is influenced by the fact that its now using different system resources than the SATA drive was but even so, with the NVMe connected and the SATA (before I formatted it) I was able to get the sound working when I booted into the SATA drive. I didn't realize it was a problem with the NVMe until after I had formatted the SATA thinking everything was good.

An identical ESP (EFI System Partition) on SATA SSD and on NVMe SSD should behave identically. If you like I can audit your configuration if you can provide the following:

• Compressed CLOVER folder from EFI partition of the NVMe SSD.
• Screenshot of /Library/Extensions folder.