Bad HDMI signal integrity, or am I doing it wrong?

zacariaz · 2017-04-07 18:28:19

Got an Asus UX305 laptop, with intel graphics and HDMI, want to mirror my laptop over HDMI so as to record it using the Avermedia gl310 lgp lite something or rather on another, more powerful laptop.
I've tried Gnomes utility for the purpose, to no avail, and then xrandr

xrandr --output eDP1 --mode 1920x1080 --output HDMI1 --mode 1920x1080 --same-as eDP1

which seems right to me, and the xrandr output also seem to suggest that everything is as it should be.
So, I hooked up my Sony A6000 camera, and there's not issues as all.

My fear is that my cable, which is 5m long, simply isn't good enough to handle that distance, but before I rush out and buy an expensive cable, or adapter so that i may use a regular HDMI cable, I wanted to ask you opinion.

I don't have other means of testing, so that's rally all there's left

Thanks.

---

Okay, here goes.

Hardware:
Laptop 1 (source 1 - micro hdmi out) Asus ux305 (intel graphics) Running Arch
Camera (source 2 - micro hdmi out) Sony A6000 - for testing purposes only.
Capture device (hdmi in) Avermedia LGP lite gl310 (usb out*)
Laptop 2 (host? receive? - usb in*) - running Windows** - Testing with open broadcast studio and avermedias own software

*I realize that USB is not one way communication.
**This should be irrelevant, but necessary since the gl310 at this point is apparently not linux friendly, though that was in fact my understanding, and the reason I bought it.

Testing the setup with the camera works, not issues at all, the source being 1080p30.
Testing with laptop 1 results in black or blank screen with OBS and "no signal" or on one rare and short lived occasion "too weak signal" in Avermedia software at 1080p60, 1080p30 and 720p60.

I enable hdmi out on laptop 1, presumably, but the command:

xrandr --output eDP1 --mode 1920x1080 --output HDMI1 --mode 1920x1080 --rate 30 --same-as eDP1

Or the equivalent for other resolutions, and xrandrs output is as follows:

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 290mm x 170mm
   1920x1080     60.00*+
   1400x1050     59.98  
   1600x900      60.00  
   1280x1024     60.02  
   1280x960      60.00  
   1368x768      60.00  
   1280x720      60.00  
   1024x768      60.00  
   1024x576      60.00  
   960x540       60.00  
   800x600       60.32    56.25  
   864x486       60.00  
   640x480       59.94  
   720x405       60.00  
   640x360       60.00  
HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 800mm x 450mm
   1920x1080     60.00 +  50.00    59.94    30.00*   25.00    24.00    29.97    23.98  
   1920x1080i    60.00    50.00    59.94  
   1680x1050     59.88  
   1280x1024     60.02  
   1440x900      59.90  
   1280x800      59.91  
   1280x720      60.00    50.00    59.94  
   1024x768      60.00  
   800x600       60.32  
   720x576       50.00  
   720x576i      50.00  
   720x480       60.00    59.94  
   720x480i      60.00    59.94  
   640x480       60.00    59.94  
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

I have no other means of testing. Suffice to say that there really are only 3 options.
1. The hdmi port on laptop 1 isn't actually outputting an appropriate signal, for whatever reason. Incompetence perhaps.
2. There is a connection issue. The cable may be of low quality, but is certainly not broken, thus I thought signal integrity.
3. Some for of copy protection, which seems unlikely.

I cannot at this time think of anyway to make it any clearer

Last edited by zacariaz (2017-04-08 13:13:03)

seth · 2017-04-07 19:09:56

Is it me or does this post lack a problem description...? o_O
If you worry about an insufficient cable, try w/ a lower resolution (eg. 720p)

zacariaz · 2017-04-07 19:54:28

seth wrote:

Is it me or does this post lack a problem description...? o_O
If you worry about an insufficient cable, try w/ a lower resolution (eg. 720p)

I'm sure the description is lagging, but frankly I have no idea how to improve it.
I didn't think of a lower resolution. In fact I didn't think it would make a difference.
Will try it and get back.

zacariaz · 2017-04-07 20:02:36

