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

[CaseySJ]

Well, I checked everything you said. But sadly, I could not boot back into the OS.

For anytime I ran kext utility. I always got the problem in attachment.
My PC seem behaves weird.

Please do a shutdown, then remove power cable for 10 seconds, reconnect, and reboot. Does this problem go away?

 

[CaseySJ]

...
You say that the Library/Extensions folder should match the CLOVER/kexts/Other folder ? Why that ? Jhahn above says to keep them in one place so I dont understand.

This is like Democrats and Republicans. There are an equal number of people who profess one of these solutions over the other. I tend to agree with JayMonkey that all third-party kexts should be installed in /Library/Extensions/ per Apple’s guidelines. There is not a single real Mac out there that uses any other directory for third-party kexts. The Clover injection method for kexts is a convenience for the purposes of setting up the system and experimenting with alternatives until problems are resolved. But once set up, we change “Inject Kexts” to “Detect” and install kexts in /L/E.

[GUIDE] Installing 3rd Party Kexts - El Capitan, Sierra, High Sierra, Mojave, Catalina

Installing 3rd Party Kexts in /Library/Extensions Note: This guide was originally written to support MacOS Mojave and older versions (< r5200) of the Clover boot-loader. The methods detailed here are now considered legacy methods and should only used with older versions of MacOS as detailed...

www.tonymacx86.com

Edit: Oh actually there is one thing I cant make work. I is the "Authorize your Apple Watch to unlock your Mac", I get a error message like: "Your Mac couldn't communicate with your Apple Watch". Any idea ? (It works with my MacBook Pro.)

This has happened to a few of us. Need to turn off the Apple Watch completely. Then turn off WiFi and Bluetooth on Hackintosh. Turn on WiFi and BT on Hackintosh. Turn on the Apple Watch. Then try to enable “unlock with Apple Watch” once again.

 

[deltanguyen]

Please do a shutdown, then remove power cable for 10 seconds, reconnect, and reboot. Does this problem go away?

Well, sadly, the problem remained. I guessed I should move on, and re-do installation again

 

[Mattioo]

This is like Democrats and Republicans. There are an equal number of people who profess one of these solutions over the other. I tend to agree with JayMonkey that all third-party kexts should be installed in /Library/Extensions/ per Apple’s guidelines. There is not a single real Mac out there that uses any other directory for third-party kexts. The Clover injection method for kexts is a convenience for the purposes of setting up the system and experimenting with alternatives until problems are resolved. But once set up, we change “Inject Kexts” to “Detect” and install kexts in /L/E.

[GUIDE] Installing 3rd Party Kexts - El Capitan, Sierra, High Sierra, Mojave, Catalina

Installing 3rd Party Kexts in /Library/Extensions Note: This guide was originally written to support MacOS Mojave and older versions (< r5200) of the Clover boot-loader. The methods detailed here are now considered legacy methods and should only used with older versions of MacOS as detailed...

www.tonymacx86.com

This has happened to a few of us. Need to turn off the Apple Watch completely. Then turn off WiFi and Bluetooth on Hackintosh. Turn on WiFi and BT on Hackintosh. Turn on the Apple Watch. Then try to enable “unlock with Apple Watch” once again.

So if I'm using Virtual SMC this needs to stay in the Clover/kexts/Others/, the four SMCBatteryManager.kext SMCLightSensor.kext SMCProcessor.kext SMCSuperIO.kext have to go in the /Library/Extensions/ folder ? What about USBInjectAll.kext and IntelMausiEthernet.kext ?

 

[CaseySJ]

So if I'm using Virtual SMC this needs to stay in the Clover/kexts/Others/, the four SMCBatteryManager.kext SMCLightSensor.kext SMCProcessor.kext SMCSuperIO.kext have to go in the /Library/Extensions/ folder ? What about USBInjectAll.kext and IntelMausiEthernet.kext ?

This is explained to some extent in the build guide, but the guidelines are as follows:

