HDMI Display monitor is not turning on with NVIDIA TX2 board

hi,

Am using two NVIDIA TX2 development kit and one NVIDIA TX1 Development kit.

In one of my NVIDIA TX2 Board i have flashed jetpack 3.1 with linux kernel 4.4.15 and it was working well for few days and now when i tried to boot the NVIDIA TX2 board, the HDMI Display is not turning on, i tried with other HMDI Display also,its showing a message like clock frequency is not matching with this monitor. i don’t know whether the problem with Display resolution or Hardware problem or with sofrtware problem- Jetpack 3.1.

With other NVIDIA TX2 board with jetpack 3.1 and with linux kernel 4.4.15, the display UI is coming with the distorted image (display is flickering).

But with the NVIDIA TX1 board with jetpack 2.3.1 everything is working well(the boot message and the UI is coming).

Please help me regarding this,i don’t know whether the problem is with Display resolution or Hardware problem or with sofrtware problem- Jetpack 3.1…

Regards,
Niranjan B

Are you using the same cable on each monitor which fails? Is this a purely HDMI cable without adapters? Do you have a second HDMI cable you can test with?

Do you have network access or serial console? If so, do you have file “/sys/kernel/debug/tegradc.0/edid”, and if you have this file, what is its content (e.g., “cat /sys/kernel/debug/tegradc.0/edid”)?

Also, can you post the content of “/var/log/Xorg.0.log”?

Niranantany,

Please describe more info about your case as what linuxdev mentioned. Also, please provide the kernel message if possible.

hi,

I have tried with other HDMI cables also, but it was same , the display is flickering…please find the below messages in Xorg.log :

[ 26.462] () tegra-snd-t186ref-mobile-rt565x Headphone Jack: always reports core events
[ 26.462] (
) evdev: tegra-snd-t186ref-mobile-rt565x Headphone Jack: Device: “/dev/input/event2”
[ 26.462] (–) evdev: tegra-snd-t186ref-mobile-rt565x Headphone Jack: Vendor 0 Product 0
[ 26.462] (–) evdev: tegra-snd-t186ref-mobile-rt565x Headphone Jack: Found keys
[ 26.462] (II) evdev: tegra-snd-t186ref-mobile-rt565x Headphone Jack: Configuring as keyboard
[ 26.462] () Option “config_info” “udev:/sys/devices/sound/sound/card1/input2/event2”
[ 26.462] (II) XINPUT: Adding extended input device “tegra-snd-t186ref-mobile-rt565x Headphone Jack” (type: KEYBOARD, id 9)
[ 26.462] (
) Option “xkb_rules” “evdev”
[ 26.462] () Option “xkb_model” “pc105”
[ 26.462] (
) Option “xkb_layout” “us”
[ 31.135] (–) NVIDIA(GPU-0): DELL ST2420L (DFP-0): connected
[ 31.135] (–) NVIDIA(GPU-0): DELL ST2420L (DFP-0): External TMDS
[ 31.716] (II) NVIDIA(0): Setting mode “HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”
[ 32.164] (–) NVIDIA(GPU-0): DELL ST2420L (DFP-0): connected
[ 32.164] (–) NVIDIA(GPU-0): DELL ST2420L (DFP-0): External TMDS
[ 33.153] (–) NVIDIA(GPU-0): DELL ST2420L (DFP-0): connected
[ 33.153] (–) NVIDIA(GPU-0): DELL ST2420L (DFP-0): External TMDS
[ 33.380] (–) NVIDIA(GPU-0): DELL ST2420L (DFP-0): connected
[ 33.380] (–) NVIDIA(GPU-0): DELL ST2420L (DFP-0): External TMDS
[ 351.626] (II) NVIDIA(0): Setting mode “HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”
[ 621.726] (II) NVIDIA(0): Setting mode “HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”
[ 645.209] (–) NVIDIA(GPU-0): DELL ST2420L (DFP-0): connected
[ 645.209] (–) NVIDIA(GPU-0): DELL ST2420L (DFP-0): External TMDS
[ 645.221] (II) NVIDIA(0): Setting mode “HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”
[ 646.415] (II) NVIDIA(0): Setting mode “HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”
[ 1103.228] (II) NVIDIA(0): Setting mode “HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”
[ 1570.841] (II) NVIDIA(0): Setting mode “HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”
[ 3062.529] (II) NVIDIA(0): Setting mode “HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}”

