step1. No HDMI display after startup.
step2. Unplug HDMI connector, execute xrandr, and then connect HDMI, the monitor displays with a resolution of 1024 * 768.
step3. Execute xrandr again, then the monitor displays a black screen.
The following is the relevant information. Why does HDMI fail to display normally?
Thanks.
Just want to clarify this first. If your HDMI monitor already render the desktop but with wrong color or noise, then it may not be the device tree issue.
Then, the hdmi does not work after update to Jeptpack 5.0.2 with the patch as above. The monitor displays “No video input”.
The monitor displays ubuntu desktop only when I perform the following actions. If you execute the xrandr command again after “step2”, the monitor turns to black screen, and displays “No video input” again.
Later, I find that the color display is abnormal when the monitor displays ubuntu desktop, just like this post.
I reflash Jetpack 5.0.1, the monitor displays boot logo, ubuntu desktop.
I follow the instruction below(use dcbtool), and reflash Jetpack 5.0.2, the monitor displays “No video input”.
Just want to double confirm with you. What is the exact step or situation that you could see ubuntu desktop under jp5.0.2? The color issue or noise is not under discussion for now.
Yes
The logs of Step1 & Step2 are as follows
dmesg:
[ 686.886374] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 1
[ 686.886390] snd_hda_codec_hdmi hdaudioC0D0: HDMI: out of range MNL 13
[ 984.579941] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[ 984.579965] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device Philips PHL 271E1 (HDMI-0)
[ 984.656689] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[ 984.656700] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[ 985.201024] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[ 985.201042] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[ 985.265995] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[ 985.266017] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
Xorg.log:
[ 984.061] (--) NVIDIA(GPU-0): DFP-0: connected
[ 984.061] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 984.061] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 984.061] (--) NVIDIA(GPU-0):
[ 984.101] (--) NVIDIA(GPU-0): DFP-0: connected
[ 984.101] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 984.101] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 984.101] (--) NVIDIA(GPU-0):
[ 984.221] (II) NVIDIA(0): Setting mode "NULL"
[ 984.321] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1024x768 +0+0 {ViewPortIn=1024x768, ViewPortOut=1024x768+0+0}"
[ 984.645] (--) NVIDIA(GPU-0): DFP-0: connected
[ 984.645] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 984.646] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 984.646] (--) NVIDIA(GPU-0):
[ 984.710] (--) NVIDIA(GPU-0): DFP-0: connected
[ 984.711] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 984.711] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[ 984.711] (--) NVIDIA(GPU-0):
[ 1033.649] (WW) NVIDIA(0): MetaMode "HDMI-0:1920x1080_75" could not be re-validated
[ 1033.649] (WW) NVIDIA(0): against the current hardware configuration; removing.
[ 1033.649] (WW) NVIDIA(0): MetaMode "HDMI-0:1920x1080_60_0" could not be re-validated
[ 1033.649] (WW) NVIDIA(0): against the current hardware configuration; removing.
[ 1033.649] (WW) NVIDIA(0): MetaMode "HDMI-0:1920x1080_50" could not be re-validated
[ 1033.649] (WW) NVIDIA(0): against the current hardware configuration; removing.
[ 1033.649] (WW) NVIDIA(0): MetaMode "HDMI-0:1680x1050" could not be re-validated against
[ 1033.649] (WW) NVIDIA(0): the current hardware configuration; removing.
[ 1033.649] (WW) NVIDIA(0): MetaMode "HDMI-0:1440x900" could not be re-validated against
[ 1033.649] (WW) NVIDIA(0): the current hardware configuration; removing.
[ 1033.649] (WW) NVIDIA(0): MetaMode "HDMI-0:1280x1024" could not be re-validated against
[ 1033.649] (WW) NVIDIA(0): the current hardware configuration; removing.
[ 1033.649] (WW) NVIDIA(0): MetaMode "HDMI-0:1280x1024_60" could not be re-validated
[ 1033.649] (WW) NVIDIA(0): against the current hardware configuration; removing.
[ 1033.649] (WW) NVIDIA(0): MetaMode "HDMI-0:1280x960" could not be re-validated against
[ 1033.649] (WW) NVIDIA(0): the current hardware configuration; removing.
[ 1033.687] (WW) NVIDIA(0): MetaMode "HDMI-0:1280x720_50" could not be re-validated
[ 1033.687] (WW) NVIDIA(0): against the current hardware configuration; removing.
[ 1033.717] (WW) NVIDIA(0): MetaMode "HDMI-0:1024x768_70" could not be re-validated
[ 1033.717] (WW) NVIDIA(0): against the current hardware configuration; removing.
[ 1033.840] (WW) NVIDIA(0): MetaMode "HDMI-0:720x576" could not be re-validated against
[ 1033.840] (WW) NVIDIA(0): the current hardware configuration; removing.
[ 1033.840] (WW) NVIDIA(0): MetaMode "HDMI-0:720x480" could not be re-validated against
[ 1033.840] (WW) NVIDIA(0): the current hardware configuration; removing.
[ 1033.862] (WW) NVIDIA(0): MetaMode "HDMI-0:640x480_72" could not be re-validated against
[ 1033.862] (WW) NVIDIA(0): the current hardware configuration; removing.
[ 1033.884] (WW) NVIDIA(0): MetaMode "HDMI-0:640x480_60_0" could not be re-validated
[ 1033.884] (WW) NVIDIA(0): against the current hardware configuration; removing.
[ 1033.884] (WW) NVIDIA(0): custom viewPortOut, 1920 x 1079 +0 +0, does not fit within
[ 1033.884] (WW) NVIDIA(0): rasterSize, 1024x768; ignoring custom viewPortOut
[ 1033.936] (WW) NVIDIA(0): custom viewPortOut, 1728 x 1080 +96 +0, does not fit within
[ 1033.936] (WW) NVIDIA(0): rasterSize, 1024x768; ignoring custom viewPortOut
It’s different from the one I’m using, but the problem is the same.
The following are logs of jp5.0.1/jp5.0.2, or different dcb setting.
(1) jp5.0.2 with new dcb setting from below.
Are you sure your EDID of this monitor is able to get read when it is jetpack5.0.1?
If you only see a hardcoded mode, it means EDID fails to read so we give you a hardcoded value.
[ 984.579965] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device Philips PHL 271E1 (HDMI-0)
[ 984.656689] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[ 984.656700] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[ 985.201024] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[ 985.201042] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
[ 985.265995] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x730245 result 0xffff:
[ 985.266017] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device HDMI-0
Is your “plug out HDMI cable and run xrandr, and it will show EDID read failure” a must-have step to make the display show the desktop? For example, if you don’t run xrandr but only hotplug HDMI, will the screen show up?
Have you ever tried other kind of monitor?
Actually you can just check the post I shared for the new DCB. The user from that post already had normal HDMI working. But just hotplug has some issue. You can go through the check we have done there.
Above steps are the full method to dump the display log. Basically, it reloads multiple drivers with debug print enabled. Please attach new dmesg again.