Hi Team,
I used L4T 32.5 to flash the Jetson AGX Xavier devkit. Flashing is successful, HDMI is also working in it. Then I tried installing Jetpack in it using the following commands,
sudo apt update
sudo apt install nvidia-jetpack
The installation is successful. Then I did reboot using reboot command. In the next boot, HDMI is not coming up, black screen is present.
I removed HDMI cable and plugged it again. I got the following logs.
[ 87.815875] tegradc 15200000.nvdisplay: blank - powerdown
[ 87.824688] tegradc 15200000.nvdisplay: unblank
[ 87.830248] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
[ 87.835007] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
[ 87.847912] Parent Clock set for DC plld3
[ 87.853700] tegradc 15200000.nvdisplay: hdmi: tmds rate:148500K prod-setting:prod_c_hdmi_111m_223m
[ 87.855328] tegradc 15200000.nvdisplay: hdmi: get YCC quant from EDID.
[ 87.890806] extcon-disp-state external-connection:disp-state: cable 48 state 1
[ 87.890810] Extcon AUX2(HDMI) enable
[ 87.906214] tegradc 15200000.nvdisplay: sync windows ret = 247
[ 87.931588] extcon-disp-state external-connection:disp-state: cable 51 state 1
[ 87.931592] Extcon HDMI: HPD enabled
[ 87.931648] tegradc 15200000.nvdisplay: hdmi: plugged
My HDMI screen is looking like this:
Can anyone help me to debug this issue? @WayneWWW @JerryChang
Thanks,
Sakthi
User ssh or serial console to access the board and then share below log
- syslog (var/log/syslog)
- xorg log (/var/log/Xorg.0.log)
Hi @WayneWWW
These are the syslog syslog.txt (1.4 MB) and xorg log xorglog.txt (19.7 KB) files.
Can you please help in fixing this issue?
Thanks,
Sakthi
Hi,
I have to tell you first that this analysis will take some time. Such issue is common here but every user has different case.
Maybe in the end we still need you to reflash your board. Thus, if you want to save your time, directly flash the board is also one method.
Below are the questions I have after reading your log
- Your xorg log gives a termination in the end. Generally, such log will not happen when you normally boot up. Thus, I also check your syslog to know why the xorg has termination. There is “Server terminated successfully” in timestamp
12:50:11
12:50:13
12:50:15
…
Until 12:50:21.
What were you doing at that time? Were you trying to power down the device? If so, then when did you dump this xorg.log?
-
Are you using one HDMI and one DP monitor here? Could you just use one monitor to test?
-
What you need to do here is “connect one monitior, boot up device, capture log and share it here”. Do not try any other things here. Please confirm if you really follow the steps.
Hi @WayneWWW,
I have re-flashed the board, installed jetpack and did reboot. After connecting HDMI monitor, I booted the board and took these logs immediately without trying any things and I have faced the same issue.
syslog.txt (1.3 MB) xorglog.txt (19.8 KB)
Can you please help me in debugging this?
Thanks,
Sakthi
Hi Sakthi,
Do you mean this issue even happen after you do a fresh reflash with sdkmanager?
What were you trying to do at time stamp Mar 1 16:15:29 in your syslog? Is the system rebooting or something else?
Please check if below error will come to your syslog when you restart the gdm3 service.
Mar 1 16:15:18 mistral-desktop gnome-shell[7260]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found.
Mar 1 16:15:18 mistral-desktop gnome-shell[7260]: Unable to initialize Clutter.
Mar 1 16:15:18 mistral-desktop gnome-session[6992]: gnome-session-binary[6992]: WARNING: App ‘org.gnome.Shell.desktop’ exited with code 1
Mar 1 16:15:18 mistral-desktop gnome-session[6992]: gnome-session-binary[6992]: WARNING: App ‘org.gnome.Shell.desktop’ respawning too quickly
Mar 1 16:15:18 mistral-desktop gnome-session-binary[6992]: WARNING: App ‘org.gnome.Shell.desktop’ exited with code 1
Mar 1 16:15:18 mistral-desktop gnome-session-binary[6992]: Unrecoverable failure in required component org.gnome.Shell.desktop
Mar 1 16:15:18 mistral-desktop gnome-session[6992]: gnome-session-binary[6992]: CRITICAL: We failed, but the fail whale is dead. Sorry…
Mar 1 16:15:18 mistral-desktop gnome-session-binary[6992]: WARNING: App ‘org.gnome.Shell.desktop’ respawning too quickly
Mar 1 16:15:18 mistral-desktop gnome-session-binary[6992]: CRITICAL: We failed, but the fail whale is dead. Sorry…
Mar 1 16:15:18 mistral-desktop gnome-screensav[7057]: gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
I have downloaded L4T and followed the steps mentioned in the Jetson Linux Developer guide to flash the board. I will try the steps mentioned by you and will update you soon.
Thanks,
Sakthi
What confused me is your boot up time is 15:13. But most of gdm3 crashed log is at time 16:15.
There was 1 hour gap here. Do you see any ubuntu desktop on the screen in this time?
I haven’t used the device for 1 hour. I just reboot and captured the log.
Now I tried to restart gdm3 service and the following log is occurring there also.
Mar 1 16:15:18 mistral-desktop gnome-shell[7260]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found.
Mar 1 16:15:18 mistral-desktop gnome-shell[7260]: Unable to initialize Clutter.
Mar 1 16:15:18 mistral-desktop gnome-session[6992]: gnome-session-binary[6992]: WARNING: App ‘org.gnome.Shell.desktop’ exited with code 1
Mar 1 16:15:18 mistral-desktop gnome-session[6992]: gnome-session-binary[6992]: WARNING: App ‘org.gnome.Shell.desktop’ respawning too quickly
Mar 1 16:15:18 mistral-desktop gnome-session-binary[6992]: WARNING: App ‘org.gnome.Shell.desktop’ exited with code 1
Mar 1 16:15:18 mistral-desktop gnome-session-binary[6992]: Unrecoverable failure in required component org.gnome.Shell.desktop
Mar 1 16:15:18 mistral-desktop gnome-session[6992]: gnome-session-binary[6992]: CRITICAL: We failed, but the fail whale is dead. Sorry…
Mar 1 16:15:18 mistral-desktop gnome-session-binary[6992]: WARNING: App ‘org.gnome.Shell.desktop’ respawning too quickly
Mar 1 16:15:18 mistral-desktop gnome-session-binary[6992]: CRITICAL: We failed, but the fail whale is dead. Sorry…
Mar 1 16:15:18 mistral-desktop gnome-screensav[7057]: gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Could you also check if xorg.0.log get refresh when you try to restart gdm3 service?
1 Like
Hi @WayneWWW,
I got to know that the version of the L4T setup I used is 32.5.0 and I am not aware of the L4T 32.5.1 release, this caused the HDMI issue after installing jetpack. Now, I upgraded to L4T 32.5.1 using the following command and rebooted. The issue is not seen.
sudo apt updgrade
Thanks for your support,
Sakthi
1 Like
