JETPACK 4.4-L4T-32.4.3- HDMI not working

  1. I flashed TX2 module for the custom board and completed the setup just fine.
  2. Added FDT /boot/tegra186-tx2-XXX.dtb into extlinux.conf file.
  3. On reboot the HDMI shows nvidia logo and the a white screen which goes away in 1-2sec. After that there is no display . Yet I can access the system from the serial console.
  4. If I remove the HDMI cable during reboot and connect it once the system is up on the serial console than HDMI works.

I have uploaded 2 boot up logs for the case when hdmi is connected while reboot and one where HDMI is connected after system comes up on the serial.
with-hdmi.txt (96.8 KB)no-hdmi.txt (83.9 KB)


  1. If I remove the HDMI cable during reboot and connect it once the system is up on the serial console than HDMI works.

That behavior is called hotplug.

Actually, you didn’t paste the full log because by default the kernel log is being silent in serial console.
Please use command dmesg or disable the silent in serial console for more verbose log.

From your current log, I don’t think the monitor is 100% work even in your hotplug case. Your hardware design probably has something wrong because EDID seems not able to be read.

And for custom carrier board, it is better to share schematic and describe your design like other forum users have shared.

You also need to tell us what you’ve done to your dts file.

Hello Wayne,

To bring it to your notice the board works fine, even on reboot. The issue begins when I update extlinux.conf file to switch between different DTB profiles.

I have attached the complete log file following cases:

  1. TX2 module flashed using script, work fine, no issues seen. (putty_no_extlinux_modififcation.txt)
  2. Next step is to update the extlinux file to add FDT to change to a different profile for same board. (putty_updated_dtb_in_extlinux.txt)

As seen from putty_updated_dtb_in_extlinux.txt:

Its giving following error:

[ 0.516567] mc-err: mcerr ops are set to t18x

[ 0.532556] mc-err: (255) csr_nvdisplayr: EMEM address decode error

[ 8.958388] irq 65: nobody cared (try booting with the “irqpoll” option)

[ 8.958405] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.140-tegra #1

[ 8.958407] Hardware name: quill (DT)

[ 8.958410] Call trace:

[ 8.958419] [] dump_backtrace+0x0/0x198

[ 8.958424] [] show_stack+0x24/0x30

[ 8.958430] [] dump_stack+0x98/0xc0

[ 8.958435] [] __report_bad_irq+0x3c/0xf8

[ 8.958439] [] note_interrupt+0x2c8/0x318

[ 8.958443] [] handle_irq_event_percpu+0x50/0x60

[ 8.958446] [] handle_irq_event+0x50/0x80

[ 8.958449] [] handle_fasteoi_irq+0xc8/0x1b8

[ 8.958453] [] generic_handle_irq+0x34/0x50

[ 8.958456] [] __handle_domain_irq+0x68/0xc0

[ 8.958460] [] gic_handle_irq+0x5c/0xb0

[ 8.958463] [] el1_irq+0xe8/0x194

[ 8.958467] [] irq_exit+0xd0/0x118

[ 8.958470] [] __handle_domain_irq+0x6c/0xc0

[ 8.958473] [] gic_handle_irq+0x5c/0xb0

[ 8.958476] [] el1_irq+0xe8/0x194

[ 8.958480] [] arch_cpu_idle+0x30/0x1b0

[ 8.958485] [] cpu_startup_entry+0x140/0x200

[ 8.958490] [] rest_init+0x84/0x90

[ 8.958495] [] start_kernel+0x370/0x384

[ 8.958499] [] __primary_switched+0x80/0x94

[ 8.958501] handlers:

[ 8.958517] [] tegra_mcerr_hard_irq threaded [] tegra_mcerr_thread

[ 8.958542] Disabling IRQ #65

Its looks like interrupt related crash, can you please let me know why its happening.

Can you let me know what are the bootargs needed for TX2, Is there any special way to sign a DTB file before adding it to extlinux.conf


putty_updated_dtb_in_extlinux.txt (107 KB)

putty_no_extlinux_modififcation.txt (86.4 KB)


If you have new issue, please file a separate topic.

The current topic is for HDMI.


I have created anew issue. I agree with you that this post is about HDMI not working. If you read the first description of the issue I clearly mention the case when HDMI is giving issues.

Can you please go through the logs and let me know if some HDMI setting is wrong.

Yes, I already went through your log for HDMI and asked you some questions in #2 which you didn’t reply…

What is your exact problem now?

I just checked your " putty_no_extlinux_modififcation.txt" log file and it appers all the HDMI error you are talking in #1 no longer exists.

Hello Wayne,

Please check putty_updated_dtb_in_extlinux.txt: as it has all the errors.

The other file was to show you that this errors do not happen when extlinux is not modified.


To be honest, I just want to know if you have at least one method to verify that your hardware (custom carrier board) can output HDMI without any error.
Is updating dtb through flash able to give you this stable result?

If that is true, I think we don’t need to care about HDMI in your “update extlinux” case because there are plenty of other errors that we cannot guarantee whether it would affect the HDMI or not.

For the error after you update extlinux.conf, you could compare the full kernel command line between the working and non-working case and see what might be missing.