Contribute
Register

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

joevt said:
You forgot to update the CRC-32c.

Code: 
open https://ravalian.com/thunderbolt/index.php
# 0) click "(OPTIONAL) Generate new Thunderbolt DROM for Z390 Designare" to change UID
# 1) click "STEP 1", to place the .dsl code in the clipboard
# 2) then paste into a new plain text file with dsl suffix (or paste into MaciASL.app)
# 3) repeat to change UID
#=========================================================================================
source /Volumes/Work/Programming/ThunderboltProjects/Scripts/ThunderboltUtil.sh
loaddslfile /Volumes/Work/Programming/ThunderboltProjects/Notes/examples/Inqnuamscriptresult.dsl
listdroms

1)
thedrom=2E0065297684880000DF1C090501690001000D00010008818002800000000882900180000000088380048001000008849003800100000585500000058650000002870B88200100640000000000038980058A504000058B5040000B0147494741425954450011025A3339302044455349474E41524500
sources:
/Volumes/Work/Programming/ThunderboltProjects/Notes/examples/Inqnuamscriptresult.dsl:\_SB.PCI0.RP05.UPSB.DSB0.NHI0._DSM:ThunderboltDROM

usedromnum 1
dumpdrom

0x01) UID: 0x0000888476296500
0x0d) Device ROM Revision: 1
0x10) Vendor ID: 0x1
0x12) Device ID: 0xD
0x14) Device Revision: 0x1
0x15) EEPROM Revision: 0
0x16)   1: 800280000000
0x1e)   2: 900180000000
0x26)   3: 800480010000
0x2e)   4: 900380010000
0x36)   5: 500000
0x3b)   6: 500000
0x40)   7:
0x42)   8: 200100640000000000
0x4d)   9: 80
0x50)   A: 504000
0x55)   B: 504000
0x5a)   1: "GIGABYTE"
0x65)   2: "Z390 DESIGNARE"
0x09) CRC32: 0x05091cdf (expected: 0x211fde47)
0x76) End

repairchecksums
makedromdsl

    "ThunderboltDROM",
    Buffer (0x76)
    {
        /* 0x00     */  0x2E,                                           // CRC8 checksum: 0x2E
        /* 0x01     */  0x00, 0x65, 0x29, 0x76, 0x84, 0x88, 0x00, 0x00, // Thunderbolt Bus 0, UID: 0x0000888476296500
        /* 0x09     */  0x47, 0xde, 0x1f, 0x21,                         // CRC32c checksum: 0x211FDE47
        /* 0x0D     */  0x01,                                           // Device ROM Revision: 1
        /* 0x0E     */  0x69, 0x00,                                     // Length: 105 (starting from previous byte)
        /* 0x10     */  0x01, 0x00,                                     // Vendor ID: 0x1
        /* 0x12     */  0x0D, 0x00,                                     // Device ID: 0xD
        /* 0x14     */  0x01,                                           // Device Revision: 0x1
        /* 0x15     */  0x00,                                           // EEPROM Revision: 0
        /* 0x16   1 */  0x08, 0x81, 0x80, 0x02, 0x80, 0x00, 0x00, 0x00,
        /* 0x1E   2 */  0x08, 0x82, 0x90, 0x01, 0x80, 0x00, 0x00, 0x00,
        /* 0x26   3 */  0x08, 0x83, 0x80, 0x04, 0x80, 0x01, 0x00, 0x00,
        /* 0x2E   4 */  0x08, 0x84, 0x90, 0x03, 0x80, 0x01, 0x00, 0x00,
        /* 0x36   5 */  0x05, 0x85, 0x50, 0x00, 0x00,
        /* 0x3B   6 */  0x05, 0x86, 0x50, 0x00, 0x00,
        /* 0x40   7 */  0x02, 0x87,
        /* 0x42   8 */  0x0b, 0x88, 0x20, 0x01, 0x00, 0x64, 0x00, 0x00, 0x00, 0x00, 0x00,
        /* 0x4D   9 */  0x03, 0x89, 0x80, // PCIe xx:04.0
        /* 0x50   A */  0x05, 0x8a, 0x50, 0x40, 0x00,
        /* 0x55   B */  0x05, 0x8b, 0x50, 0x40, 0x00,
        /* 0x5A   1 */  0x0b, 0x01, 0x47, 0x49, 0x47, 0x41, 0x42, 0x59, 0x54, 0x45, 0x00, // Vendor Name: "GIGABYTE"
        /* 0x65   2 */  0x11, 0x02, 0x5A, 0x33, 0x39, 0x30, 0x20, 0x44, 0x45, 0x53, 0x49, 0x47, 0x4E, 0x41, 0x52, 0x45, 0x00, // Device Name: "Z390 DESIGNARE"
    },
