Contribute
Register

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

Thanks a lot for your time. Attached original DSDT dump from clover

PC03 / BR3B /SL0A
Please try the attached version (remove old file and copy new one).
 

Attachments

  • SSDT-TBOLT3-X299_J-V2.aml
    2.2 KB · Views: 86
@CaseySJ THANK YOU SO MUCH FOR THE RESPONSE! EVERYTHING WORKS NOW!


Currently, I am on Catalina. But, when I first did the build, I did installed Mojave.

Yes, it boots up most time with no problem. But on occasions I have to restart the computer several times before it boots. This happened even when I had Mojave installed. That might have been what was causing that issue. I input the boot arg that you suggest will let you know if my occasional boot issue reoccurs. Again, thank you so much!
Hey @CaseySJ
Update!
Adding the boot arg did fix my boot issue, but now on occasions when I boot up my audio is gone. and I have to copy AppleALC and Lilu into the /Library/Extensions folder and reboot in order to get my audio back, even though they already exist in that folder. Any idea as to why this might be happening?
 
If you're not already doing it, be sure to:

Kext Cache Commands via Terminal:

Run after installing or removing kexts from /L/E or S/L/E

sudo touch /Library/Extensions && sudo touch /System/Library/Extensions

then:

sudo kextcache -i /

Wait. It can take awhile. Then reboot.

FWIW, all my Z390 build's kexts and drivers are in EFI/Clover
 
**Mini-Guide for Fresh Installation of Catalina 10.15.4 and Newer **


Hi @CaseySJ ,

Please excuse me. I am new to this world and doing my first Hackintosh install, using a similar spec as mentioned here:

Gigabyte Designare BIOS F9B with a 9900K processor,
32GB DDR4 RAM.
2TB NVMe drive
500MB Sata SSD
Fenvi T919
Asus 10Gbe card

I followed the instructions, but a couple of things occurred which has stopped me from getting this to work, I had the BIOS setup for a OpenCore Vanilla, are there any other adjustments I should make, as I could not find the BIOS setup section here?

I also noticed a point here (after I attempted my install) that said you need to use a monitor vs a TV, is this really critical, as I am using a 4K TV for the short term?

When I did the install it went through the first install cycle, came up so I could use disk utility to format my drive NVMe with a GUID partition and then install macOS.

It started the install and on the first reboot and the Clover menu came on, and before I can choose the correct option it continued on its own, I waited for the Apple logo and a new time to install, which came up and left it alone, thinking it was OK.

When I returned a little later, the screen was mainly white with the edges flashing, I let it carry on, until it turned itself off.

I restarted it manually and it loaded and took me the MacOS setup process, wifi worked, but bluetooth did not (hav the Fenvi board installed), it could not find the thunderbolt even in the PCI menu, it did recognized the 10gbe card. All nearly good. Then I did the last step, and copied the EFI from the USB to the SSD, and restarted, it would not boot into the SSD. The boot menu shows a blank line for each drive I have (I have the m.2 and a sata), but neither is shown by name, just a space, and it does nothing if I select it.

Can anyone tell me where I went wrong? Do I need a monitor? Is the default clover menu option wrong? Any other ideas before I try it again? How do I make the SSD bootable?


Thanks you all advance.

Foo
 
Last edited:
To enable TBSwitch7 we have to disable the 7th bit:
  • C5 = 1100 0101 where 7th bit is in red
  • 85 = 1000 0101 -- now 7th bit is turned off

By me is '02 C5' - this is a TBSwitch5, not 7. Right?

Yes it looks like Switch 9. We've seen this before on Alpine Ridge, but we're not sure what it's for.
Should I to enable the second Switch '02 C9' (1100 1001 => 1000 1001) = 89?

If we flash the Thunderbolt firmware to activate Thunderbolt Bus, then we should modify the DROM and we should inject it via SSDT.
It's not enough if I flash a modified DROM?

Thank you very much!

P.S. Thunderbolt Config is not yet decoded?
upd: Where can I find a "tb-config"? What is the offset of config from start of active partition? Thank you!
 
Last edited:
If you're not already doing it, be sure to:

Kext Cache Commands via Terminal:

Run after installing or removing kexts from /L/E or S/L/E

sudo touch /Library/Extensions && sudo touch /System/Library/Extensions

then:

sudo kextcache -i /

Wait. It can take awhile. Then reboot.

FWIW, all my Z390 build's kexts and drivers are in EFI/Clover


Thank you! Will try this out and let you know the results!
 
Should I to enable the second Switch '02 C9' (1100 1001 => 1000 1001) = 89?

Maybe this controls the Video Pass-threw? I have no video pass-threw on my alpine ridge, I think that is the last part that needs some love to get full implementation.
 
@dgsga For bullet #4, if my root port is RP21, is the following change to config.plist correct?

XML:
          <dict>
                <key>Comment</key>
                <string>change RP21._INI to RP21.XINI for ICM disable</string>
                <key>Enabled</key>
                <true/>
                <key>Find</key>
                <data>UlAyMQhMVFJaAAhPQkZaAAhMTVNMAAhMTlNMABQqX0lOSQ==</data>
                <key>Replace</key>
                <data>UlAyMQhMVFJaAAhPQkZaAAhMTVNMAAhMTlNMABQqWElOSQ==</data>
            </dict>
@sffjawsh, all looks good to me
 
  • But curiously you don't have ICMB, whose purpose is to make the Thunderbolt controller reveal itself to the operating system (OSUP). The Thunderbolt controller normally hides its Device/Vendor ID until OSUP or ICMB is called. Perhaps your BIOS option ACPI RMV is performing this function?
Regarding Titan Ridge:
  • Unfortunately the situation with Titan Ridge is far more difficult! Elias and I spent months and made some progress, but Thunderbolt devices would disconnect after about 20 seconds into boot.
  • We could activate Thunderbolt Bus, but we could not figure out why the controller would go down after 20 seconds.
@CaseySJ, when I was dismantling the SSDT piece-by-piece, I found that the ICMB method doesn't seem to be needed when Force Power is enabled in the BIOS. It made no difference to the outcome. From the feedback of other testers it's starting to look like this approach only works for built-in Alpine Ridge. If only Titan Ridge was as straightforward... I also found that removing all the power methods fixed problems with hot plug and the 20 second delay before power down. Might this be worth trying with the TR or have you already done it?
 
Last edited:
Back
Top