List of Intel Titan Ridge Thunderbolt 3 Devices  

Page 6 / 6 Prev
  RSS

joevt
(@joevt3)
Reputable Member
Joined: 1 year ago
Posts: 300
December 23, 2018 10:25 pm  
Posted by: dgsga

@joevt
Thanks very much for the tip,  I can query the current security level in Ubuntu with the command:
cat /sys/thunderbolt/devices/domain0/security
But I’m unable to write to the same location using echo as root user (permission denied). Am I missing something here?

Did you try "sudo"?

There is also the higher-level boltctl command line. It uses the boltd daemon.

There is also the older tbtadm. It uses different ACL which might conflict with bolt.
https://github.com/intel/thunderbolt-software-user-space/issues/60
https://wiki.gnome.org/Design/Whiteboards/ThunderboltAccess

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
dgsga
(@dgsga)
New Member
Joined: 1 month ago
Posts: 4
December 24, 2018 2:21 pm  

I did try sudo to no effect. Unfortunately both boltctl and tbtadm appear to only allow you to change the approval status of the attached device, not the security level of the controller. It looks like that can only be done through firmware unfortunately.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
karatekid430
(@karatekid430)
Estimable Member
Joined: 1 year ago
Posts: 147
January 1, 2019 4:28 am  

Here, try getting the return value.

echo <somevalue> | sudo tee /sys/bus/thunderbolt/devices/domain0/security

Then do the following straight afterwards to reveal the return value:

echo $?

0 would be success, anything else has a meaning that can be found in the Linux source code by somebody who knows a bit about kernel code like myself.

Edit: I am a massive idiot. I typed all of that out without checking the permissions on that sysfs entry. It is 444 which means it is read only with no kernel code to handle writing to it. It was not designed to be written to. Under /sys the filesystem is virtual, and reading and writing the entries triggers kernel-space code, and is not opening actual files. It is an illusion that makes Linux a lot more intuitive and usable. I attribute the ease of doing many things in Linux compared to Windows to this.

Here's the kernel code that is run when you query security:

There is no security_store function needed to write to the sysfs entry and it declares DEVICE_ATTR_RO (read only) permissions for the entry.

This post was modified 3 weeks ago

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
karatekid430
(@karatekid430)
Estimable Member
Joined: 1 year ago
Posts: 147
January 1, 2019 5:07 am  
Posted by: Rekka3000
Posted by: theitsage

@rekka3000 Thank you for the update on this motherboard. Which version of Intel Thunderbolt Software are you running?

Running 17.4.77.400.

Motherboard TB3 (Alpine Ridge) is running NVM Firmware 14.00
Gigabyte TitanRidge AIC was running NVM Firmware 23.00

I saw mention of the fact there are newer firmwares out there for these controllers, if the manufacturer doesn't provide newer firmwares, what's the easiest way to upgrade? Does anybody have any advice on getting the AIC working? Does my error seem likely to be fixed by the jumper pins being connected like Karatekid did?

Posted by: Rekka3000

I can confirm the AsRock Intel Z390 Phantom Gaming ITX/AC Motherboard does NOT work with the Titanridge AIC. (Or at least out of the box)

Put it in, turned off (and tried it turned on) thunderbolt 3 support in the bios. Windows detects Titanridge AIC and it detected the Sonnet Breakaway eGFX 650. Checked the about section and has all ports registered and lists as egpu are supported.  However, it didn't see the RTX 2080 I had plugged in. 

Checked device manager and there was a "PCI Express Upstream Switch Port" device that had an error 31. The device seems to be the Sonnet eGFX 650 that was plugged in as HW ID is that of the Alpine Ridge controller. Motherboard thunderbolt 3 was definitely disabled and HWInfo confirms it was disabled. Uninstalled drivers and reinstalled about 10x. No luck.