Click to expand...
Just updated!, thanks for your help
 
CaseySJ said:
  • Replace the 5 green numbers with 5 random hex numbers between 0x00 and 0xFF.
  • Then compute CRC-8 from the website linked in the guide.
  • Replace first byte with new CRC-8 value.
  • Then open the SSDT from the guide, find ThunderboltDROM section, and replace the first 9 bytes with the new bytes.
  • Save the file.
  • Replace the existing Thunderbolt SSDT with the new SSDT.
  • The Winbond chip does not have to be touched.
Click to expand...
why don't use my script? it will be very easy for him
 
Just to be sure: this procedure is only for those that have flashed the TB3 chip, correct?

Thanks,

Patrice
 
Inqnuam said:
why don't use my script? it will be very easy for him
Click to expand...
No worries. When the next version of your script is released with support for additional cards and motherboards, I'll update all of the DROM Micro-Guides.
 
CaseySJ said:
No worries. When the next version of your script is released with support for additional cards and motherboards, I'll update all of the DROM Micro-Guides.
Click to expand...
Nice, I'll add an option to change device name, but I have a question about hexs, there's limit for the characters or not?
 
MB is on its way today... and I’ll pre-order the Quantum 2626 on Monday (Canadian supplier will receive new units in mid/end of August. It is the same one for all dealers across Canada...).
 
jakemauer said:
I want to check in with my experiences with Titan Ridge cards and my 5k UltraFine display.

My hardware:
• Gigabyte Z390 Aorus Pro
• Gigabyte Titan Ridge Rev. 1 (Both unflashed and modified/flashed)
• An LG 5k UltraFine 27" Monitor
• Dual displayport output going from a 5700XT going to the Titan Ridge card.
• Catalina 10.15.5 with Opencore 0.5.9.

Behavior with an unmodified stock card on NVM 50:
1. On cold boot the BIOS and bootloader show immediately.
2. The visual/display portion of the monitor works fine when entering and using MacOS
3. None of the built-in accessories like the webcam, microphone, and even the USB-C ports work.
4. On reboot, BIOS, bootloader, and MacOS show and work, but none of the devices do.

Behavior with a pre-flashed card purchased on ebay* with a DSDT from this thread
*(I am not sure which firmware this board was flashed with. The seller only said "2nd revision of DSM2 firmware" :rolleyes: The SHA of the firmware is c608d7dec573bf385129299ef5bde21549113e46)
1. On cold boot neither the BIOS nor the bootloader show.
2. Once MacOS loads the monitor wakes up.
3. All connected devices like the webcam and USB-C ports work.
4. On reboot the BIOS and bootloader show, booting into MacOS works.

I have since bought flashing gear and the above behavior is also the same with Elias64's NVM23 firmware.

Question:
Is the behavior with the modified NVM 23 firmware and my 5K monitor the best case scenario right now? Or is there a way to get the display to turn on on cold boot AND get all of its included devices and USB ports to work?

Thank you to Elias64, CaseySJ and everyone else who has worked on getting thunderbolt 3 to work in hackintoshes.
Click to expand...
I am running the GC-Titan Ridge with patched NVM50 (@Elias64Fr/@CaseySJ) and an LG 4K UltraFine 24" monitor. I am currently running 3 monitors in my configuration. With all of my tests, I have found that with patched firmware, I must have a monitor connected directly to my GPU. My TB3 monitor will not activate during boot until it's almost completely loaded to the desktop. This is consistent with your experience. Here's a report on my latest findings:

My Latest Testing
 
Inqnuam said:
why don't use my script? it will be very easy for him
Click to expand...

i tryed to use it, but after login in my password it loads forever and i didnt came to the desktop.

(sry you wrote me a conv msg but i dont have enough post to read it :-/)
 
You must log in or register to reply here.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top