Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MP 1,1-5,1 testing TB3 AIC with MP 5,1

This is interesting from 8:25 and from 12:05

tsialex said:
Confirmed, MP51.0087.B00. Can happen with others.

Malfunction initially, like boot loops and trouble powering up, then later total corruption of the SPI flash/brick.


No, far from that. We are seeing that a lot of people who had NVRAM corruption are bricking installing the new firmwares.

Only Windows 8.1 and 10 can be installed into UEFI mode. Windows 7 don't have SecureBoot.
Click to expand...

Ok do you know if windows 7 can run the THB software ?
I would not want to deal with a corrupted EFI and i dont have W10.
and whats the diff between Titan and Alpine Ridge ?
 
  • Like
Reactions: Sixtyhorses and AdamUllstrom
NoLemon said:
Ok do you know if windows 7 can run the THB software ?
I would not want to deal with a corrupted EFI and i dont have W10.
Click to expand...
Do you have any reason to believe that the Mojave firmware update will corrupt your EFI?

Windows 10 does not require new EFI if you install using BIOS mode.

Windows 10 can be downloaded from Microsoft.
https://www.howtogeek.com/244678/you-dont-need-a-product-key-to-install-and-use-windows-10/

The older (version 16) Intel Thunderbolt software might work with Windows 7.
https://downloadcenter.intel.com/do...dows-10-8-1-and-7-for-Intel-NUC-Kit-NUC6i7KYK
 
joevt said:
Do you have any reason to believe that the Mojave firmware update will corrupt your EFI?
Click to expand...
Well yes, if you dont know if you dont know what you re doing and it has to be installed in BIOS mode. Possibly it might just do exactly that, if you pop in a W10 disc an install it directly.
Thats why I ask.
joevt said:
Windows 10 does not require new EFI if you install using BIOS mode.
Click to expand...
Now I know that, even though I never got higher that Windows 7.
the Thing is I dont even know wheree to specifie that.

joevt said:
Windows 10 can be downloaded from Microsoft.
https://www.howtogeek.com/244678/you-dont-need-a-product-key-to-install-and-use-windows-10/
Click to expand...

Yeah thanks for the hint, I read that some where, but since i mostl likely need to use it, if I get a Titan, I mightst as well get a copy.
joevt said:
The older (version 16) Intel Thunderbolt software might work with Windows 7.
https://downloadcenter.intel.com/do...dows-10-8-1-and-7-for-Intel-NUC-Kit-NUC6i7KYK
Click to expand...
[/QUOTE]
That would be great, that way I would not have to get a copy of W10.