No, lower resolution or frame rate doesn't seem to change anything.
Just seem odd to me that there should be such a difference in the signal amplitude (if that's the right term) between a small camera and a laptop.

seth · 2017-04-07 20:43:32

You say what you want to do, but nothing about the problem with that - don't you get any signal on the camera? Does the camera recording flicker, have artifacts? Did you inject a signal scanner to measure quality ... or what?
Also is the sony camera a source or an alternative (recording) output?

The camera seems to only support a limited set of resolution/frequency combinations - so what's the output of "xrandr -q" and does the used frequency match a supported one *exactly* ...

zacariaz · 2017-04-07 23:19:57

seth wrote:

You say what you want to do, but nothing about the problem with that - don't you get any signal on the camera? Does the camera recording flicker, have artifacts? Did you inject a signal scanner to measure quality ... or what?
Also is the sony camera a source or an alternative (recording) output?
The camera seems to only support a limited set of resolution/frequency combinations - so what's the output of "xrandr -q" and does the used frequency match a supported one *exactly* ...

My mistake, thought it was evident.
I wish to capture the HDMI signal from my laptop, through the the capture device. When it didn't work, I tried connecting the camera instead, to test if it was the capture device that wasn't working properly, and it worked fine. Other than that the camera has nothing to do with the situation.

Thus I'm left with my Asus UX305 laptop, which only has a micro HDMI plug, but luckily the same cable I bought for my camera fits, only it doesn't work.
Since xrandr claims that everything is in order at the laptop end, and indeed when unplugged it notices, I cannot come up with a different explanation than signal integrity, though why the camera can manage a stronger signal I do not know.

At any rate, the signal isn't getting through, and I do believe that I saw message on the other end of the capture device, claiming the signal was too weak, but only briefly, so that may have been a fluke.

Other than that I don't believe I have anything to add, I just wanted ask for advice before starting spending money on stuff I may not need.

Best regards.

headkase · 2017-04-08 00:52:48

zacariaz wrote:

want to mirror my laptop over HDMI so as to record it using the Avermedia gl310 lgp lite something or rather on another, more powerful laptop.

You do realize than HDMI is an output port right? If you want to record the signal on another machine then the port on that machine must be an input one. HDMI ports do not typically do input, the signals are meant to flow one way.

zacariaz · 2017-04-08 01:03:44

laptop1 (hdmi out) --> (hdmi in) Capture device (usb "out") --> (usb "in") laptop2
This is the setup as plain as I can explain it.
It doesn't work, but if you exchange laptop1 for my camera, which also has an hdmi out, it does work.
I hop this clears up any misunderstanding, but in short yes, I do realize that there's a difference between hdmi in and out.

seth · 2017-04-08 04:03:51

You missed the

so what's the output of "xrandr -q" and does the used frequency match a supported one *exactly*

part ;-)
(This can be critical because you've two outputs on very likely only one crtc and the eDP1 one being the dominant - you could also try turning eDP1 --off and HDMI --auto - you won't see anything but still can check the capture afterwards)

Also

When it didn't work

is no error descritption.
Did the capture device record anything at all (just black) or does it maybe have status indication that says "no signal" or did something entirely different happen.

Notice that what might seem evident to you is strongly related to the fact that you get the actual output data but provide us only vague interpretations of it (when at all) - we don't see what you see and rely on you telling us as precisely as possible.

olive · 2017-04-08 10:12:51

First as other have explained, but does not appear very obvious to you, it is not yet very clear what setup you use. Indeed capturing the hdmi output is not very common. So describe your equipment and setup carefully. What's the capture device you're speaking about? What port does it have how is it supposed to work? I guess the capture device is the "Sony 6000" but I still don't quite understand your setup. Is this camera supposed to capture HDMI and somehow output what is capturing through USB? If so what software are you using on laptop2? You should be aware that such devices are not common and that people here don't necessarily have a knowledge of it.

Note that given your HDMI cable work in a usual situation (connecting a TV), I doubt the cable is the culprit. HDMI are digital and usually it works perfectly or not at all, a better cable won't improve the situation (theoretically some devices may be more tolerant to bad signal than others, but I think it is unlikely). I guess the problem is not with the first laptop but with the rest of the setup.

