HDMI to DVI-D Connection Issues


31 posts   Page 1 of 2   1, 2
by ozymands » Thu Dec 27, 2012 8:20 pm
I purchased the "recommended" HDMI to DVI-D cable from the pi hut (http://elinux.org/RPi_VerifiedPeripherals#HDMI-.3EDVI-D) ; when I try connecting my raspberry pi (series B) to my LED panel (a 22" computer display) with that cable it works fine.

However, when I try connecting it to the DVI-D connector on my 8 year old Hitachi Plasma TV, the image displays incorrectly - blacks are displayed as green.

The problem seems to occur only when I plug the rpi into that TV.

I can use the DVI-D port on that same TV with other video sources, no problem.

I've tried increasing config_hdmi_boost all the way to 10, and have the same problem. The only difference is that the whites in the image are brighter; but the blacks are all still green.

Could there be some kind of "color mode" setting, either on the TV or in the rpi, that I need to change to correct this problem?
Posts: 15
Joined: Thu Dec 06, 2012 2:11 am
by mahjongg » Thu Dec 27, 2012 8:32 pm
sounds like a broken cable, one of the color channels missing. did you try increasing drive level?

have you read the trouble shooting section of the wiki?
User avatar
Forum Moderator
Forum Moderator
Posts: 5696
Joined: Sun Mar 11, 2012 12:19 am
by ozymands » Thu Dec 27, 2012 8:36 pm
Thanks for the reply; yes, I read the troubleshooting section on the Wiki.

I've tried increasing the drive level (and setting config_hdmi_boost at levels from 4 to 10). Neither helped.

This problem occurs with multiple cables; it only occurs when the rpi is connected to the TV. The same cables work fine with my xbox 360; they also work fine when I connect my rpi to my 22" LED panel.
Posts: 15
Joined: Thu Dec 06, 2012 2:11 am
by mahjongg » Sat Dec 29, 2012 7:34 pm
Sounds like you have a pi with a broken hdmi connector, at least that seems the only reasonable conclusion. i suggest you trade it in under guarantee.
User avatar
Forum Moderator
Forum Moderator
Posts: 5696
Joined: Sun Mar 11, 2012 12:19 am
by ozymands » Sat Dec 29, 2012 11:01 pm
mahjongg wrote:Sounds like you have a pi with a broken hdmi connector, at least that seems the only reasonable conclusion. i suggest you trade it in under guarantee.


Thanks; I may do that. But if that were the case, wouldn't the problem occur on more than just the one monitor?
Posts: 15
Joined: Thu Dec 06, 2012 2:11 am
by dom » Sat Dec 29, 2012 11:35 pm
If you use (in config.txt)
hdmi_safe=1
do you get an image with the correct colours?
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4042
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by Deuce » Sun Dec 30, 2012 4:55 am
I'm seeing this same issue sometimes. For me, I have the following:

I have three good HDMI/DVI passive cables. All of them work in a number of applications, and I have four working DVI monitors.

On one of the monitors, I have a "black = green" issue. On the other three, I get no display at all. I've set the various config.txt options forcing DVI, forcing a specific mode, boosting up to 11, and hdmi_safe. No effect was noticed in any of them.

However, when I hook it up directly to my HDMI TVs, everything looks correct.

I've confirmed all this with a bench power supply running as high as 5.25V between TP1 and TP2. I'll likely grab a 'scope from work on Tuesday and check the HDMI output before I do an exchange, but that's the last thing I have left to check.
Posts: 13
Joined: Sun Dec 30, 2012 4:41 am
Location: Lake Forest, CA, USA
by ozymands » Sun Dec 30, 2012 1:40 pm
dom wrote:If you use (in config.txt)
hdmi_safe=1
do you get an image with the correct colours?


Nope, the image is still green.
Posts: 15
Joined: Thu Dec 06, 2012 2:11 am
by ozymands » Sun Dec 30, 2012 2:20 pm
Deuce wrote:I'm seeing this same issue sometimes. For me, I have the following:

I have three good HDMI/DVI passive cables. All of them work in a number of applications, and I have four working DVI monitors.

On one of the monitors, I have a "black = green" issue. On the other three, I get no display at all. I've set the various config.txt options forcing DVI, forcing a specific mode, boosting up to 11, and hdmi_safe. No effect was noticed in any of them.

However, when I hook it up directly to my HDMI TVs, everything looks correct.

I've confirmed all this with a bench power supply running as high as 5.25V between TP1 and TP2. I'll likely grab a 'scope from work on Tuesday and check the HDMI output before I do an exchange, but that's the last thing I have left to check.


Deuce; could you try grabbing the EDIDs from each of the monitors (using "tvservice -d") and attaching them to the thread? I'll do the same. Maybe by comparing the EDID information of the non-working with working monitors we can figure out what's going on.

Also, I'm wondering (and this is just a shot in the dark) if part of the problem is that my TV panel is reporting the wrong timing information (see http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=14178 ). I'm going to set the edid_format_smart_match=1 parameter the next time I have a free minute, and see what happens.
Posts: 15
Joined: Thu Dec 06, 2012 2:11 am
by Deuce » Sun Dec 30, 2012 7:42 pm
Attached... and I think I know the problem. All the monitors claim to support YCrCb 4:2:2. This explains the colours. It didn't make any sense that black would be green, blue and yellow would work AND whites are white, but I was thinking RGB only.

I wonder if there's a config.txt option to force RGB mode... I suspect that forcing RGB mode will fix the problems.
Posts: 13
Joined: Sun Dec 30, 2012 4:41 am
Location: Lake Forest, CA, USA
by Deuce » Sun Dec 30, 2012 10:13 pm
Seems the file attachments didn't work (a secret list of extensions aren't allowed apparently) here's the decoded data.

