GPU 0: GeForce RTX 3090 (UUID: GPU-f634707c-5e3b-b685-ad8c-30e3b916f204)
Link 0: <inactive>
Link 1: <inactive>
Link 2: <inactive>
Link 3: <inactive>
GPU 1: GeForce RTX 3090 (UUID: GPU-17056259-f618-8028-163a-0f62bf47aae7)
Link 0: <inactive>
Link 1: <inactive>
Link 2: <inactive>
Link 3: <inactive>
Of course it should work. @ben.hendrickson did you properly seat the bridge, is it lit? Did you try turning off iommu? Please run nvidia-bug-report.sh as root and attach the resulting nvidia-bug-report.log.gz file to your post.
@generix I’m running into the same exact issue, here’s my nvidia-bug-report.sh dump any help is much appreciated. I am not running IOMMU and my slot is in fitted nicely. I am using the 3-slot A6000 bridge on my 2 3090 FEs. Here’s some further talk on that same setup used by others.
I’ve checked this already in another thread where the user had the same setup (2x3090+A6000 bridge). No chance, the bridge just isn’t detected. Unfortunately, there are also no reports to be found from someone using the original 3090 bridge anywhere so it’s really inconclusive whether this is a general driver-wise problem with nvlink on 3090s or the A6000 bridge is incompatible.
I haven’t searched the cuda forums since then (~2 months) but also no official info from nvidia was to be found.
Thanks for reporting back, what’s the output of
nvidia-smi nvlink -c
in your case? What’s the brand/model of your mainboard? Is it SLI capable?
I actually found one report of 2x3090+2 slot A6000 bridge working on a 4-Way SLI capable workstation mainboard.
Yes, hard to say why they’re even selling those NVLink bridges if they don’t seem to work. Must have worked when they tested them in their own labs, I think.
UPDATE:
my 2x3090 FEs with 3-slot A6000 bridge using Ubuntu 20.04 works as expected! my fitment was not tight and I realized that after re-installing the bridge and I heard a click sound! I am so happy it works