Gdm display manager does not automatically come up when Orin is turned on

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,

Is there a script to run / command to run for bringing up the display manager on boot up? For some reason our ORIN is always in the state of display manager being stopped and will only come up after running sudo systemctl start gdm. Previously, Ubuntu desktop login screen would automatically show when Orin is switched on.

Dear @chris.hoffman ,
Could you share the output of sudo systemctl status gdm after booting. Also, what is the output of ls -la /etc/init.d/?

@SivaRamaKrishnaNV
I switched off the Orin and switched it back on to check the status:

root@tegra-ubuntu:~# sudo systemctl status gdm
● gdm.service - GNOME Display Manager
     Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)
     Active: inactive (dead)
root@tegra-ubuntu:~# ls -la /etc/init.d/
total 108
drwxr-xr-x.   2 root root 4096 May 17 22:24 .
drwxr-xr-x. 109 root root 4096 May 17 23:04 ..
-rwxr-xr-x.   1 root root 5574 Nov  5  2019 alsa-utils
-rwxr-xr-x.   1 root root 3740 Oct 10  2023 apparmor
-rwxr-xr-x.   1 root root 2968 Feb 26  2020 bluetooth
-rwxr-xr-x.   1 root root 1232 Mar 27  2020 console-setup.sh
-rwxr-xr-x.   1 root root  937 Feb  4  2020 cryptdisks
-rwxr-xr-x.   1 root root  896 Feb  4  2020 cryptdisks-early
-rwxr-xr-x.   1 root root 3152 Sep 30  2019 dbus
-rwxr-xr-x.   1 root root  734 Oct 21  2019 fio
-rwxr-xr-x.   1 root root 3033 Nov 10  2020 gdm3
-rwxr-xr-x.   1 root root  985 Jan 11  2022 grub-common
-rwxr-xr-x.   1 root root 3809 Jul 28  2019 hwclock.sh
-rwxr-xr-x.   1 root root 1479 Nov 27  2019 keyboard-setup.sh
-rwxr-xr-x.   1 root root 2044 Feb 19  2020 kmod
-rwxr-xr-x.   1 root root 1942 Nov 27  2021 network-manager
-rwxr-xr-x.   1 root root  612 Feb  8  2019 pppd-dns
-rwxr-xr-x.   1 root root  924 Feb 13  2020 procps
-rwxr-xr-x.   1 root root  469 Oct 15  2020 pulseaudio-enable-autospawn
-rwxr-xr-x.   1 root root 2800 Mar  6  2019 rng-tools
-rwxr-xr-x.   1 root root 2864 Mar  7  2019 rsyslog
-rwxr-xr-x.   1 root root 3088 Oct 10  2019 smartmontools
-rwxr-xr-x.   1 root root 3939 Mar 30  2022 ssh
-rwxr-xr-x.   1 root root 6872 Apr 21  2022 udev
-rwxr-xr-x.   1 root root 2757 Jan 20  2017 x11-common

@SivaRamaKrishnaNV any feedback on this?

Dear @chris.hoffman,
Could you check reinstalling gdm fixes the issue?

@SivaRamaKrishnaNV are you able to share the steps specific to the Orin for that? I’ve tried other ways before, but they did not help.

May I know what you have tried and not worked?

@SivaRamaKrishnaNV

  1. To install the minimal GNOME desktop environment, use your system’s package manager to install the GUI and gdm3 window manager.

$ sudo apt install gnome-session gdm3

  1. After installation is complete, reboot your system and you will be presented with a GNOME login.

$ reboot

Dear @chris.hoffman
Hi , Maybe this can be fixed
Directory:/etc/system/system/
Symbolic Link File:display-manager.service
Link Destination:/lib/systemd/system/gdm3.service

①$ cd /etc/system/system/
②$ ln –s /lib/systemd/system/gdm3.service display-manager.service
③reboot

Hi @chris.hoffman,
Note that, reboot command does not work on Orin. Please see CLI reboot and poweroff commands do not work .
common_if_testapp -mcureset needs to be run on tegra to reboot.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.