Only nVidia logo is shown after flashing, cannot complete oem_config setup through GUI

I’d like to continue my discussion of a thread that was closed due to me being out of office and unable to reply to the thread for about a week.

This is the link to the prevoious thread

I am attempting to flash JetPack 4.6 to my production Xavier NX module (16gb EMMC module) connected to the nVidia Xavier NX devkit. I am trying to flash to the NVMe SSD connected to the devkit. The module had JetPack 4.6 on it from an earlier flash and I was able to use my HDMI monitor just fine, however I recently reflashed my module and I am unable to load any GUI.

My UART is able to see the login prompt and I am able to SSH into the computer as well.

I have attached the following files:

  • logs from initrd flashing as flash_1-4_0_20220811-095302.log
  • logs from UART from devkit after flashing is completed showing boot-up as xavier_301_success_postflash.log
  • syslogs after completing oem_config as syslog_noGUI.log
  • /var/log/Xorg.0.log

syslog_noGUI.log (204.1 KB)
flash_1-4_0_20220811-095302.log (21.3 KB)
xavier_301_success_postflash.log (40.0 KB)
Xorg.0.log (10.9 KB)

Please let me know what next steps I should take.

Hi,
Please check
Jetson/L4T/r32.6.x patches - eLinux.org

[flash] Only nVidia logo is shown after flashing, cannot complete oem_config setup through GUI (NX 16GB/8GB)

Thanks for referencing this. I have tried to apply the patch, however I was only able to see the initial OEM_CONFIG through HDMI on my monitor. After completing the OEM_CONFIG, I have a similar problem. Now the nVidia logo is displayed for a few seconds and then nothing is displayed on the monitor.

I have attached the flashing log generated by initrd_flash below as well as UART logs from bootup after completing oem_config.

uart_no_gui.log (40.2 KB)
flash_1-4_0_20220729-104834.log (72.0 KB)

Please let me know if there are any next steps I can take.

Hi,

Is the log you posted based on the case that you added the patch?

If so, could you share the /var/log/Xorg.0.log and dmesg ? Uart does not have kernel log now.

Also, is this related to the massflash issue you filed?

Hi Wayne,

The log I posted has the patch applied, but just to be sure I re-did the flashing procedure with the patch applied and I have added the logs again to this reply.

I flashed both 301 and 300 varients of the Xavier NX board with this patch applied using the following command:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1 -c ./tools/kernel_flash/flash_l4t_nvme_250.xml --erase-all -S 225GiB --showlogs jetson-xavier-nx-devkit-emmc nvme0n1p1 

I used an unmodified JetPack 4.6 downloaded by the SDK manager, the only changes I made were applying the display patch and adding my XML file to use the SSD as the primary storage device

On the 301 and 300 varients Jetson Xavier NX:

  • Flash completes successfully
  • During the OEM_CONFIG stage I am able to see the GUI
  • I unplug the monitor and reboot the Jetson board to complete the OEM_CONFIG through the Micro USB UART as that is our main use-case
  • After completing OEM_CONFIG through the /dev/ttyACM0 interface, I wait for the system install to complete, then I plug in the HDMI monitor and reboot the Jetson board
  • I am now only able to see the nVidia logo for a couple of seconds, then the display remains black

I don’t think this is related to the massflash issue I posted as i’ve seen this problem without using massflash, but I guess it’s possible that the issues are related.

I have included the following files:

  1. initrd flashing logs for 301 and 300 varients as flash_301_initrd_no_display.log and flash_300_initrd_no_display.log
  2. logs from /var/log/syslog after system has booted and no GUI is shown for 300 and 301 varients as syslog_301_no_gui.log and syslog_300_no_gui.log
  3. /var/log/Xorg.0.log from both Xavier NX varients as Xorg.0.301.log and Xorg.0.300.log

So I guess my title of this post is incorrect now, I am able to see OEM_CONFIG through the GUI, but the desktop doesn’t load after completion of OEM_CONFIG through /dev/ttyACM

Xorg.0.300.log (762.9 KB)
syslog_300_no_gui.log (15.5 MB)
flash_300_initrd_no_display.log (72.7 KB)
syslog_301_no_gui.log (449.8 KB)
Xorg.0.301.log (12 KB)

Hi

Did you apply the patch that shared by DaneLLL or not? That issue is known issue and your step would hit that error if you don’t add the patch.
Your comment sounds like you didn’t add itl.

I need the log after you apply the patch only.

Also, I just need your “dmesg”. I don’t need your whole syslog which is 15MB size long. dmesg is just few KB result.

Hi Wayne,

As stated in my previous comment,

I used an unmodified JetPack 4.6 downloaded by the SDK manager, the only changes I made were applying the display patch and adding my XML file to use the SSD as the primary storage device

I did apply the patch shared by DaneLLL, and all the logs I shared were taken after the patch was applied.

I have attached the dmesg output below from 300 and 301 modules. I have booted the devkits with an HDMI monitor connected when taking these logs.

test_301_dmesg.log (65.4 KB)
test_300_dmesg.log (65.4 KB)

Hi,
Could you try Jetpack 4.6.2? The latest release supports all modules and would like to know if you can flash the module successfully. To ensure the module is good. Please help try this.

Hi,

If we don’t flash nvme and just flash with flash.sh, will you see this monitor run in 1920x2160 mode?

@DaneLLL I will try JetPack 4.6.2 and see if this helps, however, we will have to validate our vendor drivers for this version so we do not want to upgrade from 4.6 yet.

@WayneWWW If i recall correctly flash.sh did indeed work on the 1920x2160 mode. I have definitely had the GUI before and it works in that mode on Xavier NX with JetPack 4.6. I will try with flash.sh tomorrow and update to confirm.

Just updating the thread, still working on implementing these suggestions and recording results, I will update the thread again by end of week.