Jump to content

Gigabyte Titan Ridge on Proxmox/OSX baremetal (WIP)


Recommended Posts

I tried connecting my iPhone to a USB-C port and it was not detected. So I wouldn't hold my hopes high on USB, but hoping to get the TB working at full speed. Unfortunately, the ROM I flashed (A Designare 390Z onboard rom) is not liked by Linux. I wonder if NVM23 modified by elias64fr has the same issue. It'd be nice to have TB working in both the Mac and the VM so I can pass-through leaf PCIE devices when in VM (since we can't seem to make the PCI bridge passthrough there).

 

Linux gives this error for now: thunderbolt 0000:8d:00.0: could not start ICM firmware

 

but the devices are detected in lspci.

 

root@designare:~# lspci -vv | grep Thunderbolt
8b:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) (prog-if 00 [Normal decode])
        Capabilities: [ac] Subsystem: Gigabyte Technology Co., Ltd JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
8c:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) (prog-if 00 [Normal decode])
        Capabilities: [ac] Subsystem: Gigabyte Technology Co., Ltd JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
8c:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) (prog-if 00 [Normal decode])
        Capabilities: [ac] Subsystem: Gigabyte Technology Co., Ltd JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
8c:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) (prog-if 00 [Normal decode])
        Capabilities: [ac] Subsystem: Gigabyte Technology Co., Ltd JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
8c:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) (prog-if 00 [Normal decode])
        Capabilities: [ac] Subsystem: Gigabyte Technology Co., Ltd JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
8d:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] (rev 06)
        Subsystem: Gigabyte Technology Co., Ltd JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018]
a3:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] (rev 06) (prog-if 30 [XHCI])
        Subsystem: Gigabyte Technology Co., Ltd JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018]

Edited by meina222
Link to post
Share on other sites
16 hours ago, meina222 said:

I think I need @iGPU's help as I have no idea how this SSDT is supposed to work.

 

I tried compiling one based on the link above, matching my ROM and my PCI path, but it doesn't seem to have any effect.

 

Attaching IOReg and SSDT I tried to use. @iGPU - any input on SSDT is much appreciated. For me this is right now pattern matching without really understanding the details. 

 

SSDT-TBOLT3-2.aml.zip 1.71 kB · 1 download MyMacPro.zip 7.28 MB · 1 download

 

Try this one and let me know what happens.

 

As I've said, USB does not presently work on this build. I'm in contact with people (such as CaseySJ) and it will take time. In the meantime, the TB functionality is excellent and this is the main point of the TB card. (After all, we do have many USB ports on the main mobo, so we're not exactly suffering from USB shortages.)

 

SSDT-TBOLT3-v3.aml.zip

Edited by iGPU
  • Like 1
Link to post
Share on other sites
  • Supervisor

I agree @iGPU but I would like to see this in mine 🙂

589535787_ScreenShot2020-09-06at07_37_50.png.77699d0260b4d64eb7a6a4075fa32a14.png.c343f4d178455df98398186ddd001d67.png

 

@meina222 not sure in linux , but a flashed card loose its functionality in Windows

 

about of your iPhone USBC test

have you done a cold boot with it connected?

without a proper SSDT hot plug does not work..I think

 

  • Like 1
Link to post
Share on other sites

@iGPU, I applied the SSDT you shared (after DTGP and a few others). Didn't get reflected in IOReg. Here is what the logs says. 1st spoiler is showing that the table by CASEY is loaded.

 

But a bit further down I have ACPI error - AE_NOT_FOUND, SSDT:TBTITAN.

 

I don't know ACPI well to know if this is BIOS or SSDT issue, but I think I tried very similar structure yesterday following guides so maybe not SSDT bug?

 

 

 

Spoiler

 


2020-09-06 10:06:53.862314-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI:
2020-09-06 10:06:53.862314-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI:
2020-09-06 10:06:53.862342-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) SSDT 0x0000000069A97000 000893 (v02 CASEY  TBTTITAN 00000000 INTL 20200110)
2020-09-06 10:06:53.862343-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) SSDT 0x0000000069A97000 000893 (v02 CASEY  TBTTITAN 00000000 INTL 20200110)
2020-09-06 10:06:53.862671-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)
2020-09-06 10:06:53.862671-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)

 

