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

... or buy (pricey) a Thunderbolt hub. You do not have an USB-C connector in front of your case? An USB type A cable with USB-C at the other end? Would be much less hassle...

**Just looked at the manual: it is supposed to come with an USB-A to USB-C cable.

***Oh wait, is it for the Scarlett or the HDD's that you need USB-C?

xtrell said:

Or: is there a way I can re-enable USB2 on the board's 2 Thunderbolt connectors and the case (and perhaps disable other ports if 15 is the limit)?

Click to expand...

Depending on your setup you can disable HS12(F_USB) or SS01(F_USB3.1_C) then enable one of HS01(F_USB2.0_C), HS08 (Real USB2.0_C), or HS13(Real USB2.0_C).

Attached USBPorts.kext disables SS01 and enables HS08(First Thunderbolt port on rear panel).
Works on iMacPro1,1 or iMac19,1 SMBIOS

Upgraded OpenCore from 0.7.1 to 0.8.2 using HackinDROM and now my system won't restart. It hangs on the BIOS screen. Does anyone have any pointers to what causes this? Thanks!

dewby said:

Upgraded OpenCore from 0.7.1 to 0.8.2 using HackinDROM and now my system won't restart. It hangs on the BIOS screen. Does anyone have any pointers to what causes this? Thanks!

Click to expand...

post 1 has lots of information for you

dewby said:

Upgraded OpenCore from 0.7.1 to 0.8.2 using HackinDROM and now my system won't restart. It hangs on the BIOS screen. Does anyone have any pointers to what causes this? Thanks!

Click to expand...

Does this mean that OpenCore Boot Picker does not appear? Or it does appear, but macOS boot process stalls?

CaseySJ said:

Does this mean that OpenCore Boot Picker does not appear? Or it does appear, but macOS boot process stalls?

Click to expand...

The OpenCore boot picker doesn't appear. It just hangs at the Gigabyte <DEL><F12> screen.

Jasonhacks said:

Just learned that "Wake for network access" works perfectly with Intel i211 Ethernet natively driven by AppleEthernetE1000.

Click to expand...

Running iStat menus, I saw quite noticeable CPU-load from the AppleEthernetE1000 driver when maxing out my 400Mbit fiber Internet ever since we discovered it works natively. So I mainly use the other gigabit Ethernet again.
Did others notice the same?
edit- added screenshot and double-checked, no visible CPU-load when using the i219 port.

CaseySJ said:

Hello @IKOBOY,

AirDrop is not supported on Intel WiFi/BT. Please see this post:

Asus Z690 ProArt Creator WiFi (Thunderbolt 4) + i7-12700K + AMD RX 6800 XT

That looks perfectly fine. AIO is connected to power supply AIO is connected to ARGB header on motherboard No USB connection @Lensjocky reported a similar issue with his Gigabyte Z490 Vision D. After replacing an AMD Vega GPU with Sapphire Pulse AMD Radeon RX 6800 XT, his system no longer...

www.tonymacx86.com

Click to expand...

Thank You @CaseySJ, I re-inserted the Fenvi adapter card back to PCIe as WiFi, remain use Intel onboard module as Bluetooth, Airdrop working now.

dewby said:

The OpenCore boot picker doesn't appear. It just hangs at the Gigabyte <DEL><F12> screen.

Click to expand...

Some suggestions:

1. Perform a cold start. This means shutdown the system, flip power switch on PSU to OFF for 10 seconds, then power back up.
2. If OpenCore boot picker does not appear, go to BIOS Setup --> Boot and confirm that first boot priority is still the internal macOS disk.
3. If that does not help, boot the system from your bootable backup disk. The EFI partition on that backup disk should still work. Then log into macOS.
4. Now we can mount the non-working EFI partition and begin to investigate why it won't boot. Feel free to compress and post that EFI folder, but remove serial numbers from config.plist --> PlatformInfo section.
   • If you didn't bother to make a bootable backup, now is the time to ask yourself why...
   • Now is the time for everyone who didn't make a bootable backup to ask themselves why.
5. If you don't have a bootable backup, there are a couple of options:
   • Option 1: You can create a brand new EFI folder by downloading the latest version from Section 1 of the spoiler at the top of Post 1 labeled "Quick Reference to Mini-Guides and Micro-Guides". New serial numbers will be needed, which will cause some iCloud/AppleID warnings. But you'll be able to boot into macOS, then follow Step 4 above.
   • Option 2: Remove the NVMe SSD from the M.2 slot and insert it into an external USB 3.0 enclosure. Connect that enclosure into any other Mac (even a MacBook), then mount EFI partition of that disk. Then follow Step 4 above.

CaseySJ said:

Some suggestions:

1. Perform a cold start. This means shutdown the system, flip power switch on PSU to OFF for 10 seconds, then power back up.
2. If OpenCore boot picker does not appear, go to BIOS Setup --> Boot and confirm that first boot priority is still the internal macOS disk.
3. If that does not help, boot the system from your bootable backup disk. The EFI partition on that backup disk should still work. Then log into macOS.
4. Now we can mount the non-working EFI partition and begin to investigate why it won't boot. Feel free to compress and post that EFI folder, but remove serial numbers from config.plist --> PlatformInfosection.
   • If you didn't bother to make a bootable backup, now is the time to ask yourself why...
   • Now is the time for everyone who didn't make a bootable backup to ask themselves why.
5. If you don't have a bootable backup, there are a couple of options:
   • Option 1: You can create a brand new EFI folder by downloading the latest version from Section 1 of the spoiler at the top of Post 1 labeled "Quick Reference to Mini-Guides and Micro-Guides". New serial numbers will be needed, which will cause some iCloud/AppleID warnings. But you'll be able to boot into macOS, then follow Step 4 above.
   • Option 2: Remove the NVMe SSD from the M.2 slot and insert it into an external USB 3.0 enclosure. Connect that enclosure into any other Mac (even a MacBook), then mount EFI partition of that disk. Then follow Step 4 above.

Click to expand...

Cold start works as expected.
Using the Restart command from OSX causes a hang on the Gigabyte BIOS screen.
Selecting Windows 10 from Startup Disk and restarting works as expected.
Selecting OSX from boot camp assistant and restarting causes a hang on the bios screen.

I just noticed that there's an APPLE folder in my EFI with a folder called FIRMWARE and UPDATERS. Do you think that could be causing the issues? Should I delete that?


The issue I'm facing is if I restart my computer from OSX my computer hangs on the Gigabyte BIOS screen and never loads the OC boot picker. If I restart from OSX in to Windows it works as expected. If I restart from Windows to OSX it works as expected with a long boot time.

I uploaded my original working EFI and my upgraded EFI.