Bypassing EDID error on Jetson Xavier

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
1

Hi

I’m currently working with the Jetson Xavier NX 8GB for an object detection project (working with jetson_inference) which is designed to operate without a monitor attached to the Jetson, out in my hobby farm. Currently the system is crashing every 15 to 75 minutes, and after checking /var/log/syslog I find the following subsequent errors every time:

Jun 29 09:08:08 ubuntu kernel: [ 131.774906] edid invalid
Jun 29 09:08:08 ubuntu kernel: [ 131.894740] tegradc 15200000.nvdisplay: blank - powerdown
Jun 29 09:08:08 ubuntu kernel: [ 131.930570] tegradc 15200000.nvdisplay: unblank
Jun 29 09:08:08 ubuntu kernel: [ 131.931432] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
Jun 29 09:08:08 ubuntu kernel: [ 131.931566] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd

From what I understand the system is checking for a display, can’t find any attached (aka can’t get EDID data from a display), throws the invalid error and shuts down the display.

Because my program is rendering the frames to display://x in order to convert to numpy array and correctly pass into my inference net, I’m assuming this is causing the reliance on a display.

I’ve tried a headless ghost/dummy HDMI plug to no avail, and attempted to create a virtual display by modifying /etc/X11/xorg.conf which went disastrously and almost bricked the system. If anyone has any insight into how to bypass this issue please let me know or DM me.

Cheers.

3

Just try to clarify if I understand your question,

are you talking about you don’t have a physical monitor connected and you have a virtual setting in xorg.conf and that seems leading to above issue?

4

Hi Wayne, thanks for replying.

I have tried setting up a virtual display in xorg.conf previously, which caused errors with the gdm daemon on boot.

At present, the xorg.conf file and its symlink are the default.

5

So you are talking about nothing is connected there and nothing is configured in the xorg conf and you still see such log appeared in syslog?

6

Yes that’s correct. I’m looking for other potential methods for bypassing the EDID check (provided that is the primary issue)

7

I would like to check why such weird behavior would happen there.

Could you share me the dmesg from your board first?

8

diagnostic_message.txt (67.8 KB)

From what I’m seeing it could be sda1 not being properly mounted? I am using a 500gb NVMe SSD as a boot drive because all the libraries I’m using won’t fit on the 16GB eMMC drive (I’m using Xavier production module with J202 carrier board from SeeedStudio).

9

I don’t really care about what happened with your sda1 drive. Your dmesg tells your filesystem is from emmc too.

What I saw is there are monitor connected logs… and even a mode info from EDID…

[ 11.373768] tegradc 15200000.nvdisplay: hdmi: tmds rate:146250K prod-setting:prod_c_hdmi_111m_223m
[ 11.394304] tegradc 15200000.nvdisplay: hdmi: plugged

Are you sure you don’t have a monitor connected?

10

Since you are using a custom board, are you sure that board can work fine with SDKM image?

11

This log was generated with a monitor and peripherals connected, it would be impossible to try extract dmesg logs after the board has crashed. After I observe a system crash, I bring the system back inside to plug into a monitor to look for error codes but I just see a frozen screen. I have to power cycle the system to open a terminal.

Can never be 100% about a custom board, however SeeedStudio state the J202 " has nearly the same design and function as NVIDIA® Jetson Xavier NX™ carrier board, perfectly works with Jetson Nano/Xavier NX/TX2 NX module" quoted from their website. I’ve used their J101 with Nano modules before with no problem.

12

Just to clarify. The method you are doing now to check the crash reason is not reliable.

You should learn to use serial console to check logs. I mean, what you observed so far may not really be related to the crash…

Also, it looks like a rel-32 log. Thus you have to remove “quiet” from /boot/extlinux/extlinux.conf to enable full loglevel in serial console.

13

UART serial console can. That is why I suggested here.

14

Alright I’ll check those out. Still learning new ways to interface with the Jetson aside from the GUI.

Thanks for your help.

16

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