I imagine it's to do with the TB3 header and needing to connect the pins together to trick it to wake up, but I tried splicing the provided TB3 header cable (plugged in 1 end into the header on the card, removed the necessary cable from the other sides jack and connected the cable, but that didn't work. I'll try it with a proper wire to see if my splice/join had errors, but does anyone have any suggestions?

Now, that Z390 motherboard is likely to have upgraded firmware that supports Titan Ridge, but because it has Alpine Ridge on the same board, and because it is from a manufacturer with no Titan Ridge products, it might be muddied. I would *definitely* change the Thunderbolt support in BIOS to "fully disabled" or if that is not available, "disabled". I had issues when Alpine Ridge support is running with Titan Ridge with devices not enumerating. Are there options in BIOS like "Titan Ridge workaround for OSUP" or something about selecting OS support? I am sure they will be there, but they might be hidden - in which case you would need to boot into an EFI shell off a USB and set variables manually. If you are interested in this approach, I will extract the IFR for your motherboard from the BIOS update from Asrock and send it to you, which will reveal the offsets of all the options. Then you can go into the EFI shell and do setup_var <offset> <desired value> to change hidden options.

What you described definitely sounds like the BIOS interfering based on my experiences, but it might not hurt to check the NVM version of the Sonnet. In Linux, "cat /sys/bus/thunderbolt/devices/?-?/nvm_version" and to check you have the right device, "cat /sys/bus/thunderbolt/devices/?-?/device_name".

Without proper BIOS support enabled (assuming that the Thunderbolt BIOS interferes when set to "enabled", requiring it to be disabled), you will not be getting busses and resources reserved, meaning the devices will have to be pre-approved and then the computer rebooted to make them detected at boot time and reserved. I am working on a Linux patch to enable perfect Titan Ridge support without an inkling of BIOS support, and it is promising, but it will take more time to tidy up and try to submit it. On Linux, you can get some results by passing to kernel parameters "pci=realloc,assign-busses,hpbussize=0x33,hpmemsize=128M,nocrs" but the issue is that passing hpmemsize too high kills it. Because it tries to assign equal amounts of 32-bit address space and 64-bit address space, when it runs out of room for the desired amount in 32-bit, it all fails - even though you ideally only want a few MB of 32-bit, but as much 64-bit space as you can get. Most graphics will want 256MB, plus other little bits, plus enough to support the Thunderbolt stuff around it. For me, it fails if I try to exceed about 128MB without a kernel patch. A simple kernel patch allows me to hot-add devices at depth 1 perfectly, but if I try to chain them, I need to write a completely new handler for the Thunderbolt special case to make sure the allocation is done properly.

The Linux kernel tries to allocate everything perfectly - doing depth-last and allocating the memory required under the parent bridges. But with Thunderbolt and hot-adding devices, this does not work. It tries to allocate, but they will inevitably fail - as it will be requesting the same amount of space from the kernel resources as in the parent bridge, and some of that space will have been consumed by the PCI endpoints. What we want is a way of saying "the hotplug bridge corresponding to the physical host Thunderbolt ports will have this amount of resources attached, and each further device will take what it needs and put the rest of the free memory to its daisy chaining port, and if we run out of memory, then we are screwed and need to reboot and request more to be reserved, and we cannot do anything about it".

This post was modified 3 weeks ago

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
karatekid430
(@karatekid430)
Estimable Member
Joined: 1 year ago
Posts: 147
January 1, 2019 5:12 am  

Oh, I came here to say that the Winstars Thunderbolt 3 to dual DisplayPort 1.4 adapter that I mentioned a while ago is confirmed to be JHL7440 with USB-C fallback. I contacted the manufacturers. Their notes say it is not recommended to mention the USB-C fallback to avoid confusing consumers, or something to that effect. Here is the official page which does not say anything about all of this: https://thunderbolttechnology.net/product/thunderbolt%E2%84%A2-3-dual-displayport-8k-adapter

It's a little bit sad - so far, I only know of the HP G2 dock and this Winstars one with the JHL7440.