2

Spoiler

 


020-09-06 10:06:53.898966-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.898967-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.899041-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [WT1A]
2020-09-06 10:06:53.899041-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [WT1A]
2020-09-06 10:06:53.899078-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_ALREADY_EXISTS
2020-09-06 10:06:53.899079-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_ALREADY_EXISTS
2020-09-06 10:06:53.899345-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload-462)
2020-09-06 10:06:53.899346-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload-462)
2020-09-06 10:06:53.899493-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
2020-09-06 10:06:53.899494-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
2020-09-06 10:06:53.899710-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) During name lookup/catalog
2020-09-06 10:06:53.899710-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) During name lookup/catalog
2020-09-06 10:06:53.899870-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psobject-310)
2020-09-06 10:06:53.899871-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psobject-310)
2020-09-06 10:06:53.900055-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
2020-09-06 10:06:53.900056-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
2020-09-06 10:06:53.900272-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) (SSDT:SHAKTOOH) while loading table
2020-09-06 10:06:53.900272-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) (SSDT:SHAKTOOH) while loading table
2020-09-06 10:06:53.900487-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-319)
2020-09-06 10:06:53.900488-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-319)
2020-09-06 10:06:53.901190-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.901190-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.901264-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [_SB_.SOD2.D2A2]
2020-09-06 10:06:53.901265-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [_SB_.SOD2.D2A2]
2020-09-06 10:06:53.901363-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_NOT_FOUND
2020-09-06 10:06:53.901364-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_NOT_FOUND
2020-09-06 10:06:53.901602-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload-292)
2020-09-06 10:06:53.901603-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload-292)
2020-09-06 10:06:53.901752-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND,
2020-09-06 10:06:53.901753-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND,
2020-09-06 10:06:53.901937-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) During name lookup/catalog
2020-09-06 10:06:53.901937-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) During name lookup/catalog
2020-09-06 10:06:53.902096-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psobject-310)
2020-09-06 10:06:53.902097-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psobject-310)
2020-09-06 10:06:53.902280-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND,
2020-09-06 10:06:53.902281-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND,
2020-09-06 10:06:53.902466-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) (SSDT:TBTTITAN) while loading table
2020-09-06 10:06:53.902467-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) (SSDT:TBTTITAN) while loading table
2020-09-06 10:06:53.902683-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-319)
2020-09-06 10:06:53.902684-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-319)
2020-09-06 10:06:53.903604-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.903605-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.903664-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) 2 table load failures, 16 successful
2020-09-06 10:06:53.903665-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) 2 table load failures, 16 successful
2020-09-06 10:06:53.903823-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-342)
2020-09-06 10:06:53.903823-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-342)

 

 

 

Attached is System DSDT (before SSDT apply)

SystemDSDT.zip

Edited by meina222
Link to post
Share on other sites
32 minutes ago, meina222 said:

@iGPU, I applied the SSDT you shared (after DTGP and a few others). Didn't get reflected in IOReg. Here is what the logs says. 1st spoiler is showing that the table by CASEY is loaded.

 

But a bit further down I have ACPI error - AE_NOT_FOUND, SSDT:TBTITAN.

 

I don't know ACPI well to know if this is BIOS or SSDT issue, but I think I tried very similar structure yesterday following guides so maybe not SSDT bug?

 

 

 

  Hide contents

 



2020-09-06 10:06:53.862314-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI:
2020-09-06 10:06:53.862314-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI:
2020-09-06 10:06:53.862342-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) SSDT 0x0000000069A97000 000893 (v02 CASEY  TBTTITAN 00000000 INTL 20200110)
2020-09-06 10:06:53.862343-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) SSDT 0x0000000069A97000 000893 (v02 CASEY  TBTTITAN 00000000 INTL 20200110)
2020-09-06 10:06:53.862671-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)
2020-09-06 10:06:53.862671-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)

 