Last edited by olive (2017-04-08 10:17:07)

zacariaz · 2017-04-08 12:55:02

Okay, here goes.

Hardware:
Laptop 1 (source 1 - micro hdmi out) Asus ux305 (intel graphics) Running Arch
Camera (source 2 - micro hdmi out) Sony A6000 - for testing purposes only.
Capture device (hdmi in) Avermedia LGP lite gl310 (usb out*)
Laptop 2 (host? receive? - usb in*) - running Windows** - Testing with open broadcast studio and avermedias own software

*I realize that USB is not one way communication.
**This should be irrelevant, but necessary since the gl310 at this point is apparently not linux friendly, though that was in fact my understanding, and the reason I bought it.

Testing the setup with the camera works, not issues at all, the source being 1080p30.
Testing with laptop 1 results in black or blank screen with OBS and "no signal" or on one rare and short lived occasion "too weak signal" in Avermedia software at 1080p60, 1080p30 and 720p60.

I enable hdmi out on laptop 1, presumably, but the command:

xrandr --output eDP1 --mode 1920x1080 --output HDMI1 --mode 1920x1080 --rate 30 --same-as eDP1

Or the equivalent for other resolutions, and xrandrs output is as follows:

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 290mm x 170mm
   1920x1080     60.00*+
   1400x1050     59.98  
   1600x900      60.00  
   1280x1024     60.02  
   1280x960      60.00  
   1368x768      60.00  
   1280x720      60.00  
   1024x768      60.00  
   1024x576      60.00  
   960x540       60.00  
   800x600       60.32    56.25  
   864x486       60.00  
   640x480       59.94  
   720x405       60.00  
   640x360       60.00  
HDMI1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 800mm x 450mm
   1920x1080     60.00 +  50.00    59.94    30.00*   25.00    24.00    29.97    23.98  
   1920x1080i    60.00    50.00    59.94  
   1680x1050     59.88  
   1280x1024     60.02  
   1440x900      59.90  
   1280x800      59.91  
   1280x720      60.00    50.00    59.94  
   1024x768      60.00  
   800x600       60.32  
   720x576       50.00  
   720x576i      50.00  
   720x480       60.00    59.94  
   720x480i      60.00    59.94  
   640x480       60.00    59.94  
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

I have no other means of testing. Suffice to say that there really are only 3 options.
1. The hdmi port on laptop 1 isn't actually outputting an appropriate signal, for whatever reason. Incompetence perhaps.
2. There is a connection issue. The cable may be of low quality, but is certainly not broken, thus I thought signal integrity.
3. Some for of copy protection, which seems unlikely.

I cannot at this time think of anyway to make it any clearer

Last edited by zacariaz (2017-04-08 13:12:41)

olive · 2017-04-08 19:12:02

Ok, now at least we understand what you trying to do. Try xrandr --verbose. Things like "color model" can possibly be set too. The hdmi cable may, in fact, be a possibility if the capture device is less tolerant too weak signal than the other equipment. I doubt it, but it is a possibility. I know nothing about copy protection, I think linux do not support it; but I don't know. Have you tried to capture the output of a Windows laptop?

zacariaz · 2017-04-08 21:05:42

olive wrote:

Ok, now at least we understand what you trying to do. Try xrandr --verbose. Things like "color model" can possibly be set too. The hdmi cable may, in fact, be a possibility if the capture device is less tolerant too weak signal than the other equipment. I doubt it, but it is a possibility. I know nothing about copy protection, I think linux do not support it; but I don't know. Have you tried to capture the output of a Windows laptop?

