Jetson Nano blank screen during and after boot

I’ve updated my Jetson Nano a couple of times in the past few months with “apt-get upgrade” using the Nano without any monitor attached.

Well, I just attached a monitor and all I get is a blank screen. There is no Nvidia logo during boot. There is no desktop after boot (I have auto-login enabled). I just have a black screen. My monitor is turning on when the Jetson Nano turns on so clearly there is a signal.

I am able to ssh login over WiFi so I looked at dmesg and I see this:

[ 227.014501] tegradc tegradc.0: unblank
[ 227.094304] tegradc tegradc.0: blank - powerdown
[ 227.574624] tegradc tegradc.0: blank - normal
[ 227.896835] tegradc tegradc.0: unblank
[ 227.896848] tegradc tegradc.0: update windows ret = -14
[ 227.896851] tegradc tegradc.0: sync windows ret = -14

Please can someone help me get my Displayport video output working again?

P.S.
(I should also mention that the monitor works fine when I plug it into my laptop and the monitor used to work fine with the Jetson Nano a few months ago. I am using the same 5V 4A power supply I used since the start.)

1 Like

Yesterday update don´t let my Jetson to boot properly…have the NVIDIA logo and some logs and no image on my monitor… I am trying to reflash sd right now

1 Like

Reflashed memory… everything worked as normal now… updated software again, reboot and the problem appears again. Definitively the last software update have a problem

1 Like

I have had the same issues as well. I have narrowed the issues down to the ubuntu updates. I do not know what package(s) is the offender but reflashing and installing only nvidia updates should not cause problems.

1 Like

Can anyone share the commands to reproduce this issue?

1 Like

I can confirm that it is not a hardware fault as I just flashed the latest image and the graphics work fine.

My existing image just had a “apt-get upgrade” done to it.

I also ran:

sudo dpkg-reconfigure gdm3

to make sure gdm was running.

1 Like

And do you have any method to get this problem again after you flash the board?

You want me to reproduce the problem using the virgin new SD image? That is asking a lot.

The SD card image I am using has been updated since October 2019 using “apt-get upgrade”.

1 Like

No offense. I just want to know what kind command would hit this problem.
We already tried apt-get upgrade these days and didn’t hit this error so I am wondering what command may trigger this.

This is for debug only. If more people share the methods or what they’ve done to trigger issue, it would be easier for us to find out cause.

Of course you can refuse if you don’t want to do that.

And some analysis based on the log.

According to the kernel log in first comment here, update windows gives a -14 error which is “EFAULT”. However, this error would only return from that function if display controller is not enabled. And it is abnormal dc is not enabled after fb driver calls unblank.

I also wonder if everyone here sees the same kernel error.

@fcomg_e @aka1105 Could you kindly share this info too?

1 Like

I’m not offended and am very grateful for your assistance. Does Nvidia have an original SD card system that has been continually upgraded since the Jetson Nano product was created?

All I can do is look at my bash history to tell you what I did with “sudo”:

I did some stuff with udev to get GPIO working
I disabled nvgetty so I could connect my peripherals to the serial port

That’s all.

Unless you have any good ideas, I will try doing a diff on my /etc directory between the virgin SD card and my SD card.

Clearly the smoking gun is the “-14” error which indicates what the actual problem is. I wish I was able to fix that.

Again today: sudo apt update && sudo apt upgrade and blank screen…

2 Likes

To see what is happening: https://www.youtube.com/watch?v=q-HYrR-DNYs

1 Like

Here you can get more information…

Hi,

Also want to know

  1. Is this issue happened to nano-2GB or 4GB?

  2. @fcomg_e although the device does not have working monitor, you should be able to ssh or use uart console to access the board. If you can do that, are you able to dump the dmesg too?

Just saw your post. I will check it.

Mine is Jetson Nano 4GB A1.

Hello @WayneWWW

