It really shouldn't require changing the LDFLAGS. I'll take a look and commit a patch if needed in the next day or two.

Incidentally, If libsdl1.2-dev is installed, SyncTERM can run in a graphics mode which more accurately shows CP437 (and others) as well as Commodore 64 and other oddball modes.

Here's what I suspect may be the problem. Assuming the top left is pin 1... all the other joints on both D2 and D3 look like 4 and 5.

Confirmed, the second Pi does not have the same issue. Inspection shows what may be a solder bridge on D3 between pins 2 and 3. This weekend I'm going to try reworking that and see if it fixes the problem.

I've ordered a second Pi, so when it arrives, I'll update this thread.

Yes. hdmi_mode and hdmi_safe both seem to behave as they should.

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...

That's how mine looks as well.

I'm using edid-decode from here:
http://cgit.freedesktop.org/xorg/app/edid-decode/

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.

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.

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 ...

Seems the file attachments didn't work (a secret list of extensions aren't allowed apparently) here's the decoded data. 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...

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...

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...