• All third-party kexts should be installed in /L/E. This includes VirtualSMC.kext.
• Then we set System Parameters --> Inject Kexts to Detect.
• What does "Detect" mean?
• It means that during boot, Clover will look for either FakeSMC.kext or VirtualSMC.kext in the /Library/Extensions folder.
  • If neither of these kexts is present in /L/E, Clover will subsequently inject all kexts that are in the CLOVER/kexts/Other folder.
  • But if either one exists in /L/E, then Clover will not inject any kext from the Clover/kexts/Other folder.
• This means that /L/E folder should contain all kexts necessary for running the system.
• But this also means that (a) during macOS installation, (b) when booting into Recovery, (c) when doing a safe boot, the /Library/Extensions folder may not be present or it may not be accessible.
  • So we still keep a minimum set of kexts in the Clover/kexts/Other folder.
  • These kexts are never injected if (a) /Library/Extensions is present and (b) FakeSMC.kext or VirtualSMC.kext is also present in /L/E.
  • The minimum set of kexts to install in CLOVER/kexts/Other is:
    • VirtualSMC.kext (or FakeSMC.kext, but not both)
    • Lilu.kext
    • WhateverGreen.kext
    • USBInjectAll.kext (because USB SSDT will not work without it)

 

[CaseySJ]

Well, sadly, the problem remained. I guessed I should move on, and re-do installation again

Yes I think that may be a good idea now! Remember to go slowly and double-check each step. Disconnect all USB and SATA drives except for keyboard, mouse, Mojave SSD, and USB install disk. You may keep the WiFi/BT card and AMD GPU installed.

 

[skittlebrau]

This is like Democrats and Republicans. There are an equal number of people who profess one of these solutions over the other. I tend to agree with JayMonkey that all third-party kexts should be installed in /Library/Extensions/ per Apple’s guidelines. There is not a single real Mac out there that uses any other directory for third-party kexts. The Clover injection method for kexts is a convenience for the purposes of setting up the system and experimenting with alternatives until problems are resolved. But once set up, we change “Inject Kexts” to “Detect” and install kexts in /L/E.

It'll all become irrelevant post-Catalina anyway when kexts are fully deprecated/no longer supported and kext patching becomes a thing of the past. Then the community will find new things to bicker about

 

[scyu]

Hi Casey,

I asked for BT issues which was suddenly fixed (I don't know exactly what the magics are). As regards the systems, I got everything running and am please to also follow your backup guide using CCC. But one thing weird id that EFI was created with "blank entry" and manual copying is required, even with the script running.

While the systems report showed all information, my PCI tab showed nothing, not even my Vega 64 and Apple BT/WiFi combo card. Any hints ?

 

[jhahn]

@Mattioo As far as I know SMCBatteryManager.kext and SMCLightSensor.kext are for laptops only, so you can remove them completely.

 

[CaseySJ]

Hi Casey,

I asked for BT issues which was suddenly fixed (I don't know exactly what the magics are). As regards the systems, I got everything running and am please to also follow your backup guide using CCC. But one thing weird id that EFI was created with "blank entry" and manual copying is required, even with the script running.

While the systems report showed all information, my PCI tab showed nothing, not even my Vega 64 and Apple BT/WiFi combo card. Any hints ?

Hello @scyu,

Can you describe the CCC problem in some detail? For example:

• Which clone script did you use?
  • EFIClone-v2.sh
  • EFIClone.sh from the GitHub repository
• When you formatted the clone disk using Disk Utility, did you specify the Scheme as GUID Partition Table?
  • In other words, does the clone disk contain an EFI partition?

At a minimum, the PCI page should show Thunderbolt NHI and Thunderbolt USB Controller. If you don't see these, then it's possible that the CLOVER folder is not properly set up. If the Thunderbolt hot plug SSDT and DTPG.aml exist in the CLOVER/ACPI/patched folder, then the PCI page should contain two Thunderbolt entries.