Xavier NX unable to bring up GUI properly on Jetpack 5.0.2

I have installed newly released Jetpack 5.0.2 on NVME SSD of Xavier NX 16 GB Module with Development Kit Carrier board.

From first installation, NX worked fine but after a reboot,
I can only see blank screen after tons of Linux kernel booting messages.
I could be able to see login display after changing terminals and back to GUI using Ctrl + Alt + F1~7
but Xavier NX brings up blank screen right after.
This problem seems very similar to when usually encounter first installing Ubuntu laptop with NVidia GPU installed.

For a moment, I found workaround from Save 1GB of Memory! Use LXDE on your Jetson - JetsonHacks, needs network connection
That is not using default Gnome Display Manager
Ctrl + Alt + F2~F6 to open terminal not GUI and login to user then,
$ sudo apt install lightdm
and on prompt after installation select lightdm not gdm(Gnome Display Manager)
then reboot.
This will bring up GUI back again at least in my case.

P.S. When booting NX it always says “Warning: Test Key Detected” on boot screen, is this okay?
P.S 2. is Xavier NX 16GB RAM model is P3668-003?


Sorry that there are few points to clarify here

  1. If you don’t flash nvme, would you hit this issue?

  2. So it won’t see in the first boot, but after the follow-up reboot?


  1. I didn’t try other methods eMMC capacity is too small and others are too slow.
  2. Yes, at first boot after installation it was fine, was able to install Jetpack SDK debian pacakges via microUSB.
    This started to happen reboot after.

Could you firstly try emmc case as experiment? We notice there seems to be some bugs in flash nvme cases.

So still doing some internal check. If you are willing to help, it may help make the progress faster. Thanks.


I’ve quick tested installing Jeptack 5.0.2 on Xavier NX 16GB model on eMMC but on a different carrier board Seeed Studio reComputer J20-1-H2 due to lack of original Development Kit board I have.
No booting issue found so far except that unable to install whole Jetpack SDK due to lack of disk space.

Another booting issue for JP5.0.2 installed on NVME. with GPIO pin is attached to UART console, it doesn’t booting at all - No booting screen or else, just blank screen forever.


We can only deal with devkit cases. Please contact the board vendor to let them report bug to us instead.

No I’m talking about No issue found on Seeed Studio Carrier Board J20-1-H2 flashing 5.0.2
All Issues I mentioned are happening in Jetpack 5.0.2 with Xavier NX 16GB on Official DevKit

If you only flash the OS but do not install any “SDK” to your emmc. Will you hit this issue?

If so, could you share me below log

  1. dmesg

  2. /var/log/Xorg.0.log

If you cannot operate the device because you don’t see anything on the GUI, please use the uart console.

BTW, not quite sure what does that mean “a GPIO pin connected to UART console”…


  1. Do you mean flash /boot only in eMMC and use other partitions?
  2. Will try soon
  3. What I meant was I have GPIO Pin 8, 10 which is connected to /dev/ttyTHS0 debugging console I know this is interactive console, how can I prevent this causing not booting? Since it wasn’t causing issue back in JP 4.6 on Xavier NX and I should use these pin
    NVIDIA Jetson Xavier NX GPIO Header Pinout - JetsonHacks


Answer to 1. No, I mean you just select “OS” in sdkmanager GUI, but un-click those “SDK” in sdkmanager gui. So that you won’t install CUDA/TensorRT at this moment. This will make your emmc has enough space.

Answer to 3. This seems not related to the original question. You can file a new topic for it.


  1. On eMMC Installation on JP5.0.2, There is no Issue flashing OS, booting else just few SDK element installation failure which is fine I mentioned this possible difference than when Issue raised so I think this is unrelated to original issue
  2. Created new topic Jetpack 5.0.2 unable to boot when UART connected and sending signals


So what is the exact scenario to his this issue? Has to use nvme to reproduce this issue?

Exact issue is just booting NVME flashed to JP5.0.2 cannot bring up GDM GUI reboot after flash “AS IS”
and was able to workaround with lightdm

Here are logs you requested

dmesg.txt (92.5 KB)
Xorg.0.log (17.4 KB)


Is the log you just shared based on GDM or based on lightdm?

Oh,These logs are acquired after boot complete and GUI brought up with lightdm
Do you need logs from GDM?

Yes, I need log from gdm.

I cannot reproduce gdm3 hang on boot after installing lightdm and switching back to gdm3 after removal of lightdm on the same hardware.

Here are the logs from GDM3 boot w/o hang
dmesg_gdm3.txt (91.7 KB)
Xorg.0.log (17.8 KB)

I think I should flash new Xavier NX 16GB on NVME to reproduce later.

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.

Please share the log after you could reproduce issue. Thanks.