It cannot be reproduced on developer kit because it does not have HDMI support.
We cannot reproduce the issue while using original DP DCB image on both developer kit and our customize board.
We are planning to purchase a Xavier NX devkit, but this process will take a few days.
In the meantime, would it be possible for you to assist us by testing on your Xavier NX devkit?
Here’s our testing procedure:
Flash the board using Jetpack 6.0 BSP.
Power on the system.
Wait until the setup GUI appears.
Press the reset button to reset the system. Alternatively, you can unplug and then replug the power cable to power cycle the system.
Repeat Steps 3 and 4.
We have been able to reproduce this issue within 10 cycles.
Your help in this matter would be greatly appreciated.
NOTE: There are two timeout messages in “ubiquity-dm.log” (copied from /var/log/installer/dm):
(gsd-xsettings:1250): xsettings-plugin-WARNING **: 06:18:51.774: Failed to get current display configuration state: Timeout was reached
(gsd-power:1247): power-plugin-WARNING **: 06:19:16.791: Could not create GnomeRRScreen: Timeout was reached
We have been seeing this with Jetpack 6.1 as well with an Orin NX 16GB and a carrier board with DisplayPort output.
I can create a test user by mounting a flashed NVMe into a Host PC, then running something like
$ cd /media/<mount-id>/
$ sudo chroot ./ adduser test
$ sudo chroot ./ usermod -aG sudo test
…then mounting that drive back in the Jetson carrier and booting.
UEFI splash screen works. Linux kernel boot messages (fbcon?) works. But then sometimes when the OEM-config GUI is supposed to launch we simply see a black screen. Often, but not always, there is a mouse cursor that we can move.
If I switch to tty2 with Ctrl+Alt+F2, then enter the test username and password, then I can poke around in that broken state.
I have been able to run sudo killall gnome-shell on the target, then switch back to the GUI with Ctrl+Alt+F7, and we see the GUI pane for the “Please review and accept the following licenses” prompt. But the pane has no window borders/decorations and there is no top menu bar or background image.
I have been unable to find any definitive reason for why the failure is occurring, but it feels like a race condition between when NVIDIA GPU drivers/services or X sessions are fully ready and when gnome’s power-plugin queries for an active display.