2

  Hide contents

 



020-09-06 10:06:53.898966-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.898967-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.899041-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [WT1A]
2020-09-06 10:06:53.899041-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [WT1A]
2020-09-06 10:06:53.899078-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_ALREADY_EXISTS
2020-09-06 10:06:53.899079-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_ALREADY_EXISTS
2020-09-06 10:06:53.899345-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload-462)
2020-09-06 10:06:53.899346-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload-462)
2020-09-06 10:06:53.899493-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
2020-09-06 10:06:53.899494-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
2020-09-06 10:06:53.899710-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) During name lookup/catalog
2020-09-06 10:06:53.899710-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) During name lookup/catalog
2020-09-06 10:06:53.899870-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psobject-310)
2020-09-06 10:06:53.899871-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psobject-310)
2020-09-06 10:06:53.900055-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
2020-09-06 10:06:53.900056-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_ALREADY_EXISTS,
2020-09-06 10:06:53.900272-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) (SSDT:SHAKTOOH) while loading table
2020-09-06 10:06:53.900272-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) (SSDT:SHAKTOOH) while loading table
2020-09-06 10:06:53.900487-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-319)
2020-09-06 10:06:53.900488-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-319)
2020-09-06 10:06:53.901190-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.901190-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.901264-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [_SB_.SOD2.D2A2]
2020-09-06 10:06:53.901265-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [_SB_.SOD2.D2A2]
2020-09-06 10:06:53.901363-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_NOT_FOUND
2020-09-06 10:06:53.901364-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  Namespace lookup failure, AE_NOT_FOUND
2020-09-06 10:06:53.901602-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload-292)
2020-09-06 10:06:53.901603-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/dswload-292)
2020-09-06 10:06:53.901752-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND,
2020-09-06 10:06:53.901753-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND,
2020-09-06 10:06:53.901937-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) During name lookup/catalog
2020-09-06 10:06:53.901937-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) During name lookup/catalog
2020-09-06 10:06:53.902096-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psobject-310)
2020-09-06 10:06:53.902097-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/psobject-310)
2020-09-06 10:06:53.902280-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND,
2020-09-06 10:06:53.902281-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Exception: AE_NOT_FOUND,
2020-09-06 10:06:53.902466-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) (SSDT:TBTTITAN) while loading table
2020-09-06 10:06:53.902467-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) (SSDT:TBTTITAN) while loading table
2020-09-06 10:06:53.902683-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-319)
2020-09-06 10:06:53.902684-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-319)
2020-09-06 10:06:53.903604-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.903605-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:
2020-09-06 10:06:53.903664-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) 2 table load failures, 16 successful
2020-09-06 10:06:53.903665-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) 2 table load failures, 16 successful
2020-09-06 10:06:53.903823-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-342)
2020-09-06 10:06:53.903823-0400 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform)  (20160930/tbxfload-342)

 

 

 

Attached is System DSDT (before SSDT apply)

SystemDSDT.zip 14.78 kB · 0 downloads

 

I'll look this over.

Edited by iGPU
Link to post
Share on other sites

I see the error and didn't notice first time when reviewing your SSDT: you have typos.

 

Replace the "O" (ohs) with "0" (zeros). Notice how D0CA is correct: zeros have a slash through the symbol; the capital letter "O" does not. So SOD2 --> S0D2.

 

403790500_ScreenShot2020-09-06at8_01_30AM.png.0a6c77878e9880fe74f578015ac31757.png

 

(This seems to be an American problem: people here say for 405: "four-oh-five", instead of saying "four-zero-five". I believe that this leads to such typos.)

 

 

Edited by iGPU
  • Like 1
Link to post
Share on other sites