I would not recommend it because it still has the attached cable. There is one with removable cable, but not Titan Ridge. I am just going to wait for them to upgrade it to Titan Ridge.  https://www.monoprice.com/product?p_id=33387

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
karatekid430
(@karatekid430)
Estimable Member
Joined: 1 year ago
Posts: 147
January 1, 2019 5:17 am  

Oh, and here's some evidence that Thunderbolt open-sourcing is still happening (they are running late, expect in 1H/2019).

https://www.cnet.com/news/how-macbook-air-showcases-the-battle-between-usb-c-and-thunderbolt/

I assumed that because they had not taken the notice down with their original plans of open-sourcing that they were still planning on doing it. But this is a lot more reassuring. I wonder if this has something to do with the 16 new PCI IDs for unknown Thunderbolt controllers in the Thunderbolt UWD driver.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Rekka3000
(@rekka3000)
Active Member
Joined: 3 months ago
Posts: 13
January 1, 2019 9:49 am  

Hey!

Cheers for the support, as I mentioned in a newer post, I got it working by doing the pre-approval + reboot method. My motherboard does indeed have "Titan Ridge workaround for OSUP" and a lot of other options. If there's anything I can do to somehow get it working, let me know.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
karatekid430
(@karatekid430)
Estimable Member
Joined: 1 year ago
Posts: 147
January 2, 2019 1:41 am  
Posted by: Rekka3000

Hey!

Cheers for the support, as I mentioned in a newer post, I got it working by doing the pre-approval + reboot method. My motherboard does indeed have "Titan Ridge workaround for OSUP" and a lot of other options. If there's anything I can do to somehow get it working, let me know.

 

Sorry, I tried to read some backposts but I probably skim read too quickly and missed things.

Okay, so experiment with those options. If Thunderbolt support must be enabled, then definitely enable anything that mentions Titan Ridge. I do not own any motherboard with the newer Thunderbolt BIOS modules inside (but have analysed them by extracting their BIOSes). I just have a couple of Titan Ridge AICs and an Alpine Ridge era motherboard.

You are never going to get official full support - as your motherboard does not have the GPIO which is officially still required (even though we have shown it does little to nothing at all, and nothing critical). The only chance you have is the fact that it is the newer generation loaded with the BIOS that knows about Titan Ridge, even though the motherboard was never meant to use it. Worst case, you use Titan Ridge with the BIOS support disabled, like the people who showed it working on AMD systems did. Hotplug will not work without OS or DSDT patches, but at least you will have something.

Care to elaborate on your workloads? If you are just attaching external graphics then it is probably not a big deal. If you are hot-adding a NVMe SSD constantly then it might be a pain. Although if you boot with something attached and it works in the first place, you should be able to yank it out and hot-add it to that same port thereafter, as the required resources will still be present after being reserved at boot time. Although it is not the best solution in the long run, the easiest solution would be for the add-in card to present as a device that appears as though all 6 devices on each port are attached while the OS boots, to get it to reserve the bus numbers and bridge resources. Intel would have to do that in firmware. But as I said, in the long run it will just make things worse - for example, if you want to boot off a Thunderbolt device, or request for more resources to be reserved for large BAR graphics cards.

Basically, if you experiment with all of the options with Thunderbolt support enabled in BIOS, and it does not work at all, you will have to disable Thunderbolt support in BIOS and just work with it without hotplug and attaching at boot time. A nuisance and not ideal, but it will not actually stop you from doing anything. The ideal thing will be to keep the Alpine Ridge port on the motherboard. Although it uses a crap controller (PCIe 3.0 x2 only), it would be nice to have. If you can get the Thunderbolt enabled in BIOS for the inbuilt port without it interfering with the Titan Ridge (even if hotplug on Titan Ridge is broken) then at least you can attach three devices at once. There might be options about AIC support in BIOS. See if disabling AIC support and enabling OSUP workaround, or some combination of the options, helps.

