Contribute
Register

tonymacx86's Skylake Thunderbolt 3 Test Build: GA-Z170X-UD5-TH - i5-6600K

Status
Not open for further replies.
I just got Thunderbolt to work on my build after all this time. The crazy thing is that I only changed one setting. In the BIOS, I moved the Thunderbolt I/O from zero to 8. The other settings are Unique ID, Ignore Thunderbolt Option ROM, and that's it.

I also booted into my Windows 10 drive and went into device management in order to go through the PCIE, USB, Thunderbolt etc. -right clicked and then updated as many parts that would run an update. I was surprised that everything from my the PCIE bridges to my ATI Radeon card actually had newer firmware.

When I booted back into El Capitan......My CalDigit Thunderbolt 2 dock was visible and the usb drive that was plugged into it was mounted and visible and I can even HOTSWAP!!!

There was only one issue. I attempted to daisy chain more Thunderbolt devices through the CalDigit dock and when you do that, it stops working.

GA-Z87x-UD7-th (rev. 2.0)
Intel Core i7 4771 LGA 1150
ATI Radeon HD
Other Hardware:
OWC 480 GB Mercury SSD [El Capitan osX]
Samsung SSD 840 EVO 500GB
1 TB [internal for separate file storage]
1 TB [Windows]
2 TB Seagate Backup Plus Thunderbolt
32 Gb G.Skillz Sniper 2400 mhz ddr3



Looks like you have a different BIOS version. I do not see the 0 to 8 option in mine.
 
Focus on the last line on the BIOS Screen, the Reserved I/O. I adjusted it from 0 to 8 and that caused the Thunderbolt to show up consistently. Last night, I increased it to 16 to test the allowance to daisy chain thunderbolt devices from one port, but it made no difference on that issue.
 

Attachments

  • IMG_20170816_113207.jpg
    IMG_20170816_113207.jpg
    6 MB · Views: 465
  • IMG_20170814_163646.jpg
    IMG_20170814_163646.jpg
    7.5 MB · Views: 381
  • IMG_20170814_172600.jpg
    IMG_20170814_172600.jpg
    3.6 MB · Views: 331
Last edited:
Focus on the last line on the BIOS Screen, the Reserved I/O. I adjusted it from 0 to 8 and that caused the Thunderbolt to show up consistently. Last night, I increased it to 16 to test the allowance to daisy chain thunderbolt devices from one port, but it made no difference on that issue.
"Extra Bus Reserved" seems high but I'm only guessing at it's purpose. The following is my reasoning:

Install lspci and use this command:
Code:
lspci -nnvt
That will show the distribution of buses. If the value 106 is related to the subordinate minus primary bus for the Thunderbolt 2 controller then maybe it should be lowered. There are only 256 total buses allowed.

My built in Thunderbolt 3 controller has bus: primary=00, secondary=09, subordinate=41 which is 57 buses.
bus 09 is the upstream port with secondary=0A, subordinate=41.
bus 0A is the downstream port
with 4 slots (downstream ports):
slot 00 has secondary/primary=0B. This is for the Thunderbolt 3 NHI endpoint.
slot 01 has secondary=0C, subordinate=25 which is 26 buses. This is for the Thunderbolt 3 port 1.
slot 02 has secondary/primary=26. This is for the Thunderbolt 3 USB 3.1 gen 2 controller.
slot 04 has secondary=27 subordinate=41 which is 27 buses. This is for the Thunderbolt 3 port 2.
 
Focus on the last line on the BIOS Screen, the Reserved I/O. I adjusted it from 0 to 8 and that caused the Thunderbolt to show up consistently. Last night, I increased it to 16 to test the allowance to daisy chain thunderbolt devices from one port, but it made no difference on that issue.
I'm running F21 BIOS and the options are different. Bottom 2 lines are default.
 

Attachments

  • IMG_4413.jpg
    IMG_4413.jpg
    2 MB · Views: 1,011