demesg log:

[ 1103.422781] tegradc 15210000.nvdisplay: Window 3 assigned to head 1
[ 1103.439464] tegradc 15210000.nvdisplay: Window 4 assigned to head 1
[ 1103.456123] tegradc 15210000.nvdisplay: Window 5 assigned to head 1
[ 1103.530901] tegradc 15210000.nvdisplay: blank - powerdown
[ 1103.632813] PD DISP2 index4 DOWN
[ 1103.632977] PD DISP1 index3 DOWN
[ 1103.632979] PD DISP0 index2 DOWN
[ 1103.648384] tegradc 15210000.nvdisplay: unblank
[ 1103.648399] PD DISP0 index2 UP
[ 1103.648526] PD DISP1 index3 UP
[ 1103.648528] PD DISP2 index4 UP
[ 1103.651504] rate get on hub 408000000
[ 1103.653225] Parent Clock set for DC plld2
[ 1103.653726] dc clk 148500000
[ 1103.660866] tegradc 15210000.nvdisplay: Link compression not supported by the panel
[ 1103.660874] rate get on compclk 148500000
[ 1103.674593] tegradc 15210000.nvdisplay: Window 3 assigned to head 1
[ 1103.691253] tegradc 15210000.nvdisplay: Window 4 assigned to head 1
[ 1103.707927] tegradc 15210000.nvdisplay: Window 5 assigned to head 1
[ 1103.779867] tegradc 15210000.nvdisplay: unblank
[ 1415.253290] tegradc 15210000.nvdisplay: blank - powerdown
[ 1415.349770] PD DISP2 index4 DOWN
[ 1415.349874] PD DISP1 index3 DOWN
[ 1415.349876] PD DISP0 index2 DOWN
[ 1570.999660] tegradc 15210000.nvdisplay: unblank
[ 1570.999692] PD DISP0 index2 UP
[ 1570.999835] PD DISP1 index3 UP
[ 1570.999842] PD DISP2 index4 UP
[ 1571.002027] rate get on hub 408000000
[ 1571.003324] Parent Clock set for DC plld2
[ 1571.004494] dc clk 148500000
[ 1571.008371] tegradc 15210000.nvdisplay: Link compression not supported by the panel
[ 1571.008376] rate get on compclk 148500000
[ 1571.023462] tegradc 15210000.nvdisplay: Window 3 assigned to head 1
[ 1571.040138] tegradc 15210000.nvdisplay: Window 4 assigned to head 1
[ 1571.056783] tegradc 15210000.nvdisplay: Window 5 assigned to head 1
[ 1571.145943] tegradc 15210000.nvdisplay: blank - powerdown
[ 1571.248335] PD DISP2 index4 DOWN
[ 1571.248491] PD DISP1 index3 DOWN
[ 1571.248493] PD DISP0 index2 DOWN
[ 1571.264071] tegradc 15210000.nvdisplay: unblank
[ 1571.264081] PD DISP0 index2 UP
[ 1571.264141] PD DISP1 index3 UP
[ 1571.264142] PD DISP2 index4 UP
[ 1571.265249] rate get on hub 408000000
[ 1571.265580] Parent Clock set for DC plld2
[ 1571.265935] dc clk 148500000
[ 1571.268406] tegradc 15210000.nvdisplay: Link compression not supported by the panel
[ 1571.268411] rate get on compclk 148500000
[ 1571.284250] tegradc 15210000.nvdisplay: Window 3 assigned to head 1
[ 1571.300912] tegradc 15210000.nvdisplay: Window 4 assigned to head 1
[ 1571.317613] tegradc 15210000.nvdisplay: Window 5 assigned to head 1
[ 1571.389862] tegradc 15210000.nvdisplay: unblank
[ 2199.041949] tegradc 15210000.nvdisplay: blank - powerdown
[ 2199.143304] PD DISP2 index4 DOWN
[ 2199.143421] PD DISP1 index3 DOWN
[ 2199.143424] PD DISP0 index2 DOWN
[ 3062.697182] tegradc 15210000.nvdisplay: unblank
[ 3062.697194] PD DISP0 index2 UP
[ 3062.697269] PD DISP1 index3 UP
[ 3062.697270] PD DISP2 index4 UP
[ 3062.698378] rate get on hub 408000000
[ 3062.698696] Parent Clock set for DC plld2
[ 3062.699024] dc clk 148500000
[ 3062.701522] tegradc 15210000.nvdisplay: Link compression not supported by the panel
[ 3062.701527] rate get on compclk 148500000
[ 3062.717341] tegradc 15210000.nvdisplay: Window 3 assigned to head 1
[ 3062.734006] tegradc 15210000.nvdisplay: Window 4 assigned to head 1
[ 3062.750670] tegradc 15210000.nvdisplay: Window 5 assigned to head 1
[ 3062.825897] tegradc 15210000.nvdisplay: blank - powerdown
[ 3062.925333] PD DISP2 index4 DOWN
[ 3062.925446] PD DISP1 index3 DOWN
[ 3062.925447] PD DISP0 index2 DOWN
[ 3062.940691] tegradc 15210000.nvdisplay: unblank
[ 3062.940704] PD DISP0 index2 UP
[ 3062.940770] PD DISP1 index3 UP
[ 3062.940771] PD DISP2 index4 UP
[ 3062.941854] rate get on hub 408000000
[ 3062.942195] Parent Clock set for DC plld2
[ 3062.942524] dc clk 148500000
[ 3062.944976] tegradc 15210000.nvdisplay: Link compression not supported by the panel
[ 3062.944980] rate get on compclk 148500000
[ 3062.960797] tegradc 15210000.nvdisplay: Window 3 assigned to head 1
[ 3062.977468] tegradc 15210000.nvdisplay: Window 4 assigned to head 1
[ 3062.994129] tegradc 15210000.nvdisplay: Window 5 assigned to head 1
[ 3063.065815] tegradc 15210000.nvdisplay: unblank

