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

[CaseySJ]

** Big Sur Users: FYI **​

macOS Big Sur upgrade can lead to data loss without ample storage | AppleInsider

An issue with Apple's macOS Big Sur installer allows users to upgrade from an earlier operating system without first verifying that the target Mac has enough free hard drive space, resulting in installation failure and data loss.

appleinsider.com

 

[CaseySJ]

lol okay so that's a no. Good!

Okay updated to 11.2.
Was on bios F9j just downgraded to F9b and reunlocked CFG through grub.
Also upgraded to OC 6.6, using guide and the attached files
Running a Radeon VII
magic mouse 2

Everything was working fine 11.1 using the bluetooth from guide as well
The lag seems to be a system wide, even a wired mouse has the lag. mouse and windows move but catches/freezes for an instant the comes back, this is pretty constant.

Some comments and questions:

• Perhaps Spotlight indexing is taking place. Check "Activity Monitor" to see which processes are taking up CPU time.
• Sounds like you tried at least two mice: one wired and one wireless?
• The specific lag you describe where a window stutters while moving may be due to something completely different. Good to check "Activity Monitor" to see what processes, if any, are consuming a lot of CPU time.

 

[archalys]

Some comments and questions:

• Perhaps Spotlight indexing is taking place. Check "Activity Monitor" to see which processes are taking up CPU time.
• Sounds like you tried at least two mice: one wired and one wireless?
• The specific lag you describe where a window stutters while moving may be due to something completely different. Good to check "Activity Monitor" to see what processes, if any, are consuming a lot of CPU time.

It seems like its a graphics issue. I googled it and it seems to be affecting actual mac users. The posted remedy was to reset the SMC. Going to try going back to OC 6.5 next.

 

[archalys]

It seems like its a graphics issue. I googled it and it seems to be affecting actual mac users. The posted remedy was to reset the SMC. Going to try going back to OC 6.5 next.

OC 6.5 didn't solve. . . yes three different mice wire, Magic Mouse 1, and Magic Mouse 2. It really seems to be more of a graphics bug that a HID thing.

System has been sitting overnight so I would think indexing has had enough time to complete?

 

[verydanny]

Has anyone run into the issue of booting Windows using F12 then when restarting it keeps adding more and more Windows entries into the BIOS boot selector?

Before:

UEFI OS (OpenCore)
Windows Boot Manager (Sabrent)

After:

Windows Boot Manager (Sabrent)
UEFI OS (OpenCore)
Windows Boot Manager (Sabrent)

After:

Windows Boot Manager (Sabrent)
Windows Boot Manager (Sabrent)
UEFI OS (OpenCore)
Windows Boot Manager (Sabrent)

I have no idea how to fix this, and it's annoying as hell. I don't want to boot Windows through OpenCore because of the SMBios stuff. I don't want a BootCamp PC. I want it native.

 

[yoghibear]

What is the difference between "Antelope YES" and "Antelope NO"? Specifically:

• Which Thunderbolt SSDT was used with "Antelope YES"?
• Which Thunderbolt SSDT was used with "Antelope NO"?

The same Thunderbolt SSDT could not have been used with both because with "Antelope YES" there is a bogus device DSB3, which does not exist in "Antelope NO".

The other difference is that "Antelope YES" has an Antelope devices at DSB2 (which is normally the USB controller), but the SSDT is incorrectly mapping DSB2 to a Thunderbolt port. Nevertheless, DSB2 contains IOAudioEngineUserClient, which is missing in "Antelope NO".

That's why I would like to look at the two SSDTs:

• The SSDT that was used with "Antelope YES"
• The SSDT that was used with "Antelope NO"

@CaseySJ

• Antelope YES is resulting from my original MacBook Pro 2012 + Mojave + Orion Studio Synergy core, therefore there's no SSDT.

• Last Antelope NO I sent you is resulting from the hackintosh with High Sierra + Asus Prime X299 A-II + NO FLASHED Titan Ridge 2.0 + ZenTour (no synergy core).

• The previous Antelope NO instead was resulting from hackintosh with Catalina + FLASHED Tian Ridge 2.0. + ZenTour (no synergy core).

Actually I don't know, I may have made confusion myself attaching the wrong files in the last post,
in case SORRY FOR THAT!
To sum up everything I'm sending you all the files in different folders.
That should eventually clarify all.
Please let me know...
thx

 

[hitINdaGs]

Is nobody else having trouble with the SATA Hotplug fix? It's driving me crazy...

 

[basett1]

That's a great build description/guide on Github!

Regarding USB-C data transfer speed:

• What is the make/model of the USB 3 device you are connecting?
• What read/write speeds are you seeing? Can you post a screenshot?

Hi @CaseySJ , for now I have only a SANDISK Ultra USB 3.0 for test, the results are similar using any computer port as you can see from the attached photos.
the problem I was referring to is related to the Thunderbolt between the hack and a NUC 10, the transfer speed is so slow, as I said abut 30mins for about 6gb, there is some test I can make to take the real speed? I'm also waiting for a NVME Thunderbolt enclosure to test the speed.

EDIT
When I connect the Thunderbolt between Hack and Nuc the speed change to 20Gb/s x2 instead of 40Gb/s x1. I I disconnect the cable the speed returns 40Gb/s x1

 

[yoghibear]

@CaseySJ
I deleted the forgot attachment of this current message and updated the previous one...

 

[jeff.m.ruth]

At the OpenCore Picker press and release CMD-V to enable Verbose. Then select the macOS SSD. When the boot process hangs please take a photo and post it as follows:

• Remove EXIF location information (there are several apps in App Store that do this)
  View attachment 508504
• Then resize the photo to about 1280 pixels in either X or Y. We really want to avoid gigapixel photos of a computer screen!

@CaseySJ See attached photos in format request. I left at 800 pixels, since making bigger made pix blurry. There are two photos. IMG_1615 is using your EFI (0.6.5) OpenCore boot folder and the IMG_1615 is using the OC 0.6.6 EFI OC boot folder(I went through the instructions again) to test with another USB stick and different versions. Looking at the log output, seems the boot is failing at the AirPortFamily kext. I did make sure I made sure I removed all kext as outlined in your conversion note(Moving from Clover to OC)