ALERT: half H2D performance issue on TI83 TB3 enclosures (Node, Venus, Devil Box...
 
Notifications
Clear all

ALERT: half H2D performance issue on TI83 TB3 enclosures (Node, Venus, Devil Box, XG Station 2)  

 of  30
  RSS

yjchua
(@yjchua)
Eminent Member
Joined: 5 years ago
 
Posted by: joevt
Posted by: yjchua

Already tried removing and reinserting it - no dice. Same with SMC and NVRAM reset. Don't have another card to try at the moment. Also tried using two different cables - the one that came with the Node and a 0.5m CableMatters TB3 cable. Maybe I should try getting an active cable?

Does the graphics card appear in the PCI section? Post a screenshot of that.

The Thunderbolt info shows the cable is ok (Speed: Up to 40 Gb/s x1, Current Link Width: x2). The problem is between the graphics card and the Thunderbolt controller of the eGPU. Maybe you need a new graphics card (test it in a different PCIe slot) or a new eGPU box (test a different PCIe card).

Posted by: yjchua

How exactly should I do this lspci thing?

Follow the links from: https://egpu.io/forums/builds/2018-13-xps13-nvidia1060-6go-galax-snpr-windows-10/#post-48096

Try the pcitree.sh command:

[Please login to see this]

Try lspci by itself. This one lists the devices:

[Please login to see this]

This one lists the devices in a tree (similar to pcitree.sh):

[Please login to see this]

The following lists the devices and most of their information. You'll probably only want to show us the devices belonging to the graphics card and the Node.

[Please login to see this]

Screen Shot 2018 11 25 at 10.26.17

Here's the PCI section.

The lspci command doesn't exist according to Terminal. 

sudo ./pcitree.sh isn't found either in Terminal.

Late-2016 15" rMBP (2.9/16/1TB/460)
Akitio Node + Asus Expedition RX 570 OC, 4GB

 
2018 Mac Mini [8th,6C,B] + RX 570 @ 32Gbps-TB3 (Razer Core X) + macOS 10.14 & Win10 [build link]  


ReplyQuote
joevt
(@joevt)
Noble Member
Joined: 4 years ago
 
Posted by: yjchua

The lspci command doesn't exist according to Terminal. 

sudo ./pcitree.sh isn't found either in Terminal.

You didn't follow the links.

Mac mini (2018), Mac Pro (Early 2008), MacBook Pro (Retina, 15-inch, Mid 2015), GA-Z170X-Gaming 7, Sapphire Pulse Radeon RX 580 8GB GDDR5, Sonnet Echo Express III-D, Trebleet Thunderbolt 3 to NVMe M.2 case


ReplyQuote
yjchua
(@yjchua)
Eminent Member
Joined: 5 years ago
 
Posted by: joevt
Posted by: yjchua

The lspci command doesn't exist according to Terminal. 

sudo ./pcitree.sh isn't found either in Terminal.

You didn't follow the links.

I did. When I typed man lspci, the manual entry came up, but running those commands threw up that error.

Late-2016 15" rMBP (2.9/16/1TB/460)
Akitio Node + Asus Expedition RX 570 OC, 4GB

 
2018 Mac Mini [8th,6C,B] + RX 570 @ 32Gbps-TB3 (Razer Core X) + macOS 10.14 & Win10 [build link]  


ReplyQuote
joevt
(@joevt)
Noble Member
Joined: 4 years ago
 
Posted by: yjchua

I did. When I typed man lspci, the manual entry came up, but running those commands threw up that error.

What error? Did you set the nvram boot arguments and disable SIP?

Mac mini (2018), Mac Pro (Early 2008), MacBook Pro (Retina, 15-inch, Mid 2015), GA-Z170X-Gaming 7, Sapphire Pulse Radeon RX 580 8GB GDDR5, Sonnet Echo Express III-D, Trebleet Thunderbolt 3 to NVMe M.2 case


ReplyQuote
yjchua
(@yjchua)
Eminent Member
Joined: 5 years ago
 
Posted by: joevt
Posted by: yjchua

I did. When I typed man lspci, the manual entry came up, but running those commands threw up that error.

What error? Did you set the nvram boot arguments and disable SIP?

Already set the boot args, didn't know I had to disable SIP (I usually try to avoid this).

Did all 4 commands and the full outputs are all in TXT files, accessible from this folder in my OneDrive:  https://1drv.ms/f/s!AkzrHH5MUh7thu5JRNkmHIGKY3G-3g

Anyway here's the output of lspci -vvnnn that's relevant to the GPU parts:

[Please login to see this]

Late-2016 15" rMBP (2.9/16/1TB/460)
Akitio Node + Asus Expedition RX 570 OC, 4GB

 
2018 Mac Mini [8th,6C,B] + RX 570 @ 32Gbps-TB3 (Razer Core X) + macOS 10.14 & Win10 [build link]  


ReplyQuote
yjchua
(@yjchua)
Eminent Member
Joined: 5 years ago
 

Update - tested it on a friend's Razer Core X and the PCIe lane width used was x4. 

Guess my Akitio Node is toast for some reason.

Late-2016 15" rMBP (2.9/16/1TB/460)
Akitio Node + Asus Expedition RX 570 OC, 4GB

 
2018 Mac Mini [8th,6C,B] + RX 570 @ 32Gbps-TB3 (Razer Core X) + macOS 10.14 & Win10 [build link]  


ReplyQuote
abelviking
(@abelviking)
Eminent Member
Joined: 2 years ago
 

@nando4
Just wondering if as of 2019 the AORUS gaming box still has this HD2 problem and if there's a way to find out which firmware is running:
https://www.gigabyte.com/Graphics-Card/GV-RX580IXEB-8GD#support-dl-firmware

FYI, AIDA64 GPGPU Benchmark errors out with a memory access violation(wondering if I have bad RAM) so I can't even test that.

This post was modified 2 years ago

Sytem InfoiMAC Late 2015. dGPU AMD M390, OSX 10.12.6, Windows 17134.rs4_release.180410-1804(1803). GYGABYTE AORUS RX580 miniITX eGPU my signature

 
2015 27" iMac 5K (R9 M390) [6th,4C] + RX 580 @ 16Gbps-TB2>TB3 (Gigabyte Gaming Box) + Win10 [build link]  


ReplyQuote
abelviking
(@abelviking)
Eminent Member
Joined: 2 years ago
 
Posted by: nando4

@alan49, are you familiar with Linux? As you've already tried to flash other vendor firmware, perhaps try under Linux? The following Linux method to do that from here may help.

Upgrading the firmware under Linux

Thunderbolt has a standardised interface to update the firmware on chipsets at either end of the link. Luckily for us Linux exposes this interface directly under /sys allowing firmware updates with no special tools required. Care has been taken to allow recovery in the event of a corrupt firmware upgrade and firmware images are checksummed to ensure that only good firmware is booted, reducing the chances of causing permanent damage to your machine or devices.

Thunderbolt devices under Linux have 2 separate firmware areas, The Active firmware area (nvm_active1) and the non-active firmware area (nvm_non_active1) only the non-active area can have firmware uploaded to it. Once this area has been written to, the firmware can be authenticated after which the device automatically reboots and boots into the new verified firmware.

on my system, The AORUS shows up at /sys/bus/thunderbolt/devices/0-0/0-1 and the Thunderbolt port at /sys/bus/thunderbolt/devices/0-0/, as you can see the AORUS device is in a directory under the Thunderbolt host device indicating where it is plugged in (this becomes helpful if you have multiple devices connected).

In these directories you can see information relating to the device such as its name, key and who built it (device_name, key and vendor*) as well as the nvm_* directories corresponding to the firmware

To perform the update procedure grab the latest firmware version from reddit/Gigabyte. As I was interested in increased PCIe/GPU performance I selected the H2D firmware which helps speed up transfers from the laptop to the device as per eGPU.io I was glad to see that Gigabyte delivered a new firmware image in a significantly faster time frame than I anticipated. I was even more encouraged when presented with a zip file that contained the raw firmware without obfuscation or embedding, allowing me to directly copy the file with minimal fuss.

Verifying the currently running firmware

It is possible to determine which firmware you are running via the nvm_version file, however in the case of the H2D vs non-H2D firmware above, these both present the same version. Luckily the running firmware can be read from memory and hashed allowing us to determine which version is running. These hashes won't match the on disk firmware versions but will allow you to differentiate between running firmwares

On my device the non-H2D version gave me the following

[Please login to see this]

While the H2D version gave me the hash shown below

[Please login to see this]

Flashing the firmware

Inside both Zip files is a '.bin' file that represents the firmware (in my case AORUS_N1070IXEB_8GD_VER10H2D.bin md5:1ed8ee21f01595efee8914e40fe638ef) upgrading was as simple as:

[Please login to see this]

After this the device disconnected, rebooted and then became visible again (after going through the authentication step above)

I then proceeded to verify the H2D bandwidth using my own H2D opencl benchmarking script but found that both firmwares provided similar numbers (2761MB/s). Due to not benchmarking pre-firmware upgrades I cannot confirm if my script is broken or if both firmwares contain the H2D fix and that the h@d firmware contains some additional tuning as per their notes on what each version is optimised for. If someone does benchmark before and after please let me know so I can update this article.

@itsage Given your pain process  with Intel Thumderbolt 3 drivers on the Aorus Gaming box: https://egpu.io/gigabyte-rx-580-gaming-box-review-little-middle/

and 

https://egpu.io/forums/thunderbolt-enclosures/guide-update-thunderbolt-3-egpu-enclosure-firmware-in-boot-camp/

I wonder if I can use this approach for TB2 on my iMac (hopefully on VMWARE).
Thanks!

Sytem InfoiMAC Late 2015. dGPU AMD M390, OSX 10.12.6, Windows 17134.rs4_release.180410-1804(1803). GYGABYTE AORUS RX580 miniITX eGPU my signature

 
2015 27" iMac 5K (R9 M390) [6th,4C] + RX 580 @ 16Gbps-TB2>TB3 (Gigabyte Gaming Box) + Win10 [build link]  


ReplyQuote
Przemysław Sobiecki
(@przemyslaw_sobiecki)
Active Member
Joined: 3 years ago
 

Hi, How did you check the version and update the FW of AKitio node on a MacBook?
Mine is underperforming (using iMac pro), and CUDA-Z runs with H2D speed at ~1480 Gb/s

To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.

.

ReplyQuote
kakahara
(@kakahara)
Active Member
Joined: 2 years ago
 

Sorry to resurrect a dead thread but what is the current state of play with these enclosures?
Would a Razer Core X - which I read has TI83 - have these issues? I guess it was released way after these initial investigations took place...

Thanks

Macbook Pro 13" i7 2019, Razer Core X, 5700XT 50th Anniversary Edition


ReplyQuote
 of  30