and the full log messages i have attached with this reply…

regards,
Niranjan B
Xorg.0.log (15.6 KB)
dmesg.log (69.9 KB)

In the dmesg log I do see plugged and unplugged events…was this from manually replugging the HDMI cable or powering the monitor off/on? If it showed unplugged with no intentional cable change and no intentional power off/on, then this is a clue…otherwise the logs look normal (without error), though I am curious about this:

[ 3062.960797] tegradc 15210000.nvdisplay: Window 3 assigned to head 1
[ 3062.977468] tegradc 15210000.nvdisplay: Window 4 assigned to head 1
[ 3062.994129] tegradc 15210000.nvdisplay: Window 5 assigned to head 1

The reason why this seems interesting is that I do not see “Window” in any of my logs, and I see it changing from “Window 4” to “Window 5”. I am also not powering my monitor off/on, nor pulling/inserting the cable, so this may account for the difference. There may be stages in boot which result in notes on video mode change and noting HDMI plugging in which are not related to any problem, but I would assume I would see similar Window messages at times.

Do you see any error from:

sha1sum -c /etc/nv_tegra_release

hi,

Actually am using two different HDMI displays to the NVIDIA TX2 board for my project purpose one is with 24 inch Dell HDMI monitor and other 11 inch monitor.

when i keep the resolution of 800x600 the GUI is coming well but if i switched it to 1280x1024 am getting distorted GUI, i doubt whether the problem with NVIDIA graphic driver or HDMI port issue in the board or the NVIDIA TX2 is not supporting for different sizes of display…

