Xavier NX won't boot to GUI when booting from nvme

Using SDK Manager, I flashed JetPack 4.6 (rev.3) to boot from a 128GB NVME. After the flash I was able to go through the first run configuration using the /dev/ttyACM0 interface over usb-dev-mode. Once that was done, I can ssh in and everything seems to be working. If I run $ systemctl get-default, it returns graphical.target. The problem I’m having is that the GUI doesn’t load. The display just shows the nvidia splash screen forever.

Looking for some help troubleshooting this.

Other Info:
This is an industrial Xavier NX with an eMMC mounted in an aftermarket clone of the Xavier NX dev board. If I flash to the eMMC, everything works as expected, including the GUI Desktop.

journalctl_log.txt (191.0 KB)
serial_console_output.txt (21.4 KB)

please dump dmesg and /var/log/Xorg.0.log.

Here you go. Thanks for looking.
dmesg_dump.txt (65.6 KB)
Xorg.0.log (10.9 KB)

Looks like display driver fails. Is this a NX 16G device?

1.928659] tegradc 15200000.nvdisplay: Display dc.ffffff800bd50000 registered with id=0
[ 1.938069] tegra_nvdisp_bandwidth_register_max_config: couldn’t find valid max config!
[ 1.938204] tegradc 15200000.nvdisplay: failed to register ihub bw client
[ 1.938586] tegradc: probe of 15200000.nvdisplay failed with error -7
[ 1.939426] tegradc 15210000.nvdisplay: disp0 connected to head1->/host1x/sor
[ 1.939470] tegradc 15210000.nvdisplay: parse_dp_settings: No dp-lt-settings node
[ 1.939666] tegradc 15210000.nvdisplay: DT parsed successfully
[ 1.939779] tegradc 15210000.nvdisplay: Display dc.ffffff800bdd0000 registered with id=0
[ 1.941258] tegra_nvdisp_bandwidth_register_max_config: couldn’t find valid max config!
[ 1.941322] tegradc 15210000.nvdisplay: failed to register ihub bw client
[ 1.941596] tegradc: probe of 15210000.nvdisplay failed with error -7

BTW, what does this mean?

This is an industrial Xavier NX with an eMMC mounted in an aftermarket clone of the Xavier NX dev board

Is this board a NX developer kit or some custom board ffrom other vendor?

I believe it’s one of these:

Can you move to rel32.7.1 /jetpack4.6.1 and see if the issue is still there?

Just flashed 4.6.1. It works fine…

@WayneWWW Thanks for the help!

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