TK1 Pro HDMI does not work

Hello. I don’t know if it’s possible to get any support for the pro kit. My problem is when the board is plugged into a monitor via HDMI nothing is displayed. I can ssh and remote connect over vnc. If possible is there a way I could re-flash the board as there are other errors.

I have only experience with L4T, so I cannot say for vibrante or any other system…
With L4T, such symptoms have been seen in different targets/kernel versions.
Especially if you’re using a VGA/HDMI adapter… HDMI/DVI adapter should allow to get EDID from monitor.

One thing to try out is hotplug. You may unplug for 20s and replug, or boot unplugged and plug HDMI in only after one minute.

If you’re running a linux OS, you may search this forum for ‘edid’ and ‘xrand’…

I am curious, does anything show up if you run:

sudo find /sys -name 'edid*'

If something does show up, what is the content of the edid file? E.g., "sudo cat ".

Thanks for the reply, hotpluging did not work. There isn’t and edid command but there is xrand.

Results of that command: /sys/kernel/debug/edid3
With contents of:

edid[000] = 00 ff ff ff ff ff ff 00 4c 2d fc 08 00 00 00 00
edid[010] = 29 15 01 03 80 10 09 78 0a ee 91 a3 54 4c 99 26
edid[020] = 0f 50 54 bd ee 00 81 c0 01 01 01 01 01 01 01 01
edid[030] = 01 01 01 01 01 01 66 21 56 aa 51 00 1e 30 46 8f
edid[040] = 33 00 a0 5a 00 00 00 1e 01 1d 00 72 51 d0 1e 20
edid[050] = 6e 28 55 00 a0 5a 00 00 00 1e 00 00 00 fd 00 18
edid[060] = 4b 0f 44 17 00 0a 20 20 20 20 20 20 00 00 00 fc
edid[070] = 00 53 41 4d 53 55 4e 47 0a 20 20 20 20 20 01 6d
edid[080] = 02 03 1f f1 47 84 05 03 10 20 22 07 23 09 07 07
edid[090] = 83 01 00 00 e2 00 0f 67 03 0c 00 20 00 b8 2d 01
edid[0a0] = 1d 80 18 71 1c 16 20 58 2c 25 00 a0 5a 00 00 00
edid[0b0] = 9e 8c 0a d0 8a 20 e0 2d 10 10 3e 96 00 a0 5a 00
edid[0c0] = 00 00 18 02 3a 80 18 71 38 2d 40 58 2c 45 00 a0
edid[0d0] = 5a 00 00 00 1e 00 00 00 00 00 00 00 00 00 00 00
edid[0e0] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
edid[0f0] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ed

From http://www.edidreader.com/ this EDID seems to be compliant with EDID v1.3.

But it looks it only supports low resolutions. Maybe the video driver fails to find a suitable timing.
Could you try another monitor ?

I assume even the TK1 Pro has “/etc/X11/xorg.conf”. If so, can you add this to section “device”:

Option "ModeDebug"

From there restart the Jetson with the monitor already plugged in, and then post the content of “/var/log/Xorg.0.log”. This might explain more about modes being accepted/rejected since EDID is valid (valid EDID implies the monitor is attached and correctly reporting its capabilities…ModeDebug will show us what the driver thinks of each video mode).

I would also guess the same as @Honey_Patouceul…things look like they are in place and there is probably just something the driver doesn’t like about this particular monitor’s modes. Even if you don’t use another monitor it would be useful debug information to see that some monitor works. Typically the ordinary desktop monitors (HDMI) with modern display resolutions (not the exotic ultra high def, not older 4:3 aspect) are most compliant.

Furthermore, it’s a bit surprizing to me that you get edid numbered 3 in debugfs… Do you have other display devices connected ? Or does this happened after hotplugging HDMI a few times ?

I saw that too, but am guessing it is a difference in the supporting carrier of the “Pro” model. My thought is that so long as EDID is valid, then the hardware is valid. Unless xorg.conf has something odd in it, then it probably will detect and use what is there…we’ll know once we get Xorg.0.log.

