Gigabyte X299X - Catalina Support

[oreoapple]

Hi @TheBloke ,

I'm using your F3C BIOS config and I noticed that @dolgarrenan[/USER]'s config has 'Above 4G' disabled. I think we are supposed to have it enabled right?
I also try dolgarrenan's TB3 SSDT, still the same behavior. I will continue to debug.

Hi @oreoapple - I'm afraid I'm not a good person to help with anything related to TB3. I still don't actually have any TB3 devices, and for that reason I haven't yet tried the firmware flashing. I've tested that the TB3 ports work as USB3 ports, and that's it. And because I haven't yet done the firmware flashing, my About This Mac -> Thunderbolt section is empty.

The SSDT in the EFI I uploaded is identical to the one provided by @dolgarrenan in his OP. I can see from the screenshot in the first post that his Thunderbolt section does say "40Gb/s x1", so yes I suppose seeing 20Gb x 2 is different and perhaps wrong. But I'm afraid I couldn't tell you why.

The only thing that does occur to me is to check your Thunderbolt BIOS settings. Do you have "SL0-No Security" set? And what values do you have for the other parameters? I believe "No security" is definitely important, but I don't know about the other options - but when I applied dolgarrenan's BIOS profiles I did notice he had some non-default values, eg I seem to recall he had Reserved I/O set to 8 (default is 0).

I have no idea if they could affect this, but you could try:

1. Saving your current BIOS settings to a profile.
   1. I normally save two: one to internal memory, one to USB; the internal memory profile is more convenient, but it gets lost if you swap to the secondary BIOS or re-flash the BIOS, whereas the USB copy can be retrieved any time.
2. Loading dolgarrenan's BIOS profile - he's uploaded two in this thread, one for BIOS F3B, one for F3C.
3. Taking a note of his Thunderbolt settings.
   1. Or capture a screenshot by hitting F12 (requires a FAT16/FAT32 formatted USB stick.)
4. Reload your profile, and adjust your Thunderbolt settings to match his.

As and when I get a TB3 device I'll try the firmware flash and report back, but that's unlikely to be until the new year so hopefully you'll have it fixed long before then!

 

[TheBloke]

Hi @TheBloke ,

I'm using your F3C BIOS config and I noticed that @dolgarrenan[/USER]'s config has 'Above 4G' disabled. I think we are supposed to have it enabled right?
I also try dolgarrenan's TB3 SSDT, still the same behavior. I will continue to debug.

Yeah, I have to have Above 4G = Enabled, otherwise my USB and Ethernet ports don't work. And enabled is the default recommended setting on our platform. I don't know why he had it disabled - maybe because in the early days of the thread he was using Clover, which might have had a special patch or something.

 

[Ellybz]

I also have Above 4G disabled. Mostly depends on your GPU or/& if you use 32-bit Apps/OS. It has always been disabled on my system ( Clover & OpenCore ). As I only use my system for audio related tasks & without intensive video processing, I don't need the Above 4G quirk. If you have a high end GPU or the newer NAVI cards, you probably need it.

No issues reported on USB or ethernet with Above 4G disabled.

PS: @TheBloke : Good job on solving the NVRAM related issue with Big Sur & Asrock/MSI X299.

 

[JTR]

As promised, here is my fork of OpenCore 0.6.4 with the patch for our board's boot failure issues: https://github.com/jacobbaratta/OpenCorePkg/tree/x299x-designare-10g_0.6.4

I've attached pre-built binaries for debug/release builds as of commit 5263e7e06999eeddbffcc7f9752f271a402796ba. I've successfully tested the debug build, but I haven't bothered with testing the release build yet.

Please test this and provide feedback!

I have yet to start work on turning this into a quirk (or alternatively, into a fully configuration-based implementation of paths to veto), but that's still on my todo list, and I do intend to finish that work and submit a PR to the upstream repo in the near future.

---

I received a reply from Gigabyte on my support ticket(s) last week, which was somehow even worse than expected:

Dear customer,

Basically we don't have such know issue reported by our system builders. So far latest bios posted on website is F3C, we don't have other newer bios available currently, You may check back later, once new bios available will post on website.

Best regards,

GIGABYTE technical support team.

When I find some time I'll be following up with the two alternate contacts I identified previously to attempt to raise this issue through alternative channels, as it's quite clear that their support is not going to be useful at all here. TBH I'm a bit shocked that they blew me off completely like this when I handed them a bug report with this level of detail and multiple PoCs...

 

[oreoapple]

Hi @dolgarrenan

