Contribute
Register

Gigabyte X299X - Catalina Support

Status
Not open for further replies.
Hi, I've been building hackintoshes since 2007, my last one in 2016 with the GA-X99-UD4. It's time to upgrade and since we're locked in our homes, it looks like I have loads of time on my hands. But before I splash the 1400,- euros for this motherboard with a corresponding CPU (i9-10900X) onto the table, I have some questions. Up until this point I have always been able to find the necessary files to get and keep my machines running, but this looks like a different beast to master and files are hard to find, except for in this post. So here it goes and I hope someone is patient enough to answer some of my questions:

- If I download the files in the first post and install them will the machine be up and running? (will be using vega64 gpu)
- The SSDT's that are listed, can I just cut and paste these lines into MacIASL and compile?
- Does it matter how I name them and do I just drop them into C/A/P?
- Do I need any other SSDT's besides the ones mentioned in the first post?

Since my knowledge on ssdt's is somewhat limited any advice and help will be greatly appreciated!

Well in my case I have had a nightmare trying to fix the Clover reboot issue. If you read the post above is something that can be bypassed and some people have not that issue. In OpenCore this reboot did not happen once but I could not get to boot the installer (noob and wrong settings in config.plist).

I had good experience with dolgarrenan clean EFI and with AiBeast EFI as well but that weird bloody issue with the Clover reboot can get you really mad. Overall the machine is a beast and I am pretty happy with it. Not one Kernel Panick in 3 weeks or more (I don't shutdown the machine and less now until I have some time to try to fix the reboot issue or someone hits the bell).

So:
1) I would say 85-90% yes.
2 ) Yes
3) Does not matter (but I am not expert)
4) You should (I haven't yet) create you personal USB SSDT following RehabMan's guide (I think) because we should config which USB are using and not use the Limit Patch. (Again I am almost a noob user)
 
Hello guys!

I'm sort of "back" (confinement-ish) so I don't have my machine with me, please post current issues, and we will try to debug them and see what's going on.

EDIT: Run this command
Code:
kextstat | grep -v apple
and post here, let's first see what .kext are you using
 
I have an issue with wifi and bluetooth, handoff and continuity it's not working. I have to check better this issue because I have not get into it in deep so it may be my mistake. Just wanted to know if it works with the on board hardware or do I need another device/hardware.

Thanks everybody ;)

Right now my Clover reboot issue is gone (I don't know why).

EFI config.plist needs to edit serial number, Sm UUID and Board ID (this last one is no need to empty right?)

kextstat|grep -v apple
Index Refs Address Size Wired Name (Version) UUID <Linked Against>
41 6 0xffffff7f85df8000 0x22000 0x22000 as.vit9696.Lilu (1.4.1) 81A9C8D0-23F6-3579-96D1-264515ADC521 <8 6 5 3 2 1>
42 0 0xffffff7f85e1a000 0x69000 0x69000 as.vit9696.WhateverGreen (1.3.6) B3305CD0-7459-3641-B85C-1E3E56DB90AA <41 13 8 6 5 3 2 1>
43 0 0xffffff7f85e83000 0x5000 0x5000 com.rehabman.driver.USBInjectAll (0.7.3) CCA1380C-23E3-3367-8B61-40647EC026D6 <13 12 5 3>
44 0 0xffffff7f85e88000 0x5000 0x5000 meow.IOIIIO.MacProMemoryNotificationDisabler (1.0.0) 1DE82929-5E49-3185-A1BA-1E8CFB131D19 <41 8 6 5 3 2 1>
45 0 0xffffff7f85e8d000 0x7000 0x7000 as.lvs1974.HibernationFixup (1.3.2) 49884940-7094-314A-AB78-6F71BCD20BBB <41 8 6 5 3 2 1>
46 0 0xffffff7f85e94000 0x129000 0x129000 as.vit9696.AppleALC (1.4.5) 9F6CE677-DDED-3BB2-A104-2DAFEB44A2B4 <41 13 8 6 5 3 2 1>
47 1 0xffffff7f85fbd000 0x11000 0x11000 as.vit9696.VirtualSMC (1.1.0) 6911F893-D8A3-32D6-A417-3E17CCC088FE <41 12 8 6 5 3 2 1>
48 0 0xffffff7f85fce000 0x5000 0x5000 as.vit9696.SMCProcessor (1.1.0) E0FA4840-0523-3FF4-93BA-D1481764EA38 <47 41 12 8 6 5 3 2 1>
56 0 0xffffff7f85fd3000 0x4000 0x4000 hu.interferenc.TSCAdjustReset (1.1) CA51711C-DBBE-3ADC-A56E-5C09447F8BF4 <8 5 3>
73 0 0xffffff7f85fd7000 0x2e000 0x2e000 com.SmallTree.driver.SmallTreeIntel8259x (3.5.0) 8E38DEAB-C6D9-3986-926F-F1018AB0C605 <18 13 6 5 3 1>
74 0 0xffffff7f86005000 0x7000 0x7000 org.rehabman.driver.FakePCIID (1.3.15) B185B092-1FC9-308E-B093-32FD88E5822D <13 8 6 5 3 1>
 

Attachments

  • EFI.zip
    6.1 MB · Views: 94
Hi dolgarrenan:

First, thanks for the big job on this. You are helping a lot at least to me, you have made my next 5 years kind of awesome ;) Also regards to AiBeast and to the rest of the people is testing and helping as well.