Verbose output:

Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
eDP1 connected primary 1920x1080+0+0 (0x47) normal (normal left inverted right x axis y axis) 290mm x 170mm
	Identifier: 0x43
	Timestamp:  95121812
	Subpixel:   unknown
	Gamma:      1.0:1.0:1.0
	Brightness: 1.0
	Clones:    
	CRTC:       0
	CRTCs:      0 1 2
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	_MUTTER_PRESENTATION_OUTPUT: 0 
	EDID: 
		00ffffffffffff0006af2d2100000000
		00170104951d11780292279858529526
		1f4d5400000001010101010101010101
		0101010101011d3680a070381e403020
		8e0025a5100000180000000f00000000
		00000000000000000020000000fe0041
		554f0a202020202020202020000000fe
		004231333348414e30322e31200a0006
	BACKLIGHT: 937 
		range: (0, 937)
	Backlight: 937 
		range: (0, 937)
	scaling mode: Full aspect 
		supported: None, Full, Center, Full aspect
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	audio: auto 
		supported: force-dvi, off, auto, on
  1920x1080 (0x47) 138.530MHz -HSync -VSync *current +preferred
        h: width  1920 start 1968 end 2000 total 2080 skew    0 clock  66.60KHz
        v: height 1080 start 1088 end 1102 total 1110           clock  60.00Hz
  1400x1050 (0x104) 122.000MHz +HSync +VSync
        h: width  1400 start 1488 end 1640 total 1880 skew    0 clock  64.89KHz
        v: height 1050 start 1052 end 1064 total 1082           clock  59.98Hz
  1600x900 (0x105) 118.997MHz -HSync +VSync
        h: width  1600 start 1696 end 1864 total 2128 skew    0 clock  55.92KHz
        v: height  900 start  901 end  904 total  932           clock  60.00Hz
  1280x1024 (0x106) 108.000MHz +HSync +VSync
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock  63.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  60.02Hz
  1280x960 (0x107) 108.000MHz +HSync +VSync
        h: width  1280 start 1376 end 1488 total 1800 skew    0 clock  60.00KHz
        v: height  960 start  961 end  964 total 1000           clock  60.00Hz
  1368x768 (0x108) 85.860MHz -HSync +VSync
        h: width  1368 start 1440 end 1584 total 1800 skew    0 clock  47.70KHz
        v: height  768 start  769 end  772 total  795           clock  60.00Hz
  1280x720 (0x109) 74.480MHz -HSync +VSync
        h: width  1280 start 1336 end 1472 total 1664 skew    0 clock  44.76KHz
        v: height  720 start  721 end  724 total  746           clock  60.00Hz
  1024x768 (0x10a) 65.000MHz -HSync -VSync
        h: width  1024 start 1048 end 1184 total 1344 skew    0 clock  48.36KHz
        v: height  768 start  771 end  777 total  806           clock  60.00Hz
  1024x576 (0x10b) 46.995MHz -HSync +VSync
        h: width  1024 start 1064 end 1168 total 1312 skew    0 clock  35.82KHz
        v: height  576 start  577 end  580 total  597           clock  60.00Hz
  960x540 (0x10c) 40.784MHz -HSync +VSync
        h: width   960 start  992 end 1088 total 1216 skew    0 clock  33.54KHz
        v: height  540 start  541 end  544 total  559           clock  60.00Hz
  800x600 (0x10d) 40.000MHz +HSync +VSync
        h: width   800 start  840 end  968 total 1056 skew    0 clock  37.88KHz
        v: height  600 start  601 end  605 total  628           clock  60.32Hz
  800x600 (0x10e) 36.000MHz +HSync +VSync
        h: width   800 start  824 end  896 total 1024 skew    0 clock  35.16KHz
        v: height  600 start  601 end  603 total  625           clock  56.25Hz
  864x486 (0x10f) 32.901MHz -HSync +VSync
        h: width   864 start  888 end  976 total 1088 skew    0 clock  30.24KHz
        v: height  486 start  487 end  490 total  504           clock  60.00Hz
  640x480 (0x110) 25.175MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.47KHz
        v: height  480 start  490 end  492 total  525           clock  59.94Hz
  720x405 (0x111) 22.176MHz -HSync +VSync
        h: width   720 start  728 end  800 total  880 skew    0 clock  25.20KHz
        v: height  405 start  406 end  409 total  420           clock  60.00Hz
  640x360 (0x112) 17.187MHz -HSync +VSync
        h: width   640 start  640 end  704 total  768 skew    0 clock  22.38KHz
        v: height  360 start  361 end  364 total  373           clock  60.00Hz