Here is the Xorg.0.log:

[    21.485] 
X.Org X Server 1.11.3
Release Date: 2011-12-16
[    21.485] X Protocol Version 11, Revision 0
[    21.485] Build Operating System: Linux 2.6.42-68-highbank armv7l Ubuntu
[    21.485] Current Operating System: Linux nvidia 3.1.10 #1 SMP PREEMPT Thu Jul 4 00:05:03 PDT 2013 armv7l
[    21.485] Kernel command line: tegraid=30.1.3.0.0 mem=2047M@2048M video=tegrafb debug_uartport=lsport,0 usbcore.old_scheme_first=1 lp0_vec=8192@0x84008140 core_edp_mv=1250 smsc95xx.mac_addr=0x00,0x00,0x00,0x00,0x00,0x00 nvsku=699-61853-0008-200 SkuVer=AB ProdInfo=000-00000-0000-000 ProdVer=  no_console_suspend=1  root=/dev/sda1 rw rootwait usbcore.old_scheme_first=1 mtdparts=tegra-nor:256K@21248K(env),11264K@21504K(userspace)   console=ttyS0,115200n8   board_id=699-61860-0000-201-D.07 

[    21.486] Build Date: 12 February 2015  02:54:30PM
[    21.486] xorg-server 2:1.11.4-0ubuntu10.17 (For technical support please see http://www.ubuntu.com/support) 
[    21.486] Current version of pixman: 0.30.2
[    21.486] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    21.486] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    21.487] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul  9 08:34:01 2013
[    21.489] (==) Using config file: "/etc/X11/xorg.conf"
[    21.489] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    21.489] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    21.495] (==) No Layout section.  Using the first Screen section.
[    21.495] (==) No screen section available. Using defaults.
[    21.495] (**) |-->Screen "Default Screen Section" (0)
[    21.495] (**) |   |-->Monitor "<default monitor>"
[    21.497] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[    21.497] (**) |   |-->Device "Tegra"
[    21.497] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    21.498] (**) Option "BlankTime" "0"
[    21.498] (**) Option "StandbyTime" "0"
[    21.498] (**) Option "SuspendTime" "0"
[    21.498] (**) Option "OffTime" "0"
[    21.498] (==) Automatically adding devices
[    21.498] (==) Automatically enabling devices
[    21.500] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    21.500] 	Entry deleted from font path.
[    21.500] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[    21.500] 	Entry deleted from font path.
[    21.500] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    21.500] 	Entry deleted from font path.
[    21.500] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[    21.500] 	Entry deleted from font path.
[    21.500] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    21.500] 	Entry deleted from font path.
[    21.501] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    21.501] 	Entry deleted from font path.
[    21.501] (WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not exist.
[    21.501] 	Entry deleted from font path.
[    21.501] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	built-ins
[    21.501] (==) ModulePath set to "/usr/lib/arm-linux-gnueabihf/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[    21.501] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    21.501] (II) Loader magic: 0x4020bd00
[    21.501] (II) Module ABI versions:
[    21.501] 	X.Org ANSI C Emulation: 0.4
[    21.501] 	X.Org Video Driver: 11.0
[    21.501] 	X.Org XInput driver : 16.0
[    21.501] 	X.Org Server Extension : 6.0
[    21.503] (--) PCI:*(0:1:0:0) 10de:12ba:10de:1025 rev 161, Mem @ 0x10000000/16777216, 0x20000000/268435456, 0x30000000/33554432, I/O @ 0x10000000/128, BIOS @ 0x????????/524288
[    21.503] (WW) "dri" will not be loaded unless you've specified it to be loaded elsewhere.
[    21.503] (WW) "dri2" will not be loaded unless you've specified it to be loaded elsewhere.
[    21.503] (WW) "glx" will not be loaded unless you've specified it to be loaded elsewhere.
[    21.503] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
[    21.503] (II) "dbe" will be loaded by default.
[    21.503] (II) "glx" will be loaded even though the default is to disable it.
[    21.503] (II) "record" will be loaded by default.
[    21.503] (II) "dri" will be loaded even though the default is to disable it.
[    21.503] (II) "dri2" will be loaded even though the default is to disable it.
[    21.503] (II) LoadModule: "extmod"
[    21.541] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[    21.544] (II) Module extmod: vendor="X.Org Foundation"
[    21.544] 	compiled for 1.11.3, module version = 1.0.0
[    21.544] 	Module class: X.Org Server Extension
[    21.544] 	ABI class: X.Org Server Extension, version 6.0
[    21.544] (II) Loading extension MIT-SCREEN-SAVER
[    21.544] (II) Loading extension XFree86-VidModeExtension
[    21.544] (II) Loading extension DPMS
[    21.545] (II) Loading extension XVideo
[    21.545] (II) Loading extension XVideo-MotionCompensation
[    21.545] (II) Loading extension X-Resource
[    21.545] (II) LoadModule: "dbe"
[    21.546] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[    21.547] (II) Module dbe: vendor="X.Org Foundation"
[    21.547] 	compiled for 1.11.3, module version = 1.0.0
[    21.547] 	Module class: X.Org Server Extension
[    21.547] 	ABI class: X.Org Server Extension, version 6.0
[    21.547] (II) Loading extension DOUBLE-BUFFER
[    21.548] (II) LoadModule: "record"
[    21.549] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[    21.550] (II) Module record: vendor="X.Org Foundation"
[    21.550] 	compiled for 1.11.3, module version = 1.13.0
[    21.550] 	Module class: X.Org Server Extension
[    21.550] 	ABI class: X.Org Server Extension, version 6.0
[    21.550] (II) Loading extension RECORD
[    21.550] (II) LoadModule: "tegra"
[    21.557] (II) Loading /usr/lib/xorg/modules/drivers/tegra_drv.so
[    21.588] (II) Module tegra: vendor="X.Org Foundation"
[    21.588] 	compiled for 1.11.0, module version = 0.4.0
[    21.588] 	Module class: X.Org Video Driver
[    21.588] 	ABI class: X.Org Video Driver, version 11.0
[    21.588] (II) NVIDIA driver for Tegra
[    21.588] (++) using VT number 7

[    21.592] (WW) Falling back to old probe method for tegra
[    21.593] (II) Loading /usr/lib/xorg/modules/drivers/tegra_drv.so
[    21.593] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    21.595] (II) TEGRA(0): GPU is a T30
[    21.595] (II) TEGRA(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    21.595] (==) TEGRA(0): Depth 24, (--) framebuffer bpp 32
[    21.595] (==) TEGRA(0): RGB weight 888
[    21.595] (==) TEGRA(0): Default visual is TrueColor
[    21.595] (==) TEGRA(0): Using gamma correction (1.0, 1.0, 1.0)
[    21.596] (**) TEGRA(0): Option "VsyncOnlyPrimary"
[    21.613] (II) TEGRA(0): Failed to initialize the display controller library
[    21.613] (EE) TEGRA(0): Error initializing the display controller.
[    21.614] (II) UnloadModule: "tegra"
[    21.614] (II) Unloading tegra
[    21.614] (EE) Screen(s) found, but none have a usable configuration.
[    21.614] 
Fatal server error:
[    21.614] no screens found
[    21.614] 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[    21.614] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    21.614] 
[    21.615]  ddxSigGiveUp: Closing log
[    21.616] Server terminated with error (1). Closing log file.

