Jetson Nano rebooting after NVIDIA logo

Hey. I was trying to upgrade my jetpack from 4.3 to 4.4 using this guide. After this steps i have rebooted it and now it stucked on NVIDIA logo. Its rebooting after few seconds. I have lots of info on an SD card so i dont want to reflash new jetpack. Is it possible to recover it somehow?

Hi,

Firstly we need the serial console log to check why the system cannot boot into kernel.

Here you are. log.txt (19.4 KB)

Hi,

I see some display driver error from your log. It looks like your monitor is not supported. Do you use a adapter or something else here? Could you find another HDMI monitor and try again?

1.509110] Host read timeout at address 5458045c
[ 1.534437] H_REF_TO_SYNC + H_SYNC_WIDTH + H_BACK_PORCH <= 20
[ 1.534447] tegradc tegradc.0: Display timing doesn’t meet restrictions.
[ 1.548894] H_REF_TO_SYNC + H_SYNC_WIDTH + H_BACK_PORCH <= 20
[ 1.548902] tegradc tegradc.0: Display timing doesn’t meet restrictions.
[ 1.548911] fbcon_init: detected unhandled fb_set_par error, error code -22
[ 1.571403] tegradc tegradc.1: dpd enable lookup fail:-19
[ 2.082985] Host read timeout at address 545c00c4

look i can log in via serial console, but still nothing on display

Summary

maybe i should reinstall something or what

Hi,

I think this is just a pure display incompatible issue. But I cannot tell why jetapck4.3 does not have this error without log.

If you don’t want to lose your data on sdcard, please find another monitor and see if it can work or not.

how can i update to the latest jetpack without data loss?

You said you had upgraded to jetpack4.4… so you are already in the latest jetpack.

Please do read my comment here…

If you don’t want to lose your data on sdcard, please find another monitor and see if it can work or not.

I have changed the monitor but still problem is the same

Could you show me the new log after you change the monitor?

i have rebooted it and now it stucked on NVIDIA logo

And are you sure you have nvidia logo on first monitor? Your log shows bootloader cannot init display at all.

Yep, wait i will do another log

Sorry for a long repply. I got new hdmi monitor and here is log new log.txt (58.1 KB)

when im booting without monitor everything is fine

Hi,

Thanks for sharing a new log. I see the HDMI is initiated in cboot now so it has boot logo.

But you didn’t have kernel log this time so I cannot tell if display issue is still there or not.

when im booting without monitor everything is fine

And I don’t think this comment really helps anything here. We already knew your board can boot kernel in previous log.

what should i do then

But you didn’t have kernel log this time so I cannot tell if display issue is still there or not.

Dump the dmesg with your new monitor for me. Thanks.

how can i do it

In this console, type command “dmesg” and copy the log to here.