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

[Tea-Bone]

Any guesses on an issue I've been having on and off for ages, with uptime ranging from hours to weeks my USB will suddenly die. I'll be working, and my Magic Mouse will freeze and my keyboard will be non-responsive and after a minute or so it will scold me about not ejecting my backup drive before removing it. (or sometimes I'll return to my desk and find it this way). Very frustrating, fortunately I have my MacBook running Synergy so I can usually clean up and reboot cleanly (or ssh in and sudo shutdown).

Build is pretty faithful to this post, on fully patched Mojave — seems a bit worse since last security update.

$ neofetch
                   'c.        
                 ,xNMM.          -----------------
               .OMMMMo           OS: macOS Mojave 10.14.6 18G6020 x86_64
               OMMM0,            Host: Hackintosh (SMBIOS: iMac19,1)
     .;loddo:' loolloddol;.      Kernel: 18.7.0
   cKMMMMMMMMMMNWMMMMMMMMMM0:    Uptime: 15 mins
 .KMMMMMMMMMMMMMMMMMMMMMMMWd.    Packages: 130 (brew)
 XMMMMMMMMMMMMMMMMMMMMMMMX.      Shell: bash 5.0.18
;MMMMMMMMMMMMMMMMMMMMMMMM:       Resolution: 2560x1440@2x, 1920x1080@2x, 1680x1050@2x
:MMMMMMMMMMMMMMMMMMMMMMMM:       DE: Aqua
.MMMMMMMMMMMMMMMMMMMMMMMMX.      WM: Quartz Compositor
 kMMMMMMMMMMMMMMMMMMMMMMMMWd.    WM Theme: Blue (Dark)
 .XMMMMMMMMMMMMMMMMMMMMMMMMMMk   Terminal: iTerm2
  .XMMMMMMMMMMMMMMMMMMMMMMMMK.   Terminal Font: JetBrainsMono-Medium 14
    kMMMMMMMMMMMMMMMMMMMMMMd     CPU: Intel i9-9900K (16) @ 3.60GHz
     ;KMMMMMMMWXXWMMMMMMMk.      GPU: Radeon RX 580
       .cooc,.    .,coo:.        Memory: 24982MiB / 65536MiB

$ lsusb
2020-08-07 10:16:01.367 system_profiler[3748:79910] SPUSBDevice: IOCreatePlugInInterfaceForService failed 0xe00002be
Bus 020 Device 004: ID 0bda:0411 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
Bus 020 Device 009: ID 05dc:b049 Lexar Media, Inc. USB_3_0 Reader  Serial: XXX
Bus 020 Device 010: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE  Serial: XXX
Bus 020 Device 008: ID 0424:5534 SMSC USB5534B
Bus 020 Device 007: ID 05e3:0608 Genesys Logic, Inc. USB2.0 Hub
Bus 020 Device 013: ID 1b1c:0c15 CORSAIR MEMORY INC. H100i Platinum  Serial: XXX
Bus 020 Device 006: ID 05e3:0608 Genesys Logic, Inc. USB2.0 Hub
Bus 020 Device 023: ID 0a5c:4500 Broadcom Corp. BRCM20702 Hub
Bus 020 Device 000: ID 05ac:828d Apple Inc. Bluetooth USB Host Controller
Bus 020 Device 002: ID 04b8:0128 Seiko Epson Corp. EPSON Scanner
Bus 020 Device 001: ID 04a9:10d5 Canon Inc. iP4800 series  Serial: XXX
Bus 020 Device 005: ID 0bda:5411 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
Bus 020 Device 003: ID 0424:2134 SMSC USB2134B
Bus 020 Device 011: ID 05e3:0608 Genesys Logic, Inc. USB2.0 Hub
Bus 020 Device 015: ID 05e3:0608 Genesys Logic, Inc. USB2.0 Hub
Bus 020 Device 020: ID 0765:5020 X-Rite Incorporated ColorMunki Display
Bus 020 Device 019: ID 046d:082d Logitech Inc. HD Pro Webcam C920  Serial: XXX
Bus 020 Device 014: ID 413c:2113 Dell Inc. Dell KB216 Wired Keyboard
Bus 000 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 000 Device 001: ID 1d6b:CITR Linux Foundation USB 3.1 Bus

Oh, and lsusb will show a second error line when it is not working, but will still list the devices. (I think all of them)

 

[CaseySJ]

Any guesses on an issue I've been having on and off for ages, with uptime ranging from hours to weeks my USB will suddenly die. I'll be working, and my Magic Mouse will freeze and my keyboard will be non-responsive and after a minute or so it will scold me about not ejecting my backup drive before removing it. (or sometimes I'll return to my desk and find it this way). Very frustrating, fortunately I have my MacBook running Synergy so I can usually clean up and reboot cleanly (or ssh in and sudo shutdown).

Build is pretty faithful to this post, on fully patched Mojave — seems a bit worse since last security update.
...
Oh, and lsusb will show a second error line when it is not working, but will still list the devices. (I think all of them)

Have you seen the USB Best Practices guide? This is particularly applicable to systems with multiple USB 2.0 devices. It may be a good starting point...

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

Catalina 10.15.6 has just been released. As always, make a full bootable backup before attempting the in-place update. Hahaha I’m always one release behind. Literally just finished testing 10.15.5

www.tonymacx86.com

 

[Togril]

Use iMac19,1 even if you have i7-8300 because USBInjectAll 0.7.1 does not support iMac19,2. You may, however, use USBInjectAll 0.7.5 with iMac19,2.

Well - it got WAY further in - a little over half way but I was greeted with a "Stop Sign" on a black screen. The main SSD in the Hackintosh is still a blank exFat drive.
I could not find a -v or Verbose mode in openCore Configurator.
Thanks though, for all you suggestions. I am still utterly stumped as to why it all worked the first time.
T.Xx

 

[CaseySJ]

First of all, @CaseySJ and @Elias64Fr, thank you very much for your hard work!

I have a laptop, Thinkpad X1 Carbon 6th gen with an Alpine Ridge Thunderbolt chip. Thunderbolt works just fine (including hotplug) without the "BIOS Assist" option in the BIOS, but adds about 2W to the CPU package power consumption. The "BIOS Assist" option removes the additional power draw but also disables hotplug functionality.

Is there any way I can mod the Thunderbolt firmware in a similar way to allow for native Thunderbolt functionality? Looking at the thread, I didn't find any specific references to the patches applied and I don't know much about the subject to try and figure it out on my own.

I'm attaching an SPI dump of the Thunderbolt chip in case that helps.

Hello @contemporarygary,

Because this is an Alpine Ridge controller, you have two options for enabling Thunderbolt Bus:

• By modifying SSDT
• By modifying Thunderbolt firmware

In both cases, however, you may see some issues with Windows.

If your main concern is to reduce the extra 2W of idle power that Thunderbolt consumes, it is better to modify SSDT alone. We can try to enable Thunderbolt power conservation.

To modify SSDT, we will need:

• Original DSDT.aml
  • This can be obtained through Hackintool as shown:
    
  • After Step 2, select a destination folder, then locate DSDT.aml and post only that file
• IOReg file by running IORegistryExplorer and selecting File --> Save As...

 

[Tea-Bone]

Have you seen the USB Best Practices guide? This is particularly applicable to systems with multiple USB 2.0 devices. It may be a good starting point...

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

Catalina 10.15.6 has just been released. As always, make a full bootable backup before attempting the in-place update. Hahaha I’m always one release behind. Literally just finished testing 10.15.5

www.tonymacx86.com

Thanks @CaseySJ - moved my USB2 hub from the USB3 hub in my monitor to the USB2 port where my scanner was plugged in and I'll see how that goes.

 

[CaseySJ]

** Preliminary Update on Big Sur Public Beta **

​

I've been encountering a persistent problem when installing Big Sur Public Beta 1 directly on Designare Z390. Using the OpenCore 0.6.0 EFI from the Mini-Guide (no changes) and standard BIOS parameters (no changes), the Big Sur installer starts up and I can (a) format the destination disk and (b) begin installation. But about 30 seconds into the process, the following error occurs (simply open the Installer Log from the menu and select "Show all Messages" from the pop-up on the right side of the log window):

Aug 7 13:06:48 iMac osinstallersetupd[234]: Extracting /Volumes/Shared Support/com_apple_MobileAsset_MacSoftwareUpdate/878ad7930fa12653a9b85de02c61ab40fcd367c6.zip -> /Volumes/Big Sur/macOS Install Data/UpdateBundle
Aug 7 13:07:23 iMac osinstallersetupd[234]: Failed to supply bytes
Aug 7 13:07:23 iMac osinstallersetupd[234]: Finished extracting: failed
Aug 7 13:07:23 iMac osinstallersetupd[234]: Operation queue failed with error: Error Domain=com.apple.OSInstallerSetup.error Code=1004 "An error occurred loading the update." UserInfo={NSLocalizedDescription=An error occurred loading the update., NSUnderlyingError=0x7fa0c751b5f0 {Error Domain=SZExtractorErrorDomain Code=2 "CRC mismatch; got: 0x59b67506 expected: 0xb65b8272 for file AssetData/payloadv2/payload.005" UserInfo={NSLocalizedDescription=CRC mismatch; got: 0x59b67506 expected: 0xb65b8272 for file AssetData/payloadv2/payload.005, SZExtractorFileOffsetErrorKey=5566683070, SZExtractorSourceFileLineErrorKey=1271, NSFilePath=AssetData/payloadv2/payload.005, SZExtractorFunctionNameErrorKey=-[StreamingUnzipper _supplyBytes:length:withReply:]}}}

After reviewing and cross-checking this with @Inqnuam and @joostiphone I did the following:

• Used my 2020 MacBook Pro to install Big Sur onto an external SATA SSD using the same downloaded installer that produced those red errors above. This means the downloaded file is okay.
• Connected the SATA SSD to Z390 Designare and copied the EFI folder from Catalina EFI to Big Sur EFI (no changes).
• Booted with the SATA SSD and, voilà, Big Sur is working. Although at the OpenCore Picker, the volume name is Preboot.

Apparently, @Inqnuam did not encounter the same problem with payload.005, and was able to install Big Sur directly.

If (a) you are encountering the same "payload.005" problem or (b) you have successfully installed Big Sur Public Beta directly, please let us know.

 

[mcnb]

** Preliminary Update on Big Sur Public Beta **​

...

No issues here. I used the opportunity to switch to OpenCore 0.6.0 from Clover, updated painlessly through Software Update. A couple extra reboots, and OpenCore shows Big Sur drive as "Preboot" but I've read that will return to drive name after a few more reboots.

 

[contemporarygary]

Hello @contemporarygary,

Because this is an Alpine Ridge controller, you have two options for enabling Thunderbolt Bus:

• By modifying SSDT
• By modifying Thunderbolt firmware

In both cases, however, you may see some issues with Windows.

If your main concern is to reduce the extra 2W of idle power that Thunderbolt consumes, it is better to modify SSDT alone. We can try to enable Thunderbolt power conservation.

To modify SSDT, we will need:

• Original DSDT.aml
  • This can be obtained through Hackintool as shown:
    View attachment 483230
  • After Step 2, select a destination folder, then locate DSDT.aml and post only that file
• IOReg file by running IORegistryExplorer and selecting File --> Save As...

Thank you! I'm attaching the files to this message.

I have one concern though, wouldn't this DSDT also include the SSDTs and ACPI patches injected with OpenCore? I'm currently using SSDT-Z390-TB3HP.aml and a couple of hotpatches for the TB hotplug

 

[kromuh]

In the drivers64UEFI folder, see these two files?

• OsxAptioFix2Drv-free2000.efi
• OsxAptioFix3Drv-64.efi

Both of them are memory EFI drivers. We can only use one at a time, and the one that works is OsxAptioFix2Drv-free2000.efi. So please delete the other one and reboot.

Eventually you should replace OsxAptioFix2Drv-free2000.efi with yet another one (but you can do this later).

@CaseySJ after removing the file “OsxAptioFix3Drv-64.efi” and keeping “OsxAptioFix2Drv-free2000.efi”, I finally ejected the bootable drive and rebooted. Now I’m stuck at this point during boot
Any idea why this would be? I plugged the boot drive back in and the same thing happened. Hoping I don’t have to start install and post install process over again. Had everything perfect except for still needing the boot drive to boot from SSD

 

[CaseySJ]

@CaseySJ after removing the file “OsxAptioFix3Drv-64.efi” and keeping “OsxAptioFix2Drv-free2000.efi”, I finally ejected the bootable drive and rebooted. Now I’m stuck at this point during boot
Any idea why this would be? I plugged the boot drive back in and the same thing happened. Hoping I don’t have to start install and post install process over again. Had everything perfect except for still needing the boot drive to boot from SSD

Please perform a CMOS Reset by shorting the two pins as explained in Designare user's manual. Then configure BIOS parameters again starting with Save & Exit --> Load Optimized Defaults. This should reset the memory map and let you get past that error.