- Nov 3, 2017
- GA-Z270X-Gaming 5
- Nvidia GTX 1060
- Mobile Phone
I don't personally own a TB3 MBP, but I can probably arrange to borrow one for a while. I don't expect it to fail when plugged into an actual Mac, as I've had these two displays plugged into a 2012 Thunderbolt 1 MBP for months with no problems.Very strange. If you had a MacBook Pro with Thunderbolt 3, then you could test this configuration on that. If that failed, then you could report it to Apple via apple bug reporter. I don't think they'd appreciate a bug report from a Hackintosh though. The MacBook Pro has 4 Thunderbolt ports, so I would try both displays connected to one Thunderbolt chip, and then one Display connected to each Thunderbolt chip.
I have not had time to run all these tests yet, but I have done the first two. Log files from all the tools you've mentioned so far (ioreg, system profiler, and USB Prober) are attached. To possibly save you some download time, I found no significant difference between whether display 1 was plugged in on port 1 or port 2. Sharper eyes than mine may see a difference, but in both cases, generally what happened was the internal USB hub got assigned address 0x40000000 and everything worked.It might be interesting to compare the results of the following (make sure no USB devices are connected to each display):
1) Thunderbolt Display 1 to Thunderbolt port 1
2) Thunderbolt Display 1 to Thunderbolt port 2
What was interesting, though, is cold boot (total shutdown + wait 10 sec for TB display to shutdown also) versus warm boot (plain restart). I've attached IOreg from both.
Consistently, after a fully cold boot, not only would the TB Display's internals not work, but the Thunderbolt card itself (the IOThunderboltController node) along with all the PCI bridges would disappear from ioreg. Following this up with a warm boot would restore the Thunderbolt controller as well as the display's internals to working order. I've attached one of each ioreg output from cold versus warm boot.
This may explain why some people earlier observed the need to boot into Windows first -- I think some initialization step is not being done, particularly on cold boot. Possibly related to hot plugging or the System Profiler not recognizing that there is a Thunderbolt controller in place?
No DSDT patch. The specific USB-related things I installed were both from Multibeast: "Increase Max Port Limit 200 Series" and "3rd Party USB 3.0" -- I've since removed both these things.What exactly was the USB hack? If it was a DSDT patch, then it would be interesting to get a ACPI dump from Clover (press F4 at the Clover boot screen, you should notice that it hangs for a couple seconds as it saves the files to the EFI partition, meaning you can't move the drive selection left or right for a couple seconds). Then we can see how the Thunderbolt Displays appear in the DSDTs, if at all, and can determine how the patch affects that.
5.3 MB Views: 123
5.2 MB Views: 134
5.7 MB Views: 146
5.6 MB Views: 128
2.7 KB Views: 162
71.8 KB Views: 139
71.8 KB Views: 152
3.1 KB Views: 291
3.1 KB Views: 219
586 bytes Views: 149
586 bytes Views: 168
2.7 KB Views: 192