HDMI1 connected 1920x1080+0+0 (0x11a) normal (normal left inverted right x axis y axis) 800mm x 450mm
	Identifier: 0x44
	Timestamp:  95121812
	Subpixel:   unknown
	Gamma:      1.0:1.0:1.0
	Brightness: 1.0
	Clones:    
	CRTC:       1
	CRTCs:      0 1 2
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
	EDID: 
		00ffffffffffff0006d8030000000000
		3517010380502d780a0dc9a057479827
		12484c210800818081009500b3000101
		010101010101023a801871382d40582c
		4500c48e2100001e0000001000000000
		00000000000000000000000000fc0041
		565420474c3331300a202020000000fd
		00183d0f44080a20202020202020015e
		020322704e0584021413112021220190
		1f0615230907078301000066030c0010
		0000023a801871382d40582c4500c48e
		2100001e011d007251d01e206e285500
		a05a0000001e00000000000000000000
		00000000000000000000000000000000
		00000000000000000000000000000000
		000000000000000000000000000000b1
	_MUTTER_PRESENTATION_OUTPUT: 0 
	aspect ratio: Automatic 
		supported: Automatic, 4:3, 16:9
	Broadcast RGB: Automatic 
		supported: Automatic, Full, Limited 16:235
	audio: auto 
		supported: force-dvi, off, auto, on
  1920x1080 (0x11a) 148.500MHz +HSync +VSync *current +preferred
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.50KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  60.00Hz
  1920x1080 (0x11b) 148.500MHz +HSync +VSync
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  56.25KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  50.00Hz
  1920x1080 (0x11c) 148.352MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.43KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  59.94Hz
  1920x1080i (0x11d) 74.250MHz +HSync +VSync Interlace
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.75KHz
        v: height 1080 start 1084 end 1094 total 1125           clock  60.00Hz
  1920x1080i (0x11e) 74.250MHz +HSync +VSync Interlace
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  28.12KHz
        v: height 1080 start 1084 end 1094 total 1125           clock  50.00Hz
  1920x1080 (0x11f) 74.250MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.75KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  30.00Hz
  1920x1080 (0x120) 74.250MHz +HSync +VSync
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  28.12KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  25.00Hz
  1920x1080 (0x121) 74.250MHz +HSync +VSync
        h: width  1920 start 2558 end 2602 total 2750 skew    0 clock  27.00KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  24.00Hz
  1920x1080i (0x122) 74.176MHz +HSync +VSync Interlace
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.72KHz
        v: height 1080 start 1084 end 1094 total 1125           clock  59.94Hz
  1920x1080 (0x123) 74.176MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.72KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  29.97Hz
  1920x1080 (0x124) 74.176MHz +HSync +VSync
        h: width  1920 start 2558 end 2602 total 2750 skew    0 clock  26.97KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  23.98Hz
  1680x1050 (0x125) 119.000MHz +HSync -VSync
        h: width  1680 start 1728 end 1760 total 1840 skew    0 clock  64.67KHz
        v: height 1050 start 1053 end 1059 total 1080           clock  59.88Hz
  1280x1024 (0x106) 108.000MHz +HSync +VSync
        h: width  1280 start 1328 end 1440 total 1688 skew    0 clock  63.98KHz
        v: height 1024 start 1025 end 1028 total 1066           clock  60.02Hz
  1440x900 (0x126) 88.750MHz +HSync -VSync
        h: width  1440 start 1488 end 1520 total 1600 skew    0 clock  55.47KHz
        v: height  900 start  903 end  909 total  926           clock  59.90Hz
  1280x800 (0x127) 71.000MHz +HSync -VSync
        h: width  1280 start 1328 end 1360 total 1440 skew    0 clock  49.31KHz
        v: height  800 start  803 end  809 total  823           clock  59.91Hz
  1280x720 (0x128) 74.250MHz +HSync +VSync
        h: width  1280 start 1390 end 1430 total 1650 skew    0 clock  45.00KHz
        v: height  720 start  725 end  730 total  750           clock  60.00Hz
  1280x720 (0x129) 74.250MHz +HSync +VSync
        h: width  1280 start 1720 end 1760 total 1980 skew    0 clock  37.50KHz
        v: height  720 start  725 end  730 total  750           clock  50.00Hz
  1280x720 (0x12a) 74.176MHz +HSync +VSync
        h: width  1280 start 1390 end 1430 total 1650 skew    0 clock  44.96KHz
        v: height  720 start  725 end  730 total  750           clock  59.94Hz
  1024x768 (0x10a) 65.000MHz -HSync -VSync
        h: width  1024 start 1048 end 1184 total 1344 skew    0 clock  48.36KHz
        v: height  768 start  771 end  777 total  806           clock  60.00Hz
  800x600 (0x10d) 40.000MHz +HSync +VSync
        h: width   800 start  840 end  968 total 1056 skew    0 clock  37.88KHz
        v: height  600 start  601 end  605 total  628           clock  60.32Hz
  720x576 (0x12b) 27.000MHz -HSync -VSync
        h: width   720 start  732 end  796 total  864 skew    0 clock  31.25KHz
        v: height  576 start  581 end  586 total  625           clock  50.00Hz
  720x576i (0x12c) 13.500MHz -HSync -VSync Interlace
        h: width   720 start  732 end  795 total  864 skew    0 clock  15.62KHz
        v: height  576 start  580 end  586 total  625           clock  50.00Hz
  720x480 (0x12d) 27.027MHz -HSync -VSync
        h: width   720 start  736 end  798 total  858 skew    0 clock  31.50KHz
        v: height  480 start  489 end  495 total  525           clock  60.00Hz
  720x480 (0x12e) 27.000MHz -HSync -VSync
        h: width   720 start  736 end  798 total  858 skew    0 clock  31.47KHz
        v: height  480 start  489 end  495 total  525           clock  59.94Hz
  720x480i (0x12f) 13.514MHz -HSync -VSync Interlace
        h: width   720 start  739 end  801 total  858 skew    0 clock  15.75KHz
        v: height  480 start  488 end  494 total  525           clock  60.00Hz
  720x480i (0x130) 13.500MHz -HSync -VSync Interlace
        h: width   720 start  739 end  801 total  858 skew    0 clock  15.73KHz
        v: height  480 start  488 end  494 total  525           clock  59.94Hz
  640x480 (0x131) 25.200MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.50KHz
        v: height  480 start  490 end  492 total  525           clock  60.00Hz
  640x480 (0x110) 25.175MHz -HSync -VSync
        h: width   640 start  656 end  752 total  800 skew    0 clock  31.47KHz
        v: height  480 start  490 end  492 total  525           clock  59.94Hz
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
	Identifier: 0x45
	Timestamp:  95121812
	Subpixel:   no subpixels
	Clones:    
	CRTCs:      3
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter:

