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

[CristianP]

Glad to hear it, but I wonder if other UAD Apollo Twin owners experience the same thing when switching between macOS and Windows...

Me too, I think that’s why nobody on this thread had this issue, it is a specific and isolated scenario.

 

[pianistslogic]

If you're running Catalina, did you have Mojave on the same SSD before (i.e. you upgraded from Mojave to Catalina)? If so, please do this:

• Post a screenshot of /Library/Extensions
• Run this command in Terminal kextstat | grep -v apple and post a screenshot of the result
• Then mount EFI partition of macOS SSD, select USBInjectAll.kext from CLOVER/kexts/Other and choose Get Info from the the Finder. What is the version of USBInjectAll.kext?

Hi CaseySJ

Just wanted to let you know that my 0xFF to 255 edit made no difference. Besides, I've found out that my fenvi wouldnt connect to any bluetooth devices on a cold boot (or so I think), but after a reboot all was well again.

I've compared my IOReg dumps from both (i.e., working and 'seemingly working' but unresponsive) bluetooth states, but couldn't find any noticeable differences. In retrospect, I think I may have looked at the wrong sub-entry when I blamed HS11 for presenting itself as a 'zero'/external usb2 port.

I still don't understand why or what, but decided to migrate to the beta Intel bluetooth drivers. Though your supplied FD R6 .aml file didn't work for me, simply swapping HS11 for HS14 (and 0x0E for 0x0F if I recall correctly) did the trick.

Never used handoff and smart watches so far so, so far so good for me. Love your continued support and assistance here, much appreciated!

 

[FormerUser-594785]

Today my computer has reset to Bios F3.
I don't understand what happened.
Then I put the F9B back in.
What I don't understand is that the computer has started even without the procedure (which I then did) of unlocking the MSR.

 

[CaseySJ]

Hi CaseySJ

Just wanted to let you know that my 0xFF to 255 edit made no difference. Besides, I've found out that my fenvi wouldnt connect to any bluetooth devices on a cold boot (or so I think), but after a reboot all was well again.

I've compared my IOReg dumps from both (i.e., working and 'seemingly working' but unresponsive) bluetooth states, but couldn't find any noticeable differences. In retrospect, I think I may have looked at the wrong sub-entry when I blamed HS11 for presenting itself as a 'zero'/external usb2 port.

I still don't understand why or what, but decided to migrate to the beta Intel bluetooth drivers. Though your supplied FD R6 .aml file didn't work for me, simply swapping HS11 for HS14 (and 0x0E for 0x0F if I recall correctly) did the trick.

Never used handoff and smart watches so far so, so far so good for me. Love your continued support and assistance here, much appreciated!

I'm surprised by the frequency of Bluetooth issues being reported on the Fenvi. In preparation for a Gigabyte Z490 Vision D build, I've ordered a new Fenvi FV-T919 -- which will be my 4th such card -- and will see if I experience these issues. But to date all three T919s in my possession have been completely problem free.

 

[CaseySJ]

Today my computer has reset to Bios F3.
I don't understand what happened.
Then I put the F9B back in.
What I don't understand is that the computer has started even without the procedure (which I then did) of unlocking the MSR.

In Clover Configurator --> Kernel and Kext Patches, if (a) KernelPM and (b) AppleIntelCPUPM are checked-on, then the system should boot without MSR 0xE2. This applies to all versions of Mojave and to Catalina 10.15.3 and older. Not so sure if this will work with 10.15.4 (haven't tried it).

 

[CaseySJ]

@vicantu,

Thank you for the detailed report; it's quite helpful. The SSDT you have already contains debug logging, but it's currently turned off. We can do the following:

• First, hot plug a Thunderbolt device then restart IORegistryExplorer to see if the device tree appears under DSB1.
• Next, to enable debug logging we just need to do this:
  • Download attached ZIP that contains 2 files.
  • Copy ACPIDebug.kext to CLOVER/kexts/Other
  • Copy SSDT-DTPG-V3.aml to CLOVER/ACPI/patched, but move the previous file (SSDT-DTPG-V2.aml) to CLOVER/misc
  • Reboot
• Thunderbolt logs can then be seen as follows (in Terminal): log show --last boot | grep ACPIDebug

 

[canyondust]

@vicantu,

Thank you for the detailed report; it's quite helpful. The SSDT you have already contains debug logging, but it's currently turned off. We can do the following:

• First, hot plug a Thunderbolt device then restart IORegistryExplorer to see if the device tree appears under DSB1.
• Next, to enable debug logging we just need to do this:
  • Download attached ZIP that contains 2 files.
  • Copy ACPIDebug.kext to CLOVER/kexts/Other
  • Copy SSDT-DTPG-V3.aml to CLOVER/ACPI/patched, but move the previous file (SSDT-DTPG-V2.aml) to CLOVER/misc
  • Reboot
• Thunderbolt logs can then be seen as follows (in Terminal): log show --last boot | grep ACPIDebug

Super-side-note: Is anyone else's OCD set alight by the fact that the SSDT is named 'DTPG' in the code block but the method it calls is 'DTGP'? (please don't shoot me)

 

[canyondust]

Another sidenote: if you plan on using SSDT-DTPG, and you're already using SBUS-MCHC, there might be a not-as-complete DTGP method definition in that SSDT that needs to be removed. Example with the method removed here:

 

[CaseySJ]

Super-side-note: Is anyone else's OCD set alight by the fact that the SSDT is named 'DTPG' in the code block but the method it calls is 'DTGP'?

In the words of Ralph Waldo Emerson, "...consistency is the hobgoblin of little minds..."

Fine Print: To be fair, this quote is often taken out of context and in fact Emerson said, "A foolish consistency is the hobgoblin of little minds, ..." and he was referring to some people's unwillingness to change the impressions that others have of them. But if 99% of the news media takes things out of context every day, well we can perhaps grant ourselves a similar transgression.

(please don't shoot me)

No worries. We won't take you out to the canyon and turn you into dust.

 

[zipb]

Yes I think the issues with RX 5700 XT have been sorted out. My PowerColor Red Dragon has never exhibited those issues, but with a Hackintosh there are no guarantees, no promises. We should always purchase components from a retailer that has a good return/exchange policy. This thread is long enough that one can search it for almost any issue and find multiple user reports from which to decide. The Intel iGPU will be used for compute tasks if the Catalina build guide is followed.

See above.

Ever since Clover 5103 there has been good compatibility with 8GB, 16GB and even 32GB memory modules (max 128GB). It may be necessary to turn off X.M.P. Profile and use the memory at 2666MHz or 2933MHz for best reliability. But try with X.M.P. Profile enabled to see how the system responds. Even the USD$6000 Mac Pro uses only 2666MHz and 2933MHz memory. Don't let anyone tell you that you're suffering the slings and arrows of outrageous fortune by down-clocking memory to these speeds.

Finally, Hackintosh is about experimentation and self-reliance. There is no AppleCare or Apple Genius or Tech Support Hotline. Anyone unable or unwilling to experiment, to do some research, and to at least try to be self-reliant should visit an Apple online or retail store instead.

Is the USB disks do not remount after sleep problem fixed for higher RAM speeds than 2666 MHz? I paid a premium for high speed RAM, but can't use it at anything higher than 2666 MHz if I want to avoid this problem.