Please post a photo of your screen on the Thunderbolt options in BIOS so I can make some suggestions. I can see what options are available in BIOS by looking in the ROM from Asrock's website, but I cannot tell which ones it exposes in the GUI and which are hidden.

On a side note, if Intel does release Thunderbolt in 1H/2019 as open-spec and actually releases control over it (public domain or grants permission for unencumbered use) then support might come back for Titan Ridge add-in cards. If it requires the motherboard vendors to make a BIOS update, then it is less likely, as they already have your money. However, Microsoft might make changes to the ntoskrnl to handle Titan Ridge on its own (as I am trying to do for Linux).

Best of luck!

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
karatekid430
(@karatekid430)
Estimable Member
Joined: 1 year ago
Posts: 147
January 9, 2019 7:51 am  

Hello,

The new Dell 9380 may or may not be Titan Ridge.

https://www.dell.com/support/home/us/en/19/drivers/driversdetails?driverId=C25P2&osCode=WT64A&productCode=xps-13-9380-laptop

You can run this NVM update utility on the Dell 9370 (and maybe any computer) and type the BIOS password if you have one and it will extract to %temp%/Dell directory.

The package contains a lot of firmwares for a lot of laptops with different controllers. But if you do

grep -r -a --byte-offset --only-matching $'\x86\x80\xeb\x15'

You get hits on a few of the files. For some reason, the byte offset of the controller in Titan Ridge firmwares is 512 higher than the Alpine Ridge ones (19472 vs 19984 or 0x4c10 vs 0x4e10).

But these are NVM35 (offset 20104 for Titan Ridge). The offset of NVM version is 19528 on Alpine Ridge firmwares. The ones with NVM40 are Alpine Ridge.

That means it is highly likely that *something* from Dell has or will have Titan Ridge (unless they just bundled all the firmwares from Intel into the package carelessly).

Anybody else care to do some sleuthing? My problem is determining which firmware in the package is for the Dell 9380.

Cheers!

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
karatekid430
(@karatekid430)
Estimable Member
Joined: 1 year ago
Posts: 147
January 9, 2019 9:17 am  

Wow, this is something which I knew possible for a long time but I never thought I would see.

I installed a NVM40 for 15d2 controller on my Dell 9370. It has not bricked the controller. But it has stopped it enumerating PCI.

Then I realised, HOLY CRAP I KNOW WHAT THIS MEANS. I went into WMI Explorer and I was 100% correct.

It has finally enabled OsNativePciEnumeration on Alpine Ridge. Not only that, but the RTD3 flag is also set, which is more than could be said for the Gigabyte GC-TITAN RIDGE in my unsupported setups.

I knew this has been possible because I talked to Mika Westerberg of Intel who is largely responsible for most of the Thunderbolt drivers, at least in Linux. He said months ago that it is possible with Alpine Ridge but it requires more work than Titan Ridge on the vendor's part, but less than Alpine Ridge without OsNativePciEnumeration.

Now I am going to see what other possibilities this has opened up. Ideally, it will make an Alpine Ridge detectable in any system (will need to eliminate the need for additional firmware to be flashed to the chipset every boot). But if I can get this working, then I will have a system with many of the benefits of Titan Ridge (minus DP1.4 support).

This means that if the Dell 9380 has NVM40 like the package name under its downloads section, then it is Alpine Ridge (*sobs*). But, it does seem to suggest that they have finally done some meaningful work on Alpine Ridge....

Edit: Disabled Thunderbolt support in Dell 9370 BIOS and can still see the Thunderbolt NHI. This is promising! Next I will try to flash the ROM onto my Alpine Ridge add-in cards with the 15d2 controller and see if it works the same magic there. Unfortunately, the Dell 9370 has not yet successfully enumerated the PCI for a device, though - I will look into it.