I'm sorry to say I haven't got a clue what it all means.

As for connecting to a windows laptop, the answer is yet and no. Yes as in, yes I've done it and it worked and no in the sense that I used a regular, and short I might add, hdmi cable as opposed to the 5m hdmi to micro hdmi.
Personally I rather doubt that is of any importance. I mean a hdmi signal is a hdmi signal, wether it comes from a linux of windows machine, right?

olive · 2017-04-09 06:12:45

Personally I rather doubt that is of any importance. I mean a hdmi signal is a hdmi signal, wether it comes from a linux of windows machine, right?

Some parameters can be set. The most obvious ones are the refresh rate and the resolution. But the way the pixel are encoded too. ycbr are common for TV and RGB for computers monitor. Proprietary Windows driver allows setting that. Some Linux proprietary driver may be also. But I don't always see as many options on open sources drivers. Normally all equipment (including TV) support RGB and that what Linux output generally, so it is generally unnoticed. My idea was to examine the graphic card driver of Windows to see exactly what parameters are set. What is the exact resolution, refresh rate and color model?

I have not see any interesting options that might be set in your xrandr --verbose.

It is not possible to give a definitive answer for the cable. Buy a micro HDMI to HDMI adapter or a short cable and try. You can find such things online for less than 5$

zacariaz · 2017-04-09 12:20:41

