Hdmi doesn't work for some monitors

with custom board ,jetpack 5.1 ,L4T 35.2.1 or L4T 35.1.0。
I found that hdmi adapts to specific monitors.

with DELL monitor model is P2319H is ok。
but with DELL monitor model is U2414Hb cannot display。

The serial port is printed as follows:
[ 21.951431] dce: dce_client_schedule_event_work:348 Failed to schedule Async event Queue Full!
[ 22.001749] dce: dce_client_schedule_event_work:348 Failed to schedule Async event Queue Full!
[ 22.759172] dce: dce_client_schedule_event_work:348 Failed to schedule Async event Queue Full!
[ 34.565300] dce: dce_client_schedule_event_work:348 Failed to schedule Async event Queue Full!
[ 34.615365] dce: dce_client_schedule_event_work:348 Failed to schedule Async event Queue Full!

If you have the failing monitor connected, and then boot, post the “/var/log/Xorg.0.log” file. Note that you can still use ssh/scp even if the GUI fails, or serial console.

Hi:
Xorg.0.log (190.7 KB)

That has an interesting error in the log. It seems to infinitely repeat the monitor query:

[    26.018] (--) NVIDIA(GPU-0): DELL U2414H (DFP-1): connected
[    26.018] (--) NVIDIA(GPU-0): DELL U2414H (DFP-1): Internal TMDS
[    26.018] (--) NVIDIA(GPU-0): DELL U2414H (DFP-1): 165.0 MHz maximum pixel clock
[    26.018] (--) NVIDIA(GPU-0): 

As background, HDMI and DP monitors (the “plug-n-play” capable monitors) have a wire known as the DDC wire. That wire uses i2c protocol to ask the monitor for its capabilities. Those capabilities are in turn in the format known as EDID data (EDID2 these days). The power for the i2c circuitry is actually provided by the GPU so that a monitor can be queried even if it is turned off. I’m thinking that something went wrong with the actual DDC/i2c/EDID, or else with the power related to this.

After booting, what do you see from this (which creates a log in the command):

dmesg | egrep -i '(hdmi|i2c|ddc|edid)' | tee log_hdmi.txt

Also, is this a purely HDMI or purely DisplayPort monitor? If there is an adapter used, is it other than the one NVIDIA provides?

This monitor is compatible with hdmi and dp interface. no use adapter。

root@tegra-ubuntu:/home/orin# dmesg | egrep -i ‘(hdmi|i2c|ddc|edid)’ | tee log_hdmi.txt
[ 4.224854] i2c /dev entries driver
[ 4.228505] tegra-i2c 3160000.i2c: Adding to iommu group 2
[ 4.234295] tegra-i2c c240000.i2c: Adding to iommu group 2
[ 4.239975] tegra-i2c 3180000.i2c: Adding to iommu group 2
[ 4.245667] tegra-i2c 3190000.i2c: Adding to iommu group 2
[ 4.251342] tegra-i2c 31c0000.i2c: Adding to iommu group 2
[ 4.257013] tegra-i2c c250000.i2c: Adding to iommu group 2
[ 4.262688] tegra-i2c 31e0000.i2c: Adding to iommu group 2
[ 4.268421] tegra-i2c 31b0000.i2c: Adding to iommu group 2
[ 12.725627] OF: graph: no port node found in /i2c@c240000/ucsi_ccg@8/connector@0
[ 12.769906] input: NVIDIA Jetson AGX Orin HDA HDMI/DP,pcm=3 as /devices/platform/3510000.hda/sound/card0/input1
[ 12.769987] input: NVIDIA Jetson AGX Orin HDA HDMI/DP,pcm=7 as /devices/platform/3510000.hda/sound/card0/input2
[ 12.770063] input: NVIDIA Jetson AGX Orin HDA HDMI/DP,pcm=8 as /devices/platform/3510000.hda/sound/card0/input3
[ 12.770118] input: NVIDIA Jetson AGX Orin HDA HDMI/DP,pcm=9 as /devices/platform/3510000.hda/sound/card0/input4
[ 12.812032] OF: graph: no port node found in /i2c@c240000/ucsi_ccg@8/connector@0
[ 12.819812] OF: graph: no port node found in /i2c@c240000/ucsi_ccg@8/connector@0
root@tegra-ubuntu:/home/orin#

Hi:
how can i test the i2c is ok?

all dmesg info
dmesg.all (91.3 KB)

I don’t see anything specifically wrong (I also don’t know if /i2c@c240000 is related to HDMI/DP or not; there are plenty of i2c unrelated which would not matter).

I don’t know what this error is about, but it repeats in the boot log, so it might be related (someone from NVIDIA would have to comment):

[   18.556935] nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for aarch64  35.2.1  Release Build  (buildbrain@mobile-u64-6348-d7000)  Tue Jan 24 15:26:53 PST 2023
[   18.590295] fuse: init (API version 7.32)
[   18.785867] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x2080013f result 0x56:
[   18.786815] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x2080017e result 0x56:
[   18.790853] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x2080014a result 0x56:
[   18.866213] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0xffff:
[   18.866596] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730190 result 0x56:
[   19.726225] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0xffff:
[   19.978104] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0xffff:

If you have an i2c analyzer it would be interesting to see if it is performing a query of the DDC wire; or even to put an oscilloscope on it and see if it looks like there is data traffic occurring as a result of HDMI insert (or the DisplayPort equivalent).

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