jetson tx2 blue screen

When I install jetpack to jetson tx2 device, enter the REC mode, due to misuse, leading to blue screen after boot, please let me know the reason.

Thanks

Do you see any error from:

sha1sum -c /etc/nv_tegra_release

Is the monitor purely HDMI? Is there any intervening adapter?

after enter command ‘sha1sum…’ every thing is ok ,the monitor is new one ,just have only hdmi port ,i am a novice .at the begining ,the device could enter the ubuntu graphic interface.

What do you see from:

sudo -s
cat `find /sys -name 'edid'`
exit

The hex data can be pasted into http://www.edidreader.com. Let’s see what the monitor is telling the video card (which is what the edid data does).

when enter the command 'cat find /sys -name 'edid'’ ,the terminal show ‘No such file or directory’

Normally if the drivers are in place the file will be there (though it might say something like “No EDID” in it). Are you positive that this had no errors?

sha1sum -c /etc/nv_tegra_release

In particular verify the two sha1sum lines of “libglx.so” in the above.

I doubt the monitor itself would cause this. Even if the driver with the i2c communications doing the query failed the file should be there. Something may be missing from the flash procedure. Can you give more details on the flash, e.g., was it via JetPack, or via command line?

my monitor is show that

nvidia@tegra-ubuntu:$[54.400760] PD IDSPO index2 UP
[54.401927] PD DISP1 index3 UP
[54.402015] PD DISP2 index4 UP
[54.403761] Parent Clock set for DC plld2
[54.405236] tegradc 15210000/nvdisplay: hdmi :pclk:148500k ,set prod-setting:prod_c_150M

nvidia@tegra-ubuntu:$sha1sum -c /etc/nv_tegra_release
every term is OK

i do not understand what your mean? the monitor could display ubuntu UI before.

Thank you for your answer

So we know the drivers are definitely in place. The monitor is working in console mode, but this does not actually require all of the drivers required when in the GUI. Since those are in place, and since the monitor uses only HDMI cable with no adapters, there is an implication that lack of EDID is from a hardware failure (the i2c communications should at least report there is data or there is not data…the file itself should not be missing).

Can you try another HDMI monitor/cable and see if the edid file shows up?

sudo -s
find /sys -name 'edid'
cat `find /sys -name 'edid'`
exit

When drivers are in place and hardware works this file should exist even if the EDID is rejected. If not, perhaps try flashing.

i find the ‘edid’ file in system, it show a matrix of tow bit hex number ,i try another HDMI cable and monitor,but the cable is also without adapters , unfortunately,it return blue screen

With a monitor in place where the edid file exists, what is the output from:

sudo -s
cat `find /sys -name 'edid'`
exit

it show a matrix of number,the number is two bit hexadecimal ,just like this

00 ff ff ff ff ff ff 00 22 f0 1b 33 01 00 00 00
2e 1b 01 03 80 32 1e 78 2a 15 20 a7 56 52 9c 27
......

We’d need the full content. It can be pasted into http://www.edidreader.com to validate checksum and see what the monitor is reporting of itself.

00 ff ff ff ff ff ff 00 22 f0 1b 33 01 00 00 00
2e 1b 01 03 80 32 1e 78 2a 15 20 a7 56 52 9c 27
0f 50 54 a1 08 00 d1 c0 b3 00 a9 c0 95 00 81 80
81 00 81 c0 01 01 02 3a 80 18 71 38 2d 40 58 2c
45 00 dc 0c 11 00 00 1e 00 00 00 fd 00 32 3c 1e
50 11 00 0a 20 20 20 20 20 20 00 00 00 fc 00 48
50 20 32 32 65 73 0a 20 20 20 20 20 00 00 00 ff
00 33 43 4d 37 34 36 30 38 30 59 20 20 20 01 6f
02 03 19 b1 49 90 1f 04 13 03 12 01 02 11 67 03
0c 00 10 00 00 22 e2 00 2b 02 3a 80 18 71 38 2d
40 58 2c 45 00 dc 0c 11 00 00 1e 02 3a 80 d0 72
38 2d 40 10 2c 45 80 dc 0c 11 00 00 1e 01 1d 00
72 51 d0 1e 20 6e 28 55 00 dc 0c 11 00 00 1e 01
1d 00 bc 52 d0 1e 20 b8 28 55 40 dc 0c 11 00 00
1e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 dc 0c 11
00 00 18 00 00 00 00 00 00 00 00 00 00 00 00 e6

every thing is ok

It looks like the monitor should be fine with the Jetson. Next you’ll want to add this to “/etc/X11/xorg.conf” within the Section “Device”:

Option   "ModeDebug"

Then reboot and post the content of “/var/log/Xorg.0.log”. This will cause the driver to give a verbose message about every mode the monitor EDID has reported.

I copy this file from jetson ,it is too long ,which part of the file should I check to locate the issue?

You can copy the file to another computer with scp (or copy to SD card or USB thumb drive). Then you can attach it to a post which already exists…if you hover your mouse over the quote icon of one of your existing posts you will see a paper clip icon also show up…you can click on the icon and attach the file there (you will have to rename it as something with .txt, e.g., “Xorg.0.log.txt” or “log.txt”).

You can copy and paste more text if you click on the code icon first and paste it into that (the “</>” icon causes the text to be put in with scrollbars).

HI Every one … I have also got the Blue screen whin i start the jetson TX2… Last time i install Jetpack 3.3 but cuda wasnot install that time having some error … Later i install cuda through command line through cuda folder already saved in home directory… I just did this and shut down my Jetson… After 3 days now after powering on the device … I got blue screen… Only login view is showing … After login the screen completely turns blue… Is anyone know about this…

have any of u recover ur device from this error…?

If the code you installed was not intended for a Jetson it could have caused overwrite of something critical. If the folder in the home directory was meant for PC (and JetPack downloads both PC and Jetson components), then this could occur. Libraries already running in RAM would be ok, and failure would occur upon reboot. Or…it could be something completely unrelated, but I suspect a PC OpenGL lib was overwritten on top of the arm64 lib (and PC is incompatible).

Either way, do you have a serial console? This is by far the best way to see what is going on (for example, serial console does not require video to work…we could see if the system is actually running, but with failed video versus the entire system failing). See:
http://www.jetsonhacks.com/2017/03/24/serial-console-nvidia-jetson-tx2/

If you hit CTRL-ALT-F2, then it might drop into a text-only console if it is only video which is failing. If this is the case, then run this command (or from serial console) to see if any of the GUI libs were broken:

sha1sum -c /etc/nv_tegra_release

If you want to clone your rootfs partition (which can be loopback mounted from a PC host and examined or edited…or even used as a substitute to the sample rootfs), then see this:
https://devtalk.nvidia.com/default/topic/1000105/jetson-tx2/tx2-cloning/

Thanks linuxdev…Actually my jet son was working fine after installation. i also restart it…but i will check this… and soon post the result…of command u have told