JTX1 Boots, but no GUI appears

My TX1 was working fine, but when I restarted it, no GUI appeared. The boot output showed up and and the monitor recognized an input, and the screen was a bit lighter, but no GUI. If I press alt + ctrl + F1, I can get the terminal, but I have to unplug the HDMI cord for a second for that to work. I am able to SSH on and have tried using different cables, different monitors, nothing works. The other odd thing is that when I go into the console, it won’t turn on my USB hub and says that it might be broken. Not sure why this is happening, as it is only a few weeks old.

Sometimes USB gets “flakey” (that’s a technical term!) when power consumption goes up on on-powered HUBs or external devices which draw power from the host. If you have a powered HUB you can substitute I’d try that. It is possible that something in USB is causing an issue without actually being “broken”. Even if the cause of issues is something else, you pretty much have to solve that to know for sure if other issues are related or not.

One test you can do is look at the X log, “/var/log/Xorg.0.log” via ssh. I wouldn’t go to console mode, I’d just let it fail, then log in remotely, and get that log. You may also see something in dmesg, though it isn’t predictable if it will be right at the end of the log or somewhere in the middle (something like “less” might be needed to figure out where X info is).

The USB seems to be working now, I’m not really sure what was going on there but I don’t think it was related. I got the xorg server log, though I’m not quite sure how to go about debugging this.