I re-flashed the jet-pack again and still the problem persists…

Please find the attached image and the log in nv_tegra_release:

/usr/lib/aarch64-linux-gnu/tegra/libnvrm_graphics.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvll.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvcamerautils.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvcolorutil.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnveglstreamproducer.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libscf.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvexif.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvddk_2d_v2.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmmlite.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvrm.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmm_contentpipe.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvcameratools.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvos.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmm_parser.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvcam_imageencoder.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvapputil.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvwinsys.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvtestresults.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvomxilclient.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmm_utils.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libglx.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvcamlog.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvosd.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvomx.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libargus_socketserver.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmmlite_utils.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnveglstream_camconsumer.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvavp.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvtnr.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmedia.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libargus_socketclient.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvparser.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libargus.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvimp.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libtegrav4l2.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvrm_gpu.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvddk_vic.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmm.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvjpeg.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvtvmr.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmmlite_image.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvmmlite_video.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvodm_imager.so: OK
/usr/lib/aarch64-linux-gnu/tegra/libnvdc.so: OK
/usr/lib/aarch64-linux-gnu/libv4l/plugins/libv4l2_nvvidconv.so: OK
/usr/lib/aarch64-linux-gnu/libv4l/plugins/libv4l2_nvvideocodec.so: OK
/usr/lib/xorg/modules/drivers/nvidia_drv.so: OK
/usr/lib/xorg/modules/extensions/libglx.so: OK

please help me regarding this…

regards,
Niranjan B
nv_tegra_release.log (2.53 KB)
800x600.jpg
1280x1024.jpg
800x600.jpg
1280x1024.jpg
800x600.jpg

800x600.jpg

1280x1024.jpg

When you run a single X server instance it has a buffer which it calls the screen. Monitors map onto part or all of that buffer. If the resolution of a monitor does not match the viewport onto the screen you will get clipping somewhere. There are cases where a monitor will support only an exact match to its resolution capabilities, and there may also be cases where the monitor allows setting to a mode which is “close” to its native display…in this latter case either the monitor itself will perform zooming, or else there will still be clipping.

This effect of matching resolution of monitor to viewport into the screen buffer is probably the most obvious part of dual screen operation. What isn’t always as obvious is that both monitors will be running in the same color depth as well…or at least the data will all be the same color depth…the monitors may be forced into a mode they do not support (which results in color problems). One monitor will generally win if it is the primary monitor and if it supports a native bit depth. I’m thinking the bit depth may be wrong for one monitor.

On top of all of this you may find the scan rate is set to something both monitors support, but one monitor may be at the edge of its performance limits while the other monitor is not…you would see some issues if one of the monitors is close to exceeding its abilities.

You may want to hook up only one monitor at a time and record the content of “xdpyinfo” in the different modes where it works. Then hook both back up, go through the modes, check xdpyinfo again…on the monitor which does not work well in this other mode see if xdpyinfo of this mode existed as working well when just that monitor was connected (I’m betting this mode did not show up when it worked well all by itself).

Overall, it looks like this is an issue of trying to mirror the settings of two different monitors using the same screen buffer data (bit depth and resolution) and scan rates. To decouple these and run them at separate resolutions, bit depths, or scan rates you would need each to have its own X server (and thus each would have its own screen/screenbuffer). For one monitor to mirror the other while decoupled you would need virtual desktop software to be exported from one screen and the client to display it on the other screen running on its own separate X server. Else they are entirely separate logins when running two separate instances of X…it is the virtual desktop software which can couple two completely independent displays.

I don’t see irregular kernel logs as well. The window 3,4,5 shown in log is normal. I thought the original problem was displays are not up. Why does #6 indicate other problem? Are we dealing with a resolution issue or a blanked monitor issue?

hi,