I'm running F21 BIOS and the options are different. Bottom 2 lines are default.
I made the adjustments to match your settings to see if it made any difference. Once I rebooted into osx, I got a 0 with the slash through it.... Soooooo, I put everything back as it was previously and Thunderbolt went back to working for one device per port with no daisy chaining. So, I'm just going to go with it. I'm building a new rig anyway. I'm going to build with a Cooler Master cosmos 2 case, a GigabyteGA-Z170X-Gaming G1 Extended motherboard, and a Core i7 7700k. I'm trying to decide on a graphics card for VR and I'll just use what I learned to get Thunderbolt running on my current rig to hopefully get it working immediately on the new one.
IMG_20170814_165236.jpg
IMG_20170802_122628.jpg
IMG_20170802_121955.jpg
 
Wished I had found this thread earlier. I wanted to share my success today in getting my onboard Thunderbolt 3 working!!!

I have a Gigabyte GA-Z170X-UD5 TH motherboard with an Intel i7 6700K, GTX 980 running 4K@60Hz with 32gb memory and a Focusrite Clarett 8pre over TB2 cable using the Apple TB3>TB2 adapter.

I think the key points were:
1. After running the Gigabyte thunderbolt firmware install utility (In Windows), you MUST go into the Program Files x86 folder > Gigabyte > TB Firmware folder and run the .exe file there to ACTUALLY update the firmware. Takes 2 min or so and counts up from 0% to 100%. Then be sure to shutdown, pull power for 30 seconds. I did a minute. Gigabyte didn't make this clear to me when I asked their support for help. They just sent me the download link and said to 'install it to update the firmware'.

Here's the link they sent me: http://download.gigabyte.us/FileList/Utility/mb_utility_thunderbolt-fw_z170x-ud5-th.zip
Version B16.0818.1 it says once unzipped. Might be beta? Latest perhaps? Worked for me! :)

2. The bios settings are KEY! I figured these out on my own just before finding this thread sadly. But the last few posters already had it figured out it seems. I happened to already upgrade my bios to F22a thinking it might help. Not sure if its required or even helped, but my options were different than prior versions it seems.

Here are pics from my BIOS settings:

Code:
https://www.amazon.com/photos/share/WmSSCFo6sZpN4GxNQQx5Njtd7i2wngJSC3aSOVj8Dgn

OiysSrDqRL69cmisa6yYjg


These are WORKING 100%! Been testing now for 3+ hours RELIABLY with reboots and it keeps the Focusrite as the chosen sound card after reboots. I'm also getting 1.5ms latency roundtrip!

I'm so stoked. Been wanting this to work now for months. Finally got it working today.

I also own a Universal Audio uaudio Apollo Twin Duo Thunderbolt gen1 and will test that next.

So please share this info with anyone who wants to know "How to get Thunderbolt 2 or 3 working with the Focusrite Clarett8pre".

In fact, I'm thinking of creating a specific thread on here for users trying to get their Focusrite Clarett 8pre and Apollo working. Should I? Might help others like me find the answers faster.

Tested with Cubase Pro 9.0.0 and 9.0.20 successfully. Smooth as butter.

Like I said, I'll share more once I test the Apollo.

Also, I installed MacOS Sierra 10.12.6 earlier today before beginning. Not sure if it has more in it that helped or not...

Summary of settings:
Gigabyte F22a bios:
Peripherals>Thunderbolt(TM) Support = Enabled
Thunderbolt Boot Support = Disabled
ThunderBolt Detachable Graphics Support = Disabled
Skip PCI OptionRom = Disabled
Security Level = No Security
Reserved Memory = 256
Reserved PMemory = 32

Then all the typical settings to get OSX to work:
FYI, I learned today that if XHCI Hand Off is DISABLED, that OSX WOULDN'T BOOT AT ALL today. Once enabled it booted. So after the bios upgrade make sure to put everything back to these specialized settings so that your MacOS Sierra will boot again.

Peripherals > XHCI Hand-off = Enabled
Chipset > VT-d = Disabled

