This morning when I went to go power on my Jetson AGX Orin Dev Kit, it would not display on my monitor. The device appears to be hung at boot, when I plug the USBC cable into my host linux machine I can see it through the lsusb command. When I VNC into it I just see the NVIDIA logo.
Anything I can do? Or do I need to reflash it. Any chance there’s a way for me to recover some of the files on it?
As an update, I got the files off through ssh.
Seems like I just can’t properly load my desktop.
Use the serial console and post a full log of the boot (just
dmesg won’t show boot content prior to the Linux kernel loading). Also, post a copy of the log file shown here:
ls -ltr /var/log/Xorg.*.log | head -n 1
The two logs together should give an idea of what is wrong.
Also, does this fail with a monitor connected directly to the Jetson? FYI, this would change which
Xorg.*.log is relevant. That log is named after the environment variable “
$DISPLAY”, which will differ for the virtual display and local physical display. The “
ls -ltr /var/log/Xorg.*.log | head -n 1” simply shows you the most recently touched file; if two files were involved, e.g., if a local monitor and virtual monitor are used, then you’d look at the two files listed in “
ls -ltr /var/log/Xorg.*.log | head -n 2”.
On my monitor connected directly to the Jetson, it is a complete black screen on boot. When I vnc into it, my display shows the NVIDIA logo and never leaves that screen.
Attached are the logs
bootlog.log (1.3 MB)
dmesg.log (76.5 KB)
Xorg.1.log (14.6 KB)
I see a network problem with a lot of repeats of this:
Aug 08 14:11:08 ubuntu dhcpd: DHCPREQUEST for 192.168.55.100 from c6:2a:07:88:44:8e (lenobuntu-Lenovo-Y50-70) via l4tbr0
Aug 08 14:11:08 ubuntu dhcpd: DHCPACK on 192.168.55.100 to c6:2a:07:88:44:8e (lenobuntu-Lenovo-Y50-70) via l4tbr0
Aug 08 14:11:15 ubuntu dhcpd: DHCPREQUEST for 192.168.55.100 from c6:2a:07:88:44:8e (lenobuntu-Lenovo-Y50-70) via l4tbr0
Aug 08 14:11:15 ubuntu dhcpd: DHCPACK on 192.168.55.100 to c6:2a:07:88:44:8e (lenobuntu-Lenovo-Y50-70) via l4tbr0
Seems like the Lenovo is blocking or not allowing a DHCP setup. That or something is not configuring correctly. If you are talking to the Jetson at
192.168.55.1, then this might explain a remote access failure. This is the standard USB network device address on Jetsons. Which network interface or method are you using?
The boot log shows a lot of available modes for a Dell monitor (that log seems to show Xorg X server messages). Is this the monitor you are displaying on? If so, then I think it probably should work. The use of a virtual monitor confuses a few things, and the actual
Xorg.1.log does not mention Dell.
I am thinking the
Xorg.1.log might be for a physically local monitor, which would not apply for any virtual monitor. This would mean there is another log besides
Xorg.1.log, and that log would likely have much of the information from the
bootlog.log (the other log and
bootlog.log would likely match, e.g., perhaps there is something like “
Xorg.10.log”…the number part of the log depends on the “
DISPLAY” environment variable).
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.