For my project purpose, sometimes i will be connecting the NVIDIA TX2 board with 11 inch HDMI Display and sometimes with 24 inch Dell monitor.but both the display are not connected at same time.
AM using only single HDMI Display connected to the NVIDA TX2 board.

i doubt whether my problem is due to connecting the board with single monitor and as well as large monitor,suddenly am getting Distorted image with higher resolution(please check #6) and with lower resolution it is coming well…

Please find the EDID.log…

sudo get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
No EDID on bus 8
1 potential busses found: 7
Bus 7 doesn’t really have an EDID…
Couldn’t find an accessible EDID on this computer.
I’m sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern pyrophobicman@gmail.com.
Partial Read… Try again

Please help me regarding this.

Regards,
Niranjan B
edid.log (5.75 KB)

When both monitors are connected what do you see from:

sudo find /sys -name edid

I’m curious if you have two edid files…you would need two for auto configuration to work on two at a time. I’m also curious as to the content of both. Use this when both monitors are connected simultaneously:

sudo -s
egrep -H '*' `find /sys -name 'edid'`
exit

I’m wondering if both monitors have EDID data, what that data is, and if having just one or both monitors at once changes the EDID (this is possible if the i2c communications mechanism does not work correctly). Note that if one monitor does not have valid and usable EDID data (such as only accepting modes the driver does not support) then the order of connecting will change whether or not the monitor works…a bad or missing EDID can result in using the prior monitor’s setting.

hi Linuxdev,

I’m using only one display to NVIDIA TX2 board. I have mentioned about two monitors because we use two different display’s (24inch and 11inch) for different purpose but not both of them at the same time. Since we keep connecting to bigger and smaller display’s frequently, its frequently switching resolutions and doubt that might have caused the problem. Now when we connect TX2 to bigger display, it is automatically catching 800x600 resolution and is working fine. Higher resolution than this is causing distorted desktop.

When we connect NVIDIA TX2 to smaller display, its just showing “OUT OF Range” message without showing and desktop.

Please find the above attachment of logs and images (#6 , #9 , #4) for reference.

Please help me regarding this.

Regards,
Niranjan B

It is important to know if EDID is available for configuration. If not, then a display without EDID will be inheriting prior settings. In some cases EDID provides data the driver does not accept, and there would still be inheritance.

I saw an earlier EDID, but it was not from the “/sys” file. The format from what I saw is different than that of the EDID file. The EDID data can be directly pasted into this tool…I don’t really know what the data is if I can’t paste it here…editing your original means manually adding a space between every single hex byte (since there are two monitors this would imply adding spaces twice):
http://www.edidreader.com

I am hoping to see what is explicitly found in the “/sys” edid file with each monitor connected (one at a time since you only use them one at a time). Once that is available logs from “/var/log/Xorg.0.log” with each monitor would be useful…but there is a catch: I’d like to see what the monitor thinks of the video modes, and this requires an additional option (an option which is pointless if the edid file does not exist). To increase logging for video modes add this to the Section “Device” of “/etc/X11/xorg.conf”:

Option    "ModeDebug"

Note: There is some mode setting in console mode prior to reaching graphical mode which could have bugs or issues completely separate from GUI mode. The “Out of Range” message would be typical of either a fallback mode or inheriting from a prior EDID.

Hi linuxdev,

i have used the following command in my terminal:

sudo find /sys -name edid

and the file was in the following path:

/sys/kernel/debug/tegra.1/edid (please find the attachment of EDID file)

i have tried to change the Option “ModeDebug” in “/etc/X11/xorg.conf”: but still the problem was same.
i have attached the xorg.0.log in #4 …when i connected it to 24inch Dell monitor…

Please help me regarding this.

Regards,
Niranjan B
EDID.log (784 Bytes)

The EDID checksum is valid for this particular monitor, so auto configuration can work. This monitor supports several older 4:3 aspect ratio modes, plus 1080p.

Note that “ModeDebug” does not change anything other than what appears in log files.

I’m not sure what the significance of this is, but in the Xorg.0.log file of #4 I see this:

[    24.846] Build Operating System: Linux <b>3.13.0-85</b>-generic aarch64 Ubuntu

Perhaps it is because I’ve updated (with apt-get…different than JetPack/L4T flash), but my R28.1 TX2 has this:

[    17.813] Build Operating System: Linux <b>4.4.0-83</b>-generic aarch64 Ubuntu

What makes this of interest is that the 3.x kernels have a different way of setting video modes than that of the 4.x kernels. The TX2 using JetPack3.1 would have flashed R28.1 and produced a 4.x kernel install. What is your “uname -r”, and also the output of “head -n 1 /etc/nv_tegra_release”? Have you installed any kernel changes (I’m guessing not since it says you are running on 4.4.15-tegra, but I want to be sure)?

On the Xorg.0.log it does not look like ModeDebug was in effect when the log was taken. Can you add the ModeDebug back in, reboot, and post Xorg.0.log with this monitor attached and ModeDebug in effect? This should dramatically increase logging of what the driver thinks of the various monitor modes.

Niranantany,
A few comments after reading the thread,

. Comparing your linux output with the one from linuxdev, it seems you are running older version of kernel (still 3.10-based rather than 4.4-based). Is that the case? Since you are using JetPack 3.1, you should see similar 4.4 version.

One way to find out is to re-flash JetPack 3.1 and let it reflash your board image and test again.

. "In one of my NVIDIA TX2 Board i have flashed jetpack 3.1 with linux kernel 4.4.15 and it was working well for few days and now when i tried to boot the NVIDIA TX2 board, the HDMI Display is not turning on…
=> what did you find out so far on this issue? Is this still an open one (as Wayne asked earlier)?

. for both HDMI display, could you use xrandr to display supported modes?

Hi Niranantany,

To clarify the problem, I have few questions and requests. Please describe clearly for every case, because you have two TX2, and 2 monitors. You can describe them as TX2-a, TX2-b and display-24, display-11.

1. Please make sure you are using full jetpack3.1 BSP, especially kernel 4.4 image.

2. Are both monitors (24" and 11") with HDMI interface without using any adapter? Could you provide the product id of them?

3. I have make a summary of your usecase, please give some comments if anything wrong.

case 1 . With 24" Dell monitor, what is the default mode when boot-up? Is it a 1080p or 800x600? After you change it to 1280x1024, it got distorted, right?
case 2. You mentioned "frequently hotplug between display-24 and display-11, does this the behavior you’ve tried before you see “OUT OF Range” on display-11?

4. Please share the edids of display-24 and display-11 by following command.

sudo -s
cat /sys/kernel/debug/tegradc.X/edid  #X maybe 0,1,2 indicated the display controller number, it should be 0 in your case

hi chijen, Am using two NVIDIA TX2(Board1 and Board2)… with the both boards i have problems.

Please find xrandr :(Board 2)

Screen 0: minimum 8 x 8, current 800 x 600, maximum 32767 x 32767
HDMI-0 connected primary 800x600+0+0 (normal left inverted right x axis y axis) 530mm x 300mm
1920x1080 60.00 + 59.95 50.00 61.25 60.05 51.04
1440x576 52.08
1440x480 62.69
1280x1024 75.03 60.00
1280x720 60.00 59.94 50.00
1152x864 75.00
1024x768 75.03 60.01
800x600 75.00 60.32*
720x576 50.00
720x480 59.94
720x400 70.04
640x480 75.00 59.94 59.94

Board 1 - In Board 1 the desktop is not coming and getting message like “input resolution 1980x1080 and clock frequency is not matching” i again re-flashed with jetpack 3.0 but still the problem is same…

Board2- In Board 2, am getting distorted desktop with higher resolution but with lower resolution(800x600) , the desktop is coming well…(please check log and images in #9 ,#13,#4).

please help me…

Regards,
Niranjan B

hi Wayne,

Thanks for your support. please find the below points:

display-24 - Dell ST2420L HDMI monitor.

display-11 - 11inch world-tech HDMI Display

TX2-a - In TX2-a the desktop GUI is not coming and getting message like “input resolution 1980x1080 and clock frequency is not matching” when connected to display-24 (Dell monitor) and when i connected with display-11 am getting “NO SIGNAL”.

TX2-b - In TX2-b, when connected to display-24 (Dell monitor)am getting distorted desktop GUI with higher resolution(1080P) but with lower resolution(800x600) , the desktop is coming well…(please check log and images in #9 ,#13,#4). and and when i connected with display-11 am getting “OUT OF RANGE”

Q1 : Please make sure you are using full jetpack3.1 BSP, especially kernel 4.4 image.

Yes i re-flashed full Jetpack 3.1 in TX2-a , but still am not getting any GUI Desktop in my HDMI monitor.

i re-flashed jetpack 3.0 in TX2-b

Q2: Are both monitors (24" and 11") with HDMI interface without using any adapter? Could you provide the product id of them?

Yes both of the display has direct HDMI port in it, power adapter is just for power supply for the display’s.

Q3: With 24" Dell monitor, what is the default mode when boot-up? Is it a 1080p or 800x600? After you change it to 1280x1024, it got distorted, right?

The default mode after boot-up is 1080p but after login… i changed my desktop resolution to 800x600 then it is coming well…

Q4: You mentioned "frequently hotplug between display-24 and display-11, does this the behavior you’ve tried before you see “OUT OF Range” on display-11?

yes i tried of connecting the TX2-b board with two different display-24 and display-11 at different times(only single either 11/24 display connected to board at time)…but still the problem was same…

please help me…

Regards,
Niranjan B

Hi Niranantany,

Let’s focus on display-24 first.

According to your comment,

tx2-a totally fails to use both panels -> Please share dmesg for both panels’ boot up procedure.

tx2-b seems work good in boot up but failed while changing to different resolution. Does other mode-change also hit the this error? For example, 720p back to 1080p. Please also share the edid for me to check.

thanks,
Wayne

hi wayne,

Please find the attachment of dmesg and EDID log for display-24 and TX2-b.

EDID:
00 ff ff ff ff ff ff 00 10 ac 68 a0 55 34 39 31
2d 15 01 03 80 35 1e 78 ea 92 65 a6 55 55 9f 28
0d 50 54 a5 4b 00 71 4f 81 80 d1 c0 01 01 01 01
01 01 01 01 01 01 02 3a 80 18 71 38 2d 40 58 2c
45 00 13 2b 21 00 00 1e 00 00 00 ff 00 57 38 56
59 39 31 42 32 31 39 34 55 0a 00 00 00 fc 00 44
45 4c 4c 20 53 54 32 34 32 30 4c 0a 00 00 00 fd
00 38 4c 1e 53 11 00 0a 20 20 20 20 20 20 01 b1
02 03 1f f1 4c 90 05 04 03 02 07 16 01 14 1f 12
13 ff 09 07 07 65 03 0c 00 10 00 83 01 00 00 02
3a 80 18 71 38 2d 40 58 2c 45 00 13 2b 21 00 00
1e 01 1d 80 18 71 1c 16 20 58 2c 25 00 13 2b 21
00 00 9e 01 1d 00 72 51 d0 1e 20 6e 28 55 00 13
2b 21 00 00 1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96
00 13 2b 21 00 00 18 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3f

and also find EDID log with "sudo get-edid | parse-edid "

This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
No EDID on bus 8
1 potential busses found: 7
Bus 7 doesn’t really have an EDID…
Couldn’t find an accessible EDID on this computer.
I’m sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern pyrophobicman@gmail.com.
Partial Read… Try again

In TX2-a display GUI is not coming…so i cannot able to go command mode also…

Regards,
Niranjan B

dmesg.log (69.9 KB)