Code: Select all
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   5a 63 1c 4e 01 01 01 01 06 10
version:         01 03
basic params:    80 26 1e 78 2e
chroma info:     a1 65 a4 58 49 98 24 11 50 54
established:     bf ee 80
standard:        81 80 81 40 71 4f 61 59 45 59 31 59 31 0a 01 01
descriptor 1:    30 2a 00 98 51 00 2a 40 30 70 13 00 78 2d 11 00 00 1e
descriptor 2:    00 00 00 ff 00 50 55 52 30 36 30 36 30 31 39 31 33 0a
descriptor 3:    00 00 00 fd 00 32 55 1e 52 0e 00 0a 20 20 20 20 20 20
descriptor 4:    00 00 00 fc 00 56 41 39 31 32 2d 33 53 45 52 49 45 53
extensions:      00
checksum:        a9

Manufacturer: VSC Model 4e1c Serial Number 16843009
Made week 6 of 2006
EDID version: 1.3
Digital display
Maximum image size: 38 cm x 30 cm
Gamma: 2.20
DPMS levels: Off
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
Default (sRGB) color space is primary color space
First detailed timing is preferred timing
Established timings supported:
  720x400@70Hz
  640x480@60Hz
  640x480@67Hz
  640x480@72Hz
  640x480@75Hz
  800x600@56Hz
  800x600@60Hz
  800x600@72Hz
  800x600@75Hz
  832x624@75Hz
  1024x768@60Hz
  1024x768@70Hz
  1024x768@75Hz
  1152x870@75Hz
Standard timings supported:
  1280x1024@60Hz
  1280x960@60Hz
  1152x864@75Hz
  1024x768@85Hz
  800x600@85Hz
  640x480@85Hz
  640x400@70Hz
Detailed mode: Clock 108.000 MHz, 376 mm x 301 mm
               1280 1328 1440 1688 hborder 0
               1024 1025 1028 1066 vborder 0
               +hsync +vsync
Serial number: PUR060601913

Monitor ranges: 50-85Hz vertical, 30-82kHz horizontal, max dotclock 140MHz
Checksum: 0xa9 (valid)
EDID block does NOT conform to EDID 1.3!
   Name descriptor not terminated with a newline


Code: Select all
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   4c 2d ae 01 30 32 52 42 03 10
version:         01 03
basic params:    80 29 1f 78 2a
chroma info:     ee 95 a3 54 4c 99 26 0f 50 54
established:     bf ef 80
standard:        a9 40 81 80 81 40 71 4f 01 01 01 01 01 01 01 01
descriptor 1:    48 3f 40 30 62 b0 32 40 40 c0 13 00 98 32 11 00 00 1e
descriptor 2:    00 00 00 fd 00 38 4b 1e 51 11 00 0a 20 20 20 20 20 20
descriptor 3:    00 00 00 fc 00 53 79 6e 63 4d 61 73 74 65 72 0a 20 20
descriptor 4:    00 00 00 ff 00 48 56 46 41 31 30 34 33 39 39 0a 20 20
extensions:      00
checksum:        46

Manufacturer: SAM Model 1ae Serial Number 1112683056
Made week 3 of 2006
EDID version: 1.3
Digital display
Maximum image size: 41 cm x 31 cm
Gamma: 2.20
DPMS levels: Off
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@67Hz
  640x480@72Hz
  640x480@75Hz
  800x600@56Hz
  800x600@60Hz
  800x600@72Hz
  800x600@75Hz
  832x624@75Hz
  1024x768@60Hz
  1024x768@70Hz
  1024x768@75Hz
  1280x1024@75Hz
  1152x870@75Hz
