Here’s a digest of information on the above…
It looks like EDID query works. parse-edid is as expected, so it should be possible for X11 to automatically configure graphics within its limitations. However, output of “get-edid | edid-decode” was truncated, I’m guessing either because it wasn’t run sudo or a copy and paste error…it is unlikely that edid-decode would fail when parse-edid would succeed. So I believe cabling and EDID response are not at issue, these can probably be ruled out as a problem.
Driver files are installed correctly with the proper Xorg ABI. This is not something a flash would change. This makes it odd to see the failure to initialize GLX message. The cause can’t be from the presence of incorrect files or symbolic links reverting to a mesa/nouveau version. It is possible that file permissions are a problem and that the X server was unable to read libglx.so because of this (or some other arcane issue). What is the output of this:
ls -l /usr/lib/xorg/modules/extensions/libglx.so
ls -l /usr/lib/arm-linux-gnueabihf/tegra/libglx.so
…it is more likely that a failure to load GLX is related to not having a monitor configured (GLX failure is quite probably not a cause but a side effect of the failed screen setup…which would mean the GLX failure is not really a clue, it’s just one of the domino effects of the real failure).
When EDID is used some (or all) of the xorg.conf may be filled in or edited automatically, and so the file itself is not necessarily a complete story of what X11 is using for configuration. However, it could be useful to manually fill in some missig parts of xorg.conf based on the EDID query just to make sure this is being used. Before doing any xorg.conf edits you may want to save a backup of this to revert to. Also, I am assuming only the one monitor is attached, having two monitors at once can drastically complicate things and invalidate debugging efforts. In xorg.conf, look at the appropriate section, and edit to become this:
Section "Monitor"
Identifier "DFP-0"
# ModelName ""
VendorName "ADA"
# Monitor Manufactured week 1 of 2007
# EDID version 1.3
# Digital Display
DisplaySize 150 100
Gamma 1.00
# Option "DPI" "168 x 168"
Option "DPMS" "false"
Modeline "Mode 0" 32.00 1024 1064 1112 1152 600 613 616 645 -hsync -vsync
EndSection
Currently DPI is commented out, this may work fine, but you may also want to try with these variants one at a time (the monitor’s URL does not give DPI…if there is another URL with complete specs for the monitor it would help):
Option "DPI" "168 x 168"
Option "DPI" "96 x 96"
With those variations reboot and see what happens, keep a copy of the Xorg.0.log each time (it rotates to Xorg.0.log.old for the previous boot, be sure to keep the correct log with the correct current boot…reboot to a new setting, see if X11 logs in, save a copy of the log, and if needed, make new edits, then repeat).
FYI, it looks like display mode was picked based on this log line:
Setting mode "DFP-0:nvidia-auto-select"
This means the EDID mode was not used. One reason this might occur is if the valid EDID mode is not supported in the driver, then the driver would revert to a different mode (one which this monitor does not support). Edits beyond just a config may be needed in this case (something in kernel may need edit).