I flashed the TB3 firmware with DESIGNARE-Z390-NVM33-Elias64Fr.bin
So I need to use your SSDT-X299X-DESIGNARE10G-THUNDERBOLT-SIMPLIFIED.aml to get full TB3 function right?
I tried SSDT-X299X-DESIGNARE10G-THUNDERBOLT.aml in you EFI OC folder and I only get 20gb/s x 2 in 'Thunderbolt' section, not 40gb/s x 1.

 

[oreoapple]

Hi @AlBeast

I also flash the firmware but I only see speed of 20gb/s x 2 in my 'thunderbolt' section.
What speed do you get? Could you post a screen shot?

I'm still having some trouble with this X299X build. I SPI programmed the TB chip with the Z390 firmware successfully and added the custom generated Z390 aml file to OC/ACPI.

It works well, only I consistently get a kernel panic -> reboot when cold booting, during loading. After this kernel panic, the system restarts and and boots successfully into macOS.

If I turn on the Apollo X4 when in macOS after a cold boot, it also freezes and restarts due to kernel panic.

So, in essence, I would argue it's working well, but it's annoying to have a to reboot every time the system is started the first time.

I've added the log files, hopefully someone has an idea.

PS: Happens on both ports. Flashing process was fine, as far as I can tell, due to checking back then, and TB information loading in System Profiler.

 

[dolgarrenan]

Hi @dolgarrenan

I flashed the TB3 firmware with DESIGNARE-Z390-NVM33-Elias64Fr.bin
So I need to use your SSDT-X299X-DESIGNARE10G-THUNDERBOLT-SIMPLIFIED.aml to get full TB3 function right?
I tried SSDT-X299X-DESIGNARE10G-THUNDERBOLT.aml in you EFI OC folder and I only get 20gb/s x 2 in 'Thunderbolt' section, not 40gb/s x 1.

Hello @oreoapple sorry to get back to you so late, yes, you need to use the simplified version of the SSDT, but let me point you in the right direction. You need to go follow steps on this link to be able to create your own SSDT, the tool was created by @CaseySJ for his build and has been the tool of my choice since we started this whole project.

His Z390 post has so much information about TB and flashing that is hard not to even find more info about other related stuff.

Hope this helps , going back to my next project guys, hope I can be around to help a little more

 

[dolgarrenan]

As promised, here is my fork of OpenCore 0.6.4 with the patch for our board's boot failure issues: https://github.com/jacobbaratta/OpenCorePkg/tree/x299x-designare-10g_0.6.4

I've attached pre-built binaries for debug/release builds as of commit 5263e7e06999eeddbffcc7f9752f271a402796ba. I've successfully tested the debug build, but I haven't bothered with testing the release build yet.

Please test this and provide feedback!

I have yet to start work on turning this into a quirk (or alternatively, into a fully configuration-based implementation of paths to veto), but that's still on my todo list, and I do intend to finish that work and submit a PR to the upstream repo in the near future.

---

I received a reply from Gigabyte on my support ticket(s) last week, which was somehow even worse than expected:

When I find some time I'll be following up with the two alternate contacts I identified previously to attempt to raise this issue through alternative channels, as it's quite clear that their support is not going to be useful at all here. TBH I'm a bit shocked that they blew me off completely like this when I handed them a bug report with this level of detail and multiple PoCs...

I also got in contact with GB a long way back and their response was very similar, they said they had no reports of the issue and that their BIOS where working as expected :/

 

[AlBeast]

[..]
I received a reply from Gigabyte on my support ticket(s) last week, which was somehow even worse than expected:
[..]

First off, thanks for your work on getting this board to work better! Secondly... yeah... that's Gigabyte's support quality for you. @dolgarrenan knows exactly what it's like

I'll report when I get to test the files, but it won't be very soon, sorry.

 

[oreoapple]

Hi @dolgarrenan

I tried your SSDT and also the SSDT from hackindrom but I still don't get 40gb/s x 1, very strange...
Could you take a look at my EFI and give some advices? Thanks!
I disable a few SSDT just to see if it helps, still no luck...

Hello @oreoapple sorry to get back to you so late, yes, you need to use the simplified version of the SSDT, but let me point you in the right direction. You need to go follow steps on this link to be able to create your own SSDT, the tool was created by @CaseySJ for his build and has been the tool of my choice since we started this whole project.

His Z390 post has so much information about TB and flashing that is hard not to even find more info about other related stuff.

Hope this helps , going back to my next project guys, hope I can be around to help a little more