Troubleshooting Compilation and Performance

The following section lists some ideas for troubleshooting the device or the host side software.

NETINT’s support team are always here to provide help and support so please ask if needed, but this list could also help to solve an issue quickly.

Performance is Lower than Expected

Performance can be affected by the following, please check to make sure everything is working as expected.

1. Make sure the device is running at PCIe Gen 4 speeds
2. Make sure the device has the correct firmware running on it
3. Make sure the software is installed correctly on the host
4. Make sure the device is not throttling. Throttling occurs when the device is too hot. Adequate cooling is needed, and the higher the load on the device the hotter the device will get over time.

See the section on Throttling for more information.

Talk to your NETINT representative for information on cooling solutions.

Compilation Failures

If the host side software, or you application is failing to compile/link, see if any of the listed help can resolve your issue.

FFMpeg Compilation fails with Quadra and CUDA

Some customers have tried to compile the latest CUDA (version 12) with FFMpeg 4.4 and Quadra.

The command for this is expected to be

bash build_ffmpeg.sh --quadra --ffnvcodec

The default for FFmpeg compilation is for it to use the Shader Modules “30” – hence the compute_30 unsupported GPU architecture message. Running the above command may result in this failure

bash build_ffmpeg.sh --quadra –ffnvcodec

nvcc -gencode arch=compute_30,code=sm_30 -O2 -m64 -ptx -c -o /tmp/ffconf.lHNCpvwM/test.o /tmp/ffconf.lHNCpvwM/test.cu
nvcc fatal : Unsupported gpu architecture 'compute_30'
ERROR: failed checking for nvcc.

To tell FFmpeg 4.4 to compile for a more recent and supported Shader Model, here for example the NVidia Turing architecture (SM75), set the following custom flags

bash build_ffmpeg.sh --quadra --ffnvcodec --custom_flags '--nvccflags=-gencode=arch=compute_75,code=compute_75'