Could a possible reason for edid being the third one is the pro board has a discrete quadro k510?

Apparently something related to what @Honey_Patouceul had mentioned has turned out to be part of the problem…you have a monitor since you have EDID, but Xorg is not configured to use it (see the earlier comment on EDID 3…usually it is EDID 1). The “Device” section describes the video driver/GPU, a “Screen” is a virtual identifier for what to render to, and a “Monitor” is bound to a Screen. It says no usable screen was found (somewhere something needs to identify the Monitor as bound to the screen…some of this should be automatic).

Since I don’t know the TK1 Pro, do you have “/etc/nv_tegra_release”? If so, see if all is ok from “sha1sum -c /etc/nv_tegra_release”. This would verify hardware drivers are in place.

Next, post the content of “/etc/X11/xorg.conf”, and also the content of “dmesg | egrep -i hdmi”.

Can anyone here verify what video ports are available on a TK1 Pro, and what the default xorg.conf points at?

# Copyright (c) 2011-2013 NVIDIA CORPORATION.  All Rights Reserved.

#
# This is the minimal configuration necessary to use the Tegra driver.
# Please refer to the xorg.conf man page for more configuration
# options provided by the X server, including display-related options
# provided by RandR 1.2 and higher.

# Disable extensions not useful on Tegra.
Section "Module"
    Disable     "dri"
    Disable     "dri2"
    Disable     "glx"
    SubSection  "extmod"
        Option  "omit xfree86-dga"
    EndSubSection