Edit2: Soldered wires onto an engineering sample MSI Thunderbolt M3 AIC (8086:15d2), backed up the ROM contents, went into Linux, flashed NVM40 to it. Hard brick, no power delivery or nothing. Restored ROM contents with programmer. I think I need to figure out how to separate the USB-C port firmware and power delivery from the MSI firmware and splice that region into the NVM40 from Dell to make it work.

As for my Dell laptop, it sorta works with Thunderbolt 3 support disabled in BIOS. I have not gotten around to editing EFI variables in EFI shell with extracted IFR information yet. But the Thunderbolt controller is always visible, now, even when no devices are attached. Strangely enough, the BIOS still reserves bus numbers and PCI root port resources with Thunderbolt disabled. Strangely enough, Windows actually does a better job of using those than Linux - which stuffs it up after the first bus. Linux is reporting the OSI handover for controlling PCIe Hotplug as failed. Usually this passes when the Thunderbolt has been disabled in BIOS - which makes me wonder if it is getting properly shut down.

This post was modified 1 week ago

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@duc_phuc_tran)
New Member
Joined: 1 week ago
Posts: 3
January 12, 2019 1:17 am  

The new ThinkPad Thunderbolt 3 Dock Gen 2 uses Titan Ridge.  Their support page spells out supported video resolutions when using TB3 vs USB-C on DP 1.2 including saying it can support DP1.4 resolutions.  I just received mine to use with a ThinkPad X1 Yoga (3rd Gen).

Support Page:  https://support.lenovo.com/us/en/solutions/PD500265
Display and Video Output Configurations - Docking Stations: https://support.lenovo.com/solutions/pd029622

The dock doesn't work with my Mac Pro Late 2013 using the Apple TB3 to TB2 Adapter. Nothing happens when I connect it to my Mac. No enumeration is happening. When cold starting with it connected, the Mac turns on but nothing happens. It required a hard shutdown. Should the dock work with my mac?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
karatekid430
(@karatekid430)
Estimable Member
Joined: 1 year ago
Posts: 147
January 14, 2019 1:24 am  
Posted by: Duc Phuc Tran

The new ThinkPad Thunderbolt 3 Dock Gen 2 uses Titan Ridge.  Their support page spells out supported video resolutions when using TB3 vs USB-C on DP 1.2 including saying it can support DP1.4 resolutions.  I just received mine to use with a ThinkPad X1 Yoga (3rd Gen).

Support Page:  https://support.lenovo.com/us/en/solutions/PD500265
Display and Video Output Configurations - Docking Stations: https://support.lenovo.com/solutions/pd029622

The dock doesn't work with my Mac Pro Late 2013 using the Apple TB3 to TB2 Adapter. Nothing happens when I connect it to my Mac. No enumeration is happening. When cold starting with it connected, the Mac turns on but nothing happens. It required a hard shutdown. Should the dock work with my mac?

It depends if it is Mac certified. It should enumerate but MacOS might not have drivers for the particular PCIe endpoints in the dock. Can you post output of "ioreg -b" command in an attachment text file? At least I think it is that command. Edit: just to clarify, with the Titan Ridge dock attached, if that was not implied clearly.

Also, do other Thunderbolt 3 self-powered devices work with that adapter?

Thunderbolt controllers need a certain level of NVM firmware to work with the Thunderbolt 2 adapter. I do not know if Apple controllers are updatable, or if Apple does it automatically behind the scenes.

I must say it is strange of you to buy a Titan Ridge dock and then use it with Thunderbolt 2, which does not have enough bandwidth for any of the benefits. Unless you are planning on upgrading the laptop in the foreseeable future. It is good to plan for the future, so in that case, excellent decision.

This post was modified 6 days ago

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@duc_phuc_tran)
New Member
Joined: 1 week ago
Posts: 3
January 14, 2019 6:12 am  