[140489.065] 
X.Org X Server 1.18.3
Release Date: 2016-04-04
[140489.065] X Protocol Version 11, Revision 0
[140489.065] Build Operating System: Linux 3.13.0-85-generic aarch64 Ubuntu
[140489.065] Current Operating System: Linux tegra-ubuntu 3.10.96-tegra #1 SMP PREEMPT Thu Sep 8 13:48:54 PDT 2016 aarch64
[140489.065] Kernel command line: fbcon=map:0 console=tty0 console=ttyS0,115200n8 androidboot.modem=none androidboot.serialno=P2180A00P00940c003fd androidboot.security=non-secure tegraid=21.1.2.0.0 ddr_die=2048M@2048M ddr_die=2048M@4096M section=256M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 debug_uartport=lsport,0 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff2bf000 nvdumper_reserved=0xff23f000 core_edp_mv=1125 core_edp_ma=4000 gpt android.kerneltype=normal androidboot.touch_vendor_id=0 androidboot.touch_panel_id=63 androidboot.touch_feature=0 androidboot.bootreason=pmc:software_reset,pmic:0x0 net.ifnames=0 root=/dev/sda1 rw rootwait
[140489.065] Build Date: 18 May 2016  01:12:13AM
[140489.065] xorg-server 2:1.18.3-1ubuntu2.2 (For technical support please see http://www.ubuntu.com/support) 
[140489.066] Current version of pixman: 0.33.6
[140489.066] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[140489.066] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[140489.066] (==) Log file: "/var/log/Xorg.1.log", Time: Thu Sep 22 12:03:53 2016
[140489.067] (==) Using config file: "/etc/X11/xorg.conf"
[140489.067] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[140489.069] (==) No Layout section.  Using the first Screen section.
[140489.070] (==) No screen section available. Using defaults.
[140489.070] (**) |-->Screen "Default Screen Section" (0)
[140489.070] (**) |   |-->Monitor "<default monitor>"
[140489.070] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[140489.070] (**) |   |-->Device "Tegra0"
[140489.070] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[140489.070] (==) Automatically adding devices
[140489.070] (==) Automatically enabling devices
[140489.070] (==) Automatically adding GPU devices
[140489.071] (==) Max clients allowed: 256, resource mask: 0x1fffff
[140489.071] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[140489.071] 	Entry deleted from font path.
[140489.071] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[140489.071] 	Entry deleted from font path.
[140489.071] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[140489.071] 	Entry deleted from font path.
[140489.071] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[140489.071] 	Entry deleted from font path.
[140489.071] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[140489.071] 	Entry deleted from font path.
[140489.071] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/Type1,
	built-ins
[140489.071] (==) ModulePath set to "/usr/lib/aarch64-linux-gnu/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[140489.071] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[140489.071] (II) Loader magic: 0x5562cc9d68
[140489.071] (II) Module ABI versions:
[140489.071] 	X.Org ANSI C Emulation: 0.4
[140489.071] 	X.Org Video Driver: 20.0
[140489.071] 	X.Org XInput driver : 22.1
[140489.072] 	X.Org Server Extension : 9.0
[140489.074] (++) using VT number 8

[140489.074] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[140489.075] (II) no primary bus or device found
[140489.075] (WW) "dri" will not be loaded unless you've specified it to be loaded elsewhere.
[140489.075] (II) "glx" will be loaded by default.
[140489.075] (II) LoadModule: "extmod"
[140489.075] (II) Module "extmod" already built-in
[140489.076] (II) LoadModule: "glx"
[140489.078] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[140489.103] (II) Module glx: vendor="NVIDIA Corporation"
[140489.103] 	compiled for 4.0.2, module version = 1.0.0
[140489.103] 	Module class: X.Org Server Extension
[140489.103] (II) NVIDIA GLX Module  24.2.0  Release Build  (integ_stage_rel)  (buildbrain@mobile-u64-1076)  Thu Sep  8 13:51:20 PDT 2016
[140489.103] (II) LoadModule: "nvidia"
[140489.104] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[140489.108] (II) Module nvidia: vendor="NVIDIA Corporation"
[140489.108] 	compiled for 4.0.2, module version = 1.0.0
[140489.108] 	Module class: X.Org Video Driver
[140489.108] (II) NVIDIA dlloader X Driver  24.2.0  Release Build  (integ_stage_rel)  (buildbrain@mobile-u64-1076)  Thu Sep  8 13:52:54 PDT 2016
[140489.108] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[140489.970] (WW) Falling back to old probe method for NVIDIA
[140489.970] (II) Loading sub module "fb"
[140489.970] (II) LoadModule: "fb"
[140489.972] (II) Loading /usr/lib/xorg/modules/libfb.so
[140489.984] (II) Module fb: vendor="X.Org Foundation"
[140489.984] 	compiled for 1.18.3, module version = 1.0.0
[140489.984] 	ABI class: X.Org ANSI C Emulation, version 0.4
[140489.984] (II) Loading sub module "wfb"
[140489.984] (II) LoadModule: "wfb"
[140489.985] (II) Loading /usr/lib/xorg/modules/libwfb.so
[140489.985] (II) Module wfb: vendor="X.Org Foundation"
[140489.985] 	compiled for 1.18.3, module version = 1.0.0
[140489.985] 	ABI class: X.Org ANSI C Emulation, version 0.4
[140489.986] (II) Loading sub module "ramdac"
[140489.986] (II) LoadModule: "ramdac"
[140489.986] (II) Module "ramdac" already built-in
[140489.987] (II) NVIDIA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[140489.987] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[140489.987] (==) NVIDIA(0): RGB weight 888
[140489.987] (==) NVIDIA(0): Default visual is TrueColor
[140489.987] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[140489.988] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration" "true"
[140489.988] (**) NVIDIA(0): Enabling 2D acceleration
[140489.993] (--) NVIDIA(0): Valid display device(s) on GPU-0 at SoC
[140489.993] (--) NVIDIA(0):     DFP-0
[140489.993] (--) NVIDIA(0): VIZ E32-C1 (DFP-0): connected
[140489.993] (--) NVIDIA(0): VIZ E32-C1 (DFP-0): External TMDS
[140489.993] (II) NVIDIA(GPU-0): Found DRM driver drm-nvdc (0)
[140489.993] (WW) NVIDIA(GPU-0): Unexpected DRM driver drm-nvdc found: ignoring
[140490.001] (II) NVIDIA(0): NVIDIA GPU NVIDIA Tegra X1 (nvgpu) (NVIDIA Tegra X1) at SoC
[140490.001] (II) NVIDIA(0):     (GPU-0)
[140490.001] (--) NVIDIA(0): Memory: 4090068 kBytes
[140490.001] (--) NVIDIA(0): VideoBIOS: 
[140490.001] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[140490.001] (**) NVIDIA(0):     device VIZ E32-C1 (DFP-0) (Using EDID frequencies has been
[140490.001] (**) NVIDIA(0):     enabled on all display devices.)
[140490.001] (==) NVIDIA(0): 
[140490.001] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[140490.001] (==) NVIDIA(0):     will be used as the requested mode.
[140490.002] (==) NVIDIA(0): 
[140490.002] (II) NVIDIA(0): Validated MetaModes:
[140490.002] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select"
[140490.002] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[140490.005] (--) NVIDIA(0): DPI set to (69, 70); computed from "UseEdidDpi" X config
[140490.005] (--) NVIDIA(0):     option
[140490.005] (--) Depth 24 pixmap format is 32 bpp
[140490.006] (II) NVIDIA: Reserving 3072.00 MB of virtual memory for indirect memory
[140490.006] (II) NVIDIA:     access.
[140490.006] (WW) NVIDIA(GPU-0): Failed to enter interactive mode. 
[140490.020] (EE) NVIDIA(0): Failed to allocate NVIDIA Error Handler
[140490.020] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[140490.020] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[140490.020] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[140490.020] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[140490.020] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[140490.020] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[140490.020] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[140490.021] (II) NVIDIA(0):     Config Options in the README.
[140490.088] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[140490.501] (==) NVIDIA(0): Disabling shared memory pixmaps
[140490.501] (==) NVIDIA(0): Backing store enabled
[140490.501] (==) NVIDIA(0): Silken mouse enabled
[140490.509] (==) NVIDIA(0): DPMS enabled
[140490.515] (EE) NVIDIA(0): Failed to allocate NVIDIA Damage Manager
[140490.515] (II) Loading sub module "dri2"
[140490.515] (II) LoadModule: "dri2"
[140490.515] (II) Module "dri2" already built-in
[140490.515] (II) NVIDIA(0): [DRI2] Setup complete
[140490.515] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[140490.516] (--) RandR disabled
[140490.525] (II) SELinux: Disabled on system
[140490.526] (II) Initializing extension GLX
[140490.526] (II) Indirect GLX disabled.
[140490.607] (II) config/udev: Adding input device gpio-keys (/dev/input/event4)
[140490.608] (**) gpio-keys: Applying InputClass "evdev keyboard catchall"
[140490.608] (II) LoadModule: "evdev"
[140490.608] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[140490.609] (II) Module evdev: vendor="X.Org Foundation"
[140490.609] 	compiled for 1.18.1, module version = 2.10.1
[140490.609] 	Module class: X.Org XInput Driver
[140490.609] 	ABI class: X.Org XInput driver, version 22.1
[140490.609] (II) Using input driver 'evdev' for 'gpio-keys'
[140490.609] (**) gpio-keys: always reports core events
[140490.609] (**) evdev: gpio-keys: Device: "/dev/input/event4"
[140490.609] (--) evdev: gpio-keys: Vendor 0x1 Product 0x1
[140490.609] (--) evdev: gpio-keys: Found keys
[140490.609] (II) evdev: gpio-keys: Configuring as keyboard
[140490.609] (**) Option "config_info" "udev:/sys/devices/platform/gpio-keys.47/input/input4/event4"
[140490.609] (II) XINPUT: Adding extended input device "gpio-keys" (type: KEYBOARD, id 6)
[140490.609] (**) Option "xkb_rules" "evdev"
[140490.609] (**) Option "xkb_model" "pc105"
[140490.609] (**) Option "xkb_layout" "us"
[140490.611] (II) config/udev: Adding input device tegra-snd-t210ref-mobile-rt565x Headphone Jack (/dev/input/event3)
[140490.611] (**) tegra-snd-t210ref-mobile-rt565x Headphone Jack: Applying InputClass "evdev keyboard catchall"
[140490.611] (II) Using input driver 'evdev' for 'tegra-snd-t210ref-mobile-rt565x Headphone Jack'
[140490.611] (**) tegra-snd-t210ref-mobile-rt565x Headphone Jack: always reports core events
[140490.611] (**) evdev: tegra-snd-t210ref-mobile-rt565x Headphone Jack: Device: "/dev/input/event3"
[140490.611] (--) evdev: tegra-snd-t210ref-mobile-rt565x Headphone Jack: Vendor 0 Product 0
[140490.611] (--) evdev: tegra-snd-t210ref-mobile-rt565x Headphone Jack: Found keys
[140490.611] (II) evdev: tegra-snd-t210ref-mobile-rt565x Headphone Jack: Configuring as keyboard
[140490.611] (**) Option "config_info" "udev:/sys/devices/platform/sound.27/sound/card1/input3/event3"
[140490.611] (II) XINPUT: Adding extended input device "tegra-snd-t210ref-mobile-rt565x Headphone Jack" (type: KEYBOARD, id 7)
[140490.611] (**) Option "xkb_rules" "evdev"
[140490.611] (**) Option "xkb_model" "pc105"
[140490.611] (**) Option "xkb_layout" "us"
[140490.613] (II) config/udev: Adding input device CM Storm QuickFire Rapid keyboard (/dev/input/event0)
[140490.613] (**) CM Storm QuickFire Rapid keyboard: Applying InputClass "evdev keyboard catchall"
[140490.613] (II) Using input driver 'evdev' for 'CM Storm QuickFire Rapid keyboard'
[140490.613] (**) CM Storm QuickFire Rapid keyboard: always reports core events
[140490.613] (**) evdev: CM Storm QuickFire Rapid keyboard: Device: "/dev/input/event0"
[140490.613] (--) evdev: CM Storm QuickFire Rapid keyboard: Vendor 0x2516 Product 0x4
[140490.613] (--) evdev: CM Storm QuickFire Rapid keyboard: Found keys
[140490.613] (II) evdev: CM Storm QuickFire Rapid keyboard: Configuring as keyboard
[140490.613] (**) Option "config_info" "udev:/sys/devices/platform/tegra-xhci/usb1/1-3/1-3.3/1-3.3:1.0/input/input0/event0"
[140490.613] (II) XINPUT: Adding extended input device "CM Storm QuickFire Rapid keyboard" (type: KEYBOARD, id 8)
[140490.613] (**) Option "xkb_rules" "evdev"
[140490.613] (**) Option "xkb_model" "pc105"
[140490.613] (**) Option "xkb_layout" "us"
[140490.614] (II) config/udev: Adding input device CM Storm QuickFire Rapid keyboard (/dev/input/event1)
[140490.614] (**) CM Storm QuickFire Rapid keyboard: Applying InputClass "evdev keyboard catchall"
[140490.614] (II) Using input driver 'evdev' for 'CM Storm QuickFire Rapid keyboard'
[140490.614] (**) CM Storm QuickFire Rapid keyboard: always reports core events
[140490.615] (**) evdev: CM Storm QuickFire Rapid keyboard: Device: "/dev/input/event1"
[140490.615] (--) evdev: CM Storm QuickFire Rapid keyboard: Vendor 0x2516 Product 0x4
[140490.615] (--) evdev: CM Storm QuickFire Rapid keyboard: Found keys
[140490.615] (II) evdev: CM Storm QuickFire Rapid keyboard: Configuring as keyboard
[140490.615] (**) Option "config_info" "udev:/sys/devices/platform/tegra-xhci/usb1/1-3/1-3.3/1-3.3:1.1/input/input1/event1"
[140490.615] (II) XINPUT: Adding extended input device "CM Storm QuickFire Rapid keyboard" (type: KEYBOARD, id 9)
[140490.615] (**) Option "xkb_rules" "evdev"
[140490.615] (**) Option "xkb_model" "pc105"
[140490.615] (**) Option "xkb_layout" "us"
[140490.616] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event2)
[140490.616] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
[140490.616] (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
[140490.616] (**) Logitech USB Optical Mouse: always reports core events
[140490.616] (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event2"
[140490.616] (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc05a
[140490.616] (--) evdev: Logitech USB Optical Mouse: Found 3 mouse buttons
[140490.616] (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
[140490.616] (--) evdev: Logitech USB Optical Mouse: Found relative axes
[140490.616] (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
[140490.616] (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
[140490.616] (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
[140490.617] (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
[140490.617] (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[140490.617] (**) Option "config_info" "udev:/sys/devices/platform/tegra-xhci/usb1/1-3/1-3.4/1-3.4:1.0/input/input2/event2"
[140490.617] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 10)
[140490.617] (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
[140490.617] (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
[140490.617] (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
[140490.617] (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
[140490.617] (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
[140491.885] (--) NVIDIA(GPU-0): VIZ E32-C1 (DFP-0): connected
[140491.886] (--) NVIDIA(GPU-0): VIZ E32-C1 (DFP-0): External TMDS
[140492.012] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[140492.640] (--) NVIDIA(GPU-0): VIZ E32-C1 (DFP-0): connected
[140492.640] (--) NVIDIA(GPU-0): VIZ E32-C1 (DFP-0): External TMDS
[140499.403] (II) evdev: Logitech USB Optical Mouse: Close
[140499.403] (II) UnloadModule: "evdev"
[140499.403] (II) evdev: CM Storm QuickFire Rapid keyboard: Close
[140499.403] (II) UnloadModule: "evdev"
[140499.403] (II) evdev: CM Storm QuickFire Rapid keyboard: Close
[140499.403] (II) UnloadModule: "evdev"
[140499.403] (II) evdev: tegra-snd-t210ref-mobile-rt565x Headphone Jack: Close
[140499.403] (II) UnloadModule: "evdev"
[140499.403] (II) evdev: gpio-keys: Close
[140499.403] (II) UnloadModule: "evdev"
[140499.812] (II) NVIDIA(GPU-0): Deleting GPU-0
[140499.814] (II) Server terminated successfully (0). Closing log file.

I don’t see any explicit error there, it looks like a lack of config data. You said you use HDMI, and that it worked before, so it sounds like the cabling is correct. You may want to install packages “read-edid” and “edid-decode”. This should let you query what the monitor says about itself via remote ssh login or serial console:

sudo get-edid | parse-edid
sudo get-edid | edid-decode

This should let you find out if the monitor is still responding properly to query. Have there been any software updates? Sometimes updates change defaults, and if video was working through default instead of through EDID, then the new default could fail.

Ok so I ran those commands, and here are the outputs:

sudo get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
1 potential busses found: 2
Bus 2 doesn't really have an EDID...
Couldn't find an accessible EDID on this computer.
I'm sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern <pyrophobicman@gmail.com>.
Partial Read... Try again
sudo get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
1 potential busses found: 2
Bus 2 doesn't really have an EDID...
Couldn't find an accessible EDID on this computer.
I'm sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern <pyrophobicman@gmail.com>.
Partial Read... Try again
ubuntu@tegra-ubuntu:~$ sudo get-edid | edid-decode
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
1 potential busses found: 2
Bus 2 doesn't really have an EDID...
Couldn't find an accessible EDID on this computer.
I'm sorry nothing was successful. Maybe try some other arguments
if you played with them, or send an email to Matthew Kern <pyrophobicman@gmail.com>.
Extracted contents:
header:          00 00 00 00 00 00 00 00
serial number:   00 00 00 00 00 00 00 00 00 00
version:         00 00
basic params:    00 00 00 00 00
chroma info:     00 00 00 00 00 00 00 00 00 00
established:     00 00 00
standard:        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 1:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 2:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 3:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
descriptor 4:    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
extensions:      00
checksum:        00

No header found
Manufacturer: @@@ Model 0 Serial Number 0
EDID version: 0.0
Analog display, Input voltage level: 0.7/0.3 V
Sync: 
Image size is variable
Gamma: 1.00
Monochrome or grayscale display
Established timings supported:
Standard timings supported:
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
non-conformant standard timing (0 horiz)
Manufacturer-specified data, tag 0
Manufacturer-specified data, tag 0
Manufacturer-specified data, tag 0
Manufacturer-specified data, tag 0
Checksum: 0x0 (valid)
EDID block does not conform at all!
	Bad year of manufacture
	Manufacturer name field contains garbage

It seems like there is an error, but I don’t know what it mean.

Describe your video cables and type of monitor connector. No EDID could mean a missing EDID response from an older cable type, or it could mean malformed EDID response.

I’m just using straight HDMI into the monitor. Not quite sure as to the specs of them, but I’ve tried multiple monitors and HDMI cables that all support high quality video and are less than a year old. I’m not sure if this is relevant but it stopped working after the power cut out and turned off the TX1 (I am aware that this is terrible, I didn’t have much control) during and installation of ROS from source.

HDMI is good with EDID. The old 15-pin D-Sub is the one that doesn’t work. So your cables should be fine.

Basically there are many devices which can respond to the i2c protocol, the monitor is one, but it has a defined response. The query software got a response, but it was all NULL…either it wasn’t the monitor, or the values were all erased. Regardless of why it can’t read the EDID, it does explain why the monitor no longer gets set up correctly. Having this happen with multiple monitors tends to validate that the issue is at the Jetson side…most likely just software, although a power spike could do damage to hardware.

I’d suggest you reflash the Jetson. In the case of software this should resolve the issue. You could clone the root partition first if you want to preserve data. See:
http://elinux.org/Jetson/Cloning

Awesome, I really appreciate the help. This is all off a SSD, so when I tried to mount it on the host, it doesn’t show up. It does show up on my TX1 when I boot off the flash, so I guess I should just erase the drive. What would be the best practice for this, as I’m not trying to brick the drive.

A failed drive could do a lot of things, and may be related to the EDID read failure, but not necessarily (you could still have a different problem even if the SSD is bad). The EDID is read by software based on a response from the monitor…both software and hardware issues can break this.

Does the Jetson boot without the SSD (and how does video change with or without SSD)? Does the Jetson boot with the SSD as an alternate boot source (ignore this question if you are not using the SSD as a root partition)? On your host, does the SSD show with “lsblk”?

I can boot with everything working off the flash storage. When I do that, the SSD does show up through lsblk. When I tried on my host, however, nothing showed up (this could be due to a bad SATA to USB cord though).

Does the monitor work now without the SSD, or is that still an issue? If removing a bad SSD fixed things it becomes one of those interesting curiosities.