Can't see Xavier GUI on monitor after message 'Started Update UTMP about System Runlevel Changes'

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
#1

I have configured Xavier from OEM-config as per this post and it was working fine with DeepStream 5. It has latest Jetpack 4.4. Yesterday, I tried to setup DeepStream Test5 App to test with Azure IoT and installed iotedge package as per the README in deepstream-test5 C example. I got issues about iotedge certificate, so I re-installed it and then it worked fine. Now, when I rebooted device, it’s not showing GUI after message ‘Started Update UTMP about System Runlevel Changes’.

xavier-boot
xavier-boot1736×2312 773 KB

I can still access it from SSH and run commands, GUI doesn’t show up after connecting to monitor.
After first boot,sudo apt-get update gives below errors:

Ign:1 https://repo.download.nvidia.com/jetson/common r32.4 InRelease
Ign:2 https://packages.microsoft.com/ubuntu/18.04/multiarch/prod bionic InRelease                       
Ign:3 https://repo.download.nvidia.com/jetson/t194 r32.4 InRelease                                      
Hit:4 http://ports.ubuntu.com/ubuntu-ports bionic InRelease                    
Err:5 https://repo.download.nvidia.com/jetson/common r32.4 Release                                             
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate.  Could not handshake: Error in the certificate verification. [IP: XX.XX.XX.XX 443]
Err:6 https://packages.microsoft.com/ubuntu/18.04/multiarch/prod bionic Release                                                                                
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate.  Could not handshake: Error in the certificate verification. [IP: XX.XX.XX.XX 443]
Err:7 https://repo.download.nvidia.com/jetson/t194 r32.4 Release                                                                                               
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses not yet valid certificate.  Could not handshake: Error in the certificate verification. [IP: XX.XX.XX.XX 443]
Hit:8 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease                                      
Hit:9 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease
Hit:10 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease
Reading package lists... Done                      
E: The repository 'https://repo.download.nvidia.com/jetson/common r32.4 Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'https://packages.microsoft.com/ubuntu/18.04/multiarch/prod bionic Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'https://repo.download.nvidia.com/jetson/t194 r32.4 Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease is not valid yet (invalid for another 88d 7h 36min 32s). Updates for this repository will not be applied.
E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease is not valid yet (invalid for another 998d 15h 27min 14s). Updates for this repository will not be applied.
E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease is not valid yet (invalid for another 998d 15h 28min 5s). Updates for this repository will not be applied.
E: Release file for http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease is not valid yet (invalid for another 998d 15h 26min 32s). Updates for this repository will not be applied.

After every reboot, the system date is : Sun Jan 28 09:24:03 PST 2018, no matter whatever I set before reboot.
If I set it to current PDT time and the ‘sudo apt-get update’ command worked fine.

But still the issue related to GUI is same.
The output of sha1sum -c /etc/nv_tegra_release is:
sha1sum: /etc/nv_tegra_release: no properly formatted SHA1 checksum lines found

I tried to connect from USB C-port and sudo picocom -b 115200 /dev/ttyACM0 to get logs, but asks for username and password, after which it shows normal terminal prompt.

#2

This sha1sum command only applied to non-package-based releases, earlier in history:

You can still find the release with one of these:

  • head -n 1 /etc/nv_tegra_release
  • `dpkg -l | grep ‘nvidia-l4t-core’

About:

…this is what is supposed to happen. You log in, and although the port is serial and thus immune to network or GUI failures, it is still a normal login.

No GUI showing up is common, but it sounds like the system is otherwise functioning correctly. See:
https://elinux.org/Jetson/General_debug

#3

@linuxdev Thanks for the details. If the system is normal, then how to get the GUI back?

#4

You would have to follow the steps in the debug URL posted above. It isn’t possible to know yet why video failed. The basic requirement is the monitor has to be true HDMI or DisplayPort, and any VGA adapter will cause failure. The URL above is for the rest of the steps in debugging.

#5