Thanks for the reply. I should have been clearer that I was asking in a more general sense if the Apple Thunderbolt 3 to Thunderbolt 2 Adapter is expected to work with peripherals using a Titan Ridge JHL7440 with USB-C computer port compatibility enabled. I believe it is supposed to work but does not when I tried. I didn’t want to waste time trying if others have attempted with the same outcome. The Titan Ridge controllers are a compatible extension of the Alpine Ridge controllers, so it is supposed to work.

I don’t think it is a matter of certification since many devices work without being certified. Nor is it strange. The two major Titan Ridge features are DP 1.4 and USB-C computer port compatibility which provide for single-cable monitors and enterprise docks. You buy a single Titan Ridge dock so you can use it with various host systems including those with much lower bandwidth than TB3. A quote from an Intel product announcement:

Enterprise dock makers can deploy a single Thunderbolt 3 dock for thousands of employees to streamline hardware installations and accelerate the speed of IT delivery.

I would say it is common to obtain TB3 peripherals to use with TB2 hosts especially on this site since the External GPU Buyer’s Guide says:

Note: better value Thunderbolt 3 enclosures work with TB2/TB1 Macs in macOS and with PC notebooks via a US$49 Apple TB3 to TB2 adapter.

I actually bought the dock for a ThinkPad X1 Yoga (3rd Gen) which is a business class laptop. The dock does not enumerate so there is nothing of significance in the output of ioreg.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@duc_phuc_tran)
New Member
Joined: 1 week ago
Posts: 3
January 16, 2019 9:50 pm  

There was a firmware update for the ThinkPad dock.  It now works with my Mac Pro Late 2013 using the Apple Thunderbolt 3 to Thunderbolt 2 Adapter when hot plugged running macOS.  It does not work from boot. It still hangs my Mac.

The Intel Titan Ridge Thunderbolt xHCI embedded USB 3.1 Gen 2 host controller uses the AppleUSBXHCITR driver and the speed is 10 Gb/sec. I did a quick test with a Samsung T5 using USB-C. It was reported using 10 Gb/s and achieved ~500 MB/s. It was only ~360 MB/s using USB 3.1 Gen 1 in a previous test on the internal controller. I was able to connect a DisplayPort monitor to the downstream Thunderbolt 3 port.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
AlexD
(@alexd)
New Member
Joined: 10 hours ago
Posts: 2
January 19, 2019 1:03 pm  

Hello everyone! I'm wondering if anyone here has any experience connecting Apple Thunderbolt Display to PC with Titan Ridge JHL7540 Thunderbolt chip (either onboard or as an add-in TB card)?

I've recently finished my PC build based on latest Gigabyte's Z390 Designare. It features an onboard JHL7540 Titan Ridge controller and two built-in Thunderbolt 3 ports, as well as DP Input to route the discrete video card's DP output to motherboard TB controller.

Unfortunately, I hadn't figured out the way to connect my Apple Thunderbolt Display via standard Apple TB3 to TB2 adapter. Display simply stays black and won't turn on. Never.

Tried various BIOS TB settings, tried latest Windows 10, latest Ubuntu and even latest macOS 10.14.2. Display never shows up and never turns on.

I heard that Apple Thunderbolt Display worked fine with Alpine Ridge, so there might be some incompatibility issues with Titan Ridge and this particular display maybe?

I already talked to Intel Thunderbolt team engineers and they confirmed, that JHL7540 should work fine with previous gen devices. But Gigabyte engineers said to me, that Titan Ridge chip operates only in native mode and doesn't support any older devices (TB1/2) that may require legacy mode. They said it's a hardware limitation and can't be adjusted by BIOS or whatever. 

So my question is: is it true? Please let me know your thoughts on it. Are there really any reports of some devices stopped working with Titan Ridge while they were working fine with previous gens of TB controllers?

My thought was that Titan Ridge may properly switch its operating mode depending on the device being plugged in. And my second thought was that Titan Ridge as a next, more powerful version of Alpine Ridge should do and should support everything that Alpine Ridge could, and provide even more.

