TX2 screen flickering. Can not start GDM normally after flashing with SDK Manager

Autonomous Machines Jetson & Embedded Systems Jetson TX2
#1

Hi, I was following the official guide to flash my new Nvidia TX2 with SDK Manager. I’m flashing the latest version of JetPack 4.6.2. In the beginning, the TX2 is able to start the GUI and set up the user info without a problem. But after setting up the user info on TX2 and finishing the flash procedure on the SDK manager, the gdm service can not be started successfully on the TX2 and keep restarting to make the screen flickering. Here are some log files of my TX2 system. Could you please help me point out which step is going wrong? Thank you!

Xorg.0.log (7.5 KB)

gdm service status

● gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)
   Active: active (running) since Wed 2022-05-11 13:36:48 CST; 21min ago
  Process: 16010 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
 Main PID: 16033 (gdm3)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/gdm.service
           └─16033 /usr/sbin/gdm3

May 11 13:39:08 ubuntu gdm3[16033]: Child process -26742 was already dead.
May 11 13:39:08 ubuntu gdm-launch-environment][26748]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
May 11 13:39:08 ubuntu gdm-launch-environment][26748]: pam_unix(gdm-launch-environment:session): session closed for user gdm
May 11 13:39:08 ubuntu gdm3[16033]: GdmLaunchEnvironment: Unknown user gdm
May 11 13:39:08 ubuntu gdm3[16033]: GLib-GObject: g_object_set: assertion 'G_IS_OBJECT (object)' failed
May 11 13:39:08 ubuntu gdm3[16033]: Child process -26763 was already dead.
May 11 13:39:08 ubuntu gdm3[16033]: Child process 26748 was already dead.
May 11 13:39:08 ubuntu gdm3[16033]: Unable to kill session worker process
May 11 13:39:08 ubuntu gdm3[16033]: Unable to run script: Too many open files
May 11 13:39:08 ubuntu gdm3[16033]: Unable to run script: Too many open files
#3

Are you sure this is pure jetpack image? Is your carrier board a custom board or the devkit?

#4

Thanks for your reply!
I’m using the SDK manager from here to flash my board, so I think it’s a pure jetpack image.
My board is not a custom board, I’m using this devkit

#5

Ok.

Could you share me the result of “lsmod” command?

#6

I’m connecting to my board with SSH, and the ‘lsmod’ command shows nothing.

sudo lsmod
Module                  Size  Used by

This is additional dmesg log.
dmesg.log (165.0 KB)

#7

This seems not a pure jetpack4.6.2 image.

Do you have any storage device like nvme, usb or sdcard connected on the board?

#8

I saw there is a sdcard connected on the board.

Is there any other jetpack BSP on this sdcard?

1.917905] mmc2: hw tuning done …
[ 1.917962] mmc2: new ultra high speed SDR104 SDXC card at address 5048
[ 1.918423] mmcblk2: mmc2:5048 SD128 117 GiB

#9

Thank you for helping me!
I removed the SD card on the board and it seems loading the right image and without the problems after reboot!

1 Like
#10

The kernel was loaded from your sdcard so the real jp4.6.2 linux kernel was not loaded up at all.

1 Like