[JP6.0.0] Sometimes black screen while running ubiquity-dm in nv-oem-config-firstboot when using HDMI dcb image

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
, , ,
1

Hi,

目前在customize board上測試JP6.0.0時，有測到一個狀況：

當使用HDMI版本的DCB image時，若執行ubiquity-dm有時會黑畫面(僅有滑鼠游標)，無法正常顯示setup GUI；若將DCB image更換為Devkit的DP版本，就無法複現此狀況(但DP++僅能支援到1080P)。

以下為出現黑畫面時的Log：
boot.log (72.2 KB)
Xorg.0.log (19.1 KB)
ubiquity-dm.log (3.9 KB)

以下為目前使用的HDMI DCB image：
pjai-c200ao-display-dcb-hdmi.dtsi.txt (27.0 KB)

請協助幫忙看一下，感謝！

NOTE:

  1. 測試手法：透過reset button一直重開，觀察是否可正常開啟setup GUI
  2. 複製出問題的機率有20%以上
  3. 搭AGX Orin 32G或是AGX Orin 64G皆可看到此問題
  4. ubiquity-dm是在第一次登入Ubuntu時，於/usr/sbin/nv-oem-config-firstboot內執行
  5. 目前僅有在執行ubiquity-dm時，有觀察到此問題
4

Hi,
Please check if the issue can be reproduced on developer kit. If yes, please share us the steps. We will set up and check.

5

Hi DaneLLL,

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.

6

Please use Orin NX/Nano + Xavier NX devkit if you want to reproduce any HDMI issue on devkit.

7

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:

  1. Flash the board using Jetpack 6.0 BSP.
  2. Power on the system.
  3. Wait until the setup GUI appears.
  4. Press the reset button to reset the system. Alternatively, you can unplug and then replug the power cable to power cycle the system.
  5. 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.

8

Release 36.4 has been released. Please test it on your side if the issue is still.

9

Unfortunately, it can be reproduced on JP6.1(L4T 36.4) too.

Below are the log files while black screen occurred:
boot.log (70.4 KB)
Xorg.0.log (13.8 KB)
ubiquity-dm.log (3.9 KB)

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
11

Hi,

How did you get the xorg log while first configuration is not yet done?

12

I use following command to flash OS into an USB disk:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device sda1  -c tools/kernel_flash/flash_l4t_t234_ext_13g.xml -S 11GiB -p "-c bootloader/generic/cfg/flash_t234_qspi.xml"   --showlogs --network usb0 <board_name> internal

Then I can check the log in the rootfs via other host PC.

13

I mean the system is not able to be operated when first boot configuration is not yet done.
How did you capture log in this situation?

14

不好意思我改用中文解釋

我是將OS燒錄在USB隨身碟上，當問題發生時，LOG一樣會記錄在USB隨身碟的rootfs內，此時可將隨身碟接至其他電腦將LOG取出

1 Like
16

Hi,

It looks like the reproduce rate is low. And it seems next reboot might make it work again.

Please use this (reboot) as a workaround first.

17

Hi,

Would it be possible to fix this in the next release?