Just trying to figure out the way to connect my lovely Apple display to my new PC build. Thank you in advance for any thoughts or feedback.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
joevt
(@joevt3)
Reputable Member
Joined: 1 year ago
Posts: 300
January 19, 2019 2:39 pm  
Posted by: AlexD

Hello everyone! I'm wondering if anyone here has any experience connecting Apple Thunderbolt Display to PC with Titan Ridge JHL7540 Thunderbolt chip (either onboard or as an add-in TB card)?

I've recently finished my PC build based on latest Gigabyte's Z390 Designare. It features an onboard JHL7540 Titan Ridge controller and two built-in Thunderbolt 3 ports, as well as DP Input to route the discrete video card's DP output to motherboard TB controller.

Unfortunately, I hadn't figured out the way to connect my Apple Thunderbolt Display via standard Apple TB3 to TB2 adapter. Display simply stays black and won't turn on. Never.

Tried various BIOS TB settings, tried latest Windows 10, latest Ubuntu and even latest macOS 10.14.2. Display never shows up and never turns on.

I heard that Apple Thunderbolt Display worked fine with Alpine Ridge, so there might be some incompatibility issues with Titan Ridge and this particular display maybe?

I already talked to Intel Thunderbolt team engineers and they confirmed, that JHL7540 should work fine with previous gen devices. But Gigabyte engineers said to me, that Titan Ridge chip operates only in native mode and doesn't support any older devices (TB1/2) that may require legacy mode. They said it's a hardware limitation and can't be adjusted by BIOS or whatever. 

So my question is: is it true? Please let me know your thoughts on it. Are there really any reports of some devices stopped working with Titan Ridge while they were working fine with previous gens of TB controllers?

My thought was that Titan Ridge may properly switch its operating mode depending on the device being plugged in. And my second thought was that Titan Ridge as a next, more powerful version of Alpine Ridge should do and should support everything that Alpine Ridge could, and provide even more.

Just trying to figure out the way to connect my lovely Apple display to my new PC build. Thank you in advance for any thoughts or feedback.

I think those Gigabyte engineers are full of crap.

I've successfully connected Thunderbolt 2 and Thunderbolt 1 devices to the Titan Ridge ports of a Mac Mini 2018. I've tried a display via a Thunderbolt 2 dock. I've done the same with a GC-TITAN RIDGE card. I have not tried an Apple Thunderbolt Display.

Did you try using both Thunderbolt 3 ports of the motherboard?

Does the Intel Thunderbolt software ask you to authorize the Apple Thunderbolt Display?

Do the devices (USB 2.0 controller, FireWire OHCI controller, Gigabit Ethernet controller) of the Apple Thunderbolt Display appear in Device Manager?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


AlexD liked
ReplyQuote
AlexD
(@alexd)
New Member
Joined: 10 hours ago
Posts: 2
January 19, 2019 3:08 pm  
Posted by: joevt
Posted by: AlexD

Hello everyone! I'm wondering if anyone here has any experience connecting Apple Thunderbolt Display to PC with Titan Ridge JHL7540 Thunderbolt chip (either onboard or as an add-in TB card)?

I've recently finished my PC build based on latest Gigabyte's Z390 Designare. It features an onboard JHL7540 Titan Ridge controller and two built-in Thunderbolt 3 ports, as well as DP Input to route the discrete video card's DP output to motherboard TB controller.

Unfortunately, I hadn't figured out the way to connect my Apple Thunderbolt Display via standard Apple TB3 to TB2 adapter. Display simply stays black and won't turn on. Never.

Tried various BIOS TB settings, tried latest Windows 10, latest Ubuntu and even latest macOS 10.14.2. Display never shows up and never turns on.

I heard that Apple Thunderbolt Display worked fine with Alpine Ridge, so there might be some incompatibility issues with Titan Ridge and this particular display maybe?