Internal Graphics = Disabled (I'm using a GTX980. Read that shutting off the onboard Intel graphics helps the CPU run cooler as 1/2 the CPU die is graphics. Not sure if that's really true, but would love to confirm this if so. About it helping it run cooler I mean.

Chipset > IOAPIC 24-119 Entries - I have these off currently and it is working. Read that it may not matter after Sierra. Can anyone confirm?

BIOS > Windows 8/10 Features = Other OS

Peripherals > Trusted computing = Disabled (Not sure this matters? I have it disabled currently and it is working.)
Peripherals > Super IO Configuration = Disabled
Peripherals > Intel(R) Bios Guard Technology = Disabled (Not sure this matters? I have it disabled currently and it is working.)

Please let me know if the above could be enabled as they might be nice security features to have in place and active. If so I'll update my summary guide here.

Hope that helps!

Edit: I haven't tested it in Win 10 yet. I'll try that next and let you know as well.

Edit 2: Focusrite drivers used successfully:
Mac: Focusrite Control 2.1.7
14/06/2017

IMG_9368.JPG
 
Last edited:
Wished I had found this thread earlier. I wanted to share my success today in getting my onboard Thunderbolt 3 working!!!

I have a Gigabyte GA-Z170X-UD5 TH motherboard with an Intel i7 6700K, GTX 980 running 4K@60Hz with 32gb memory and a Focusrite Clarett 8pre over TB2 cable using the Apple TB3>TB2 adapter.

I think the key points were:
1. After running the Gigabyte thunderbolt firmware install utility (In Windows), you MUST go into the Program Files x86 folder > Gigabyte > TB Firmware folder and run the .exe file there to ACTUALLY update the firmware. Takes 2 min or so and counts up from 0% to 100%. Then be sure to shutdown, pull power for 30 seconds. I did a minute. Gigabyte didn't make this clear to me when I asked their support for help. They just sent me the download link and said to 'install it to update the firmware'.

Here's the link they sent me: http://download.gigabyte.us/FileList/Utility/mb_utility_thunderbolt-fw_z170x-ud5-th.zip

2. The bios settings are KEY! I figured these out on my own just before finding this thread sadly. But the last few posters already had it figured out it seems. I happened to already upgrade my bios to F22a thinking it might help. Not sure if its required or even helped, but my options were different than prior versions it seems.

Here are pics from my BIOS settings:

Code:
https://www.amazon.com/photos/share/WmSSCFo6sZpN4GxNQQx5Njtd7i2wngJSC3aSOVj8Dgn

OiysSrDqRL69cmisa6yYjg


These are WORKING 100%! Been testing now for 3+ hours RELIABLY with reboots and it keeps the Focusrite as the chosen sound card after reboots. I'm also getting 1.5ms latency roundtrip!

I'm so stoked. Been wanting this to work now for months. Finally got it working today.

I also own a Universal Audio uaudio Apollo Twin Duo Thunderbolt gen1 and will test that next.

So please share this info with anyone who wants to know "How to get Thunderbolt 2 or 3 working with the Focusrite Clarett8pre".

In fact, I'm thinking of creating a specific thread on here for users trying to get their Focusrite Clarett 8pre and Apollo working. Should I? Might help others like me find the answers faster.

Tested with Cubase Pro 9.0.0 and 9.0.20 successfully. Smooth as butter.

Like I said, I'll share more once I test the Apollo.

Also, I installed MacOS Sierra 10.12.6 earlier today before beginning. Not sure if it has more in it that helped or not...

Summary of settings:
Gigabyte F22a bios:
Peripherals>Thunderbolt(TM) Support = Enabled
Thunderbolt Boot Support = Disabled
ThunderBolt Detachable Graphics Support = Disabled
Skip PCI OptionRom = Disabled
Security Level = No Security
Reserved Memory = 256
Reserved PMemory = 32

Then all the typical settings to get OSX to work:
FYI, I learned today that if XHCI Hand Off is DISABLED, that OSX WOULDN'T BOOT AT ALL today. Once enabled it booted. So after the bios upgrade make sure to put everything back to these specialized settings so that your MacOS Sierra will boot again.

Peripherals > XHCI Hand-off = Enabled
Chipset > VT-d = Disabled

Internal Graphics = Disabled (I'm using a GTX980. Read that shutting off the onboard Intel graphics helps the CPU run cooler as 1/2 the CPU die is graphics. Not sure if that's really true, but would love to confirm this if so. About it helping it run cooler I mean.

Chipset > IOAPIC 24-119 Entries - I have these off currently and it is working. Read that it may not matter after Sierra. Can anyone confirm?

BIOS > Windows 8/10 Features = Other OS

Peripherals > Trusted computing = Disabled (Not sure this matters? I have it disabled currently and it is working.)
Peripherals > Super IO Configuration = Disabled
Peripherals > Intel(R) Bios Guard Technology = Disabled (Not sure this matters? I have it disabled currently and it is working.)

Please let me know if the above could be enabled as they might be nice security features to have in place and active. If so I'll update my summary guide here.

Hope that helps!

Edit: I haven't tested it in Win 10 yet. I'll try that next and let you know as well.

This is excellent to know. It makes me feel very positive that as I put this next build together using the Z170x G1 extended, that there will be much less of a hassle getting those Thunderbolt ports fired up. I love the teamwork on this site.
 
ThunderboltWorkingInDeviceManager2.jpg :)

Yep. Well said SpaceGhost.

And guess what? :) The Apollo is working too!!! Muwahahahahahahaha. It's a good day.