For what I understand now.

We need to delete this part from the config.plist

Code:
                <dict>
                    <key>Comment</key>
                    <string>X299X - RTC</string>
                    <key>Disabled</key>
                    <false/>
                    <key>Find</key>
                    <data>oAuTU1RBUwo=</data>
                    <key>Replace</key>
                    <data>oAqRCv8L//8=</data>
                </dict>


And replace it with the SSDT RTC0 you posted in the end of your, right? Obviously we need to open it with MaciASL-DSDT, compile it and save is as binary in Acpi/Patches. (if am not mistaken)

Code:
DefinitionBlock ("", "SSDT", 2, "RTC0", "DESG10G", 0x00000000)
{
    External (_SB_.PCI0.LPCB, DeviceObj)

    Scope (_SB.PCI0.LPCB)
    {
        Device (RTC0)
        {
            Name (_HID, EisaId ("PNP0B00"))
            Name (_CRS, ResourceTemplate ()
            {
                IO (Decode16,
                    0x0070,
                    0x0070,
                    0x01,
                    0x08,
                    )
                IRQNoFlags ()
                    {8}
            })
            Method (_STA, 0, NotSerialized)
            {
                If (_OSI ("Darwin")) {
                    Return (0x0F)
                } Else {
                    Return (0);
                }
            }
        }
    }
}
 
Unfortunately I don't have a X299X motherboard, but I still have a working build with Gigabyte X299UD4 PRO , so I could provide help from this configuration , past year, in 2018 we made extensive research with @nmano and Kgp for the Thunderbolt SSDT.aml.
Hi, do you still have X299UD4 PRO? Have you succeeded with the latest Catalina? I try to install it with no success. Any help will be much appreciated. Thank you.
 
Hi, do you still have X299UD4 PRO? Have you succeeded with the latest Catalina? I try to install it with no success. Any help will be much appreciated. Thank you.
Yes, i still uses this build for two years now with RX 570 OC
I just download it but not tried yet because of Thunderbolt tests but may be this week-end : I 'll report soon
 
That is correct, remove the hotpatch and compile the acpi table with maciasl, you can save it as .dsl and .aml (dsl is for compiling and making changes the right way, editing a .aml is a bit scruffy and can lead to problems because you would have to delete certain values on order to have a clean and responsive table) but you have to in ACPI Machine Language Binary (.aml).
 
So guys, I went the trouble of trying to achieve the perfect Thunderbolt functionality with our boards as some of you may know, and it is finally here!
Screenshot 2020-04-16 at 20.14.17.png

Thunderbolt Bus is correctly loading with completely populated device tree on ioreg, and the perfect network companion below!
Screenshot 2020-04-16 at 20.17.51.png

The two Thunderbolt ports with activated Networking capabilities! Our machines are closest to a real mac than any hackintosh ever build! This wouldn't have been possible without the help from @CaseySJ, @Elias64Fr and some users in Casey's thread.

Next thing for me to do is to upload the "how to" flash our boards with the modified firmware in order to gain this amazing functionality (disassembly of the board is necessary, so have some handy tools prepared).

Flashing the firmware ins't difficult, and the equipment needed isn't even expensive, here is a link to the SPI Flasher I bought from Amazon (Spanish site, just look for SPI flasher in your Amazon).

I will update the first post once I have the "guide" finished, and also few updates regarding bootloader and a bit more. We will get back to issues too.
 
So guys, I went the trouble of trying to achieve the perfect Thunderbolt functionality with our boards as some of you may know, and it is finally here!
View attachment 462921
Thunderbolt Bus is correctly loading with completely populated device tree on ioreg, and the perfect network companion below!
View attachment 462923
The two Thunderbolt ports with activated Networking capabilities! Our machines are closest to a real mac than any hackintosh ever build! This wouldn't have been possible without the help from @CaseySJ, @Elias64Fr and some users in Casey's thread.

Next thing for me to do is to upload the "how to" flash our boards with the modified firmware in order to gain this amazing functionality (disassembly of the board is necessary, so have some handy tools prepared).

Flashing the firmware ins't difficult, and the equipment needed isn't even expensive, here is a link to the SPI Flasher I bought from Amazon (Spanish site, just look for SPI flasher in your Amazon).

I will update the first post once I have the "guide" finished, and also few updates regarding bootloader and a bit more. We will get back to issues too.

Awesome! Currently testing nvm33 on a TR AIC PCIe card. Working well but I only see one network interface. Would you mind sharing your SSDT?
 
Status
Not open for further replies.
Back
Top