Error: no CUDA-capable device is detected on Nvidia Drive AGX Orin

Please provide the following info (tick the boxes after creating this topic):
Software Version
[*] DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
[*] Linux
QNX
other

Hardware Platform
[*] DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.3.10904
[*] other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
[*] native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Hello,

We were trying to run sample_hello_world code on the drive unit however we kept getting the following error:

“Driveworks exception thrown: Platform: cannot retrieve GPU device count… Error cudaErrorNoDevice: no CUDA-capable device is detected”

here is the screenshot:

Can you please have a look and us know how to solve this?

Thanks

Dear @kevin.kal,
Are you running the sample on target?
If running on target, the GPU seems to be not detected. Could you please reflash the target to see if it is a SW issue?

Dear @SivaRamaKrishnaNV,

The samples we are trying to run is from the target itself. The host PC runs fine with docker.

Dear @kevin.kal,
Ok. Please reflash the target and update the status for further guidance.

I have re-flashed it - it seems to work now. However we don’t know what caused the error mentioned above. I wonder if this might happen at randomly. We can’t keep flashing every time.

1 Like

Dear @kevin.kal,
Do you notice this previously as well? If you see the same issue next time, file a new topic with boot logs and syslog to get some insights .

This was the first time that happened. How can we access the boot logs and syslog in the future if it happens again?

Dear @kevin.kal,
You can connect to target via minicom and reboot the target to get boot logs.
syslog can be find at /var/log/syslog

Sure thanks for the info