My jetson Orin was working fine suddenly no display from it.
I can see green light and fan is spinning but no display from the hardware. I have changed the display cables, connectors and monitors.
Still no display from the hardware.
please follow the website to check logs from serial console.
We had an Orin Nano do the same thingā¦after no luck with several tries , we finally used a linux machine & Jetson SDK to completely reflash the Jeson, basically a full resetāand it came back to life.
Thanks alot.
Can you please list the steps you took to reflash the Jetson Orin Nano. Would be very helpful.
Hi Im still not able to fix the problem. There is constantly no display. Im not able to flash the hardware as there are errors while doing that. You can see the errors above in the thread.
Please let me what should I do. The support is saying they wont claim warrenty unless moderator says that it is a hardware issue. Im running out of time to finish the project.
It has been 3 weeks now since this problem was reported.
Regards
Zaid Saeed
Hi,
Please
Do not copy and paste logs into forum directly. If you keep doing this, this whole post is just full of text and it would be a disaster to read.
Please attach your log as attachment instead of copy and paste.
Also, your flash log does not capture the useful part. Please click the āexport logsā button on the sdkm GUI and attach the whole file here for us to check.
From your partial log, I guess this issue totally has nothing to do with your Jetson device at all. It is just your host PC setting has some issue.
SDKM_logs_2025-04-30_14-53-35.zip (297.8 KB)
Here are the attached logs. please let me know the next steps please.
The flash process did not even start. This issue is purely host PC side problem.
**********************14:52:07.245 - Info: exec_command: /home/zaid/.nvsdkm/replays/scripts/JetPack_6.2_Linux/NV_L4T_FILE_SYSTEM_AND_OS_COMP.sh14:52:27.170 - Info: Ign:1 cdrom://Ubuntu 20.04.6 LTS Focal Fossa - Release amd64 (20230316) focal InRelease
14:52:27.171 - Info: Err:2 cdrom://Ubuntu 20.04.6 LTS Focal Fossa - Release amd64 (20230316) focal Release
14:52:27.171 - Info: Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
14:52:27.171 - Info: Get:3 file:/var/l4t-cuda-repo-cross-aarch64-ubuntu2004-12-6-local InRelease [1,572 B]
14:52:27.177 - Info: Get:4 file:/var/l4t-cuda-repo-ubuntu2004-12-6-local InRelease [1,572 B]
14:52:27.177 - Info: Get:3 file:/var/l4t-cuda-repo-cross-aarch64-ubuntu2004-12-6-local InRelease [1,572 B]
14:52:27.184 - Info: Get:4 file:/var/l4t-cuda-repo-ubuntu2004-12-6-local InRelease [1,572 B]
14:52:27.255 - Info: Hit:5 Index of /ubuntu focal InRelease
14:52:27.274 - Info: Hit:6 Index of /ubuntu focal-updates InRelease
14:52:27.290 - Info: Hit:7 Index of /ubuntu focal-backports InRelease
14:52:27.310 - Info: Hit:8 Index of /ubuntu focal-security InRelease
14:52:27.344 - Info: Hit:9 Index of linux/ubuntu/ focal InRelease
14:52:27.378 - Info: Hit:10 Index of /ubuntu focal InRelease
14:52:27.420 - Info: Hit:11 Index of /repos/code/ stable InRelease
14:52:27.496 - Info: Hit:12 http://packages.ros.org/ros/ubuntu focal InRelease
14:52:27.568 - Info: Get:13 Index of /gazebo/ubuntu-stable/ focal InRelease [4,279 B]
14:52:27.571 - Info: Hit:14 https://dl.google.com/linux/chrome/deb stable InRelease
14:52:28.443 - Info: Err:13 Index of /gazebo/ubuntu-stable/ focal InRelease
14:52:28.443 - Info: The following signatures couldnāt be verified because the public key is not available: NO_PUBKEY 67170598AF249743
14:52:37.667 - Info: Reading package listsā¦
14:52:38.895 - Error: E: The repository ācdrom://Ubuntu 20.04.6 LTS Focal Fossa - Release amd64 (20230316) focal Releaseā does not have a Release file.
14:52:38.895 - Error: W: GPG error: Index of /gazebo/ubuntu-stable/ focal InRelease: The following signatures couldnāt be verified because the public key is not available: NO_PUBKEY 67170598AF249743
14:52:38.895 - Error: E: The repository āIndex of /gazebo/ubuntu-stable/ focal InReleaseā is not signed.
14:52:38.898 - Error: [exec_command]: /bin/bash -c /home/zaid/.nvsdkm/replays/scripts/JetPack_6.2_Linux/NV_L4T_FILE_SYSTEM_AND_OS_COMP.sh; [error]: E: The repository ācdrom://Ubuntu 20.04.6 LTS Focal Fossa - Release amd64 (20230316) focal Releaseā does not have a Release file.
W: GPG error: Index of /gazebo/ubuntu-stable/ focal InRelease: The following signatures couldnāt be verified because the public key is not available: NO_PUBKEY 67170598AF249743
E: The repository āIndex of /gazebo/ubuntu-stable/ focal InReleaseā is not signed.
14:52:38.898 - Info: [ Package Install Finished with Error ]14:52:38.898 - Info: [host] [ 5.52 GB used. Disk Avail on Partition /dev/nvme0n1p7: 200.38 GB ]14:52:38.898 - Info: [ NV_L4T_FILE_SYSTEM_AND_OS_COMP Install took 32s ]
Are you sure your host PC can run apt-get update without any error?
HI
Thanks you were right the issue was in the host system that I have fixed. during flash the installation failed again.
please find again new error logs.
SDKM_logs_JetPack_6.2_Linux_for_Jetson_Orin_Nano_[8GB_developer_kit_version]_2025-04-30_15-31-21.zip (411.0 KB)
Are you trying to flash the sdcard there?
Yes, i tried to reflash the sdcard and do full reflash of the jetson orin nano.
Hi @WayneWWW
I tried to connect using minicom by following the link you posted to get the logs from jetson. Im not able to get any data logs from the jetson.
I believe my configurations are correct.
Hi,
Your flash process already went after those logs
ā15:38:24.987 - Info: Waiting for target to boot-upā¦
15:38:26.066 - Info: Waiting for target to boot-upā¦
15:38:27.143 - Info: Waiting for target to boot-upā¦
15:38:28.223 - Info: Waiting for target to boot-upā¦
15:38:29.305 - Info: Waiting for target to boot-upā¦
15:38:30.382 - Info: Waiting for target to boot-upā¦
15:38:31.459 - Info: Waiting for target to boot-upā¦ā
If flash process passed this part, then UART side 100% will print logs. Thus, your setting for dumping log is probably still wrong
Also, flash failure happened here,
15:47:57.101 - Info: Either the device cannot mount the NFS server on the host or a flash command has failed. Check your network setting (VPN, firewall,ā¦) to make sure the device can mount NFS server. Debug log saved to /tmp/tmp.tdIVl4dpkp. You can access the targetās terminal through āsshpass -p root ssh root@fc00:1:1:0::2ā
15:47:57.745 - Info: Cleaning upā¦
Do you have firewall setting on your host ? If so, please disable it first.
Hi ,
Could you please help identify which part of the log configuration is incorrect?
Iāve been trying to get this board working for over a month now, and itās been incredibly frustrating. Iād really appreciate any guidance you can provide to help resolve this issue.
Very poor customer experience.
Check whether ufw is enabled on your host PC and if it is, disable it.
Or actually you could try other Ubuntu host and it may be more easier for this situation.
For example, previous error is that your host PC not able to run apt-get correctly. This thing has nothing to do with any of Jetson board or our tool. That behavior exists on your host before all these started.
HI ,
Not able to run apt-get has been fixed now.
Ill check with other hosts and changing the settings.
I donāt know whether you know understand what I am telling here or not.
15:47:57.101 - Info: Either the device cannot mount the NFS server on the host or a flash command has failed. Check your network setting (VPN, firewall,ā¦) to make sure the device can mount NFS server. Debug log saved to /tmp/tmp.tdIVl4dpkp. You can access the targetās terminal through āsshpass -p root ssh root@fc00:1:1:0::2ā
15:47:57.745 - Info: Cleaning upā¦
This is the error you hit now in flash because our flash process will need to mount NFS storage.
ufw is the ubuntu firewall which may block the NFS mount. If you have it enabled, please try to disable it.
Also, in the meantime you could also try other ubuntu x86 host.
Hi,
I have checked the ufw it was already disabled. If I take out the USB i see the error on minicom terminal. but when I power it again I dont see anything on the terminal. The Nvidia board is also getting very hot now.
Hi,
What āusbā are you trying to tell here? A usb cable or USB ssd? or something else?
What error did you see on minicom?
Since your flash attempt was not successful yet, I donāt see much point to check the boot up log now.