Gigabyte Titan Ridge on Proxmox/OSX baremetal (WIP)

[fabiosun]

TB3 Device:

GC Titan Ridge

https://www.amazon.it/gp/product/B07K6PW4M1/

 

Eprom programmer:

https://www.amazon.it/gp/product/B07SNTL5V6/

 

Digital Multimeter:

https://www.amazon.it/gp/product/B0872RY4CC/

 

in this thread we can talk about progress with this latest important goal to achieve.

 

useful link:

https://github.com/ameyrupji/thunderbolt-macpro-5-1/blob/master/GC-TitanRidge.md

 

guide to flashing programming from CaseySJ

 

DISCLAIMER:

this is a very risky procedure also for experienced users.

TAKE NOTE OF THIS.

DO AT YOUR OWN RISK

 

Edited March 10, 2022 by fabiosun
rimosso un link non piu' presente

[fabiosun]

49:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
        Kernel driver in use: pcieport
4a:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
        Kernel driver in use: pcieport
4a:01.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
        Kernel driver in use: pcieport
4a:02.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
        Kernel driver in use: pcieport
4a:04.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
        Kernel driver in use: pcieport
4b:00.0 System peripheral [0880]: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] [8086:15eb] (rev 06)
        Subsystem: Gigabyte Technology Co., Ltd JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] [1458:a207]
        Kernel driver in use: vfio-pci
        Kernel modules: thunderbolt
4d:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
        Subsystem: Gigabyte Technology Co., Ltd JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [1458:a207]
        Kernel driver in use: vfio-pci
        Kernel modules: xhci_pci

More or less the same @iGPUresults and conclusion

for now not all Is "passable"

[iGPU]

9 hours ago, fabiosun said:

49:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
        Kernel driver in use: pcieport
4a:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
        Kernel driver in use: pcieport
4a:01.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
        Kernel driver in use: pcieport
4a:02.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
        Kernel driver in use: pcieport
4a:04.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
        Kernel driver in use: pcieport
4b:00.0 System peripheral [0880]: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] [8086:15eb] (rev 06)
        Subsystem: Gigabyte Technology Co., Ltd JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] [1458:a207]
        Kernel driver in use: vfio-pci
        Kernel modules: thunderbolt
4d:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev 06)
        Subsystem: Gigabyte Technology Co., Ltd JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [1458:a207]
        Kernel driver in use: vfio-pci
        Kernel modules: xhci_pci

More or less the same @iGPUresults and conclusion

for now not all Is "passable"

 

 

Yes, same issues I found earlier. Until the pci-bridge sections (49 and the 4a's) are passed, the TB device cannot function on the Mac side.

 

This presently applies to all bridged devices and is a Linux/VM limitation.

Edited July 30, 2020 by iGPU

[fabiosun]

[fabiosun]

[iGPU]

14 minutes ago, fabiosun said:

 

This looks promising!

 

For proper TB functioning, an SSDT is necessary. (I can supply one later today to test.)

 

The only problem that I see, is that to date, I've not been able to get any SSDT to change anything in the SF0 device. My SSDTs seemingly work on most other devices. (I've not written here about this SSDT matter.) I've gotten the feeling that SF0 is somehow formed after the SSDTs are loaded. Ideally, if you could try a different PCIe slot to move the device from SF0...

[fabiosun]

SSDT-TB3-RP21-4.zip

 

my problem is I have no tb device for testing 🙂

this SSDT is from site you advised me time ago where also I have found instructions to flash

[iGPU]

7 minutes ago, fabiosun said:

SSDT-TB3-RP21-4.zip 1.67 kB · 1 download

 

my problem is I have no tb device for testing 🙂

this SSDT is from site you advised me time ago where also I have found instructions to flash

 

 

I'd advise you not to flash just yet. Let's see how your TB device behaves natively. I'll work on SSDT later (I must leave house soon for several hours).

[fabiosun]

these results are with flashed rom

 

[iGPU]

28 minutes ago, fabiosun said:

these results are with flashed rom

 

 

Sorry, I misunderstood and thought native.

[fabiosun]