EndSection

Section "Device"
    Identifier  "Tegra"
    Driver      "tegra"
    Option	"ModeDebug"

# OverlayDepth is a 32-bit integer which is used to control overlay
# stacking order.  The overlay with the lowest depth is in front of
# all others.  This value has meaning only when multiple overlays are
# present on a display. This value can range between 0 & 255 (both values
# inclusive). The default being 255.

#    Option      "OverlayDepth" "0"

# OverlayCombineMode determines how the X overlay is combined with the
# overlay behind it during scanout.  Available modes are: Opaque
# (default), SourceAlphaBlend, and PremultSourceAlphaBlend.  This
# value has meaning only when an external process has created a
# display which is behind the X server.

#    Option      "OverlayCombineMode" "PremultSourceAlphaBlend"

# ARGBHWCursor controls whether the X driver uses an overlay to
# display 32-bit "true-color" cursors, or whether such cursors are
# emulated in software.  Valid values are "true" to enable hardware
# cursors, and "false" (default) to disable them.

#    Option      "ARGBHWCursor"

# Set the maximum number of pixmap caches used by the X driver.
# Valid values are 0 through 16 (default)
# A value of 0 disables the use of the caches for pixmaps.
# To use less memory, but still retain performance, the recommendation
# is to use one pixmap heap, set a small size, and limit the size
# of the surfaces that utilizes the pixmap cache.
#    Option      "PixmapCacheMaxHeaps"  "1"

# Set the size of each pixmap cache, in bytes.
# Valid values are 64 KiB though 64 MiB. Up to
# "PixmapCacheMaxHeaps" (see above) will be allocated
# if necessary. The default value is 8 MiB.
#    Option      "PixmapCacheSize"  "65536"

# Set the maximum size for a surface that uses
# the pixmap cache. If a surface exceeds this size
# it will be allocated as a separate allocation, outside
# the pixmap cache.
# The default value is the same as "PixmapCacheSize"
#    Option      "PixmapCacheMaxSurfaceSize"  "4096"

# 3DSwapBlits causes swap blits to use the 3D engine which will prevent
# a particular tearing artifact for GLES based compositors, but with
# generally lower overall performance.
#    Option      "3DSwapBlits"

# Use monitor section with identifier LVDS for output named LVDS-1
#    Option      "monitor-LVDS-1" "LVDS"
    Option      "monitor-HDMI-1" "HDMI"

# VsyncOnlyPrimary causes only the primary display to obey vsync for
# swap flips.  While this allows tearing on secondary displays,
# it reduces jitter and may improve overall performance.
    Option      "VsyncOnlyPrimary"
EndSection

#Section "Monitor"
#    Identifier  "LVDS"

# The following values will override the ones set in the device section
#    Option      "OverlayDepth" "1"
#    Option      "OverlayCombineMode" "SourceAlphaBlend"
#EndSection

