Error trying to enable HDMI

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.8.0.10363
other (1.7.9)

Host Machine Version
native Ubuntu 18.04
other

Hey Nvidia Team,

I finished flashing my hardware, and I am having a hard time enabling desktop. I keep getting an error around python dependencies and ubiquity dependencies, see below. I cannot seem to repair or install necessary python or ubiquity packages.

gdm3error (3.8 KB)

Please let me know how I can fix this issue, thanks!

Gurmeet

2

Dear @gurmeet.sidhu1,
Did you check the discussion on No screen visible after DRIVE AGX reflashing ?

3

It seems to have failed at this step:

sudo apt-get install gdm3 ubuntu-unity-desktop

I think I may have removed some Python dependencies and I am having difficulty installing at this point.

4

I’m not sure what causes this problem.
Please try running the two steps right after installing DRIVE OS 5.2.6.

$ sudo apt update
$ sudo apt install gdm3 ubuntu-unity-desktop

6

Hey VickNV,

I reflashed the drive and ran the steps above but I ran into an interesting error.

The GUI worked initially, it asked me to install some updates so I did, it asked me to restart, so I did. But after the restart the desktop is no longer working

gdm is on as a service and as you can see below it exists, its installed but there is no directory for it and HDMI is back to not working …

Screenshot from 2022-06-15 14-41-44
Screenshot from 2022-06-15 14-41-44770×614 88 KB

Let me know how I can resolve this.

Thanks,
Gurmeet

7

What are the updates? Could you reflash and not update them?

8

When I opened up the GUI it said there were 100mb of updates to install. So I accepted them, however when it booted up again it didn’t launch the GUI but I could login via minicom/debug. I am not sure what the updates were.

9

Okay I was able to run the following commands and it appears that I have gdm3 back up and running however I still don’t see a desktop when I connect the box to my monitor.

 sudo apt purge gdm3
 sudo reboot
 sudo apt install gdm3
 sudo service gdm start

The update must have deleted some files from the gdm3 but I have reconfigured the config.conf to look like this:

# GDM configuration storage
# 
# See /usr/share/gdm/gdm.schemas for a list of available options.

[daemon]
# Uncoment the line below to force the login screen to use Xorg
#WaylandEnable=false

# Enabling automatic login
AutomaticLoginEnable = true
AutomaticLogin = nvidia

# Enabling timed login
#  TimedLoginEnable = true
#  TimedLogin = user1
#  TimedLoginDelay = 10

[security]

[xdmcp]

[chooser]

And I have restarted the box, I have attached the log of what that looks like, but I get the following messages when I run status on gdm3/desktop-manager

==== AUTHENTICATION COMPLETE ===
nvidia@tegra-ubuntu:~$ systemctl start gdm3
==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
Authentication is required to start 'gdm.service'.
Authenticating as: nvidia
Password: 
==== AUTHENTICATION COMPLETE ===
nvidia@tegra-ubuntu:~$ ��verify_rate_range: FMON_NVDISPLAYHUB: rate 2781250 below min 18750000
fmon_update_config: FMON_NVDISPLAYHUB: detected fault 0x4000
verify_rate_range: FMON_NVDISPLAYHUB: rate 2781250 below min 18750000
fmon_update_config: FMON_NVDISPLAYHUB: detected fault 0x4000
verify_rate_range: FMON_NVDISPLAYHUB: rate 2781250 below min 18750000
fmon_update_config: FMON_NVDISPLAYHUB: detected fault 0x4000
��^C
nvidia@tegra-ubuntu:~$ systemctl status gdm3
● gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabl
   Active: active (running) since Thu 2022-06-16 20:29:35 UTC; 22s ago
  Process: 16793 ExecStartPre=/usr/share/gdm/generate-config (code=exited, statu
 Main PID: 16795 (gdm3)
    Tasks: 4 (limit: 4915)
   CGroup: /system.slice/gdm.service
           └─16795 /usr/sbin/gdm3

Jun 16 20:29:57 tegra-ubuntu gdm3[16795]: GdmDisplay: display lasted 0.393528 se
Jun 16 20:29:57 tegra-ubuntu gdm3[16795]: Child process -18740 was already dead.
Jun 16 20:29:57 tegra-ubuntu gdm3[16795]: Child process 18722 was already dead.
Jun 16 20:29:57 tegra-ubuntu gdm3[16795]: Unable to kill session worker process
Jun 16 20:29:58 tegra-ubuntu gdm-launch-environment][18751]: pam_unix(gdm-launch
Jun 16 20:29:58 tegra-ubuntu gdm-launch-environment][18751]: pam_unix(gdm-launch
Jun 16 20:29:58 tegra-ubuntu gdm3[16795]: Child process -18769 was already dead.
Jun 16 20:29:58 tegra-ubuntu gdm3[16795]: Child process 18751 was already dead.
Jun 16 20:29:58 tegra-ubuntu gdm3[16795]: Unable to kill session worker process
Jun 16 20:29:58 tegra-ubuntu gdm-launch-environment][18781]: pam_unix(gdm-launch
lines 1-19/19 (END)

The screen flashes black for a moment and then it goes back to no signal

startup.txt (70.1 KB)

10

Please refer to Error trying to connect monitor.