native was in the initial post whern you said you have had similar results..i have then flashed Elias firmware..i see all that stuf but type c I have is not seen

Asmedia controller sees it well (my proxmox booting disk is there)

 

[iGPU]

6 hours ago, fabiosun said:

native was in the initial post whern you said you have had similar results..i have then flashed Elias firmware..i see all that stuf but type c I have is not seen

Asmedia controller sees it well (my proxmox booting disk is there)

 

 

Attached are 2 SSDT-TB. One is set up for SF0 (0x03 as shown in image above). The other is set for S80 at 0x01. Both have descriptions of PCIe slot 4 (but this is description and does not affect function; can be changed inside file).

 

As I mentioned, I've never seen SF0 properly rename using an SSDT on these TRX40 mobos. Also, sometimes, when trying to re-name a device in SF0, the macOS would not boot, so keep an alternative boot EFI (which I know you do!).

 

 

SSDT-TRX40-TB-candidates-v2.zip

Edited July 31, 2020 by iGPU
S80 needed to be 0x00 not 0x01

[fabiosun]

I have reverted before this your message to latest 50 version  not patched firmware for Titan Ridge
In windows same behaviour

I am asking I f there is a way to understand if my TB header pached cable is working or not and if also USB2.0 connection is working

 

[fabiosun]

and this below are my IOREG screenshots without patching the card:

 

@iGPU do you advice to use patched one named:

GC-TITAN-RIDGE-NVM23-Elias64Fr.bin ?

 

or stay with latest not patched one?

Thank you

 

[iGPU]

I would not re-flash. What you have looks good. Also, USB-2 usually does not work on TB ports (don't bother testing; un-important for us).

 

The next step is trying to get an SSDT to work. But first let me describe the TB features seen in a properly working setup. (I sourced the images off the internet, so not mine as I'm working on different computer; I'll update once I locate better images). These features depend upon a good SSDT to show up.

 

First, you want to see the following in a TB tree when using IORegistryExplore (the device shown is at RP05; this can differ for our mobos). There are a few important features: sections DSB0-DSB4, where DSB0 contains NHI (actual TB) and DSB2 contains the USB section (ideally 2 parts for AIC). IOThuderboltPort@7 (this is for TitanRidge; it will differ for other chips; eg, Alpine Ridge uses Port@5) is also important for proper TB behavior.

 

 

 

 

IOThuderboltPort@7:

 

 

Next, for proper TB behavior, you should see entries in the following 3 areas in the System Information window.

 

A. PCI slot pane: notice that there are entries for TB and TB-USB. These are injected through the SSDT.

 

B. PCI TB. This section, even with marginally functioning TB will often be empty ("No Thunderbolt devices."). However, if a proper SSDT with flashed firmware and you'll see an entry as below. Also, the speed of the device should be 40GB/sec.

 

Link Speed is adjusted to 40 with this SSDT entry: 

 

 

C. TB-USB. If TB and TB-USB is properly working, you'll now see a TB bridge entry in the PCI-USB pane as shown below.

 

If a device, like a TB external HD is connected, then the following will appear::

 

 

 

 

Edited July 31, 2020 by iGPU
Updated images.

[fabiosun]

@iGPU I have to synch my area location time with yours 🙂

I have reflashedto start with a complete (more complete Output)

I have a reference Korey of a X299 board and naming apart it is pretty similar to mine

 

Point A,B,C seems to have some problem with pictures

 

[fabiosun]

[iGPU]

32 minutes ago, fabiosun said:

@iGPU I have to synch my area location time with yours 🙂

 

Point A,B,C seems to have some problem with pictures

 

 

I updated the images, so please re-fresh page to view. (And yes, we must sync our times! But now, I'm off to work...)

[iGPU]

48 minutes ago, fabiosun said:

 

Which firmware flash are you using for these latest images? (I recall having used GC-TITAN-RIDGE-NVM23-Elias64Fr.bin, but some of these firmwares have been updated since I last flashed any cards.)

 

Also, specifically, what VM instructions are you using and passing-through for the TB device?

 

And are you blacklisting any TB items (I know you normally do not, but just checking for completeness)?

 

(I'll re-test my TB cards this weekend.)

Edited July 31, 2020 by iGPU

[fabiosun]

@iGPU

first is stock firmware updated to v50 (my Titan came wit v43 on board

right one is with v23 patched firmware (it seems the same you tested

 

to answer to your latter questions:

 

0)

hostpci12: 4b:00

hostpci13: 4d:00

 

1)

no

 

then I have this output for LSPCI -nnk (Thunderbolt/Proxmox related):

 

Spoiler

49:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06)
        Kernel driver in use: pcieport
4a:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev ff)
        Kernel driver in use: pcieport
4a:01.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev ff)
        Kernel driver in use: pcieport