1.- It is on the new Jetson Nano 2Gb

  1. In my case, when starting the Jetson Nano after NVIDIA logo appears, I see some logs and then only the prompt blinking but I can´t do anything. I have no control over the Jetson Nano.

I´m reflashing at this moment again…

I appreciate your help, thanks!

I appreciate your help, thanks!

Here is my full kernel log relating to the problem:

Nov 25 18:35:13 nano-desktop kernel: [    0.437489] iommu: Adding device tegradc.0 to group 14
Nov 25 18:35:13 nano-desktop kernel: [    0.437536] platform tegradc.0: domain=ffffffc0f952c198 allocates as[0]=ffffffc0f9bd8248
Nov 25 18:35:13 nano-desktop kernel: [    0.438049] platform tegradc.0: IOVA linear map 0x00000000d7000000(19000000)
Nov 25 18:35:13 nano-desktop kernel: [    0.438360] iommu: Adding device tegradc.1 to group 15
Nov 25 18:35:13 nano-desktop kernel: [    0.438410] platform tegradc.1: domain=ffffffc0f952c3d8 allocates as[0]=ffffffc0f9bd82b0
Nov 25 18:35:13 nano-desktop kernel: [    0.438913] platform tegradc.1: IOVA linear map 0x00000000d7000000(19000000)
Nov 25 18:35:13 nano-desktop kernel: [    0.985521] tegradc tegradc.0: disp0 connected to head0->/host1x/sor1
Nov 25 18:35:13 nano-desktop kernel: [    0.985871] tegradc tegradc.0: DT parsed successfully
Nov 25 18:35:13 nano-desktop kernel: [    0.985916] tegradc tegradc.0: Display dc.ffffff800ab80000 registered with id=0
Nov 25 18:35:13 nano-desktop kernel: [    0.989452] tegradc tegradc.0: probed
Nov 25 18:35:13 nano-desktop kernel: [    0.990169] tegradc tegradc.0: fb registered
Nov 25 18:35:13 nano-desktop kernel: [    0.991465] tegradc tegradc.1: disp1 connected to head1->/host1x/sor
Nov 25 18:35:13 nano-desktop kernel: [    0.991542] tegradc tegradc.1: No lt-data, using default setting
Nov 25 18:35:13 nano-desktop kernel: [    0.991569] tegradc tegradc.1: No hpd-gpio in DT
Nov 25 18:35:13 nano-desktop kernel: [    0.991602] tegradc tegradc.1: DT parsed successfully
Nov 25 18:35:13 nano-desktop kernel: [    0.991650] tegradc tegradc.1: Display dc.ffffff800ad00000 registered with id=1
Nov 25 18:35:13 nano-desktop kernel: [    0.993142] tegradc tegradc.1: dpd enable lookup fail:-19
Nov 25 18:35:13 nano-desktop kernel: [    1.504534] tegradc tegradc.1: probed
Nov 25 18:35:13 nano-desktop kernel: [    1.504904] tegradc tegradc.1: fb registered
Nov 25 18:35:13 nano-desktop kernel: [    1.512077] tegradc tegradc.1: Display timing doesn't meet restrictions.
Nov 25 18:35:13 nano-desktop kernel: [    1.512097] tegradc tegradc.1: tegra_dc_set_fbcon_boot_mode: set DC mode from modedb, err = -22
Nov 25 18:35:13 nano-desktop kernel: [    1.512115] tegradc tegradc.1: Failed to set fbcon mode for DC 1
Nov 25 18:35:13 nano-desktop kernel: [    1.519605] tegradc tegradc.1: nominal-pclk:25200000 parent:25200000 div:1.0 pclk:25200000 24948000~27468000
Nov 25 18:35:13 nano-desktop kernel: [    1.521912] tegradc tegradc.1: tegra_dp_get_bpp: vmode=0x0 did not specify bpp
Nov 25 18:35:13 nano-desktop kernel: [    1.525520] tegradc tegradc.1: DP: no prod_c_hbr prod settings node in device tree
1 Like