Section "Monitor"
    Identifier  "HDMI"

    Option      "OverlayDepth" "1"
    Option      "OverlayCombineMode" "SourceAlphaBlend"
EndSection

“dmesg | egrep -i hdmi” Returned nothing. “/etc/nv_tegra_release” Does not exist.

If someone has an xorg.conf from a known working TK1 Pro it would help for comparison. I do see that Monitor has Identifier “HDMI”, and this is in section “Device”:

# Use monitor section with identifier LVDS for output named LVDS-1
#    Option      "monitor-LVDS-1" "LVDS"
    Option      "monitor-HDMI-1" "HDMI"

I’m wondering if “monitor-HDMI-1” and “HDMI” correspond to the monitor currently plugged in…but I have no idea what kind of monitor connectivity a TK1 Pro has. Can someone with knowledge of the TK1 Pro xorg.conf and video connectors comment if his monitor in his above xorg.conf is valid for the connector he is using?

@nickcj234, what physical connector is used on this?

On the TK1 Pro there is a full sized HDMI connected to the Tegra soc (VCM Card) and two mini HDMI connected to the Quadro card on the pcie bus. Currently I am trying to use the Tegra HDMI port.

Edit: On the ssd There is a partition with spare “rootfs” for the regular tegra installation and one using the Quadro. If you want I can post the xorg.conf for Quadro the version.

The other xorg.conf would be of interest, but what I’m really interested in is if the monitor/display declaration normally goes to a different HDMI port. It seems the hardware is working, but the X server doesn’t think there is a valid screen due to binding the wrong HDMI port to the screen.

I didn’t realize there would be two rootfs (does it run two o/s simultaneously?), but it is also possible that if there is a second rootfs, that perhaps the HDMI declared in that would be the one needing declaration where you are now. It’s basically a lot of guessing unless someone knows which HDMI to declare to give a valid screen for the connector you are using. Correct hardware and driver setup won’t help if it is configured to point at the wrong connector (this would be a case of no valid screen found).

Here is the unedited xorg.conf for the OS using the Quadro.

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 319.37  (buildmeister@swio-display-x64-rhel04-12)  Wed Jul  3 16:49:49 PDT 2013

# Copyright (c) 2011-2013 NVIDIA CORPORATION.  All Rights Reserved.
#
## This is the minimal configuration necessary to use the Tegra driver.
# Please refer to the xorg.conf man page for more configuration
# options provided by the X server, including display-related options
# provided by RandR 1.2 and higher.
# Disable extensions not useful on Tegra.
#Section "Monitor"
#    Identifier  "LVDS"
# The following values will override the ones set in the device section
#    Option      "OverlayDepth" "1"
#    Option      "OverlayCombineMode" "SourceAlphaBlend"
#EndSection
#Section "Monitor"
#    Identifier  "HDMI"
#    Option      "OverlayDepth" "1"
#    Option      "OverlayCombineMode" "SourceAlphaBlend"
#EndSection

Section "ServerLayout"
    Identifier     "Default Layout"
    Screen         "Default Screen" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Module"

#    Disable     "dri"
#    Disable     "dri2"
#    Disable     "glx"
    SubSection     "extmod"
        Option         "omit xfree86-dga"
    EndSubSection
    Load           "glx"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "keyboard"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Option	"ModeDebug"
