Contribute
Register

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

Attached is the GC-Titan Ridge firmware backup NVM22
 

Attachments

  • GC-Titan-Ridge-NVM22.bin.zip
    530.2 KB · Views: 106
most of the errors do not bother me, however,
(AppleACPIPlatform) AppleACPIPlatformPower Wake reason: PEG1 PEGP PEG2 PEGP PXSX RP03 PXSX RP06 PXSX RP07 PXSX RP08 PXSX PXSX RP10 PXSX RP11 PXSX RP12 PXSX RP13 PXSX RP14 PXSX RP15 P
is a constant error that occurs multiple times every hour and wakes it up each time. It's more of a headache for me above anything.
That's understandable. Quite different from a brief maintenance wake every 2 hours.
I attached my own USBMAP kext, but is the USBMAP and DSDT different? If they are different, not sure which would be causing this error
That's not a recognized file. Please compress the kext first.
 
That's understandable. Quite different from a brief maintenance wake every 2 hours.

That's not a recognized file. Please compress the kext first.

Attached compressed file and also attached DSDT dump file
 

Attachments

  • USBPorts.kext.zip
    1.8 KB · Views: 110
  • DumpLog.txt
    10.6 KB · Views: 122
@CaseySJ @Elias64Fr @scottkendall @NorthAmTransAm
Here are my results with the flashed GC-AlpineRidge card. All of these tests were done with complete power shutdown, and with resetting BIOS optimized defaults after each HW change.


Firmware Windows Functionality Mac TB3 Tree TB3Header Cable Antelope Audio Working
Orig from Box Devices stay connected for 3 seconds then disconnect None No No
Orig from Box No None Yes No
After stock GC-TBTFlash on W10 Devices connect for even less time None No No
After stock GC-TBTFlash on W10 Devices connect for even less time None Yes No
GC-AR Elias64FR-v1 None None No No

GC-AR Elias64FR-v1 None None Yes No
GC-AR Elias64FR-v2 None None No No
GC-AR Elias64FR-v2 None None Yes No


I think the BIOS on my board doesn't like when 2 TB3 controllers appear, since the card seems to not want to function like the Titan Ridge does. Also similarly, the stock firmware checksums don't match before and after updating the card with Gigabyte TBTFlash utility.

Code:
-Stock from box-
5d3eaa15ebe19c43c2417e7681dadd0492788e2a  GC-AlpineRideBackup-3.bin
-After TBTFlash Update-
4e45e9894eb504ea394cd2304c7d266a9e24d8c1  GC-AlpineRideBackup-4.bin

Attached are the stock firmware dumps I made to see if there are any differences in what everyone has been working with (doubtful).

Cheers!
 

Attachments

  • GCAR-Firmware Backups - QTG.zip
    292.1 KB · Views: 103
Attached compressed file and also attached DSDT dump file
Couple small issues with your USB map:
  • HS01 is set to 10. That's an external USB-C with a built-in switch so it should be Type 9.
  • SS01 is the USB 3 analog of HS01 so it should also be Type 9.
Your version inject USB power properties (which should be a good thing) whereas mine does not, which is why I use SSDT-USBX.aml to compensate.

I'll change HS01 and SS01 to 9 and deploy your USB kext all day today. I won't shut down the system so long term sleep behavior can be checked.
 
Couple small issues with your USB map:
  • HS01 is set to 10. That's an external USB-C with a built-in switch so it should be Type 9.
  • SS01 is the USB 3 analog of HS01 so it should also be Type 9.
Your version inject USB power properties (which should be a good thing) whereas mine does not, which is why I use SSDT-USBX.aml to compensate.

I'll change HS01 and SS01 to 9 and deploy your USB kext all day today. I won't shut down the system so long term sleep behavior can be checked.


few questions --
are you saying that i do not need to also have SSDT-USBX.aml in my EFI folder? I currently have SSDT-EC-USBX which is a combo of the SSDT-EC and SSDT-USBX amls.

Can you upload the two changes so that i can also test and see if either of those fix my issue?
-- I created the usbmap kext using hackintool so i dont believe that i have a way to change to type 9

EDIT: so I mapped HS01/SS01 as USBC because I have the NZXT h510 case with the USBC port on the top. is that not right?
 
Last edited:
What Boot Arguments are you using in config.plist. You may post a screenshot of Clover Configurator --> Boot (after opening config.plist). If you're using any shikigva value, change it to 16.

No Idea how to change my shikigva value -

here's my config - Just noticed a legacy option is selected.. I don't have an option to deselect, same as in the guide
Screen Shot 2020-03-31 at 11.16.59 AM.png
 
I created a new EFI folder for that system on a USB flash disk maybe 2 days ago using the procedure in the 10.15.4 Catalina Mini-Guide (and the files from the ZIP attached there).

I used config-AMD-GPU.plist and copied/pasted the SMBIOS/RtVariables sections from old config.plist into this file, then renamed it to config.plist.

Then I made sure MSR 0xE2 was unlocked (native NVRAM) and Clover "rc" scripts were deleted.

After booting from the USB flash disk, I verified that Catalina 10.15.4 was able to load and run just fine. Then I copied the EFI folder from USB flash disk to the EFI partition of the Catalina internal SSD.

And then today I ran the Combo Update with no issues at all. And yes those leftover install volumes are completely and totally gone.

I'm building out the USB EFI folder between other tasks. I noticed my existing acpi\patched folder did not include the nvram aml, questions on that. Is the NVRAM aml enabling the native NVRAM support and could this be the reason 10.15.4 is erring out at the end with messages about not know startup disk?
 
few questions --
are you saying that i do not need to also have SSDT-USBX.aml in my EFI folder? I currently have SSDT-EC-USBX which is a combo of the SSDT-EC and SSDT-USBX amls.

Can you upload the two changes so that i can also test and see if either of those fix my issue?
-- I created the usbmap kext using hackintool so i dont believe that i have a way to change to type 9

EDIT: so I mapped HS01/SS01 as USBC because I have the NZXT h510 case with the USBC port on the top. is that not right?
Modified file attached.

There are two settings for USB-C:
  • If you connect a USB-C device to a USB-C port, a certain row in Hackintool or a certain port in IORegistryExplorer will light up.
  • If you now eject that USB-C disk, flip it over, and reinsert it (because USB-C ports are symmetrical), does the same row or the same port light up?
    • If the same row or port lights up then it's a Type 9 device.
    • If different rows or ports light up then it's a Type 10 device.
 

Attachments

  • USBPorts-ncrispi.kext.zip
    2.8 KB · Views: 78
Hi, CaseySJ. Can you make TB firmware patches for my motherboard(Gigabyte X99 Designare-EX)? The main control of TB3 is DSL6540(Alpine Ridge). Thank you very much.
 

Attachments

  • GIGABYTE_GA_X99_Designare_EX.zip
    140.6 KB · Views: 74
Back
Top