olive wrote:

Personally I rather doubt that is of any importance. I mean a hdmi signal is a hdmi signal, wether it comes from a linux of windows machine, right?
Some parameters can be set. The most obvious ones are the refresh rate and the resolution. But the way the pixel are encoded too. ycbr are common for TV and RGB for computers monitor. Proprietary Windows driver allows setting that. Some Linux proprietary driver may be also. But I don't always see as many options on open sources drivers. Normally all equipment (including TV) support RGB and that what Linux output generally, so it is generally unnoticed. My idea was to examine the graphic card driver of Windows to see exactly what parameters are set. What is the exact resolution, refresh rate and color model?
I have not see any interesting options that might be set in your xrandr --verbose.
It is not possible to give a definitive answer for the cable. Buy a micro HDMI to HDMI adapter or a short cable and try. You can find such things online for less than 5$

Will do, thanks for the help.

seth · 2017-04-15 07:18:46

Just struck me like a train: HDMI audio. Try to disable it. (there's another thread about hdmi audio on amd/ati causing a pink artifact ...)

xrandr --output HDMI1 --set audio off

There might be kernel parameters to the snd-hda-* module in use or you might try to unload/blacklist snd-hda-codec-hdmi

zacariaz · 2017-04-15 07:38:19

seth wrote:

Just struck me like a train: HDMI audio. Try to disable it. (there's another thread about hdmi audio on amd/ati causing a pink artifact ...)
xrandr --output HDMI1 --set audio off
There might be kernel parameters to the snd-hda-* module in use or you might try to unload/blacklist snd-hda-codec-hdmi

Thanks a bunch, I'll look into it. I have also ordered an adapter, but when it will arrive is anybody's guess.
That being said, it that is indeed, it is a bit sad, as I had hoped to be able to get audio too.

Last edited by zacariaz (2017-04-15 07:39:04)

zacariaz · 2017-05-06 21:06:03

Wrong thread...

Last edited by zacariaz (2017-05-07 12:05:13)

Arch Linux

#1 2017-04-07 18:28:19

Bad HDMI signal integrity, or am I doing it wrong?

#2 2017-04-07 19:09:56

Re: Bad HDMI signal integrity, or am I doing it wrong?

#3 2017-04-07 19:54:28

Re: Bad HDMI signal integrity, or am I doing it wrong?

#4 2017-04-07 20:02:36

Re: Bad HDMI signal integrity, or am I doing it wrong?

#5 2017-04-07 20:43:32

Re: Bad HDMI signal integrity, or am I doing it wrong?

#6 2017-04-07 23:19:57

Re: Bad HDMI signal integrity, or am I doing it wrong?

#7 2017-04-08 00:52:48

Re: Bad HDMI signal integrity, or am I doing it wrong?

#8 2017-04-08 01:03:44

Re: Bad HDMI signal integrity, or am I doing it wrong?

#9 2017-04-08 04:03:51

Re: Bad HDMI signal integrity, or am I doing it wrong?

#10 2017-04-08 10:12:51

Re: Bad HDMI signal integrity, or am I doing it wrong?

#11 2017-04-08 12:55:02

Re: Bad HDMI signal integrity, or am I doing it wrong?

#12 2017-04-08 19:12:02

Re: Bad HDMI signal integrity, or am I doing it wrong?

#13 2017-04-08 21:05:42

Re: Bad HDMI signal integrity, or am I doing it wrong?

#14 2017-04-09 06:12:45

Re: Bad HDMI signal integrity, or am I doing it wrong?

#15 2017-04-09 12:20:41

Re: Bad HDMI signal integrity, or am I doing it wrong?

#16 2017-04-15 07:18:46

Re: Bad HDMI signal integrity, or am I doing it wrong?

#17 2017-04-15 07:38:19

Re: Bad HDMI signal integrity, or am I doing it wrong?

#18 2017-05-06 21:06:03

Re: Bad HDMI signal integrity, or am I doing it wrong?

Board footer