Dear user of this forum,
I just received the TK1.
As I power on the board, no output is displayed through the hdmi port.
I did exactly what the Quick start guide told me to do.
Have you got any idea’s
Because I am lost right now.
Thank you in advance.
Arno
There can be issues if the monitor detection fails. One reason to fail is if you used an old style 15-pin VGA connector (with or without any other adapter), as the old VGA connector lacks the wire used for monitor query. What kind of cabling is used? Can you give more information on the monitor itself?
Also, serial console is very very useful, as it functions even if video has failed. Consider getting the 9-pin D-Sub cable for connection to your desktop host…you can get a USB version if your desktop does not have a matching 9-pin serial port. If you have this, the setting is 115200 8N1.
On my toshiba 47 inch screen it works fine.
But on my 15.4 inch screen it doesn’t
get-edid | get-edid says:
root@tegra-ubuntu:/home/ubuntu# get-edid | get-edid
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 1
No EDID on bus 2
No EDID on bus 0
No EDID on bus 4
No EDID on bus 1
No EDID on bus 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
������I��
ץ�YJ�$PT����{P 00 6��Q0@�7 V�2LP
�AAA
�#tO�# �f
��R� �(U@Ď!��r ,%�Ď!��
Њ �->��!�
Looks like i2c was successful. Have a good day.
А @1
@U�!�No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.
root@tegra-ubuntu:/home/ubuntu#
parse-edid says:
root@tegra-ubuntu:/home/ubuntu# get-edid | parse-edid
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier "AAA"
ModelName "AAA"
VendorName "ROW"
# Monitor Manufactured week 6 of 2013
# EDID version 1.3
# Digital Display
# Display Physical Size not given. Normal for projectors.
Gamma 1.00
Option "DPMS" "false"
Horizsync 30-80
VertRefresh 50-76
# Maximum pixel clock is 160MHz
#Not giving standard mode: 1280x720, 60Hz
#Extension block found. Parsing...
Hmm, you have data blocks, but not video ones... weird
Something strange happened. Please contact the author,
Matthew Kern at <pyrophobicman@gmail.com>
root@tegra-ubuntu:/home/ubuntu#
with a standard 15,4 inch LCD screen which btw works fine using my orangePI (with ubuntu/hdmi & raspberryPi/hdmi)
You’ll want to trade the “get-edid | get-edid” for “get-edid | edid-decode”. The “get-edid” reads the information, but leaves it in binary format, so pipes to the other commands are needed if people are reading it. “parse-edid” and “edid-decode” are different views of the data with human readable formatting.
This part is of interest:
Hmm, you have data blocks, but not video ones... weird
It would be useful on this to see how edid-decode and parse-edid both deal with this. Note that in the sample you posted the format of output is attempting to fill in a “Monitor” section of the xorg.conf configuration file. When it reaches the unusual data, it fails to complete the configuration block and the block becomes invalid for lack of closing tag. So depending on what part of the system is reading this EDID response, the behavior will depend on how errors effect the software…there isn’t a definition of how X11 should behave under truncated configuration.
Although it still is not confirmed, there is a high probability that the system is running fine, but the monitor configuration is truncated and so video won’t show up. Different consumers of this data on different versions of X11 or Linux will probably have different sensitivities to how bad the odd data truncation behaves. If you can get both the parse-edid and edid-decode together you can probably send the information to the email address in the test which comments about the odd data and get a fix in to deal with this quirk. The only reason I say this is not confirmed is that we don’t know yet if a proper EDID would cause the software to work with the monitor…but I suspect it would.
As an alternative to having both the edid-decode and parse-edid response you could probably use one of the “/sys” edid files, but the actual parse-edid and edid-decode are probably better to send to that email address.
Hi!
Thank you linuxdev.
To which email adress should I send this snippet?
I can’t seem to find it.
Thank you in advance.
Kind regards,
Arnoz
Adding some info concerning: /var/log/Xorg.0.log:
[ 12.541]
X.Org X Server 1.15.1
Release Date: 2014-04-13
[ 12.542] X Protocol Version 11, Revision 0
[ 12.542] Build Operating System: Linux 3.2.0-67-highbank armv7l Ubuntu
[ 12.542] Current Operating System: Linux tegra-ubuntu 3.10.40-gdacac96 #1 SMP PREEMPT Thu Jun 25 15:25:11 PDT 2015 armv7l
[ 12.542] Kernel command line: console=ttyS0,115200n8 console=tty1 no_console_suspend=1 lp0_vec=2064@0xf46ff000 mem=2015M@2048M memtype=255 ddr_die=2048M@2048M section=256M pmuboard=0x0177:0x0000:0x02:0x43:0x00 tsec=32M@3913M otf_key=c75e5bb91eb3bd947560357b64422f85 usbcore.old_scheme_first=1 core_edp_mv=1150 core_edp_ma=4000 tegraid=40.1.1.0.0 debug_uartport=lsport,3 power_supply=Adapter audio_codec=rt5640 modem_id=0 android.kerneltype=normal fbcon=map:1 commchip_id=0 usb_port_owner_info=0 lane_owner_info=6 emc_max_dvfs=0 touch_id=0@0 board_info=0x0177:0x0000:0x02:0x43:0x00 root=/dev/mmcblk0p1 rw rootwait tegraboot=sdmmc gpt
[ 12.542] Build Date: 12 February 2015 02:55:07PM
[ 12.542] xorg-server 2:1.15.1-0ubuntu2.7 (For technical support please see http://www.ubuntu.com/support)
[ 12.542] Current version of pixman: 0.30.2
[ 12.542] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 12.542] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 12.543] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Jan 1 00:00:22 2000
[ 12.545] (==) Using config file: "/etc/X11/xorg.conf"
[ 12.546] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 12.550] (==) No Layout section. Using the first Screen section.
[ 12.550] (==) No screen section available. Using defaults.
[ 12.550] (**) |-->Screen "Default Screen Section" (0)
[ 12.550] (**) | |-->Monitor "<default monitor>"
[ 12.551] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 12.551] (**) | |-->Device "Tegra0"
[ 12.551] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 12.551] (==) Automatically adding devices
[ 12.551] (==) Automatically enabling devices
[ 12.551] (==) Automatically adding GPU devices
[ 12.558] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 12.558] Entry deleted from font path.
[ 12.558] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[ 12.558] Entry deleted from font path.
[ 12.558] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[ 12.558] Entry deleted from font path.
[ 12.559] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[ 12.559] Entry deleted from font path.
[ 12.559] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[ 12.559] Entry deleted from font path.
[ 12.559] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/Type1,
built-ins
[ 12.559] (==) ModulePath set to "/usr/lib/arm-linux-gnueabihf/xorg/extra-modules,/usr/lib/xorg/extra-modules,/usr/lib/xorg/modules"
[ 12.559] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 12.559] (II) Loader magic: 0xb6fa1f10
[ 12.560] (II) Module ABI versions:
[ 12.560] X.Org ANSI C Emulation: 0.4
[ 12.560] X.Org Video Driver: 15.0
[ 12.560] X.Org XInput driver : 20.0
[ 12.560] X.Org Server Extension : 8.0
[ 12.560] Initializing built-in extension Generic Event Extension
[ 12.560] Initializing built-in extension SHAPE
[ 12.560] Initializing built-in extension MIT-SHM
[ 12.560] Initializing built-in extension XInputExtension
[ 12.560] Initializing built-in extension XTEST
1,1 Top
[ 12.560] Initializing built-in extension XInputExtension
[ 12.560] Initializing built-in extension XTEST
[ 12.560] Initializing built-in extension BIG-REQUESTS
[ 12.560] Initializing built-in extension SYNC
[ 12.560] Initializing built-in extension XKEYBOARD
[ 12.560] Initializing built-in extension XC-MISC
[ 12.561] Initializing built-in extension SECURITY
[ 12.561] Initializing built-in extension XINERAMA
[ 12.561] Initializing built-in extension XFIXES
[ 12.561] Initializing built-in extension RENDER
[ 12.561] Initializing built-in extension RANDR
[ 12.561] Initializing built-in extension COMPOSITE
[ 12.561] Initializing built-in extension DAMAGE
[ 12.561] Initializing built-in extension MIT-SCREEN-SAVER
[ 12.561] Initializing built-in extension DOUBLE-BUFFER
[ 12.561] Initializing built-in extension RECORD
[ 12.561] Initializing built-in extension DPMS
[ 12.561] Initializing built-in extension Present
[ 12.561] Initializing built-in extension DRI3
[ 12.561] Initializing built-in extension X-Resource
[ 12.561] Initializing built-in extension XVideo
[ 12.561] Initializing built-in extension XVideo-MotionCompensation
[ 12.561] Initializing built-in extension SELinux
[ 12.561] Initializing built-in extension XFree86-VidModeExtension
[ 12.561] Initializing built-in extension XFree86-DGA
[ 12.561] Initializing built-in extension XFree86-DRI
[ 12.561] Initializing built-in extension DRI2
[ 12.561] (WW) "dri" will not be loaded unless you've specified it to be loaded elsewhere.
[ 12.561] (II) "glx" will be loaded by default.
[ 12.561] (WW) "xmir" is not to be loaded by default. Skipping.
[ 12.561] (II) LoadModule: "extmod"
[ 12.561] (II) Module "extmod" already built-in
[ 12.562] (II) LoadModule: "glx"
[ 12.565] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 12.867] (II) Module glx: vendor="NVIDIA Corporation"
[ 12.868] compiled for 4.0.2, module version = 1.0.0
[ 12.868] Module class: X.Org Server Extension
[ 12.868] (II) NVIDIA GLX Module 21.4 Release Build (integ_stage_rel) (buildbrain@mobile-u64-286) Thu Jun 25 15:24:45 PDT 2015
[ 12.868] Loading extension GLX
[ 12.868] (II) LoadModule: "nvidia"
[ 12.868] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 12.906] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 12.906] compiled for 4.0.2, module version = 1.0.0
[ 12.907] Module class: X.Org Video Driver
[ 12.929] (II) NVIDIA dlloader X Driver 21.4 Release Build (integ_stage_rel) (buildbrain@mobile-u64-286) Thu Jun 25 15:26:03 PDT 2015
[ 12.930] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 12.930] (++) using VT number 7
[ 12.930] (WW) Falling back to old probe method for NVIDIA
[ 12.930] (II) Loading sub module "fb"
[ 12.930] (II) LoadModule: "fb"
[ 12.931] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 12.935] (II) Module fb: vendor="X.Org Foundation"
[ 12.935] compiled for 1.15.1, module version = 1.0.0
[ 12.935] ABI class: X.Org ANSI C Emulation, version 0.4
[ 12.936] (WW) Unresolved symbol: fbGetGCPrivateKey
[ 12.936] (II) Loading sub module "wfb"
[ 12.936] (II) LoadModule: "wfb"
[ 12.936] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 12.940] (II) Module wfb: vendor="X.Org Foundation"
[ 12.941] compiled for 1.15.1, module version = 1.0.0
57,1 29%
[ 12.940] (II) Module wfb: vendor="X.Org Foundation"
[ 12.941] compiled for 1.15.1, module version = 1.0.0
[ 12.941] ABI class: X.Org ANSI C Emulation, version 0.4
[ 12.941] (II) Loading sub module "ramdac"
[ 12.941] (II) LoadModule: "ramdac"
[ 12.941] (II) Module "ramdac" already built-in
[ 12.942] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 12.942] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[ 12.942] (==) NVIDIA(0): RGB weight 888
[ 12.942] (==) NVIDIA(0): Default visual is TrueColor
[ 12.942] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 12.943] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration" "true"
[ 12.943] (**) NVIDIA(0): Enabling 2D acceleration
[ 13.119] (II) NVIDIA(0): NVIDIA GPU GK20A/NullRM (GK20A) at SoC (GPU-0)
[ 13.119] (--) NVIDIA(0): Memory: 1937408 kBytes
[ 13.119] (--) NVIDIA(0): VideoBIOS:
[ 13.119] (--) NVIDIA(0): Valid display device(s) on GK20A/NullRM at SoC
[ 13.119] (--) NVIDIA(0): DFP-0 (connected)
[ 13.119] (--) NVIDIA(0): DFP-1
[ 13.119] (--) NVIDIA(0): DFP-0: External TMDS
[ 13.119] (--) NVIDIA(0): DFP-1: External TMDS
[ 13.119] (**) NVIDIA(0): Option "Ignore"
[ 13.119] (**) NVIDIA(0): Ignoring display device DFP-0
[ 13.119] (==) NVIDIA(0):
[ 13.119] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 13.119] (==) NVIDIA(0): will be used as the requested mode.
[ 13.119] (==) NVIDIA(0):
[ 13.120] (--) NVIDIA(0): No enabled display devices found; starting anyway because
[ 13.120] (--) NVIDIA(0): AllowEmptyInitialConfiguration is enabled
[ 13.120] (II) NVIDIA(0): Validated MetaModes:
[ 13.120] (II) NVIDIA(0): "NULL"
[ 13.120] (II) NVIDIA(0): Virtual screen size determined to be 640 x 480
[ 13.120] (WW) NVIDIA(0): Unable to get display device for DPI computation.
[ 13.120] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
[ 13.120] (--) Depth 24 pixmap format is 32 bpp
[ 13.121] (WW) NVIDIA(GPU-0): Failed to enter interactive mode.
[ 13.134] (EE) NVIDIA(0): Failed to allocate NVIDIA Error Handler
[ 13.134] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 13.134] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 13.134] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 13.135] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 13.135] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 13.135] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 13.135] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 13.135] (II) NVIDIA(0): Config Options in the README.
[ 13.135] (II) NVIDIA(0): Setting mode "NULL"
[ 13.162] (II) NVIDIA(0): Built-in logo is bigger than the screen.
[ 13.164] Loading extension NV-GLX
[ 13.174] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 13.174] (==) NVIDIA(0): Backing store enabled
[ 13.174] (==) NVIDIA(0): Silken mouse enabled
[ 13.175] (==) NVIDIA(0): DPMS enabled
[ 13.175] Loading extension NV-CONTROL
[ 13.185] (EE) NVIDIA(0): Failed to allocate NVIDIA Damage Manager
[ 13.185] (II) Loading sub module "dri2"
[ 13.185] (II) LoadModule: "dri2"
[ 13.185] (II) Module "dri2" already built-in
[ 13.185] (II) NVIDIA(0): [DRI2] Setup complete
[ 13.185] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 13.186] (--) RandR disabled
116,1 60%
[ 13.185] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 13.186] (--) RandR disabled
[ 13.215] (II) SELinux: Disabled on system
[ 13.220] (II) Initializing extension GLX
[ 13.287] (II) XKB: reuse xkmfile /var/lib/xkb/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[ 13.296] (II) config/udev: Adding input device gpio-keys.4 (/dev/input/event3)
[ 13.297] (**) gpio-keys.4: Applying InputClass "evdev keyboard catchall"
[ 13.297] (II) LoadModule: "evdev"
[ 13.297] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 13.300] (II) Module evdev: vendor="X.Org Foundation"
[ 13.300] compiled for 1.15.0, module version = 2.8.2
[ 13.300] Module class: X.Org XInput Driver
[ 13.300] ABI class: X.Org XInput driver, version 20.0
[ 13.300] (II) Using input driver 'evdev' for 'gpio-keys.4'
[ 13.300] (**) gpio-keys.4: always reports core events
[ 13.300] (**) evdev: gpio-keys.4: Device: "/dev/input/event3"
[ 13.300] (--) evdev: gpio-keys.4: Vendor 0x1 Product 0x1
[ 13.300] (--) evdev: gpio-keys.4: Found keys
[ 13.300] (II) evdev: gpio-keys.4: Configuring as keyboard
[ 13.300] (**) Option "config_info" "udev:/sys/devices/platform/gpio-keys.4/input/input3/event3"
[ 13.301] (II) XINPUT: Adding extended input device "gpio-keys.4" (type: KEYBOARD, id 6)
[ 13.301] (**) Option "xkb_rules" "evdev"
[ 13.301] (**) Option "xkb_model" "pc105"
[ 13.301] (**) Option "xkb_layout" "us"
[ 13.304] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event0)
[ 13.304] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 13.304] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 13.304] (**) Logitech USB Receiver: always reports core events
[ 13.304] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event0"
[ 13.304] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc517
[ 13.304] (--) evdev: Logitech USB Receiver: Found keys
[ 13.304] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 13.304] (**) Option "config_info" "udev:/sys/devices/platform/tegra-ehci.2/usb2/2-1/2-1:1.0/input/input0/event0"
[ 13.304] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 7)
[ 13.304] (**) Option "xkb_rules" "evdev"
[ 13.304] (**) Option "xkb_model" "pc105"
[ 13.305] (**) Option "xkb_layout" "us"
[ 13.306] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event1)
[ 13.306] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[ 13.306] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 13.306] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 13.307] (**) Logitech USB Receiver: always reports core events
[ 13.307] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event1"
[ 13.307] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc517
[ 13.307] (--) evdev: Logitech USB Receiver: Found 12 mouse buttons
[ 13.307] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[ 13.307] (--) evdev: Logitech USB Receiver: Found relative axes
[ 13.307] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[ 13.307] (--) evdev: Logitech USB Receiver: Found absolute axes
[ 13.307] (II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
[ 13.307] (--) evdev: Logitech USB Receiver: Found keys
[ 13.307] (II) evdev: Logitech USB Receiver: Configuring as mouse
[ 13.307] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 13.307] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[ 13.307] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[ 13.307] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 13.307] (**) Option "config_info" "udev:/sys/devices/platform/tegra-ehci.2/usb2/2-1/2-1:1.1/input/input1/event1"
[ 13.307] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 8)
[ 13.308] (**) Option "xkb_rules" "evdev"
[ 13.308] (**) Option "xkb_model" "pc105"
[ 13.308] (**) Option "xkb_layout" "us"
175,1 92%
[ 13.308] (**) Option "xkb_model" "pc105"
[ 13.308] (**) Option "xkb_layout" "us"
[ 13.308] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[ 13.308] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.
[ 13.309] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[ 13.309] (**) Logitech USB Receiver: (accel) acceleration profile 0
[ 13.309] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 13.309] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 13.310] (II) config/udev: Adding input device tegra-rt5639 Headphone Jack (/dev/input/event2)
[ 13.310] (II) No input driver specified, ignoring this device.
[ 13.310] (II) This device may have been added with another device file.
[ 1115.447] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 1115.447] (**) NVIDIA(0): device DFP-1 (Using EDID frequencies has been enabled on
[ 1115.447] (**) NVIDIA(0): all display devices.)
[ 1115.539] (II) NVIDIA(0): Setting mode "NULL"
[ 1115.616] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1280x800 +0+0 {ViewPortIn=1280x800, ViewPortOut=1280x800+0+0}"
[ 1824.213] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1280x800 +0+0 {ViewPortIn=1280x800, ViewPortOut=1280x800+0+0}"
[ 13.300] (**) evdev: gpio-keys.4: Device: "/dev/input/event3"
[ 13.300] (--) evdev: gpio-keys.4: Vendor 0x1 Product 0x1
[ 13.300] (--) evdev: gpio-keys.4: Found keys
[ 13.300] (II) evdev: gpio-keys.4: Configuring as keyboard
[ 13.300] (**) Option "config_info" "udev:/sys/devices/platform/gpio-keys.4/input/input3/event3"
[ 13.301] (II) XINPUT: Adding extended input device "gpio-keys.4" (type: KEYBOARD, id 6)
[ 13.301] (**) Option "xkb_rules" "evdev"
[ 13.301] (**) Option "xkb_model" "pc105"
[ 13.301] (**) Option "xkb_layout" "us"
[ 13.304] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event0)
[ 13.304] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 13.304] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 13.304] (**) Logitech USB Receiver: always reports core events
[ 13.304] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event0"
[ 13.304] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc517
[ 13.304] (--) evdev: Logitech USB Receiver: Found keys
[ 13.304] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 13.304] (**) Option "config_info" "udev:/sys/devices/platform/tegra-ehci.2/usb2/2-1/2-1:1.0/input/input0/event0"
[ 13.304] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 7)
[ 13.304] (**) Option "xkb_rules" "evdev"
[ 13.304] (**) Option "xkb_model" "pc105"
[ 13.305] (**) Option "xkb_layout" "us"
[ 13.306] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event1)
[ 13.306] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[ 13.306] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 13.306] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 13.307] (**) Logitech USB Receiver: always reports core events
[ 13.307] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event1"
[ 13.307] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc517
[ 13.307] (--) evdev: Logitech USB Receiver: Found 12 mouse buttons
[ 13.307] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[ 13.307] (--) evdev: Logitech USB Receiver: Found relative axes
[ 13.307] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[ 13.307] (--) evdev: Logitech USB Receiver: Found absolute axes
[ 13.307] (II) evdev: Logitech USB Receiver: Forcing absolute x/y axes to exist.
[ 13.307] (--) evdev: Logitech USB Receiver: Found keys
[ 13.307] (II) evdev: Logitech USB Receiver: Configuring as mouse
[ 13.307] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 13.307] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[ 13.307] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[ 13.307] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 13.307] (**) Option "config_info" "udev:/sys/devices/platform/tegra-ehci.2/usb2/2-1/2-1:1.1/input/input1/event1"
[ 13.307] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 8)
[ 13.308] (**) Option "xkb_rules" "evdev"
[ 13.308] (**) Option "xkb_model" "pc105"
[ 13.308] (**) Option "xkb_layout" "us"
[ 13.308] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[ 13.308] (WW) evdev: Logitech USB Receiver: ignoring absolute axes.
[ 13.309] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[ 13.309] (**) Logitech USB Receiver: (accel) acceleration profile 0
[ 13.309] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 13.309] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 13.310] (II) config/udev: Adding input device tegra-rt5639 Headphone Jack (/dev/input/event2)
[ 13.310] (II) No input driver specified, ignoring this device.
[ 13.310] (II) This device may have been added with another device file.
[ 1115.447] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 1115.447] (**) NVIDIA(0): device DFP-1 (Using EDID frequencies has been enabled on
[ 1115.447] (**) NVIDIA(0): all display devices.)
[ 1115.539] (II) NVIDIA(0): Setting mode "NULL"
[ 1115.616] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1280x800 +0+0 {ViewPortIn=1280x800, ViewPortOut=1280x800+0+0}"
[ 1824.213] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1280x800 +0+0 {ViewPortIn=1280x800, ViewPortOut=1280x800+0+0}"
So far as adding attachments in the forums goes, you add the attachment after the post is created. When you have made a post there is a quote mark icon in the upper right corner of the reply. If you hover a mouse over that quote icon you will also see a paper clip icon then show up…click on that and you can add an attachment to the message. For anything not of large size often just the “code block </>” markup does the job.
Can you post the output of “sudo get-edid | edid-decode” from the failed monitor? If the monitor works on another Linux computer, it might be interesting what that other computer says as well.
About the Xorg log…there is a lot of log showing your Logitech input devices, and it shows the nVidia driver is found. It seems to have issues figuring out anything about the monitor, and in one place it decides to default to screen size 640x480, but later on attempts to run at 1280x800. I’m wondering if your failing monitor is even capable of 1280x800. If you have a URL for specs on the monitor which shows its available resolutions (all modes, not just how many pixels it has) it might be possible to verify that the defaults are incompatible, but that wouldn’t fix anything without a lot of manual configuration. If EDID were working correctly I’d expect the configuration to not get confused, so getting all of the EDID information needed for EDID fix is the proper solution (there is that email address in the get-edid output, which if correct information can be sent to that email would likely result in a fairly quick solution for this monitor’s quirks).
Hereby the output of sudo get-edid | edid-decode:
root@tegra-ubuntu:/home/ubuntu# sudo get-edid | edid-decode
This is read-edid version 3.0.1. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.
Extracted contents:
header: 00 ff ff ff ff ff ff 00
serial number: 49 f7 00 00 00 00 00 00 06 17
version: 01 03
basic params: 80 00 00 00 0a
chroma info: d7 a5 a2 59 4a 96 24 14 50 54
established: af ce 00
standard: 81 c0 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1: 12 1b 00 7b 50 20 15 30 30 20 36 00 05 a3 10 00 00 18
descriptor 2: 0e 1f 00 80 51 00 1e 30 40 80 37 00 20 56 00 00 00 1c
descriptor 3: 00 00 00 fd 00 32 4c 1e 50 10 00 0a 20 20 20 20 20 20
descriptor 4: 00 00 00 fc 00 41 41 41 0a 20 20 20 20 20 20 20 20 0a
extensions: 01
checksum: fd
Manufacturer: ROW Model 0 Serial Number 0
Made week 6 of 2013
EDID version: 1.3
Digital display
Image size is variable
Gamma: 1.00
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
720x400@70Hz
640x480@60Hz
640x480@72Hz
640x480@75Hz
800x600@56Hz
800x600@60Hz
800x600@72Hz
800x600@75Hz
1024x768@60Hz
1024x768@70Hz
1024x768@75Hz
Standard timings supported:
1280x768@60Hz
Detailed mode: Clock 69.300 MHz, 261 mm x 163 mm
1280 1328 1360 1403 hborder 0
800 803 809 821 vborder 0
-hsync -vsync
Detailed mode: Clock 79.500 MHz, 32 mm x 86 mm
1280 1344 1472 1664 hborder 0
768 771 778 798 vborder 0
-hsync +vsync
Monitor ranges: 50-76HZ vertical, 30-80kHz horizontal, max dotclock 160MHz
Monitor name: AAA
Has 1 extension blocks
Checksum: 0xfd
CEA extension block
Extension version: 3
31 bytes of CEA data
Video data block
VIC 16
VIC 31 (native)
VIC 20
VIC 05
VIC 04
VIC 19
VIC 18
VIC 22
VIC 17
VIC 21
VIC 03
VIC 07
VIC 02
VIC 06
Audio data block
Speaker allocation data block
Vendor-specific data block, OUI 000c03 (HDMI)
Source physical address 1.0.0.0
Supports_AI
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
4 native detailed modes
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
1280 1720 1760 1980 hborder 0
720 725 730 750 vborder 0
+hsync +vsync
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
1920 2448 2492 2640 hborder 0
540 542 547 562 vborder 0
+hsync +vsync interlaced
Detailed mode: Clock 27.000 MHz, 531 mm x 398 mm
720 736 798 858 hborder 0
480 489 495 525 vborder 0
-hsync -vsync
Detailed mode: Clock 27.000 MHz, 531 mm x 398 mm
720 732 796 864 hborder 0
576 581 586 625 vborder 0
-hsync -vsync
Checksum: 0x9d
root@tegra-ubuntu:/home/ubuntu#
And here the exact type LCD I am using now and to which the above output corresponds to:
http://www.newegg.com/Product/Product.aspx?Item=9SIA7BJ2N80895
I don’t see 1280x800 in the modes, so if the X server is defaulting to this I’m not surprised it doesn’t work. The EDID data needs to be used, but the other software is preventing this. In the first EDID query you will see an email address:
Hmm, you have data blocks, but not video ones... weird
Something strange happened. Please contact the author,
Matthew Kern at <pyrophobicman@gmail.com>
You will probably want to send the information of both “sudo get-edid | edid-decode” and “sudo get-edid | parse-edid” there and see if he can update (it wouldn’t hurt to give monitor info as well). There is a good chance that if the EDID quirks don’t get in the way the monitor would work. Otherwise, you’ll be manually tweaking X11 configs to get it to default to a mode which the monitor works with.
Well I received a message from Matthew:
Now I want to compile the 3.0.2 version of read-edid on the jetson tk1 And I get the following error:
root@tegra-ubuntu:/home/ubuntu/read-edid-3.0.2# cmake .
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
X86_LIBRARY
linked by target "get-edid" in directory /home/ubuntu/read-edid-3.0.2/get-edid
-- Configuring incomplete, errors occurred!
See also "/home/ubuntu/read-edid-3.0.2/CMakeFiles/CMakeOutput.log".
How can I install a X86 Lib on my jetson tk1 using the standard delivered ubuntu 14.04?
EDIT: Oops, did not see he wanted 3.0.2. This might be a problem, but it is likely 3.0.2 will be in the Ubuntu 14.04 repos soon. Checking on source code. Are you using R21.5?
Read-edid, if you “sudo apt update” and “sudo apt-get upgrade”, will be version 3.0.1-2 (this is what both my R21.4 and R21.5 Jetson TK1s have on them. You may need to uncomment some repositories if this fails to update. No need for compiling. But it does make me curious which version you currently have. To verify:
sudo dpkg --list | grep read-edid
FYI, no x86 executable or library will run on a JTK1, it’s ARMv7 (compiling source code could produce ARMv7, but then it is source code which is not dependent on architecture…if a package says it is for x86, then it has been compiled via an incompatible compiler).
I see a source of armhf (ARMv7) source, version 3.0.2-1, here:
https://packages.debian.org/sid/armhf/read-edid/download
I’m using this one specifically:
http://ftp.us.debian.org/debian/pool/main/r/read-edid/read-edid_3.0.2-1_armhf.deb
From this you get “read-edid_3.0.2-1_armhf.deb”, and can install it this way:
sudo dpkg -i read-edid_3.0.2-1_armhf.deb
Ok… So the interesting part here, is that when I install your suggested version and reboot, the monitor will not start automatically.
So I felt lost again…
But as soon as I used noMachine to take over the screen… somehow the monitor(the correct one, connected with HDMI) turs on in the correct resolution. So while I think yes!!! IT worked!! I closed the noMachine session with the Tk1 and suddenly my lcd screen turns off!
The good thing is that this is the first time I see the screen working because it never did. But now it only works when having a noMAchine session open from my mac book.
ubuntu@tegra-ubuntu:~$ 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 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier "AAA"
ModelName "AAA"
VendorName "ROW"
# Monitor Manufactured week 6 of 2013
# EDID version 1.3
# Digital Display
# Display Physical Size not given. Normal for projectors.
Gamma 1.00
Option "DPMS" "false"
Horizsync 30-80
VertRefresh 50-76
# Maximum pixel clock is 160MHz
#Not giving standard mode: 1280x720, 60Hz
#Extension block found. Parsing...
Modeline "Mode 17" 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 0" 69.30 1280 1328 1360 1403 800 803 809 821 -hsync -vsync
Modeline "Mode 1" 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync
Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 3" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 4" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
Modeline "Mode 5" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
Modeline "Mode 6" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
Modeline "Mode 7" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 9" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
Modeline "Mode 10" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 11" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
Modeline "Mode 12" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 13" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
Modeline "Mode 14" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 15" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
Modeline "Mode 16" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
Modeline "Mode 18" 74.25 1920 2448 2492 2640 540 542 547 562 +hsync +vsync interlace
Modeline "Mode 19" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 20" 27.00 720 732 796 864 576 581 586 625 -hsync -vsync
Option "PreferredMode" "Mode 17"
EndSection
ubuntu@tegra-ubuntu:~$
When I change the resolution to 1920 x 1080, suddenly the screen turns on and it works perfectly. When saving the settings and do a reboot. I get a black screen again.
How can I set the working resolution to be used as the default one?
Exerpt of /var/log/Xorg.0.log:
[ 49.932] (II) NVIDIA(0): Setting mode "NULL"
[ 49.984] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select @1280x800 +0+0 {ViewPortIn=1280x800, ViewPortOut=1280x800+0+0}"
[ 101.684] (II) NVIDIA(0): Setting mode "HDMI-0: 1920x1080 @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
I’m not positive about what’s going on, but I think odds are that the Jetson is missing some EDID data, with defaults not being compatible with the monitor…but then the noMachine connects and actually provides some EDID data which is compatible (if not mistaken, noMachine is real-time remote display on one machine of the desktop on another…the desktops are linked in real time as clones of each other). It seems the X end is working when EDID is available.
So with no noMachine (an odd tongue twister when said quickly) what does the new get-edid say? The example you pasted above indicates many modes were found…was this with noMachine or without noMachine? I’m going to guess it is with noMachine…if it is, can you show the output from the Jetson with no remote desktop software running?
Ok… So, without noMAchine on the Jetson I get:
root@tegra-ubuntu:/home/ubuntu# 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 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier "AAA"
ModelName "AAA"
VendorName "ROW"
# Monitor Manufactured week 6 of 2013
# EDID version 1.3
# Digital Display
# Display Physical Size not given. Normal for projectors.
Gamma 1.00
Option "DPMS" "false"
Horizsync 30-80
VertRefresh 50-76
# Maximum pixel clock is 160MHz
#Not giving standard mode: 1280x720, 60Hz
#Extension block found. Parsing...
Modeline "Mode 17" 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 0" 69.30 1280 1328 1360 1403 800 803 809 821 -hsync -vsync
Modeline "Mode 1" 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync
Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 3" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 4" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
Modeline "Mode 5" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
Modeline "Mode 6" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
Modeline "Mode 7" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 9" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
Modeline "Mode 10" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 11" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
Modeline "Mode 12" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 13" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
Modeline "Mode 14" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 15" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
Modeline "Mode 16" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
Modeline "Mode 18" 74.25 1920 2448 2492 2640 540 542 547 562 +hsync +vsync interlace
Modeline "Mode 19" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 20" 27.00 720 732 796 864 576 581 586 625 -hsync -vsync
Option "PreferredMode" "Mode 17"
EndSection
root@tegra-ubuntu:/home/ubuntu#
I did not find what I was looking for in that EDID output. Other than white space the two EDID readings (with versus without noMachine) did not change. I found stray white space, perhaps this causes an issue, but I highly doubt that (it wasn’t the indenting which I was looking at, it was stray white space at ends of a couple of lines from the EDID under noMachine…those stray characters did not exist without noMachine…perhaps they are even mouse copy and paste issues).
noMachine could be pretending it is that screen for virtual desktop emulation purposes (I have no idea how noMachine and other remote desktop software deals with EDID), so although the monitor ID information (Identifier, ModelName, VendorName) did not change between the working-with-noMachine EDID and the purely non-working not-noMachine EDID information, it is still possible your host is how EDID was read (at minimum your experiments with noMachine prove the remote desktop software can have an effect on the Jetson).
Is it possible to connect the non-working 15.4" screen to another Linux computer to gether the EDID information there? And if you can get this working on a different computer, can you post a copy of the output of xrandr?
I used the Orange PI to check the edid info there. I Installed the same version of edid 3.0.2 on the OrangePi but then I get the following:
arnoz@orangepiplus2e:~/Downloads$ 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
Looks like no busses have an EDID. Sorry!
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
arnoz@orangepiplus2e:~/Downloads$
The OrangePi is an armv71 running with Xfce
The strange thing here is, that the screen works immediately.
xrandr does:
arnoz@orangepiplus2e:~/Downloads$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1280 x 720, current 1280 x 720, maximum 1280 x 720
default connected 1280x720+0+0 0mm x 0mm
1280x720 0.00*
arnoz@orangepiplus2e:~/Downloads$
Recall that under get-edid prior to the version 3.0.2 you had this message:
Hmm, you have data blocks, but not video ones... weird
Something strange happened. Please contact the author,
Basically that’s code for handling something the programming didn’t understand. I’m thinking probably the OrangePi suffers from the same thing, but simply has a different error response (the OrangePi might work because the defaults are compatible with the monitor). It is also possible that different parts of a system use different software to read the same thing, e…g, a certain EDID software used with X11 may differ from that used with text-mode console…when one works, the other does not necessarily inherit that success.
Just to verify, is it correct that your EDID queries for that monitor on the JTK1 no longer produce the “you have data blocks, but not video ones” message? On the JTK1 with that non-working monitor, what is the output of “find /sys/kernel/debug/ -type f -name ‘edid’” and “sudo cat /sys/kernel/debug/edid1”? You should find raw hex data. All of the EDID interfaces should base their response on that data (the raw hex data should be from what the monitor replies, but without any interpretation of whether or not it is valid…further processing determines if the data is useful or valid).
Regardless, if you have any other computer which can run Linux and work with that monitor, I’d still want to see what the “get-edid | parse-edid” and “get-edid | edid-decode” say. Maybe if you have another computer but it isn’t running Linux you could use a live CD for the testing (which wouldn’t require an install and wouldn’t interfere with anything already installed).
You are correct: now I don’t get the : you have data blocks, but not video ones on the JTK1 any more.
I still get:
ubuntu@tegra-ubuntu:~$ 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 2
No EDID on bus 4
No EDID on bus 5
1 potential busses found: 3
256-byte EDID successfully retrieved from i2c bus 3
Looks like i2c was successful. Have a good day.
Checksum Correct
Section "Monitor"
Identifier "AAA"
ModelName "AAA"
VendorName "ROW"
# Monitor Manufactured week 6 of 2013
# EDID version 1.3
# Digital Display
# Display Physical Size not given. Normal for projectors.
Gamma 1.00
Option "DPMS" "false"
Horizsync 30-80
VertRefresh 50-76
# Maximum pixel clock is 160MHz
#Not giving standard mode: 1280x720, 60Hz
#Extension block found. Parsing...
Modeline "Mode 17" 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 0" 69.30 1280 1328 1360 1403 800 803 809 821 -hsync -vsync
Modeline "Mode 1" 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync
Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 3" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 4" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
Modeline "Mode 5" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
Modeline "Mode 6" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
Modeline "Mode 7" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 9" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
Modeline "Mode 10" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 11" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
Modeline "Mode 12" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 13" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
Modeline "Mode 14" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 15" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
Modeline "Mode 16" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
Modeline "Mode 18" 74.25 1920 2448 2492 2640 540 542 547 562 +hsync +vsync interlace
Modeline "Mode 19" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 20" 27.00 720 732 796 864 576 581 586 625 -hsync -vsync
Option "PreferredMode" "Mode 17"
EndSection
ubuntu@tegra-ubuntu:~$
sudo cat /sys/kernel/debug/edid1
Result in:
ubuntu@tegra-ubuntu:~$ sudo cat /sys/kernel/debug/edid1
edid[000] = 00 ff ff ff ff ff ff 00 49 f7 00 00 00 00 00 00
edid[010] = 06 17 01 03 80 00 00 00 0a d7 a5 a2 59 4a 96 24
edid[020] = 14 50 54 af ce 00 81 c0 01 01 01 01 01 01 01 01
edid[030] = 01 01 01 01 01 01 12 1b 00 7b 50 20 15 30 30 20
edid[040] = 36 00 05 a3 10 00 00 18 0e 1f 00 80 51 00 1e 30
edid[050] = 40 80 37 00 20 56 00 00 00 1c 00 00 00 fd 00 32
edid[060] = 4c 1e 50 10 00 0a 20 20 20 20 20 20 00 00 00 fc
edid[070] = 00 41 41 41 0a 20 20 20 20 20 20 20 20 0a 01 fd
edid[080] = 02 03 23 74 4f 10 9f 14 05 04 13 12 16 11 15 03
edid[090] = 07 02 06 01 23 09 0f 03 83 01 00 00 66 03 0c 00
edid[0a0] = 10 00 80 01 1d 00 bc 52 d0 1e 20 b8 28 55 40 c4
edid[0b0] = 8e 21 00 00 1e 01 1d 80 d0 72 1c 16 20 10 2c 25
edid[0c0] = 80 c4 8e 21 00 00 9e 8c 0a d0 8a 20 e0 2d 10 10
edid[0d0] = 3e 96 00 13 8e 21 00 00 18 8c 0a d0 90 20 40 31
edid[0e0] = 20 0c 40 55 00 13 8e 21 00 00 18 00 00 00 00 00
edid[0f0] = 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9d
ubuntu@tegra-ubuntu:~$
The EDID definitely looks valid. Let’s try an experiment to see if we can manually enter that data and get it to work via bypassing of EDID.
Go to the “/etc/X11” directory, note that xorg.conf is probably a symbolic link to xorg.conf.jetson-tk1. Verify this (ls -l xorg.conf). Assuming this is a symbolic link, remove the symlink (rm xorg.conf), and directly copy the original hard file in:
cp xorg.conf.jetson-tk1 xorg.conf
…otherwise you’ll need to back up the original.
Within that file you will find this:
Section "Monitor"
Identifier "DSI-0"
Option "Ignore"
EndSection
Within your posted “get-edid | parse-edid” you will see it quotes what section “monitor” would be if EDID were to successfully convey the information to the X server. You can actually have more than one “Monitor” section since you can have more than one monitor. As a first experiment, just add an extra section “Monitor” which is a copy of the above “get-edid | parse-edid” Monitor section.
Additionally, it may be necessary to add this to Device section, but wait to see first if the manual Monitor section addition works:
Section "Device"
...
Option "UseEDID" "FALSE"
...
EndSection
There are actually two steps involved in making things work…one is getting the EDID to X, and the second stage is getting X to work with the data. This experiment is an attempt to bypass needing to get EDID to X, and to instead find out whether X likes the data that is there. Depending on the result it’ll narrow down where the problem is at…if the manually pasted data fails, then it may not be related to EDID, but instead to video not liking the modes the monitor has.
Just FYI, you probably won’t use it, but the hex EDID data has an online parser you can use to split things out for machines that can’t parse the EDID, but which has the hex data from “/sys”:
http://www.edidreader.com/
If you ever need to manually create modelines, you’ll see that the output of the online utility has sections “Detailed Timing Descriptor…”. Compare those timings to the lines in the parse-edid output, and you’ll see this is how modelines are constructed (there are also URLs on modeline construction utilities, e.g., http://xtiming.sourceforge.net/cgi-bin/xtiming.pl). The experiment above is to use outside utilities to directly inject those values into the X server without requiring any EDID information.
Ok so I started with the experiment. I removed the symlink and copied the content of the original file to xorg.conf resulting in:
# Copyright (c) 2011-2015 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"
SubSection "extmod"
Option "omit xfree86-dga"
EndSubSection
EndSection
Section "Device"
Identifier "Tegra0"
Option "UseEDID" "FALSE"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration" "true"
EndSection
Section "Monitor"
Identifier "DSI-0"
Option "Ignore"
EndSection
Section "Monitor"
Identifier "AAA"
ModelName "AAA"
VendorName "ROW"
# Monitor Manufactured week 6 of 2013
# EDID version 1.3
# Digital Display
# Display Physical Size not given. Normal for projectors.
Gamma 1.00
Option "DPMS" "false"
Horizsync 30-80
VertRefresh 50-76
# Maximum pixel clock is 160MHz
#Not giving standard mode: 1280x720, 60Hz
#Extension block found. Parsing...
Modeline "Mode 17" 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 0" 69.30 1280 1328 1360 1403 800 803 809 821 -hsync -vsync
Modeline "Mode 1" 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync
Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 3" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 4" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
Modeline "Mode 5" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
Modeline "Mode 6" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
Modeline "Mode 7" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 9" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
Modeline "Mode 10" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 11" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace
Modeline "Mode 12" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 13" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
Modeline "Mode 14" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 15" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace
Modeline "Mode 16" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
Modeline "Mode 18" 74.25 1920 2448 2492 2640 540 542 547 562 +hsync +vsync interlace
Modeline "Mode 19" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 20" 27.00 720 732 796 864 576 581 586 625 -hsync -vsync
Option "PreferredMode" "Mode 17"
EndSection
After a couple of tests I eventually added:
Option "UseEDID" "FALSE"
in the device section.
1st test:
After reboot the screen stays off and somehow the symlink is back.
So I moved the original file to the home dir. Created an xorg.conf file again with the addition of the get-edid | parse-edid info.
2nd test:
After reboot the the screen still stays off. The symlink has ben created again. with xorg.conf being empty
Some how after a reboot it creates the symlink and removes the data in the custom xorg.conf.