image.png.47b24d17e6ead7b7b2cff14698085f89.png

 

I often make this mistake and have the habit of double checking while typing, but not this time.

 

IOReg w fix attached. It's now structured as coded. Thanks! On to testing some functionality.

MyMacPro.zip

 

System Report:

 

Thunderbolt Bus 3:

  Vendor Name:	GIGABYTE
  Device Name:	Mac Pro
  UID:	0xA082E226C821B763
  Route String:	0
  Firmware Version:	33.0
  Domain UUID:	3AC728ED-EC64-447D-9971-23EAADD8D456
  Port:
  Status:	No device connected
  Link Status:	0x7
  Speed:	Up to 40 Gb/s x0
  Current Link Width:	0x1
  Receptacle:	1
  Link Controller Firmware Version:	1.99.0
  Port:
  Status:	No device connected
  Link Status:	0x7
  Speed:	Up to 40 Gb/s x0
  Current Link Width:	0x1
  Receptacle:	1
  Link Controller Firmware Version:	1.99.0
  Port:
  Status:	No device connected
  Link Status:	0x7
  Speed:	Up to 40 Gb/s x0
  Current Link Width:	0x1
  Receptacle:	2
  Link Controller Firmware Version:	1.99.0
  Port:
  Status:	No device connected
  Link Status:	0x7
  Speed:	Up to 40 Gb/s x0
  Current Link Width:	0x1
  Receptacle:	2
  Link Controller Firmware Version:	1.99.0

 

Edited by meina222
  • +1 1
Link to post
Share on other sites
7 minutes ago, meina222 said:

image.png.47b24d17e6ead7b7b2cff14698085f89.png

 

I often make this mistake and have the habit of double checking while typing, but not this time.

 

IOReg w fix attached. It's now structured as coded. Thanks! On to testing some functionality.

MyMacPro.zip 7.29 MB · 0 downloads

 

Hey, this is NOT fair!!

 

You've got USB-C activated!!

 

If you now load up Hackintool, you'll see XHC5 (I re-named it so that it will be distinguished from other XHCx devices).

 

149471811_ScreenShot2020-09-06at9_02_23AM.png.f9e6cb62f69e922c18aee58b3e8acdf1.png

 

Edited by iGPU
Link to post
Share on other sites
Just now, fabiosun said:

685004556_ScreenShot2020-09-06at18_03_21.png.0f4312cacbb8f69caf8a127811fa9288.png

 

I would like to have this 🙂

why @iGPUwe do not have it?

maybe a different patched firmware?

or Gigabyte does this better than MSI?

I think he has USB exposed also without SSDT

 

 

I think it's because GB Designare is made to support TB. I think it has to do with power being injected, which is an area I've been studying. It might be possible using a custom DSDT.

Link to post
Share on other sites
  • Supervisor
3 minutes ago, meina222 said:

I don't think it works. Don't have a proper USB-C device to check so use my iPhone w a USB-C cable. It doesn't trigger any change in IOReg unlike onboard USB-C ports.

I have proper usb..but I have not that beautiful ioreg you have 🙂

 

@meina222 @igpu have given with his word this idea to my desperate puppies 🙂 🙂

 

are you connecting thunderbolt header to your motherboard? also your usb cable?

could you do a test without?

only for the science and for my puppies crying 🙂

 

 

  • Like 1
Link to post
Share on other sites

Might be the NVM33 rom. I don't think the Designare does anything special but who knows. I'm guessing it's the ROM but I have no experience in this area. I may experiment some more and flash back to NVM23 mod to see if Linux likes it better and will share. On the other hand a pretty IOReg is not so worthy without function :).

 

Edit: FWIW that USB-C does charge my iPhone so not a complete waste 😂

 

