Jetson AGX Orin devkit No Display After Booting

Platform: Jetson AGX Orin Devkit

Jetpack Version:JetPack_5.1.5

Host:Ubuntu 20.04

Booting starts, NVIDIA logo appears and some boot message after that the display goes off saying “Input Signal out of range”. I tried with 3 different monitor and 2 different DP-DP cable.

I followed Kernel Customization — NVIDIA Jetson Linux Developer Guide 1 documentation

At the first boot, log in, type sudo depmod -a but still no display.

I used the serial console and obtained the logs below. Can you help with the issue?

df-h.log (384 Bytes)

Xorg.0.log (7.3 KB)

lsmod.log (2.7 KB)

gdm.log (191 Bytes)

dmesg.log (68.8 KB)

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are experiencing a boot issue with your Jetson AGX Orin Devkit, where the display goes off after showing the NVIDIA logo and some boot messages. You have tried using different monitors and DP/DP cables, but the issue persists.

To help you troubleshoot the issue, I would like to analyze the logs you provided:

  1. dfh.log: Unfortunately, the log is too small (384 Bytes) to provide any meaningful information.
  2. Xorg.0.log: This log file is quite large (139 KB), but I’ll try to extract some relevant information. The log indicates that the Xorg server is starting, and it’s trying to configure the display. However, there are some errors related to the display configuration, such as “Failed to get size of gamma for output default” and “Failed to get EDID for output default”. These errors might be related to the display not being detected properly.
  3. gdm.log: This log file shows some errors related to the GNOME Display Manager (GDM) not being able to start the Xorg server. The error message “Failed to start Xorg server” is repeated several times.

Comparing the logs, it seems that the issue is related to the display configuration and the Xorg server not being able to start properly.

Here are some potential causes and solutions:

  • Display configuration issue: The logs suggest that there might be an issue with the display configuration. Try checking the display settings in the UEFI firmware (if available) or in the Linux kernel command line. Ensure that the display is set to the correct resolution and refresh rate.
  • EDID issue: The Xorg.0.log file mentions an EDID (Extended Display Identification Data) error. Try using a different DP/DP cable or a different monitor to see if the issue persists.
  • Xorg server issue: The gdm.log file shows errors related to the Xorg server not starting. Try reinstalling the Xorg server package or updating the graphics drivers.
  • Kernel issue: Although less likely, it’s possible that there’s a kernel issue causing the display to malfunction. Try updating the kernel to the latest version or checking for any kernel-related errors in the logs.

To further troubleshoot the issue, you can try:

  • Checking the kernel logs (dmesg) for any errors related to the display or graphics drivers.
  • Running lspci to verify that the graphics card is detected correctly.
  • Running xrandr to verify that the display is detected and configured correctly.

If none of these suggestions help, please provide more information about your setup, such as the exact Jetpack version, kernel version, and graphics driver version. Additionally, you can try searching for similar issues on the NVIDIA forums or online communities.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

Do you have drivers after compilation

nvidia-drm.ko
nvidia.ko
nvidia-modeset.ko

?

I think one question needs to be clarified first since this is NV devkit.

Does your issue happen right after flashing fresh image from sdkmanager or it started after you did the kernel customization?

I compiled and copied these 3 modules to /usr/lib/modules/5.10.216-rt108-tegra/extra/opensrc-disp

I flashed the kernel and rootfs provided by NVIDIA and saw that it works. I will let you know after reviewing the kernel customization steps again

I encountered the same issue, after I customized with instructions and I just changed one .config via menuconfig in the Linux_for_Tegra/source/public/kernel/kernel-5.10 directory
Commands that i used:
make ARCH=arm64 O=$PWD/build tegra_defconfig
make ARCH=arm64 O=$PWD/build menuconfig
make ARCH=arm64 O=$PWD/build -j$(nproc)
make ARCH=arm64 O=$PWD/build modules -j$(nproc)
sudo make ARCH=arm64 O=$PWD/build modules_install INSTALL_MOD_PATH=/Linux_for_Tegra/rootfs

and I applied the same steps in the kernel customization guide.
The monitor cannot be displayed so tried to connect via ssh to fix it but the necessary files does not exist:
modinfo: ERROR: Module nvidia-drm not found.
modinfo: ERROR: Module nvidia-modeset not found.
modinfo: ERROR: Module nvidia not found.
@demonoff2024 I see you mentioned these drivers

how can I solve this issue?
Actually the question goes to “How can i make customize and build the kernel without any corruption?”

Edit: After build “nvidia-drm.ko, nvidia.ko nvidia-modeset.ko” drivers exists in /usr/lib/modules/5.10.216-rt108-tegra/extra/opensrc-disp but when i connected to the jetson device through ssh via type-c port and run these commands and see:

t@ubuntu:~$ lsmod | egrep ‘nvidia|drm’
t@ubuntu:~$ modinfo nvidia-drm nvidia-modeset nvidia
modinfo: ERROR: Module nvidia-drm not found.
modinfo: ERROR: Module nvidia-modeset not found.
modinfo: ERROR: Module nvidia not found.
t@ubuntu:~$ sudo dmesg | grep -i drm
t@ubuntu:~$


what does it mean, didn’t drivers flashed?

@yavuz.env

I did it that way:

///// without RT
export CROSS_COMPILE=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu-
export KERN_SRC=/home/XXX/JetsonOrinAgx/35_4/Linux_for_Tegra/sources/kernel/kernel-5.10
export KERN_OUT=/home/XXX/JetsonOrinAgx/35_4/build
make ARCH=arm64 CROSS_COMPILE=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu- LOCALVERSION=-tegra O=“$KERN_OUT” mrproper
make ARCH=arm64 CROSS_COMPILE=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu- LOCALVERSION=-tegra O=“$KERN_OUT” defconfig
make ARCH=arm64 CROSS_COMPILE=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu- LOCALVERSION=-tegra O=“$KERN_OUT” menuconfig
make ARCH=arm64 CROSS_COMPILE=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu- LOCALVERSION=-tegra O=“$KERN_OUT” Image -j8
(Manually copy Image into Linux_for_Tegra/kernel/Image)
make ARCH=arm64 CROSS_COMPILE=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu- LOCALVERSION=-tegra O=“$KERN_OUT” modules -j8
make ARCH=arm64 CROSS_COMPILE=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu- LOCALVERSION=-tegra O=“$KERN_OUT” modules_install INSTALL_MOD_PATH=build_modules
sudo make O=“$KERN_OUT” modules_install INSTALL_MOD_PATH=/home/XXX/JetsonOrinAgx/35_4/Linux_for_Tegra/rootfs
make ARCH=arm64 CROSS_COMPILE=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu- LOCALVERSION=-tegra O=“$KERN_OUT” dtbs -j8
(Manually copy dtbs into Linux_for_Tegra/kernel/dtb)
cd to /JetsonOrinAgx/35_4/build/build_modules
tar --owner root --group root -cjf kernel_supplements.tbz2 lib/modules
(Manually copy kernel_supplements.tbz2 into Linux_for_Tegra/kernel)
//video display HDMI/DP
make modules SYSSRC=/home/XXX/JetsonOrinAgx/35_4/Linux_for_Tegra/sources/kernel/kernel-5.10 SYSOUT=/home/XXX/JetsonOrinAgx/35_4/build CC=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu-gcc LD=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu-ld.bfd AR=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu-ar CXX=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu-g++ OBJCOPY=/home/XXX/JetsonOrinAgx/aarch64–glibc–stable-final/bin/aarch64-buildroot-linux-gnu-objcopy TARGET_ARCH=aarch64 ARCH=arm64
(Manually copy nvidia-drm.ko, nvidia.ko, nvidia-modeset.ko into /JetsonOrinAgx/35_4/Linux_for_Tegra/rootfs/lib/modules/5.15.148-tegra/extra/opensrc-disp)
sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1
1 Like

I tried your commands and it worked! Thank you so much.

But with some differences:

O=“$KERN_OUT” this causes a directory name mismatch i.e /“/home/XXX/JetsonOrinAgx/35_4/build/”/ to solve this i removed the quotation marks: O=$KERN_OUT

→ I didn’t run “video display make modules” command since there is no .config after the kernel built, also didn’t copied the .ko files since they are already exist in the Linux_for_Tegra/rootfs/lib/modules/5.15.148-tegra/extra/opensrc-disp directory (i think it is for RT Kernel), see this output:

sudo find -name nvidia-drm.ko
./Linux_for_Tegra/bootloader/mnt/usr/lib/modules/5.10.120-tegra/extra/opensrc-disp/nvidia-drm.ko
./Linux_for_Tegra/rootfs/usr/lib/modules/5.10.120-tegra/extra/opensrc-disp/nvidia-drm.ko

I wanna ask that did you copied nvgpu.ko to this directory:Linux_for_Tegra/rootfs/usr/lib/modules/$(uname -r)/kernel/drivers/gpu/nvgpu/?

Btw, now i cannot see the usb-c connection now i will try to build out-of-tree modules.

@yavuz.env

No, I copied 3 modules to the folder JetsonOrinAgx/36_4/Linux_for_Tegra/rootfs/lib/modules/5.15.148-tegra/extra/opensrc-disp

1 Like

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