Hello! After applying Jetson BSP 36.4.4 to my OrinNX image, I’m having an issue with Xorg not binding to any card0/1, resulting in a black screen on my device. I’ve attached a diff of the Xorg logs between my images running BSP 36.3 and BSP 36.4.4. On my old image: sudo log /dev/dri/* COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME Xorg 1338 root 12u CHR 226,0 0t0 267 /dev/dri/card0 Xorg 1338 root 13u CHR 226,128 0t0 266 /dev/dri/renderD128 Xorg 1338 root 19u CHR 226,128 0t0 266 /dev/dri/renderD128 Xorg 1338 root 28u CHR 226,128 0t0 266 /dev/dri/renderD128 Xorg 1338 root 31u CHR 226,128 0t0 266 /dev/dri/renderD128 chromium 1637 root 26u CHR 226,128 0t0 266 /dev/dri/renderD128 chromium 1637 root 34u CHR 226,128 0t0 266 /dev/dri/renderD128 On my new image: sudo log /dev/dri/* COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME Xorg 1296 root 13u CHR 226,128 0t0 262 /dev/dri/renderD128 Xorg 1296 root 18u CHR 226,128 0t0 262 /dev/dri/renderD128 Xorg 1296 root 27u CHR 226,128 0t0 262 /dev/dri/renderD128 Xorg 1296 root 30u CHR 226,128 0t0 262 /dev/dri/renderD128 chromium 1600 root 26u CHR 226,128 0t0 262 /dev/dri/renderD128 chromium 1600 root 34u CHR 226,128 0t0 262 /dev/dri/renderD128 Xorg-log-diff.txt (99.5 KB)

We’ve run into the same thing, and it’s a real pain because the out of the box behaviour is nondeterministic. Our solution has been to add soft dependencies in /etc/modprobe.d to ensure that the kernel loads drivers in the same order so that card0 and card1 are assigned properly. Here’s the contents of what we put in /etc/modprobe.d/fix-orin-gpu.conf: options nvidia_drm modeset=1 fbdev=1 softdep nvidia pre: host1x tegra_drm drm_kms_helper softdep nvidia_modeset pre: host1x tegra_drm drm_kms_helper nvidia softdep nvidia_drm pre: host1x tegra_drm drm_kms_helper nvidia_modeset

For our Custom Board I’m building from a clean Linux_for_Tegra ( using git clean and reset commands ) for each build. I’ve primarily been re-flashing my board. But, I’ve also tested out a path we have to update from an old image to new, and it results in the same issue.

Jetson OrinNX - Xorg not binding to card0 after BSP Update from 36.3 to 36.4.4

Robotics & Edge Computing Jetson Systems Jetson Orin NX

DaneLLL November 6, 2025, 2:03am 6

Hi,
For information, do you hit the issue on developer kit or your custom board?

And for After applying Jetson BSP 36.4.4 to my OrinNX image, do you mean you have a clean Linux_for_tegra of r36.4.4 and re-flash the system? For kernel customization we would suggest have a clean Linux_for_Tegra folder like:
No data from Joystick Logitech-f710 - #10 by DaneLLL

Topic		Replies	Views
AGX Orin – Xorg / display errors after update, possible NVIDIA driver version mismatch Jetson AGX Orin driver	5	315	January 9, 2026
Jetson Orin NX not mounting issue while boot Jetson Orin NX ubuntu	15	586	June 3, 2025
Issues bringing in upstream kernel (6.8.12 in Ubuntu 24.04 LTS) Jetson Orin Nano	5	678	March 10, 2025
Jetson AGX Developer Kit no display on console Jetson AGX Orin ubuntu	5	504	April 24, 2024
Failed to start X11 server in Jetson Orin Nano Jetson Orin Nano dp-display , x11	10	984	February 10, 2025
Jetson Orin AGX 64GB devkit only shows black screen after flashing Jetson AGX Orin reflash	25	1016	June 17, 2025
Jetson orin nx 开机在R35.4.1上开机黑屏 Jetson Orin NX boot , chinese	14	1047	July 5, 2024
Orin NX 16GB on Waveshare IO-BASE-B: no display under Linux, UEFI works — clean flashes of L4T 36.3.0 and 36.4.7 both fail Jetson Orin NX dp-display	9	160	October 4, 2026
Booting from SD card, blank screen Jetson AGX Orin boot	3	172	August 8, 2024
Nvidia Jetson AGX Orin 64gb Developer kit doesn't display Jetson AGX Orin boot , reflash	30	2170	August 9, 2023

Jetson OrinNX - Xorg not binding to card0 after BSP Update from 36.3 to 36.4.4

Related topics