# OverlayDepth is a 32-bit integer which is used to control overlay
# stacking order.  The overlay with the lowest depth is in front of
# all others.  This value has meaning only when multiple overlays are
# present on a display. This value can range between 0 & 255 (both values
# inclusive). The default being 255.
#    Option      "OverlayDepth" "0"
# OverlayCombineMode determines how the X overlay is combined with the
# overlay behind it during scanout.  Available modes are: Opaque
# (default), SourceAlphaBlend, and PremultSourceAlphaBlend.  This
# value has meaning only when an external process has created a
# display which is behind the X server.
#    Option      "OverlayCombineMode" "PremultSourceAlphaBlend"
## ARGBHWCursor controls whether the X driver uses an overlay to
# display 32-bit "true-color" cursors, or whether such cursors are
# emulated in software.  Valid values are "true" to enable hardware
# cursors, and "false" (default) to disable them.
#    Option      "ARGBHWCursor"
## Set the maximum number of pixmap caches used by the X driver.
# Valid values are 0 through 16 (default)
# A value of 0 disables the use of the caches for pixmaps.
# To use less memory, but still retain performance, the recommendation
# is to use one pixmap heap, set a small size, and limit the size
# of the surfaces that utilizes the pixmap cache.
#    Option      "PixmapCacheMaxHeaps"  "1"
# Set the size of each pixmap cache, in bytes.
# Valid values are 64 KiB though 64 MiB. Up to
# "PixmapCacheMaxHeaps" (see above) will be allocated
# if necessary. The default value is 8 MiB.
#    Option      "PixmapCacheSize"  "65536"
# Set the maximum size for a surface that uses
# the pixmap cache. If a surface exceeds this size
# it will be allocated as a separate allocation, outside
# the pixmap cache.
# The default value is the same as "PixmapCacheSize"
#    Option      "PixmapCacheMaxSurfaceSize"  "4096"
# 3DSwapBlits causes swap blits to use the 3D engine which will prevent
# a particular tearing artifact for GLES based compositors, but with
# generally lower overall performance.
#    Option      "3DSwapBlits"
# Use monitor section with identifier LVDS for output named LVDS-1
#    Option      "monitor-LVDS-1" "LVDS"
#    Option      "monitor-HDMI-1" "HDMI"
# VsyncOnlyPrimary causes only the primary display to obey vsync for
# swap flips.  While this allows tearing on secondary displays,
# it reduces jitter and may improve overall performance.
    Identifier     "NVIDIA"
    Driver         "nvidia"
EndSection

Section "Screen"
    Identifier     "Default Screen"
    Device         "NVIDIA"
    Monitor        "Monitor0"
    Option         "VsyncOnlyPrimary"
    SubSection     "Display"
        Modes      "nvidia-auto-select"
    EndSubSection
EndSection

I believe there are three partitions, 2 being Tegra Linux and one android OS. AFAIK, they do not run simultaneously. As for the HDMI port it is physically connected to the Tergra SOC and the other two are connected to the Quadro.

Here’s what we need to know: Is your connector Monitor0? Probably the horizontal and vertical refresh would need to be removed and EDID used if that were the case. With the sample refresh rates I suspect Monitor0 was intended for LVDS or other non-HDMI connect. Note also that the Monitor section with “HDMI” is commented out…I’m thinking this needs to be uncommented and set up for EDID, whereas the other Monitor0 needs to be commented out. Someone who has a working xorg.conf using the same connector you use would be able to get us past that question. I’ve never seen a TK1 Pro, I have no idea how connectors are attached, and I have no sample hardware to look at to test.

No matter what is changed in the xorg.conf running startx returns with this error:

nvdc: open: No such device or address
nvdc: failed to open '/dev/tegra_dc_1'.

Is there a way to force this to ‘/dev/tegra_dc_0’?

I honestly can’t think of any way to fix this and it might be a deeper problem. These boards were supposed to be shipped with HDMI out of the box but this isn’t the case with this one. I might as well just setup a vnc server on it to save the desk space with having to have a monitor.

I sorry but I have worked to the best of my ability on this one and I think this is a lost cause.

I think there is just some configuration information someone familiar with the TK1 Pro will recognize, but it may take time before someone who has this information sees this post. The device special files you are interested in are a result of drivers supporting hardware…they are not “real” files. Whether or not a driver shows up for a specific video device would depend on what the driver requires. I will suggest that some time in this next week someone knowing about this configuration will be able to answer.

Sorry to bump but I have solved the problem.

In a different linux system we were having problems with certain devices and decided to delete the /dev/ folder. This seems to be the fix for whatever reason.