Standard timings supported:
  1600x1200@60Hz
  1280x1024@60Hz
  1280x960@60Hz
  1152x864@75Hz
Detailed mode: Clock 162.000 MHz, 408 mm x 306 mm
               1600 1664 1856 2160 hborder 0
               1200 1201 1204 1250 vborder 0
               +hsync +vsync
Monitor ranges: 56-75Hz vertical, 30-81kHz horizontal, max dotclock 170MHz
Monitor name: SyncMaster
   Serial number: HVFA104399
 
Checksum: 0x46 (valid)


Code: Select all
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   4c 2d ae 01 30 32 52 42 1f 10
version:         01 03
basic params:    80 29 1f 78 2a
chroma info:     ee 95 a3 54 4c 99 26 0f 50 54
established:     bf ef 80
standard:        a9 40 81 80 81 40 71 4f 01 01 01 01 01 01 01 01
descriptor 1:    48 3f 40 30 62 b0 32 40 40 c0 13 00 98 32 11 00 00 1e
descriptor 2:    00 00 00 fd 00 38 4b 1e 51 11 00 0a 20 20 20 20 20 20
descriptor 3:    00 00 00 fc 00 53 79 6e 63 4d 61 73 74 65 72 0a 20 20
descriptor 4:    00 00 00 ff 00 48 56 46 4c 38 30 31 31 38 33 0a 20 20
extensions:      00
checksum:        24

Manufacturer: SAM Model 1ae Serial Number 1112683056
Made week 31 of 2006
EDID version: 1.3
Digital display
Maximum image size: 41 cm x 31 cm
Gamma: 2.20
DPMS levels: Off
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@67Hz
  640x480@72Hz
  640x480@75Hz
  800x600@56Hz
  800x600@60Hz
  800x600@72Hz
  800x600@75Hz
  832x624@75Hz
  1024x768@60Hz
  1024x768@70Hz
  1024x768@75Hz
  1280x1024@75Hz
  1152x870@75Hz
Standard timings supported:
  1600x1200@60Hz
  1280x1024@60Hz
  1280x960@60Hz
  1152x864@75Hz
Detailed mode: Clock 162.000 MHz, 408 mm x 306 mm
               1600 1664 1856 2160 hborder 0
               1200 1201 1204 1250 vborder 0
               +hsync +vsync
Monitor ranges: 56-75Hz vertical, 30-81kHz horizontal, max dotclock 170MHz
Monitor name: SyncMaster
   Serial number: HVFL801183
 
Checksum: 0x24 (valid)
Posts: 13
Joined: Sun Dec 30, 2012 4:41 am
Location: Lake Forest, CA, USA
by Deuce » Sun Dec 30, 2012 10:24 pm
Setting the pixel format in the config.txt file doesn't seem to make any difference... the display appears the same regardless of what value (0-3) I set for hdmi_pixel_encoding which suggests to me that it's not being honoured.

The list of things I've tried frobbing with the 204T (the only one that shows anything) is:
    hdmi_force_hotplug=1
    hdmi_group=2
    hdmi_pixel_encoding=[0,1,2,3]
    hdmi_set_spd=9
    hdmi_pixel_clock_type=[0,1]
    hdmi_mode=[4,51]
    hdmi_drive=1
    avoid_edid_fuzzy_match=1
    config_hdmi_boost=[4,7,11]
    hdmi_ignore_edid=0xa5000080
    framebuffer_depth=[8,16,24,32]
    hdmi_safe=1

Of all of these, only hdmi_safe and hdmi_mode make visible differences. I've also created an EDID file without the YCbCr mode and used hdmi_edid_file=1
Posts: 13
Joined: Sun Dec 30, 2012 4:41 am
Location: Lake Forest, CA, USA
by dom » Sun Dec 30, 2012 10:28 pm
Deuce wrote:I wonder if there's a config.txt option to force RGB mode... I suspect that forcing RGB mode will fix the problems.

Zip the edid.dat up and then you can attach it.

You can try adding:
hdmi_pixel_encoding=<n>

to config.txt. n can be:

HDMI_PIXEL_ENCODING_RGB_LIMITED = 0
HDMI_PIXEL_ENCODING_RGB_FULL = 1,
HDMI_PIXEL_ENCODING_YCbCr444_LIMITED = 2,
HDMI_PIXEL_ENCODING_YCbCr444_FULL = 3,
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 4042
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge
by Deuce » Sun Dec 30, 2012 10:34 pm
Archive attached. 204T-fixed.edid is the one with YCbCr disabled.

