Hi,
I encountered a display issue after installing JetPack 7.2 (Ubuntu 24.04) on a Jetson AGX Orin 64GB.
Environment
- Board: Jetson AGX Orin 64GB
- JetPack: 7.2
- Ubuntu: 24.04
- Display connection: DP-to-HDMI cable
- Monitor: 4K monitor
- Tested with two different 4K monitors
Problem
The system boots successfully, but the display behaves abnormally.
The issue disappeared after reflashing JetPack 6.2.2 on the same hardware.
Symptoms:
- GUI flickers 2–3 times after boot.
- Display resolution is limited to 640×480.
xrandr only reports 640×480.- During boot, repeated NVRM_RPC_DCE timeout messages appear.
Example boot log:
NVRM: GPU0 rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call
Call timed out (NV_ERR_TIMEOUT)
xrandr output:
DP-0 connected primary 640x480
640x480 59.94*
I also attempted to read the monitor EDID.
The result was:
No EDID on bus 1
No EDID on bus 2
...
Looks like no busses have an EDID.
What I tried
- Reinstalled JetPack 7.2
- Reflashed the device
- Tested with two different 4K monitors
- Used the same DP-to-HDMI cable
- Checked the display using
xrandr
- Checked EDID
Comparison
The same Jetson AGX Orin 64GB, same monitor, and same cable work correctly with JetPack 6.2.2.
After reverting to JetPack 6.2.2, the display works normally and the resolution is detected correctly.
Question
Has anyone experienced the same issue with JetPack 7.2?
Is this a known DCE/EDID problem or a display driver regression?
If there are any patches or debug steps I should try, I would appreciate your advice.
I can also provide boot logs, dmesg output, and a short video demonstrating the issue.
Thank you.
If you test native DP monitor, will you see such issue?
I also tested a native DisplayPort connection (without any adapter). In that case, the monitor showed no signal at all, so I couldn’t even reach the desktop. The issue only occurs differently depending on the connection method.
How did you install the Jetpack7.2 version? What is the method?
I installed JetPack 7.2 using NVIDIA SDK Manager with the Direct Flash method.
The system was flashed to the internal eMMC, and the Jetson booted from the eMMC after the installation.
The installation completed successfully without any reported errors. The display issue appeared immediately after the first boot.
Could you ssh to your board and share the following logs?
sudo dmesg
cat /var/log/Xorg.0.log.
Please do not capture any screenshot to share logs. They are not completed logs as full text.
I collected the logs via SSH as requested.
Attached files:
The issue was reproduced on JetPack 7.2 after boot.
dmesg.txt (130.2 KB)
Xorg.0.log.txt (26.5 KB)
Hi,
Please reboot your device and dump dmesg since the first boot up time. The log you shared has some logs missing.
also, what does xrandr show you there?
Hi,
I rebooted the device and collected the boot log immediately after startup.
Please find the attached dmesg log.
I also ran xrandr --verbose. The output is below.
Screen 0: minimum 8 x 8, current 640 x 480, maximum 32767 x 32767
DP-0 connected primary 640x480+0+0 (0x18b) normal (normal left inverted right x axis y axis) 0mm x 0mm
Identifier: 0x18a
Timestamp: 57206
Subpixel: unknown
Gamma: 1.0:1.0:1.0
Brightness: 1.0
Clones:
CRTC: 0
CRTCs: 0 1
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0
0 1
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
EDID:
00ffffffffffff003ac4000000000000
0000010495000078ee91a3544c99260f
50540020000001010101010101010101
01010101010100000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000092
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: DisplayPort
supported: DisplayPort
ConnectorType: DisplayPort
ConnectorNumber: 0
_ConnectorLocation: 0
non-desktop: 0
supported: 0, 1
640x480 (0x18b) 25.175MHz -HSync -VSync *current +preferred
h: width 640 start 656 end 752 total 800 skew 0 clock 31.47KHz
v: height 480 start 490 end 492 total 525 clock 59.94Hz
DP-1 disconnected (normal left inverted right x axis y axis)
Identifier: 0x18c
Timestamp: 57206
Subpixel: unknown
Clones:
CRTCs: 0 1
Transform: 1.000000 0.000000 0.000000
0.000000 1.000000 0.000000
0.000000 0.000000 1.000000
filter:
CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0
0 1
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: TMDS
supported: TMDS
ConnectorType: DisplayPort
ConnectorNumber: 0
_ConnectorLocation: 0
non-desktop: 0
supported: 0, 1
xrandr.txt (1.9 KB)
dmesg_boot.txt (130.1 KB)
From the output, only 640x480 is detected as both the current and preferred mode, and no other display modes are listed.
Please let me know if you need any additional logs or tests.
HI,
want to confirm. Is this EDID really the one from this monitor?
I mean what is the xrandr giving you when this monitor is connected on other platform?
or even the result on rel-36.x Orin AGX
BTW, looks like dmesg still not starts since the beginning.
Please share /var/log/kern.log instead. This one shall record all the kernel boot log.
Hi,
I attached the requested kern.log from JetPack 7.2.
I also checked the same monitor on JetPack 6.2.2 (L4T r36.4.x) using the same Jetson AGX Orin 64GB, the same DisplayPort cable, and the same monitor.
On JetPack 6.2.2:
- The monitor is detected correctly as Lenovo ThinkVision P32u-10.
- EDID is read correctly.
- The available display mode is 3840×2160 @ 60 Hz, and the display works normally without flickering.
- (Desktop scaling is set to 150%, so the logical desktop size reported by
xrandr is larger than the physical resolution.)
I have attached the xrandr output from JetPack 6.2.2 for comparison.
On JetPack 7.2, with the same hardware setup, the display is only detected as 640×480, and the desktop continuously flickers.
Please let me know if you need any additional tests or logs.
kern_jp622.txt (178.5 KB)
xrandr_jp622.txt (8.4 KB)
Looks like you attached the jp622 log but didn’t attach the 7.2 one?
Just wonder. Do you have other DP monitors there to test? Want to know if this is specific to only this Lenovo monitor.
Hi,
Sorry, I attached the JetPack 6.2.2 log by mistake. I have now attached the correct JetPack 7.2 kern.log.
I also tested the same Jetson AGX Orin 64GB with another DisplayPort monitor (Dell P3421W) using the same DisplayPort cable.
The result was the same:
- The display is only detected as 640×480.
- The desktop continuously flickers.
Therefore, the issue does not appear to be specific to the Lenovo ThinkVision P32u-10 monitor.
Please let me know if you need any additional logs or tests.
Sorry, where is the JP7.2 kernel log exactly? I still don’t see any attachment.
Sorry, it looks like the attachment did not upload correctly.
I have re-attached the JetPack 7.2 kern.log file to this reply.
Please let me know if you still cannot access it.
kern_jp72.txt (553.6 KB)
Could you also provide me the result of this?
cat /etc/nv_boot_control.conf
Hi,
Please find the requested nv_boot_control.conf attached.
The relevant entry is:
nv_boot_control_jp72.txt (226 Bytes)
TEGRA_BOOT_STORAGE nvme0n1
Please let me know if you need any additional information or logs.