Forgot to say - I also don't connect that TB to internal motherboard header as I only have two USB 2.0 headers. One is taken by the front USB hub of the case, the other by the Bluetooth PCI card I got. So I fished a USB adapter cable like this one https://www.amazon.com/CRJ-9-Pin-Dupont-Header-Single/dp/B07Q4QZW57/ref=sr_1_12?dchild=1&keywords=usb+2.0+adapter+cable+9+pin&qid=1599408979&s=electronics&sr=1-12 to one of my rear USB 2.0 ports. So TB is connected to cable, connected to USB 2.0 port and not internal hub. Not sure if it matters.

Edited by meina222
Link to post
Share on other sites
  • Supervisor

ops..which rom exactly have you used

please say 23 not others I do not want to enter in my big loop of flashing this poor card again 🙂 🙂

Thank you

 

by the way you have a lightning cable to usb C?

Or iPhone cable is compatible with TB's usb c at all?

 

  • Like 1
Link to post
Share on other sites

I sat down yesterday and read a thread on MacRumors. Several people there claimed "DESIGNARE-Z390-NVM33-Elias64Fr.bin" which is taken from the actual onboard controller of the GB motherboard in the name of the file, to be the "best" as it solved some issues, but details were lacking as to why it was best. So I just decided to try this 1st (actually I flashed NVM23 and verified it is detected but never tested it with SSDT or Linux). If NVM23 is better with Linux, I'd prefer that and delete the USB tree, which I don't really need.

 

The holy grail for me would be - attach leaf devices and pass through to VM and have native TB 40gbs in Bare Metal on same firmware.

Edited by meina222
Link to post
Share on other sites
10 minutes ago, meina222 said:

Might be the NVM33 rom. I don't think the Designare does anything special but who knows. I'm guessing it's the ROM but I have no experience in this area. I may experiment some more and flash back to NVM23 mod to see if Linux likes it better and will share. On the other hand a pretty IOReg is not so worthy without function :).

 

Edit: FWIW that USB-C does charge my iPhone so not a complete waste 😂

 

Forgot to say - I also don't connect that TB to internal motherboard header as I only have two USB 2.0 headers. One is taken by the front USB hub of the case, the other by the Bluetooth PCI card I got. So I fished a USB adapter cable like this one https://www.amazon.com/CRJ-9-Pin-Dupont-Header-Single/dp/B07Q4QZW57/ref=sr_1_12?dchild=1&keywords=usb+2.0+adapter+cable+9+pin&qid=1599408979&s=electronics&sr=1-12 to one of my rear USB 2.0 ports. So TB is connected to cable, connected to USB 2.0 port and not internal hub. Not sure if it matters.

 

Some users have reported that TB header not needed. USB-2 connection and the power connections are optional (the latter for supplying charging, so maybe connecting iPhone not a good idea as it will require over 1A). A better thing to connect to test is a USB-C SSD.

 

In reading your posts, it said you initially flashed NVM23 and implied you flashed NVM33 over that. I've used NVM33 for Titan Ridge cards. I don't think from tests (I've been involved with CaseySJ's work since he started), that 23 or 33 will adversely affect USB function.

 

In looking over your DSDT file, it is very similar to the MSI DSDT. I've not yet located anything in it that would suggest a more robust USB response to our SSDTs.

Link to post
Share on other sites

@iGPU - precisely. I never had exposure to this TB problem so I spend 2 hours reading stuff yesterday. Then I flashed NVM23 as suggested by @fabiosun, put it in the PCI slot 4 and checked Bare Metal was fine. But then I came across a post claiming quote

 

3, 6 are both patched versions of NVM33 taken from the onboard titan ridge controller in a gigabyte designaire motherboard. Having tested all firmwares on my titan ridge AIC this is the best of them all by a long way. Both thunderbolt ports work with hot plug (complex devices that requires macOS to load drivers will still require a warm reboot) and others have reported that the display passthrough works best on this version as well. 

 end quote (you can find it on macrumors) and of course I thought to myself that I'd regret if I didn't have the "best" rom so while everything was still set-up with the flasher, I took card out and re-flashed. I don't understand or know why NVM33 is better (if at all).

 

