We designed a custom carrier board, using the image package packaged by sudo BOARDID=$BOARDID BOARDSKU=$BOARDSKU FAB=$FAB BOARDREV=$BOARDREV CHIP_SKU=$CHIP_SKU ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_nvme.xml -S 80GiB -p “-c bootloader/generic/cfg/flash_t234_qspi.xml --no-systemimg” --no-flash --massflash 5 --network usb0 $CONFIG external ; After the nx 16 g module is burned with firmware, sometimes a black screen will appear when the device is started, with only one mouse on the screen and everything else is black; The strange thing is that the black screen does not appear every time . We have restarted the computer many times and sometimes it appears, but sometimes it does not. Also, after setting the account password, there has never been a black screen. This is very strange. Is there any solution?
Hi,
Do you have a dev kit board to cross check whether the issue exists?
Or provide the serial log when issue occur
Also dump
/var/log/Xorg.0.log- The output of
lsmodsaved to a file:lsmod > lsmod.txt - The output of
dmesgsaved to a file:dmesg > dmesg.txt ps aux | grep gdm3
Thanks
This seems to only occur during the nv-oem-config process. Is there any place where I can debug this process?
I found a post ([JP6.0.0] Sometimes black screen while running ubiquity-dm in nv-oem-config-firstboot when using HDMI dcb image - #19 by alex76) that modified glib, which did solve the problem of the screen not lighting up, but this library is too low-level, will it affect other applications? Does NVIDIA recommend using this method? Can NVIDIA analyze the cause of this problem?
Hi,
Please note these glib patches don’t fully resolve the issue for Jetpack 6, especially for AGX Orin.
Did you continue debugging? Which step did this library affect and cause the black screen?
Hi,
No, we’re simply notifying end users about this known issue and recommending a system reboot as a workaround.
Hi,
Please apply this solution for a try:
Jetson/L4T/r36.4.x patches - eLinux.org
[Orin] Display drivers install to the wrong path with official document instructions
The path is wrong and please manually copy the files to correct path.
I found that the system does not have the problems described in these two posts, so they are probably not caused by the same reason. I also found this problem in the latest jectpack6.2.1. Is there any further solution for this problem?