I've tried all four pixel formats with no change... I also updated the firmware today.
Attachments
EDIDs.zip
Archive of EDID dumps. 204T.edid is the monitor which has an incorrect display.
(1.05 KiB) Downloaded 34 times
Posts: 13
Joined: Sun Dec 30, 2012 4:41 am
Location: Lake Forest, CA, USA
by mob-i-l » Sun Dec 30, 2012 11:00 pm
I have exactly the same problem with my monitors and DVI-D.

One screen is substitutes green for black and has this edid: http://rpi.orbin.se/lg-flatron-l1932p.edid

The other is completely black (no signal after a while) and has this edid: http://rpi.orbin.se/hp-1740.edid (I had to extract it using SSH from another computer.)

My Raspberry Pi and HDMI-cable works well with a TV-set. Both screens have worked temporarily with correct colors but I might have had other settings then in config.txt. I use a DVD-D adapter with the HDMI-cable. I have tried config_hdmi_boost=5. I also tried hdmi_safe=1.
Posts: 96
Joined: Sat Dec 29, 2012 2:45 am
Location: Lund, Skåne/Scania, Sweden
by ozymands » Sun Dec 30, 2012 11:22 pm
Hmm. Did you still have hdmi_ignore_edid=0xa5000080 set? Maybe some other setting is preventing the color settings from taking hold.
Posts: 15
Joined: Thu Dec 06, 2012 2:11 am
by Deuce » Sun Dec 30, 2012 11:53 pm
Nope, I've tested it by itself and with other combinations. The pixel format option doesn't seem to work. Which, since there's only one format supported by both the Pi and the monitor (RGB) makes sense.
Posts: 13
Joined: Sun Dec 30, 2012 4:41 am
Location: Lake Forest, CA, USA
by ozymands » Tue Jan 01, 2013 2:50 pm
Deuce wrote:Archive attached. 204T-fixed.edid is the one with YCbCr disabled.

I've tried all four pixel formats with no change... I also updated the firmware today.


What utility are you using to dump the EDID? I'll do the same, I just want to make sure I post mine in the same format.
Posts: 15
Joined: Thu Dec 06, 2012 2:11 am
by Deuce » Wed Jan 02, 2013 2:04 am
Posts: 13
Joined: Sun Dec 30, 2012 4:41 am
Location: Lake Forest, CA, USA
by mob-i-l » Thu Jan 03, 2013 12:58 pm
You can see my green screen in this video: http://youtu.be/UYA69vPzeqA?t=1m3s
It works well in VGA with all colors but when I use HDMI to DVI-D-converter with Raspberry Pi I get this mostly green screen. I have not tested this monitor yet with another HDMI-device. I have not tested the HDMI to DVI-D-adapter with another monitor successfully. My only other monitor with DVI-D is completely black. I have tested my RPi and HDMI-cable with a TV-set and that worked well.

Right now I'm mostly using my RPi with TightVNC (i.e. it sends the RPi screen to another computer).
Raspberry Pi A @ 700MHz & Raspberry Pi B2 @ 800MHz w/ Raspbian (from NOOBS Lite). Started w/ BASIC on ABC80 & ZX81 then Forth, Z80… http://scratch.mit.edu/users/mobluse/ https://www.youtube.com/user/MOBiL4u/ https://twitter.com/MOB_i_L/
Posts: 96
Joined: Sat Dec 29, 2012 2:45 am
Location: Lund, Skåne/Scania, Sweden
by Deuce » Thu Jan 03, 2013 6:32 pm
That's how mine looks as well.
Posts: 13
Joined: Sun Dec 30, 2012 4:41 am
Location: Lake Forest, CA, USA
by Deuce » Thu Jan 03, 2013 8:51 pm
So, with my Pi at work, the Samsung 204Bs that I have there still do not work at all, but the Delll P2312Ht works perfectly. A bunch of meaningless correlations can be draw from this small sample size.

    1) Older monitors don't work in varying degrees
    2) Widescreen monitors DO work
    3) Samsung monitors suck

I'll try a few more monitors and update here with EDIDs.
Posts: 13
Joined: Sun Dec 30, 2012 4:41 am
Location: Lake Forest, CA, USA
by ozymands » Thu Jan 03, 2013 8:58 pm
Deuce; were you at least able to change resolutions on the non-working monitors by changing settings in config.txt?
Posts: 15
Joined: Thu Dec 06, 2012 2:11 am
by Deuce » Thu Jan 03, 2013 9:18 pm
Yes. hdmi_mode and hdmi_safe both seem to behave as they should.
Posts: 13
Joined: Sun Dec 30, 2012 4:41 am
Location: Lake Forest, CA, USA
by Deuce » Fri Jan 04, 2013 9:02 pm
I've ordered a second Pi, so when it arrives, I'll update this thread.
Posts: 13
Joined: Sun Dec 30, 2012 4:41 am
Location: Lake Forest, CA, USA