Just some specifics. I downloaded the latest UAD drivers from uaudio.com . v930 for the Mac. Actually had them installed prior to all of my above post. But when I plugged in the Apollo and booted up it stated that it required a firmware update and asked to proceed. Just out of curiosity I tried playing some audio before applying the Apollo firmware update and it worked! Then applied the firmware and shut off the Apollo as instructed then turned it back on, but it wouldn't play audio until I rebooted the PC.

But it works now! Yeah baby. Even the input works as evidenced by the input level meter in settings. Didn't realize this had an onboard mic...

Anyway, couldn't wait to share the good news. I'll try booting into indows 10 next.

And notice I updated the first post with the version info on the firmware file Gigabyte sent me. Hope it helps.

Edit: And the exact drivers I used for the Focusrite Clarett are:
Mac: Focusrite Control 2.1.7
14/06/2017

Update: The Apollo worked immediately as soon as I booted into Win 10. :) It applied some auto update immediately to the software on its own but was working both before and after that. I'm downloading the v930 version for Win now as it still has the old drivers on my Win10 drive. But it's working no problem already.

I'll test the Focusrite next in Windows and let you know.
 
Last edited:
View attachment 273245 :)

Yep. Well said SpaceGhost.

And guess what? :) The Apollo is working too!!! Muwahahahahahahaha. It's a good day.

Just some specifics. I downloaded the latest UAD drivers from uaudio.com . v930 for the Mac. Actually had them installed prior to all of my above post. But when I plugged in the Apollo and booted up it stated that it required a firmware update and asked to proceed. Just out of curiosity I tried playing some audio before applying the Apollo firmware update and it worked! Then applied the firmware and shut off the Apollo as instructed then turned it back on, but it wouldn't play audio until I rebooted the PC.

But it works now! Yeah baby. Even the input works as evidenced by the input level meter in settings. Didn't realize this had an onboard mic...

Anyway, couldn't wait to share the good news. I'll try booting into indows 10 next.

And notice I updated the first post with the version info on the firmware file Gigabyte sent me. Hope it helps.

Edit: And the exact drivers I used for the Focusrite Clarett are:
Mac: Focusrite Control 2.1.7
14/06/2017

Update: The Apollo worked immediately as soon as I booted into Win 10. :) It applied some auto update immediately to the software on its own but was working both before and after that. I'm downloading the v930 version for Win now as it still has the old drivers on my Win10 drive. But it's working no problem already.

I'll test the Focusrite next in Windows and let you know.


I use the Apogee Ensemble firewire. I've been holding off on getting a Thunderbolt version...but now!!! Oh it's going down!
 
Not to rain on everyone's parade. I followed all the steps and got TB working. My issue is that is not 100% rock solid. I have said before, it works 8 times out of 10. But those 2 times suck, and why? If it works, it should work all the time. I didn't really get the sense that it wasn't 100% reliable until some time had passed. It worked for the first 2 weeks no problem. Then I get the startup without the drive mounting????? What changed - nothing? Then it would be fine for another week-ish or so. Then another no mount?? I just wish I could figure out why on the times that the drive won't mount??? I really hope that it's just me and my setup. I don't want this to happen to everyone. I just want it to be consistent. I'll keep plugging away trying to figure out why it isn't 100% until I get it.........
 
Status
Not open for further replies.
Back
Top