Skip to main content
Question

GPU device discovery failed

  • February 5, 2026
  • 7 replies
  • 152 views

I try to use Metis M.2 on Jetson Nano, I followed all the steps to install the board but when I try to run the first example from Voyager-SDK I get the following error:

(venv) adrianza@ubuntu:~/voyager-sdk$ ./inference.py yolov5s-v7-coco media/traffic1_1080p.mp4
2026-02-05 09:54:10.578538286 [W:onnxruntime:Default, device_discovery.cc:164 DiscoverDevicesForPlatform] GPU device discovery failed: device_discovery.cc:89 ReadFileContents Failed to open file: "/sys/class/drm/card1/device/vendor"
WARNING : Failed to get OpenCL platforms : clGetPlatformIDs failed: PLATFORM_NOT_FOUND_KHR
WARNING : Please check the documentation for installation instructions
INFO : Deploying model yolov5s-v7-coco for 4 cores. This may take a while...
|████████████████████████████████████████| 7:53.1
Opening in BLOCKING MODE
NvMMLiteOpen : Block : BlockType = 261
NvMMLiteBlockCreate : Block : BlockType = 261
WARNING : capsfilter0: BUS: not negotiated
WARNING : (../libs/gst/base/gstbasetransform.c(1431): gst_base_transform_reconfigure_unlocked (): /GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstCapsFilter:capsfilter0:
WARNING : not negotiated)
ERROR : qtdemux0: BUS: Internal data stream error.
ERROR : -> ../gst/isomp4/qtdemux.c(6760): gst_qtdemux_loop (): /GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstQTDemux:qtdemux0:
ERROR : streaming stopped, reason not-negotiated (-4)
WARNING : An error occurred whilst in pre-roll pipeline: IndexError('list index out of range'), stopping pipeline
ERROR : list index out of range
terminate called after throwing an instance of 'std::system_error'
what(): Invalid argument
Aborted (core dumped)

Can you guide me to solve this problem? Thank you!

7 replies

Spanner
Axelera Team
Forum|alt.badge.img+3
  • Axelera Team
  • February 6, 2026

Hi ​@AdrianZa ! Hmm, do you know which Jetson it is? The Orin is supported by Voyager in 1.5, but I don’t think the original Jetson Nano is.

The kernal needs patching too for the Orin - did that work okay, do you know?


  • Author
  • Cadet
  • February 6, 2026

Hi ​@Spanner,

It's Jetson Orin Nano Developer Kit (8GB). I rebuilt the kernel according to https://support.axelera.ai/hc/en-us/articles/29755841693458-Bring-up-Metis-M-2-in-Jetson-Orin, without errors.


Spanner
Axelera Team
Forum|alt.badge.img+3
  • Axelera Team
  • February 6, 2026

I feel like I remember something about the Jetson hardware video decoder being tricky sometimes. I think this’ll work, as a way to go around it for the moment - maybe worth a shot anyway!

./inference.py yolov5s-v7-coco media/traffic1_1080p.mp4 --force-software-codec

And we could even try with --no-display, if you’re not using one, to rule that out too.

./inference.py yolov5s-v7-coco media/traffic1_1080p.mp4 --force-software-codec --no-display

Potentially with and without --force-software-codec, just in case I’m making that one up 😅 More info on inference.py here too, in case that’s useful. Let me know how it goes!


  • Author
  • Cadet
  • February 7, 2026

It seems that the --force-software-codec argument does not exist for inference.py

I reinstalled the Voyager-SDK and now, even though the same warnings appear, the inference is executed:

(venv) adrianza@ubuntu:~/voyager-sdk$ ./inference.py yolov5s-v7-coco media/traffic1_1080p.mp4
2026-02-07 14:07:24.316039775 [W:onnxruntime:Default, device_discovery.cc:164 DiscoverDevicesForPlatform] GPU device discovery failed: device_discovery.cc:89 ReadFileContents Failed to open file: "/sys/class/drm/card1/device/vendor"
WARNING : Failed to get OpenCL platforms : clGetPlatformIDs failed: PLATFORM_NOT_FOUND_KHR
WARNING : Please check the documentation for installation instructions
Opening in BLOCKING MODE
NvMMLiteOpen : Block : BlockType = 261
NvMMLiteBlockCreate : Block : BlockType = 261
Core Temp : 36.0°C
CPU % : 34.8%
End-to-end : 158.3fps
Latency : 103.7ms (min:34.8 max:518.2 σ:30.4 x̄:106.5)ms

 


Spanner
Axelera Team
Forum|alt.badge.img+3
  • Axelera Team
  • February 9, 2026

Morning mate! Ah, so I wonder if something borked during the first installation, maybe? Great to hear that it’s running now, and 158fps is very respectable on the Orin Nano, I think. Nice work!

As you noticed, those OpenCL and GPU discovery warnings are still showing but they're not causing any issues, and I believe that's expected behaviour on Jetson.

Out of interest, if you get five minutes could you share the output of these?

uname -r
axdevice

And which SDK version you're running? It’d be interesting to keep track in case anyone else hits the same issue on Jetson Orin Nano. 👍


  • Author
  • Cadet
  • February 9, 2026

Hi ​@Spanner,

5.15.185-tegra-axl

Device 0: metis-4:1:0 1GiB m2 flver=1.3.2 bcver=1.4 clock=800MHz(0-3:800MHz) mvm=0-3:100%

 


  • Author
  • Cadet
  • February 9, 2026

Voyager-SDK 1.5.3