I already talked to Intel Thunderbolt team engineers and they confirmed, that JHL7540 should work fine with previous gen devices. But Gigabyte engineers said to me, that Titan Ridge chip operates only in native mode and doesn't support any older devices (TB1/2) that may require legacy mode. They said it's a hardware limitation and can't be adjusted by BIOS or whatever. 

So my question is: is it true? Please let me know your thoughts on it. Are there really any reports of some devices stopped working with Titan Ridge while they were working fine with previous gens of TB controllers?

My thought was that Titan Ridge may properly switch its operating mode depending on the device being plugged in. And my second thought was that Titan Ridge as a next, more powerful version of Alpine Ridge should do and should support everything that Alpine Ridge could, and provide even more.

Just trying to figure out the way to connect my lovely Apple display to my new PC build. Thank you in advance for any thoughts or feedback.

I think those Gigabyte engineers are full of crap.

I've successfully connected Thunderbolt 2 and Thunderbolt 1 devices to the Titan Ridge ports of a Mac Mini 2018. I've tried a display via a Thunderbolt 2 dock. I've done the same with a GC-TITAN RIDGE card. I have not tried an Apple Thunderbolt Display.

Did you try using both Thunderbolt 3 ports of the motherboard?

Does the Intel Thunderbolt software ask you to authorize the Apple Thunderbolt Display?

Do the devices (USB 2.0 controller, FireWire OHCI controller, Gigabit Ethernet controller) of the Apple Thunderbolt Display appear in Device Manager?

Thank you very much for your response @joevt !
I fully agree with you and I believe that they did something really wrong with Titan Ridge on PCH implementation in their Z390 Designare. It may be improper/incomplete BIOS support for this TB controller, bugs in firmware (in conversation with Intel Thunderbolt team I was told that currently the control over firmware modifications is up to vendors) or something else.

Seems like there are problems with proper TB devices enumeration/initialization which prevent the display from being recognized. I had a very long conversation with Gigabyte USA recently, but in the end I felt like I'm talking to walls. They refuse to confirm the issue and just keep telling me that it's Titan Ridge's hardware limitation. 

Yes, of course, I tried both TB 3.0 ports on the motherboard.

None of them recognizes Apple Thunderbolt Display. None of the internals of the display (usb, camera, sound, ethernet, firewire) appear in Windows.

Thunderbolt Software just shows me two empty ports all the time without any devices listed below. No notifications, alerts or connect attempts at all.

I'm running latest 17.4.77.400 driver and NVM version is 33 (Thunderbolt package was downloaded from Gigabyte official website). Just in case you might be interested: I tried vaious security settings (from Disabled/Legacy to User Authorization and Secure Connect). No luck, even at legacy mode. Which is absolutely strange for me. I believed, the older TB1/2 devices should be working well when no authorization is required (legacy mode).

In Ubuntu, the OS itself recognizes the controller (Titan Ridge) but there are no connected devices recognized as well.

Same for macOS 10.14.2. Apple Thunderbolt Display stays black all the time and never turns on.

USB-C flash drive is working perfectly if plugged into any of those ports, btw.

On another forum there's a thread about Z390 Designare and people posting that they had success connecting various audio TB devices (UAD mostly). Someone posted that even his LG Ultrafine 5K is working perfectly in macOS. It is TB3 display and for some reason Titan Ridge seems to support it without any issues. Other USB-C (DisplayPort, not true TB) monitors are also supported if connected to any of those two ports on the back of the motherboard.

So it seems like the issue is ONLY with true Thunderbolt monitors of previous generations (TB1/2).

I'm still wondering: why Apple Thunderbolt Display isn't supported by Titan Ridge JHL7540. I had really big hopes for this motherboard and its Thunderbolt capabilites.
Just don't want to believe that with Titan Ridge introduction they are trying to force people to buy the only most recent TB3 hardware.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Page 6 / 6 Prev