4a:02.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev ff)
        Kernel driver in use: pcieport
4a:04.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev ff)
        Kernel driver in use: pcieport
4b:00.0 System peripheral [0880]: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] [8086:15eb] (rev ff)
        Kernel driver in use: vfio-pci
        Kernel modules: thunderbolt
4d:00.0 USB controller [0c03]: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] [8086:15ec] (rev ff)
        Kernel driver in use: vfio-pci
        Kernel modules: xhci_pci

 

my first goal is to see a device connected (an external usb type case with a disk)

Before I was saying about USB because we have to connect to an internal USB our card) and my internal one are not working in HighSierra

i am installing Catalina by now because it has a better management and support for our new motherboard USB

 

Or do you think without completing with a proper SSDT I can't see also a simple usb connection?

 

[fabiosun]

PS A and B i have as you shown without using a SSDT

first part is achievable with:

 

 JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018]    Generic system perip System peripheral    pci8086,15eb@15 pci8086,15eb

PciRoot(0x1)/Pci(0x1E,0x0)/Pci(0x3,0x0)/Pci(0x15,0x0) 

JHL7540 Thunderbolt 3 USB Controller [Titan Ridge  Serial bus controlle USB controller       pci8086,15ec@16 pci8086,15ec    

PciRoot(0x1)/Pci(0x1E,0x0)/Pci(0x3,0x0)/Pci(0x16,0x0) 
 

and I miss this thunderbolt 7 that I have empty :

 

 

 

 

Edited July 31, 2020 by fabiosun
Add my empty TB port 7

[iGPU]

4 hours ago, fabiosun said:

@iGPU

first is stock firmware updated to v50 (my Titan came wit v43 on board

right one is with v23 patched firmware (it seems the same you tested

 

my first goal is to see a device connected (an external usb type case with a disk)

Before I was saying about USB because we have to connect to an internal USB our card) and my internal one are not working in HighSierra

i am installing Catalina by now because it has a better management and support for our new motherboard USB

 

Or do you think without completing with a proper SSDT I can't see also a simple usb connection?

 

 

 

USB-C works well off TB3 (just not USB-2), and can use the less expensive USB-C cables (note: USB-C and TB cable have same connection and look the same, but are not the same).

 

I think you can get USB-C connection without SSDT (but I am not absolutely certain; too long since I tried: I can test on another machine this weekend to verify).

[iGPU]

I don't have a free Titan Ridge card to test, but I do have an available, flashed Alpine Ridge TB3 card. Placing it in slot 4 (farthest from CPU), gives an entry in to SF0, but very incomplete. I provided an SSDT which loaded (see other image), but it did not affect the AR card. I'll try some variations of the SSDT file.

 

Pathetic TB tree and how it should be labelled with SSDT (but SF0 should be a device like RP21, not UPSB):

 

 

Display loaded ACPIs (command: log show --last boot | grep ACPI ) 

Edited August 1, 2020 by iGPU
Incorrect device location for TB3

[fabiosun]

@iGPUwsiting for your test

i think problem is inside OS X 

I can see in ovmf bios usbc disk connected on ridge via usb c cable

but no in booted OS X 

but, also in windows I can’t see it

so maybe multiple problems or disk is not good for Titan ridge

by the way on ASMedia 3.2 usb I can see on all systems (Linux, OS X, windows)

[iGPU]

13 minutes ago, fabiosun said:

@iGPUwsiting for your test

 

but, also in windows I can’t see it

 

 

Once you flash a TB card, it won't work in Windows.