I remember I saw another "source" promoting this NVM33 firmware (and a few others saying it's best for ver 1.0 TB AIC which I have):

 

https://www.insanelymac.com/forum/topic/335193-help-installing-mojave-on-xeon-w-2175-and-asus-ws-c422-mobo/?page=26

 

 

@IGPU, indeed Hackintool has XHC5. I need to get external back-up drive for all the VMs and other disks so I'll shop for both USB-C and TB drives soon now that I am finally able to use this AIC. Will report results when I have the hardware.

 

image.png.0184abb71faf9c5f6be2a9b247910c84.png

 

 

Edited by meina222
Link to post
Share on other sites

Yes, I connect to the TB header on the motherboard.

 

When you start actual testing things don't looks so rosy. I have a TB 3 display (proper not USB-C ) with fully rated TB cable. When I connected the GPU to the TB card with a DP to mini DP bridge cable and then the monitor to TB port, PC won't even boot - BIOS error code 61 (NVRAM initialization). Not sure what this is about but maybe this NVM33 rom is not so nice for me. I enabled above 4G - same issue. I did try to increase memory per port in BIOS for TB - wonder if this is it. Back to DP, boot error is gone.

 

Wonder if this is related to the Linux firmware error. Maybe the flash was not so good.

 

I also run a GB beta BIOS. Who knows if Slot 4 is indeed tested. The only way to find out is to reflash back to default and try. Sigh 😞

Edited by meina222
Link to post
Share on other sites
20 minutes ago, fabiosun said:

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

 

I bought this to test

but if I do not achieving your result in ioreg I can't see any choice to have it working

 

 

You hardly need to buy anything to test. Just looking at Hackintool will tell you if the USB ports are active.

 

Marking up meina222's image above (low res so not much detail) as compared to our MSI. When TB-USB is working, the top section, which shows the available USB devices is same for both mobos. 

 

The bottom section, which are the active ports, is populated on the GB mobo by TB USB (XHC5), but is empty on our MSI mobos. The GB mobo properly shows the ports as TypeC+Sw, which are the high speed USB3/C ports.

 

So the SSDT is properly injecting both TB and USB properties on the GB mobo. The 33 firmware is just fine; don't change it.

 

We need to study the meina222's GB DDST file to determine what is different from our MSI DDST file with respect to power for USB.

 

 

GB mobo:

meina222-TB.png.6e9762aca3c1d293768f9b8eb8dad708.png

 

 

MSI mobo:

825825468_ScreenShot2020-09-06at10_25_22AM.png.e4ecaa58bf673073544195aeec0f15b4.png

 

Edited by iGPU
  • Like 1
Link to post
Share on other sites
17 minutes ago, meina222 said:

Yes, I connect to the TB header on the motherboard.

 

When you start actual testing things don't looks so rosy. I have a TB 3 display (proper not USB-C ) with fully rated TB cable. When I connected the GPU to the TB card with a DP to mini DP bridge cable and then the monitor to TB port, PC won't even boot - BIOS error code 61 (NVRAM initialization). Not sure what this is about but maybe this NVM33 rom is not so nice for me. I enabled above 4G - same issue. I did try to increase memory per port in BIOS for TB - wonder if this is it. Back to DP, boot error is gone.

 

Wonder if this is related to the Linux firmware error. Maybe the flash was not so good.

 

I also run a GB beta BIOS. Who knows if Slot 4 is indeed tested. The only way to find out is to reflash back to default and try. Sigh 😞

 

 

My understanding is that once firmware is flashed to enable a TB AIC to work in macOS, it will not work in Windows. I would suspect Linux may be a problem too.

Link to post
Share on other sites

This is before we get to any OS. On BIOS f4c and tb card in slot 2 with original firmware I could easily boot and see image on TB connected display. Now I can’t boot. This could be BIOS issue or ROM but I’d like to be able to go to daisy changing thru my display  so I need to figure this.

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.