Before I get a Titan, I`d like to find some convenient way to get that reboot thing as painless as possible.
There must be some way to automate this, with a minimized windows or linux to trigger the card and reboot.
Really cool would be, push the power button and wait until it hits the MAC OS login.

Thanks for the answers.
Lemon
 
NoLemon said:
Well yes, if you dont know if you dont know what you re doing and it has to be installed in BIOS mode. Possibly it might just do exactly that, if you pop in a W10 disc an install it directly.
Thats why I ask.
Click to expand...
Isn't the firmware update kind of a seamless part of the Mojave installation? I don't have a MacPro5,1 so I don't know the details. tsialex said corruption only happens with people that already have corrupted NVRAM.

NoLemon said:
Now I know that, even though I never got higher that Windows 7.
the Thing is I dont even know wheree to specifie that.
Click to expand...
I think you just install it like you did for Windows 7. Boot Camp Assistant will modify the disk's first block to create a hybrid MBR/GPT disk to support BIOS booting or you can do that yourself (I use iPartition or gpt fdisk: gdisk).

It should be a simple task to fix the boot method using the tools on the Windows 10 installer (https://neosmart.net/wiki/fix-mbr/) to make it both UEFI and BIOS. For UEFI, the files go in the EFI partition. For BIOS, the MBR and the first block of the partition containing Windows are affected and the BCD files go on the Windows partition.

NoLemon said:
That would be great, that way I would not have to get a copy of W10.
Click to expand...
I'm not sure if version 16 supports Titan Ridge? It appears that support for Titan Ridge devices was added to version 16 but support for Titan Ridge hosts wasn't added until version 17.
https://downloadmirror.intel.com/28104/eng/release notes.txt
 
joevt said:
Isn't the firmware update kind of a seamless part of the Mojave installation? I don't have a MacPro5,1 so I don't know the details. tsialex said corruption only happens with people that already have corrupted NVRAM.
Click to expand...
The way I understood, they got it corrupted by installing Windows by UEFI.
then they installed the 14.000 firmware and killed it completely.
joevt said:
.
I think you just install it like you did for Windows 7. Boot Camp Assistant will modify the disk's first block to create a hybrid MBR/GPT disk to support BIOS booting or you can do that yourself (I use iPartition or gpt fdisk: gdisk).
Click to expand...
I never used Boot Champ Assistant it sux and it doesent work most of the times.
I installed it directly.
joevt said:
.
It should be a simple task to fix the boot method using the tools on the Windows 10 installer (https://neosmart.net/wiki/fix-mbr/) to make it both UEFI and BIOS. For UEFI, the files go in the EFI partition. For BIOS, the MBR and the first block of the partition containing Windows are affected and the BCD files go on the Windows partition.
Click to expand...
Looks like I have to deal with windows 10 ... :mad::eek:

joevt said:
.
I'm not sure if version 16 supports Titan Ridge? It appears that support for Titan Ridge devices was added to version 16 but support for Titan Ridge hosts wasn't added until version 17.
https://downloadmirror.intel.com/28104/eng/release notes.txt
Click to expand...

I guess Ill try to get the latest version then.
 
I like to know of its possible to connect it like a daisychain setup for extra pci connections external?
 
Dielske said:
I like to know of its possible to connect it like a daisychain setup for extra pci connections external?
Click to expand...
Yes, you can daisy chain six Thunderbolt devices to a Thunderbolt host port.

Some eGPUs contain two Thunderbolt controllers chained together. They count as two Thunderbolt devices. They are discussed in the eGPU.io buyer's guide and forums.

If you try to connect a seventh device, Windows won't see it. If you try six devices, Windows might hang during the second boot. A second boot into Windows is not necessary, so if that happens you should just warm boot macOS after the first boot into Windows.

Here's my Mac Pro 2008 with six Thunderbolt devices connected:
Code: 
export LC_ALL=en_CA.UTF-8
export LANG=en_CA.UTF-8

cd ~/amfeltec_tests

#chmod 744 fast.sh
#chmod 744 pcitree.sh

alias pcitree.sh="sudo ~/amfeltec_tests/pcitree.sh"
alias fast.sh="sudo ~/amfeltec_tests/fast.sh"

fast.sh 2 00:01.0
# Before: PCIe 1.0 x4
#  After: PCIe 2.0 x4

pcitree.sh
#=========================================================================================
┬[0000:00]
├─00:00.0                         # g1x4           [8086:4003] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset Memory Controller Hub
├┬00:01.0-[01-29]                 # g2x16 > g2x4   [8086:4021] [0604] (rev 20) PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 1
│└┬01:00.0-[02-29]                # g3x4 > g2x4    [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ ├┬02:00.0-[03]                  # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ │└─03:00.0                      # g1x4           [8086:15eb] [0880] (rev 06) System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018]
│ ├┬02:01.0-[04-27]               # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ │└┬04:00.0-[05-27]              # g1x4           [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ ├┬05:00.0-[06]                # g3x1 > g2x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─06:00.0                    # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │ ├┬05:01.0-[07]                # g3x1 > g2x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─07:00.0                    # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │ ├┬05:02.0-[08]                # g3x1 > g1x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─08:00.0                    # g1x1           [11c1:5901] [0c00] (rev 08) FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller
│ │ ├┬05:03.0-[09]                # g3x1 > g1x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─09:00.0                    # g1x1           [8086:1533] [0200] (rev 03) Ethernet controller: Intel Corporation I210 Gigabit Network Connection
│ │ └┬05:04.0-[0a-27]             # g1x4           [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │  └┬0a:00.0-[0b-27]            # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │   ├┬0b:01.0-[0c]              # g3x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │   │└─0c:00.0                  # g3x4           [144d:a804] [0108] Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961
│ │   └┬0b:04.0-[0d-27]           # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │    └┬0d:00.0-[0e-27]          # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │     ├┬0e:01.0-[0f]            # g3x2 > g2x2    [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │     │└─0f:00.0                # g2x2           [1b21:0625] [0106] (rev 01) SATA controller: ASMedia Technology Inc. Device
│ │     └┬0e:04.0-[10-27]         # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │      └┬10:00.0-[11-27]        # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │       ├┬11:01.0-[12]          # g3x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │       │└─12:00.0              # g3x4           [144d:a804] [0108] Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961
│ │       └┬11:04.0-[13-27]       # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │        └┬13:00.0-[14-27]      # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │         ├┬14:01.0-[15-1f]     # g3x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │         │└┬15:00.0-[16-1f]    # g3x4           [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ ├┬16:00.0-[17-1c]   # g3x8           [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ │└┬17:00.0-[18-1c]  # g3x16 > g3x8   [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ ├┬18:08.0-[19]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ ├┬18:09.0-[1a]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ ├┬18:0a.0-[1b]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ └┬18:0b.0-[1c]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ ├┬16:01.0-[1d]      # g3x8 > g1x0    [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ ├┬16:08.0-[1e]      # g3x8 > g1x0    [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ └┬16:09.0-[1f]      # g3x4 > g1x0    [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         └┬14:04.0-[20-27]     # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │          └┬20:00.0-[21-27]    # g1x4           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           ├┬21:00.0-[22]      # g2x1           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─22:00.0          # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │           ├┬21:01.0-[23]      # g2x1 > g1x1    [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─23:00.0          # g1x1           [8086:1533] [0200] (rev 03) Ethernet controller: Intel Corporation I210 Gigabit Network Connection
│ │           ├┬21:02.0-[24]      # g2x1           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─24:00.0          # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │           ├┬21:03.0-[25]      # g2x1 > g1x1    [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─25:00.0          # g1x1           [11c1:5901] [0c00] (rev 08) FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller
│ │           ├┬21:04.0-[26]      # g1x4           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           └┬21:05.0-[27]      # g1x4           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ ├┬02:02.0-[28]                  # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ │└─28:00.0                      # g1x4           [8086:15ec] [0c03] (rev 06) USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018]
│ └┬02:04.0-[29]                  # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
├┬00:05.0-[2a]                    # g2x16 > g1x16  [8086:4025] [0604] (rev 20) PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 5
│├─2a:00.0                        # g2x16 > g1x16  [10de:1180] [0300] (rev a1) VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 680]
│└─2a:00.1                        # g2x16 > g1x16  [10de:0e0a] [0403] (rev a1) Audio device: NVIDIA Corporation GK104 HDMI Audio Controller
├┬00:09.0-[2b-33]                 # g2x4 > g1x4    [8086:4029] [0604] (rev 20) PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 9
│├┬2b:00.0-[2c-32]                # g1x8 > g1x4    [8086:3500] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port
││├┬2c:00.0-[2d-30]               # g1x4           [8086:3510] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1
│││└┬2d:00.0-[2e-30]              # g2x4 > g1x4    [12d8:2308] [0604] PCI bridge: Pericom Semiconductor Device
│││ ├┬2e:01.0-[2f]                # g2x2           [12d8:2308] [0604] PCI bridge: Pericom Semiconductor Device
│││ │└─2f:00.0                    # g2x2           [1b21:1242] [0c03] USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
│││ └┬2e:02.0-[30]                # g2x2           [12d8:2308] [0604] PCI bridge: Pericom Semiconductor Device
│││  └─30:00.0                    # g2x2           [1b21:0625] [0106] (rev 01) SATA controller: ASMedia Technology Inc. Device
││├┬2c:01.0-[31]                  # g1x4 > g1x0    [8086:3514] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2
││└┬2c:02.0-[32]                  # g1x4           [8086:3518] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3
││ ├─32:00.0                      # g1x4           [8086:1096] [0200] (rev 01) Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper)
││ └─32:00.1                      # g1x4           [8086:1096] [0200] (rev 01) Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper)
│└┬2b:00.3-[33]                   # g1x8 > g1x4    [8086:350c] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge
├─00:0f.0                         # g0x0           [8086:402f] [0880] (rev 20) System peripheral: Intel Corporation 5400 Chipset QuickData Technology Device
├─00:10.0                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.1                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.2                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.3                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.4                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:11.0                         #                [8086:4031] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset CE/SF Registers
├─00:15.0                         #                [8086:4035] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:15.1                         #                [8086:4035] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:16.0                         #                [8086:4036] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:16.1                         #                [8086:4036] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:1b.0                         # g0x0           [8086:269a] [0403] (rev 09) Audio device: Intel Corporation 631xESB/632xESB High Definition Audio Controller
├┬00:1c.0-[34]                    # g1x1 > g1x0    [8086:2690] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1
├┬00:1c.1-[35]                    # g1x1 > g1x0    [8086:2692] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 2
├┬00:1c.2-[36-37]                 # g1x1           [8086:2694] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 3
│└┬36:00.0-[37]                   # g1x1           [104c:823e] [0604] PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express]
│ └─37:00.0                       #                [104c:823f] [0c00] FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express]
├┬00:1c.3-[38]                    # g1x1           [8086:2696] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 4
│└─38:00.0                        # g1x1           [14e4:4328] [0280] (rev 03) Network controller: Broadcom Inc. and subsidiaries BCM4321 802.11a/b/g/n
├─00:1d.0                         #                [8086:2688] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1
├─00:1d.1                         #                [8086:2689] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2
├─00:1d.2                         #                [8086:268a] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3
├─00:1d.3                         #                [8086:268b] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4
├─00:1d.7                         #                [8086:268c] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller
├┬00:1e.0-[39]                    #                [8086:244e] [0604] (rev d9) PCI bridge: Intel Corporation 82801 PCI Bridge
├─00:1f.0                         #                [8086:2670] [0601] (rev 09) ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller
├─00:1f.1                         #                [8086:269e] [0101] (rev 09) IDE interface: Intel Corporation 631xESB/632xESB IDE Controller
├─00:1f.2                         #                [8086:2681] [0106] (rev 09) SATA controller: Intel Corporation 631xESB/632xESB SATA AHCI Controller
└─00:1f.3                         #                [8086:269b] [0c05] (rev 09) SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller

Here's a summary of the connected Thunderbolt devices:
Code: 
  00:01.0                   Mac Pro slot 2
   01:00.0                  GC-TITAN RIDGE
    02:01.0                     Titan Ridge Port 1
     04:00.0                OWC Thunderbolt 3 Dock (two USB controllers, one Ethernet, one FireWire)
      05:04.0                   Port 2
       0a:00.0              Sonnet Echo Express SE I (Thunderbolt 3) (contains Samsung 960 Pro NVMe)
        0b:04.0                 Port 2
         0d:00.0            AKiTiO Thunder3 Duo Pro (contains SATA drive)
          0e:04.0               Port 2
           10:00.0          OWC Helios  (contains Samsung 960 Pro NVMe)
            11:04.0             Port 2
             13:00.0        Sonnet Echo Express III-D (Thunderbolt 3) (contains 3 slots with only the middle slot populated by an Amfeltec gen 3 x16 4 M.2 carrier with no M.2 devices connected)
              14:04.0           Port 2
               20:00.0      OWC Thunderbolt 2 Dock (two USB controllers, one Ethernet, one FireWire)
                21:04.0         Port 2
    02:02.0                 Titan Ridge bridge for USB controller
     28:00.0                    Titan Ridge USB controller
    02:04.0                 Titan Ridge Port 2 (nothing connected here because a USB hard drive is connected to the Thunderbolt port)
 
  • Like
Reactions: AdamUllstrom
joevt said:
Yes, you can daisy chain six Thunderbolt devices to a Thunderbolt host port.

Some eGPUs contain two Thunderbolt controllers chained together. They count as two Thunderbolt devices. They are discussed in the eGPU.io buyer's guide and forums.

If you try to connect a seventh device, Windows won't see it. If you try six devices, Windows might hang during the second boot. A second boot into Windows is not necessary, so if that happens you should just warm boot macOS after the first boot into Windows.

Here's my Mac Pro 2008 with six Thunderbolt devices connected:
Code: 
export LC_ALL=en_CA.UTF-8
export LANG=en_CA.UTF-8

cd ~/amfeltec_tests

#chmod 744 fast.sh
#chmod 744 pcitree.sh

alias pcitree.sh="sudo ~/amfeltec_tests/pcitree.sh"
alias fast.sh="sudo ~/amfeltec_tests/fast.sh"

fast.sh 2 00:01.0
# Before: PCIe 1.0 x4
#  After: PCIe 2.0 x4

pcitree.sh
#=========================================================================================
┬[0000:00]
├─00:00.0                         # g1x4           [8086:4003] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset Memory Controller Hub
├┬00:01.0-[01-29]                 # g2x16 > g2x4   [8086:4021] [0604] (rev 20) PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 1
│└┬01:00.0-[02-29]                # g3x4 > g2x4    [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ ├┬02:00.0-[03]                  # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ │└─03:00.0                      # g1x4           [8086:15eb] [0880] (rev 06) System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018]
│ ├┬02:01.0-[04-27]               # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ │└┬04:00.0-[05-27]              # g1x4           [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ ├┬05:00.0-[06]                # g3x1 > g2x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─06:00.0                    # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │ ├┬05:01.0-[07]                # g3x1 > g2x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─07:00.0                    # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │ ├┬05:02.0-[08]                # g3x1 > g1x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─08:00.0                    # g1x1           [11c1:5901] [0c00] (rev 08) FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller
│ │ ├┬05:03.0-[09]                # g3x1 > g1x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─09:00.0                    # g1x1           [8086:1533] [0200] (rev 03) Ethernet controller: Intel Corporation I210 Gigabit Network Connection
│ │ └┬05:04.0-[0a-27]             # g1x4           [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │  └┬0a:00.0-[0b-27]            # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │   ├┬0b:01.0-[0c]              # g3x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │   │└─0c:00.0                  # g3x4           [144d:a804] [0108] Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961
│ │   └┬0b:04.0-[0d-27]           # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │    └┬0d:00.0-[0e-27]          # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │     ├┬0e:01.0-[0f]            # g3x2 > g2x2    [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │     │└─0f:00.0                # g2x2           [1b21:0625] [0106] (rev 01) SATA controller: ASMedia Technology Inc. Device
│ │     └┬0e:04.0-[10-27]         # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │      └┬10:00.0-[11-27]        # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │       ├┬11:01.0-[12]          # g3x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │       │└─12:00.0              # g3x4           [144d:a804] [0108] Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961
│ │       └┬11:04.0-[13-27]       # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │        └┬13:00.0-[14-27]      # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │         ├┬14:01.0-[15-1f]     # g3x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │         │└┬15:00.0-[16-1f]    # g3x4           [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ ├┬16:00.0-[17-1c]   # g3x8           [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ │└┬17:00.0-[18-1c]  # g3x16 > g3x8   [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ ├┬18:08.0-[19]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ ├┬18:09.0-[1a]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ ├┬18:0a.0-[1b]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ └┬18:0b.0-[1c]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ ├┬16:01.0-[1d]      # g3x8 > g1x0    [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ ├┬16:08.0-[1e]      # g3x8 > g1x0    [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ └┬16:09.0-[1f]      # g3x4 > g1x0    [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         └┬14:04.0-[20-27]     # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │          └┬20:00.0-[21-27]    # g1x4           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           ├┬21:00.0-[22]      # g2x1           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─22:00.0          # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │           ├┬21:01.0-[23]      # g2x1 > g1x1    [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─23:00.0          # g1x1           [8086:1533] [0200] (rev 03) Ethernet controller: Intel Corporation I210 Gigabit Network Connection
│ │           ├┬21:02.0-[24]      # g2x1           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─24:00.0          # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │           ├┬21:03.0-[25]      # g2x1 > g1x1    [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─25:00.0          # g1x1           [11c1:5901] [0c00] (rev 08) FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller
│ │           ├┬21:04.0-[26]      # g1x4           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           └┬21:05.0-[27]      # g1x4           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ ├┬02:02.0-[28]                  # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ │└─28:00.0                      # g1x4           [8086:15ec] [0c03] (rev 06) USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018]
│ └┬02:04.0-[29]                  # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
├┬00:05.0-[2a]                    # g2x16 > g1x16  [8086:4025] [0604] (rev 20) PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 5
│├─2a:00.0                        # g2x16 > g1x16  [10de:1180] [0300] (rev a1) VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 680]
│└─2a:00.1                        # g2x16 > g1x16  [10de:0e0a] [0403] (rev a1) Audio device: NVIDIA Corporation GK104 HDMI Audio Controller
├┬00:09.0-[2b-33]                 # g2x4 > g1x4    [8086:4029] [0604] (rev 20) PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 9
│├┬2b:00.0-[2c-32]                # g1x8 > g1x4    [8086:3500] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port
││├┬2c:00.0-[2d-30]               # g1x4           [8086:3510] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1
│││└┬2d:00.0-[2e-30]              # g2x4 > g1x4    [12d8:2308] [0604] PCI bridge: Pericom Semiconductor Device
│││ ├┬2e:01.0-[2f]                # g2x2           [12d8:2308] [0604] PCI bridge: Pericom Semiconductor Device
│││ │└─2f:00.0                    # g2x2           [1b21:1242] [0c03] USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
│││ └┬2e:02.0-[30]                # g2x2           [12d8:2308] [0604] PCI bridge: Pericom Semiconductor Device
│││  └─30:00.0                    # g2x2           [1b21:0625] [0106] (rev 01) SATA controller: ASMedia Technology Inc. Device
││├┬2c:01.0-[31]                  # g1x4 > g1x0    [8086:3514] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2
││└┬2c:02.0-[32]                  # g1x4           [8086:3518] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3
││ ├─32:00.0                      # g1x4           [8086:1096] [0200] (rev 01) Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper)
││ └─32:00.1                      # g1x4           [8086:1096] [0200] (rev 01) Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper)
│└┬2b:00.3-[33]                   # g1x8 > g1x4    [8086:350c] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge
├─00:0f.0                         # g0x0           [8086:402f] [0880] (rev 20) System peripheral: Intel Corporation 5400 Chipset QuickData Technology Device
├─00:10.0                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.1                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.2                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.3                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.4                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:11.0                         #                [8086:4031] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset CE/SF Registers
├─00:15.0                         #                [8086:4035] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:15.1                         #                [8086:4035] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:16.0                         #                [8086:4036] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:16.1                         #                [8086:4036] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:1b.0                         # g0x0           [8086:269a] [0403] (rev 09) Audio device: Intel Corporation 631xESB/632xESB High Definition Audio Controller
├┬00:1c.0-[34]                    # g1x1 > g1x0    [8086:2690] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1
├┬00:1c.1-[35]                    # g1x1 > g1x0    [8086:2692] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 2
├┬00:1c.2-[36-37]                 # g1x1           [8086:2694] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 3
│└┬36:00.0-[37]                   # g1x1           [104c:823e] [0604] PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express]
│ └─37:00.0                       #                [104c:823f] [0c00] FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express]
├┬00:1c.3-[38]                    # g1x1           [8086:2696] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 4
│└─38:00.0                        # g1x1           [14e4:4328] [0280] (rev 03) Network controller: Broadcom Inc. and subsidiaries BCM4321 802.11a/b/g/n
├─00:1d.0                         #                [8086:2688] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1
├─00:1d.1                         #                [8086:2689] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2
├─00:1d.2                         #                [8086:268a] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3
├─00:1d.3                         #                [8086:268b] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4
├─00:1d.7                         #                [8086:268c] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller
├┬00:1e.0-[39]                    #                [8086:244e] [0604] (rev d9) PCI bridge: Intel Corporation 82801 PCI Bridge
├─00:1f.0                         #                [8086:2670] [0601] (rev 09) ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller
├─00:1f.1                         #                [8086:269e] [0101] (rev 09) IDE interface: Intel Corporation 631xESB/632xESB IDE Controller
├─00:1f.2                         #                [8086:2681] [0106] (rev 09) SATA controller: Intel Corporation 631xESB/632xESB SATA AHCI Controller
└─00:1f.3                         #                [8086:269b] [0c05] (rev 09) SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller

Here's a summary of the connected Thunderbolt devices:
Code: 
  00:01.0                   Mac Pro slot 2
   01:00.0                  GC-TITAN RIDGE
    02:01.0                     Titan Ridge Port 1
     04:00.0                OWC Thunderbolt 3 Dock (two USB controllers, one Ethernet, one FireWire)
      05:04.0                   Port 2
       0a:00.0              Sonnet Echo Express SE I (Thunderbolt 3) (contains Samsung 960 Pro NVMe)
        0b:04.0                 Port 2
         0d:00.0            AKiTiO Thunder3 Duo Pro (contains SATA drive)
          0e:04.0               Port 2
           10:00.0          OWC Helios  (contains Samsung 960 Pro NVMe)
            11:04.0             Port 2
             13:00.0        Sonnet Echo Express III-D (Thunderbolt 3) (contains 3 slots with only the middle slot populated by an Amfeltec gen 3 x16 4 M.2 carrier with no M.2 devices connected)
              14:04.0           Port 2
               20:00.0      OWC Thunderbolt 2 Dock (two USB controllers, one Ethernet, one FireWire)
                21:04.0         Port 2
    02:02.0                 Titan Ridge bridge for USB controller
     28:00.0                    Titan Ridge USB controller
    02:04.0                 Titan Ridge Port 2 (nothing connected here because a USB hard drive is connected to the Thunderbolt port)
Click to expand...
joevt said:
Yes, you can daisy chain six Thunderbolt devices to a Thunderbolt host port.

Some eGPUs contain two Thunderbolt controllers chained together. They count as two Thunderbolt devices. They are discussed in the eGPU.io buyer's guide and forums.

If you try to connect a seventh device, Windows won't see it. If you try six devices, Windows might hang during the second boot. A second boot into Windows is not necessary, so if that happens you should just warm boot macOS after the first boot into Windows.

Here's my Mac Pro 2008 with six Thunderbolt devices connected:
Code: 
export LC_ALL=en_CA.UTF-8
export LANG=en_CA.UTF-8

cd ~/amfeltec_tests

#chmod 744 fast.sh
#chmod 744 pcitree.sh

alias pcitree.sh="sudo ~/amfeltec_tests/pcitree.sh"
alias fast.sh="sudo ~/amfeltec_tests/fast.sh"

fast.sh 2 00:01.0
# Before: PCIe 1.0 x4
#  After: PCIe 2.0 x4

pcitree.sh
#=========================================================================================
┬[0000:00]
├─00:00.0                         # g1x4           [8086:4003] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset Memory Controller Hub
├┬00:01.0-[01-29]                 # g2x16 > g2x4   [8086:4021] [0604] (rev 20) PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 1
│└┬01:00.0-[02-29]                # g3x4 > g2x4    [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ ├┬02:00.0-[03]                  # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ │└─03:00.0                      # g1x4           [8086:15eb] [0880] (rev 06) System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018]
│ ├┬02:01.0-[04-27]               # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ │└┬04:00.0-[05-27]              # g1x4           [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ ├┬05:00.0-[06]                # g3x1 > g2x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─06:00.0                    # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │ ├┬05:01.0-[07]                # g3x1 > g2x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─07:00.0                    # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │ ├┬05:02.0-[08]                # g3x1 > g1x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─08:00.0                    # g1x1           [11c1:5901] [0c00] (rev 08) FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller
│ │ ├┬05:03.0-[09]                # g3x1 > g1x1    [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │ │└─09:00.0                    # g1x1           [8086:1533] [0200] (rev 03) Ethernet controller: Intel Corporation I210 Gigabit Network Connection
│ │ └┬05:04.0-[0a-27]             # g1x4           [8086:15d3] [0604] (rev 02) PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016]
│ │  └┬0a:00.0-[0b-27]            # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │   ├┬0b:01.0-[0c]              # g3x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │   │└─0c:00.0                  # g3x4           [144d:a804] [0108] Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961
│ │   └┬0b:04.0-[0d-27]           # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │    └┬0d:00.0-[0e-27]          # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │     ├┬0e:01.0-[0f]            # g3x2 > g2x2    [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │     │└─0f:00.0                # g2x2           [1b21:0625] [0106] (rev 01) SATA controller: ASMedia Technology Inc. Device
│ │     └┬0e:04.0-[10-27]         # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │      └┬10:00.0-[11-27]        # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │       ├┬11:01.0-[12]          # g3x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │       │└─12:00.0              # g3x4           [144d:a804] [0108] Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961
│ │       └┬11:04.0-[13-27]       # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │        └┬13:00.0-[14-27]      # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │         ├┬14:01.0-[15-1f]     # g3x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │         │└┬15:00.0-[16-1f]    # g3x4           [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ ├┬16:00.0-[17-1c]   # g3x8           [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ │└┬17:00.0-[18-1c]  # g3x16 > g3x8   [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ ├┬18:08.0-[19]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ ├┬18:09.0-[1a]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ ├┬18:0a.0-[1b]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ │ └┬18:0b.0-[1c]    # g3x4 > g1x0    [10b5:8732] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch
│ │         │ ├┬16:01.0-[1d]      # g3x8 > g1x0    [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ ├┬16:08.0-[1e]      # g3x8 > g1x0    [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         │ └┬16:09.0-[1f]      # g3x4 > g1x0    [10b5:8724] [0604] (rev ca) PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI Express Gen 3 (8 GT/s) Switch, 19 x 19mm FCBGA
│ │         └┬14:04.0-[20-27]     # g1x4           [8086:1578] [0604] PCI bridge: Intel Corporation DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
│ │          └┬20:00.0-[21-27]    # g1x4           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           ├┬21:00.0-[22]      # g2x1           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─22:00.0          # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │           ├┬21:01.0-[23]      # g2x1 > g1x1    [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─23:00.0          # g1x1           [8086:1533] [0200] (rev 03) Ethernet controller: Intel Corporation I210 Gigabit Network Connection
│ │           ├┬21:02.0-[24]      # g2x1           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─24:00.0          # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
│ │           ├┬21:03.0-[25]      # g2x1 > g1x1    [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           │└─25:00.0          # g1x1           [11c1:5901] [0c00] (rev 08) FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller
│ │           ├┬21:04.0-[26]      # g1x4           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ │           └┬21:05.0-[27]      # g1x4           [8086:156d] [0604] PCI bridge: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013]
│ ├┬02:02.0-[28]                  # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ │└─28:00.0                      # g1x4           [8086:15ec] [0c03] (rev 06) USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018]
│ └┬02:04.0-[29]                  # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
├┬00:05.0-[2a]                    # g2x16 > g1x16  [8086:4025] [0604] (rev 20) PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 5
│├─2a:00.0                        # g2x16 > g1x16  [10de:1180] [0300] (rev a1) VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 680]
│└─2a:00.1                        # g2x16 > g1x16  [10de:0e0a] [0403] (rev a1) Audio device: NVIDIA Corporation GK104 HDMI Audio Controller
├┬00:09.0-[2b-33]                 # g2x4 > g1x4    [8086:4029] [0604] (rev 20) PCI bridge: Intel Corporation 5400 Chipset PCI Express Port 9
│├┬2b:00.0-[2c-32]                # g1x8 > g1x4    [8086:3500] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port
││├┬2c:00.0-[2d-30]               # g1x4           [8086:3510] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1
│││└┬2d:00.0-[2e-30]              # g2x4 > g1x4    [12d8:2308] [0604] PCI bridge: Pericom Semiconductor Device
│││ ├┬2e:01.0-[2f]                # g2x2           [12d8:2308] [0604] PCI bridge: Pericom Semiconductor Device
│││ │└─2f:00.0                    # g2x2           [1b21:1242] [0c03] USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
│││ └┬2e:02.0-[30]                # g2x2           [12d8:2308] [0604] PCI bridge: Pericom Semiconductor Device
│││  └─30:00.0                    # g2x2           [1b21:0625] [0106] (rev 01) SATA controller: ASMedia Technology Inc. Device
││├┬2c:01.0-[31]                  # g1x4 > g1x0    [8086:3514] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2
││└┬2c:02.0-[32]                  # g1x4           [8086:3518] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3
││ ├─32:00.0                      # g1x4           [8086:1096] [0200] (rev 01) Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper)
││ └─32:00.1                      # g1x4           [8086:1096] [0200] (rev 01) Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper)
│└┬2b:00.3-[33]                   # g1x8 > g1x4    [8086:350c] [0604] (rev 01) PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge
├─00:0f.0                         # g0x0           [8086:402f] [0880] (rev 20) System peripheral: Intel Corporation 5400 Chipset QuickData Technology Device
├─00:10.0                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.1                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.2                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.3                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:10.4                         #                [8086:4030] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FSB Registers
├─00:11.0                         #                [8086:4031] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset CE/SF Registers
├─00:15.0                         #                [8086:4035] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:15.1                         #                [8086:4035] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:16.0                         #                [8086:4036] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:16.1                         #                [8086:4036] [0600] (rev 20) Host bridge: Intel Corporation 5400 Chipset FBD Registers
├─00:1b.0                         # g0x0           [8086:269a] [0403] (rev 09) Audio device: Intel Corporation 631xESB/632xESB High Definition Audio Controller
├┬00:1c.0-[34]                    # g1x1 > g1x0    [8086:2690] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1
├┬00:1c.1-[35]                    # g1x1 > g1x0    [8086:2692] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 2
├┬00:1c.2-[36-37]                 # g1x1           [8086:2694] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 3
│└┬36:00.0-[37]                   # g1x1           [104c:823e] [0604] PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express]
│ └─37:00.0                       #                [104c:823f] [0c00] FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express]
├┬00:1c.3-[38]                    # g1x1           [8086:2696] [0604] (rev 09) PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 4
│└─38:00.0                        # g1x1           [14e4:4328] [0280] (rev 03) Network controller: Broadcom Inc. and subsidiaries BCM4321 802.11a/b/g/n
├─00:1d.0                         #                [8086:2688] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1
├─00:1d.1                         #                [8086:2689] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2
├─00:1d.2                         #                [8086:268a] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3
├─00:1d.3                         #                [8086:268b] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4
├─00:1d.7                         #                [8086:268c] [0c03] (rev 09) USB controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller
├┬00:1e.0-[39]                    #                [8086:244e] [0604] (rev d9) PCI bridge: Intel Corporation 82801 PCI Bridge
├─00:1f.0                         #                [8086:2670] [0601] (rev 09) ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller
├─00:1f.1                         #                [8086:269e] [0101] (rev 09) IDE interface: Intel Corporation 631xESB/632xESB IDE Controller
├─00:1f.2                         #                [8086:2681] [0106] (rev 09) SATA controller: Intel Corporation 631xESB/632xESB SATA AHCI Controller
└─00:1f.3                         #                [8086:269b] [0c05] (rev 09) SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller

Here's a summary of the connected Thunderbolt devices:
Code: 
  00:01.0                   Mac Pro slot 2
   01:00.0                  GC-TITAN RIDGE
    02:01.0                     Titan Ridge Port 1
     04:00.0                OWC Thunderbolt 3 Dock (two USB controllers, one Ethernet, one FireWire)
      05:04.0                   Port 2
       0a:00.0              Sonnet Echo Express SE I (Thunderbolt 3) (contains Samsung 960 Pro NVMe)
        0b:04.0                 Port 2
         0d:00.0            AKiTiO Thunder3 Duo Pro (contains SATA drive)
          0e:04.0               Port 2
           10:00.0          OWC Helios  (contains Samsung 960 Pro NVMe)
            11:04.0             Port 2
             13:00.0        Sonnet Echo Express III-D (Thunderbolt 3) (contains 3 slots with only the middle slot populated by an Amfeltec gen 3 x16 4 M.2 carrier with no M.2 devices connected)
              14:04.0           Port 2
               20:00.0      OWC Thunderbolt 2 Dock (two USB controllers, one Ethernet, one FireWire)
                21:04.0         Port 2
    02:02.0                 Titan Ridge bridge for USB controller
     28:00.0                    Titan Ridge USB controller
    02:04.0                 Titan Ridge Port 2 (nothing connected here because a USB hard drive is connected to the Thunderbolt port)
Click to expand...

Many thnx for youre reply
Is it possible to post a video or a YouTube link. So that everyone here can see it in action? What speeds do you achieve read write whith external nvme?
 
Dielske said:
Many thnx for youre reply
Is it possible to post a video or a YouTube link. So that everyone here can see it in action? What speeds do you achieve read write whith external nvme?
Click to expand...
I've posted NVMe speeds before in previous posts in this thread. One post included PCIe 3.0 x4 speeds (connecting the GC-TITAN RIDGE to an amfeltec x16 gen 3 carrier using an adapter - the carrier converts PCIe 3.0 x4 of the M.2 adapter to PCIe 2.0 x16 of the Mac Pro slot 2).

Write Read speeds for this configuration of six chained Thunderbolt devices:
787 912 : OWC Mercury Elite Pro Dual mini connected to Titan Ridge USB Controller (Titan Ridge USB 3.1 gen 2)
626 1476 : Sonnet Echo Express SE I (NVMe read limited by PCIe 2.0 x4 of Mac Pro slot 2. Using SoftRAID driver.)
43 41 : AKiTiO Thunder3 Duo Pro (mechanical 2.5 inch SATA harddisk)
390 1456 : OWC Mercury Helios 3 (Slower than Sonnet above because the OWC is later in the chain? Using normal driver.)

I don't know why the write speeds of the NVMe drives are slow. The USB speed is faster than anything you can get with a ASM1142 based controller (PCIe 2.0 x2) because the Titan Ridge USB controller benefits from PCIe 2.0 x4 connection. USB controllers are discussed in the USB 3.x PCIe Cards for Classic Mac Pro thread.

Picture of devices below (excuse the poor lighting and blurriness). Mac Pro 2008 is on the extreme left behind a Dell 4K display. The OWC Thunderbolt 3 Dock is on top of the OWC Mercury Elite Pro Dual mini (only the top of the Dual mini is visible as it's behind another drive). Continuing from left to right is the Sonnet Echo Express SE I (black), AKiTiO Thunder3 Duo Pro (silver), OWC Mercury Helios 3 (black), Sonnet Echo Express III-D (black, cover removed, amfeltec shown in the x16 slot), OWC Thunderbolt 2 Dock sitting on top several power bricks. Behind the Thunderbolt devices is a PC with Apple CRT on the right and another CRT below. There's a Dell 5K display below the Thunderbolt devices.Not pictured is the Apple 30" Cinema display below the Mac Pro and to the left of the Dell 5K and a Mac Mini 2018 under the Dell 4K display.
six devices.jpg
 
joevt said:
I've posted NVMe speeds before in previous posts in this thread. One post included PCIe 3.0 x4 speeds (connecting the GC-TITAN RIDGE to an amfeltec x16 gen 3 carrier using an adapter - the carrier converts PCIe 3.0 x4 of the M.2 adapter to PCIe 2.0 x16 of the Mac Pro slot 2).

Write Read speeds for this configuration of six chained Thunderbolt devices:
787 912 : OWC Mercury Elite Pro Dual mini connected to Titan Ridge USB Controller (Titan Ridge USB 3.1 gen 2)
626 1476 : Sonnet Echo Express SE I (NVMe read limited by PCIe 2.0 x4 of Mac Pro slot 2. Using SoftRAID driver.)
43 41 : AKiTiO Thunder3 Duo Pro (mechanical 2.5 inch SATA harddisk)
390 1456 : OWC Mercury Helios 3 (Slower than Sonnet above because the OWC is later in the chain? Using normal driver.)

I don't know why the write speeds of the NVMe drives are slow. The USB speed is faster than anything you can get with a ASM1142 based controller (PCIe 2.0 x2) because the Titan Ridge USB controller benefits from PCIe 2.0 x4 connection. USB controllers are discussed in the USB 3.x PCIe Cards for Classic Mac Pro thread.

Picture of devices below (excuse the poor lighting and blurriness). Mac Pro 2008 is on the extreme left behind a Dell 4K display. The OWC Thunderbolt 3 Dock is on top of the OWC Mercury Elite Pro Dual mini (only the top of the Dual mini is visible as it's behind another drive). Continuing from left to right is the Sonnet Echo Express SE I (black), AKiTiO Thunder3 Duo Pro (silver), OWC Mercury Helios 3 (black), Sonnet Echo Express III-D (black, cover removed, amfeltec shown in the x16 slot), OWC Thunderbolt 2 Dock sitting on top several power bricks. Behind the Thunderbolt devices is a PC with Apple CRT on the right and another CRT below. There's a Dell 5K display below the Thunderbolt devices.Not pictured is the Apple 30" Cinema display below the Mac Pro and to the left of the Dell 5K and a Mac Mini 2018 under the Dell 4K display.
View attachment 816892
Click to expand...

Nice thnx. But you do this whith 2008 mac Pro. I love to see a comparison whith the 5.1
Is there omebody here that done it?
[doublepost=1548171666][/doublepost]
Dielske said:
Nice thnx. But you do this whith 2008 mac Pro. I love to see a comparison whith the 5.1
Is there somebody here that done it?
Click to expand...
I mean are the read write speeds higher if you use the mac pro 5.1
 
Dielske said:
I mean are the read write speeds higher if you use the mac pro 5.1
Click to expand...
The MacPro5,1 might be slightly faster than the MacPro3,1 but not by much. The MacPro3,1 slows down after 4000 MB/s - it can reach up to 5226 MB/s but the later MacPros can get up to 5900+ MB/s. Read some benchmarks in the amfeltec thread for raiding four NVMe drivers using the gen 3 amfeltec x16. My hackintosh can get 6315 MB/s using the same PCIe 2.0 speed limitation of the Mac Pros so I would expect the MacPro5,1 to get between 5226 MB/s and 6315 MB/s.

Anyway, none of that matters since Thunderbolt 3 is limited to 2750 MB/s and in a PCIe 2.0 slot it is limited to less than 2000 MB/s (but still performs better than Thunderbolt 2). So any big speed difference at these low speeds would point to a bug in the computer with the lower performance.
 
  • Like
Reactions: rawweb
Searching for Linux thunderbolt 3, I found some interesting things.
There might be a way to at least take out the drag abit.
https://gitlab.freedesktop.org/bolt/bolt is a THB3 Control Panel for Linux which might be copiled with this https://mesonbuild.com --> for Mac.
That would then be just a reboot, definitely less of a pain.
We probably wont get around rebooting.
I dont know how to the tec side on this one. I tried to install .Json packages before,
only got it to work for seconds, way to much Terminal stuff which, i dont know. o_O
 
NoLemon said:
Searching for Linux thunderbolt 3, I found some interesting things.
There might be a way to at least take out the drag abit.
https://gitlab.freedesktop.org/bolt/bolt is a THB3 Control Panel for Linux which might be copiled with this https://mesonbuild.com --> for Mac.
That would then be just a reboot, definitely less of a pain.
We probably wont get around rebooting.
I dont know how to the tec side on this one. I tried to install .Json packages before,
only got it to work for seconds, way to much Terminal stuff which, i dont know. o_O
Click to expand...
boltd is interesting but it just interfaces with the thunderbolt sysfs stuff so you would probably want to start with the sysfs stuff. You don't compile for macOS since Linux is totally different. You would need to create a kext with a user client to interface with the code that talks to the Thunderbolt controller. Then a user command line uses the user client to talk to the kext. This would be like the lspci command line of pciutils, the directhw.kext and it's user client. I think the lspci that I use uses the built-in AppleACPIPlatform.kext. There is a version of lspci that uses lspcidrv.kext. Each part of sysfs could be a different command in the user client. Listing devices (names and UUIDs), their connection types (link width and speed), versions, authorizing devices, reading NVM, writing NVM, etc.
 
joevt said:
boltd is interesting but it just interfaces with the thunderbolt sysfs stuff so you would probably want to start with the sysfs stuff. You don't compile for macOS since Linux is totally different.
Click to expand...
You would need to create a kext with a user client to interface with the code that talks to the Thunderbolt controller. Then a user command line uses the user client to talk to the kext. This would be like the lspci command line of pciutils, the directhw.kext and it's user client. I think the lspci that I use uses the built-in AppleACPIPlatform.kext. There is a version of lspci that uses lspcidrv.kext. Each part of sysfs could be a different command in the user client. Listing devices (names and UUIDs), their connection types (link width and speed), versions, authorizing devices, reading NVM, writing NVM, etc.[/QUOTE]
Ok, what about using a Linux instead of Windows to have it running with a reboot ?
 
NoLemon said:
Ok, what about using a Linux instead of Windows to have it running with a reboot ?
Click to expand...
Linux is unable to enable the GC-TITAN RIDGE in my MacPro3,1. Windows has something extra. Maybe linux has code to do it but it's not being used. Even if I boot Windows first, then go into Linux, some of the sysfs stuff is missing for the thunderbolt controller and devices.
 
Okay, I still have a few questions I need to clarify before/or even if I buy the titan-ridge card!

My current setup:

MacPro 4,1-5,1
2x 6Core 3,46GHz
64GB 1333 RAM
GeForce GTX Titan X
256GB Samsung SM951 NVMe M.2 SSD
4x USB 3.0 Controller Card

iPad Pro 12,9“ (2018) vonnected via VNC

My dream setup:

MacPro 4,1-5,1
2x 6Core 3,46GHz
64GB 1333 RAM
GeForce GTX Titan X
HighPoint SSD7101A with 4x 1TB Samsung 970 Pro RAID0
2x 2TB Samsung 860 Pro Sata SSD for TimeMachine and/or Windows (if no other option appears for the TB3 solution of this thread)
GC-Titan-Ridge

4K or 5K Monitor depending on the final best deal I can find.

iPad Pro 12,9“ (2018) connected via Duet Display with USB-C cable.

Thunderbolt 3 Dockingstation.

My use case:

Graphic Design on macOS with AdobeCC
Video Editing on macOS with FCPX

Drawing with Procreate
Video Editing on LumaFusion
Using the iPad as a graphic tablet of Adobe Apps over Duet

Connecting my iPad to the monitor if I need a bigger screen for some tasks
Connecting my MacPro on a „separate“ channel of my Monitor when I work from there.

Right now I am using the internal 2x 6Pin connectors to drive my Titan X, I have not modded it with PixlasMod.

Here my questions:

1. If I want to connect a TB3 Dockingstation like for example Elgato Thunderbolt 3 of CalDigit TS3 and use the ports, do I need the extra power from the internal cablemods?
2. To get a picture on the screen I only need to connect it to the Totan-Ridge? Or do I need externally the TitanX to the Titan-Ridge?
3. To use only one monitor for two devices (MP & iPP) would it to connect everything to the docking station? Especially as the LG 5K monitor is only TB3 and the iPad Pro is only USB-C. LG 4K is at least also „only“ USB-C so I could connect it directly.
4. If I find a Display with has several input channels and I connect both devices to several channels, am I still needing Windows to expose the iPad Pro on my Mac for DuetDisplay? Or would this daisychaining method be enough?

Or is this in my case not even needed, if I just use a USB-C to USB-A cable for the iPad Pro as a graphic tablet and separate channels/ports for my MP and iPP as video input devices?

Thanks in advance for any advice!
 
misanthrophy said:
1. If I want to connect a TB3 Dockingstation like for example Elgato Thunderbolt 3 of CalDigit TS3 and use the ports, do I need the extra power from the internal cablemods?
2. To get a picture on the screen I only need to connect it to the Totan-Ridge? Or do I need externally the TitanX to the Titan-Ridge?
3. To use only one monitor for two devices (MP & iPP) would it to connect everything to the docking station? Especially as the LG 5K monitor is only TB3 and the iPad Pro is only USB-C. LG 4K is at least also „only“ USB-C so I could connect it directly.
4. If I find a Display with has several input channels and I connect both devices to several channels, am I still needing Windows to expose the iPad Pro on my Mac for DuetDisplay? Or would this daisychaining method be enough?

Or is this in my case not even needed, if I just use a USB-C to USB-A cable for the iPad Pro as a graphic tablet and separate channels/ports for my MP and iPP as video input devices?

Thanks in advance for any advice!
Click to expand...
1) No, thunderbolt docks have their own power supply.
2) The Titan X needs to be connected to the GC-TITAN RIDGE for displays to work from the Thunderbolt ports.
3) For the iPad Pro to use the display, the display needs to be connected to the iPad Pro directly (USB-C or DisplayPort, not Thunderbolt) or through a USB-C dock. You will need to switch wires to move the display from the Mac Pro to the iPad Pro.

You might be able to use a Thunderbolt display with the iPad Pro by connecting a USB-C to mini DisplayPort cable from the iPad Pro to one of the mini DisplayPort inputs of the GC-TITAN RIDGE. You still need to switch wires to move the display from the Mac Pro to the iPad Pro. This should allow 4K on DisplayPort 1.2 displays (like the LG Ultrafine 4K display or LG UltraFine 5K (Thunderbolt)) and 5K on DisplayPort 1.4 displays (The LG 34WK95U-W is a 5K2K UltraWide display that supports DisplayPort 1.4, Thunderbolt, and USB-C). The iPad Pro won't be able to see any of the USB or PCIe devices of the display - they will remain connected to the Mac Pro).

4) I believe Duet uses a USB connection between the iPad Pro and Mac Pro to work. Windows is not required for USB functionality to work on the GC-TITAN RIDGE. Windows is required if the USB port is on a Thunderbolt device.
 
  • Like
Reactions: Amethyst1
joevt said:
1) No, thunderbolt docks have their own power supply.
2) The Titan X needs to be connected to the GC-TITAN RIDGE for displays to work from the Thunderbolt ports.
3) For the iPad Pro to use the display, the display needs to be connected to the iPad Pro directly (USB-C or DisplayPort, not Thunderbolt) or through a USB-C dock. You will need to switch wires to move the display from the Mac Pro to the iPad Pro.

You might be able to use a Thunderbolt display with the iPad Pro by connecting a USB-C to mini DisplayPort cable from the iPad Pro to one of the mini DisplayPort inputs of the GC-TITAN RIDGE. You still need to switch wires to move the display from the Mac Pro to the iPad Pro. This should allow 4K on DisplayPort 1.2 displays (like the LG Ultrafine 4K display or LG UltraFine 5K (Thunderbolt)) and 5K on DisplayPort 1.4 displays (The LG 34WK95U-W is a 5K2K UltraWide display that supports DisplayPort 1.4, Thunderbolt, and USB-C). The iPad Pro won't be able to see any of the USB or PCIe devices of the display - they will remain connected to the Mac Pro).

4) I believe Duet uses a USB connection between the iPad Pro and Mac Pro to work. Windows is not required for USB functionality to work on the GC-TITAN RIDGE. Windows is required if the USB port is on a Thunderbolt device.
Click to expand...

Thanks for the quick answer. So that means in my case the most „inconvenient“ part is to switch wires when I need another video output. No Windows and no additional power cables.

Would you even install the GC-Titan-Ridge? Or if at all use a USB-C card like mentioned in other posts (Sonnett Allegro or CalDigit Fasta...) because the LG 4K also only has USB-C same as the iPad?
 
misanthrophy said:
Would you even install the GC-Titan-Ridge? Or if at all use a USB-C card like mentioned in other posts (Sonnett Allegro or CalDigit Fasta...) because the LG 4K also only has USB-C same as the iPad?
Click to expand...
If you want to use an LG UltraFine 4K with your Mac Pro, then you need a USB-C port that supports both USB 2.0 and DisplayPort alt mode. You can use a Sunix UPD2018 or a Delock 89582 or a GC-ALPINE RIDGE or a GC-TITAN RIDGE. I don't think any other USB-C cards support DisplayPort alt mode (they need a DisplayPort input). The Sunix and Delock are PCIe x1 so can only allow up 5 Gbps for USB in a Mac Pro (PCIe 3.0 is required for speeds greater than that).

Currently, USB functionality for the GC-ALPINE RIDGE doesn't work. USB 2.0 functionality for the GC-TITAN RIDGE doesn't work unless you connect two USB ports to the 9 pin header (maybe consider an internal USB hub). Another option is to connect the display to the Thunderbolt 3 port of a Thunderbolt 3 Dock which would require Windows to enable. USB 2.0 (and 3.0 and 3.1 gen 2) should work fine from the Thunderbolt port of the Thunderbolt 3 Dock.

The GC-TITAN RIDGE gives the fastest USB 3.1 gen 2 speeds in a Mac Pro. It can support two USB-C or Thunderbolt displays.
 
joevt said:
If you want to use an LG UltraFine 4K with your Mac Pro, then you need a USB-C port that supports both USB 2.0 and DisplayPort alt mode. You can use a Sunix UPD2018 or a Delock 89582 or a GC-ALPINE RIDGE or a GC-TITAN RIDGE. I don't think any other USB-C cards support DisplayPort alt mode (they need a DisplayPort input). The Sunix and Delock are PCIe x1 so can only allow up 5 Gbps for USB in a Mac Pro (PCIe 3.0 is required for speeds greater than that).

Currently, USB functionality for the GC-ALPINE RIDGE doesn't work. USB 2.0 functionality for the GC-TITAN RIDGE doesn't work unless you connect two USB ports to the 9 pin header (maybe consider an internal USB hub). Another option is to connect the display to the Thunderbolt 3 port of a Thunderbolt 3 Dock which would require Windows to enable. USB 2.0 (and 3.0 and 3.1 gen 2) should work fine from the Thunderbolt port of the Thunderbolt 3 Dock.

The GC-TITAN RIDGE gives the fastest USB 3.1 gen 2 speeds in a Mac Pro. It can support two USB-C or Thunderbolt displays.
Click to expand...

Okay I bit the bullet and invested the money into the Titan-Ridge as it would be the best option for the future to connect different types of devices!

I will report back when I received it what is working and what not.

Thanks in the meantime for your support and advice!
 
do somone actually know if apple « could if they would » do a firmware upgrade to have those card actually real plug an play.
i mean is there something missing in the hardware of a cMP that prevents it?
 
edgerider said:
do somone actually know if apple « could if they would » do a firmware upgrade to have those card actually real plug an play.
i mean is there something missing in the hardware of a cMP that prevents it?
Click to expand...
I don't think there is but I don't know for sure. Apple's not going to do it because they want you to buy a new Mac. It mostly works now. I mean Windows can detect new Thunderbolt devices. macOS can enumerate them. Just need to get some software to do both on macOS.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back