Orin NX can not display 1080p on HDMI with monitor - ASUS VS247H

[student0804]

I used Orin Nx and monitor, ASUS VS247H, and just only display less than 1600 x 900 resolution.

How could I do to display 1920x1080 resolution ?

[WayneWWW]

How did you flash your board?

[student0804]

I used orin nx SOM + xavier nx ca board.

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 p3509-a02+p3767-0000 internal

[WayneWWW]

Could you share the result of xrandr command?

[student0804]

Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
HDMI-0 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1024x768 60.00*+
1600x900 59.82
1400x900 59.88
1368x768 59.88 59.85
1360x768 59.96 59.80
1280x800 59.91 59.81
1280x720 59.86 59.74
1152x864 60.00
1024x576 59.90 59.82
960x540 59.82 59.63
864x486 59.92 59.57
800x600 72.19 60.32 56.25
640x480 59.94

[WayneWWW]

Hi,

Could you share the log (/var/log/Xorg.0log)? There is no 1080p list out in the xrandr.

[student0804]

Xorg.0.log (17.5 KB)

[WayneWWW]

The result looks weird.

Is it a custom board or nv devkit?

Please enable full log in xorg by below method and share log again.

#Add below option in /etc/X11/xorg.conf, ‘Section “Device”’. Verbose mode logging will be shown in

/var/log/Xorg.0.log
Section “Device”
…
Option “ModeDebug”
…
EndSection

[student0804]

The log is produced by custom board,
but I had the same problem with nv devkit (Xavier NX ca board)

Xorg.0.log (64 KB)

[WayneWWW]

Hi,

The log says it fails to read EDID from the monitor.

[ 16.500] (WW) NVIDIA(GPU-0): The EDID read for display device HDMI-0 is invalid:
[ 16.500] (WW) NVIDIA(GPU-0): - The EDID has an unrecognized version.

I don’t think devkit software/hardware has such issue. Could you test more monitors on devkit and check the xorg log with above method?

[linuxdev]

Incidentally, if the carrier board is from a third party, then typically device tree edits are required for i2c to function correctly. The DDC wire of HDMI uses i2c protocol, and is what reads EDID. Without that there is no possibility of automatic setup, and only defaults would be visible. With the failed EDID I am surprised the Xorg log showed any mode pool at all (which is normally the result of EDID).