My Pi only outputs DVI, not HDMI

I actually managed to find the manual for the TV (PDP-436SXE) and it states HDMI1.1

It also lists the screen modes, so I'll try some of those, although I thought I had already.

Can't do this until this afternoon probably.

Thanks

Tim

IIRC, my HP3220 is the only display device I've ever seen that claims to support a mode it doesn't.

I have had a similar issue with one of my older visio  TVs  changing cables etc didn't work.  I eventually found disconnecting the hdmi cable from the tv unplugging the TV then powering up the TV then the device the problem resolved. 

I've tried various combinations of powering down/up - no difference. Thanks anyway

I have now run a tvservice -n / -M DMT / -m CEA with the pi connected to all three TVs (the one that works plus the two that don't). In all cases I'm getting back identical results ! (see the bottom of this post).

Also been through trying every mode supported (according to the Pioneer manual) - no luck.  Initially I got Group 1 and 2 mixed up (I'm sure they're listed somewhere the other way around !)  So all the modes I tried were group=1 which I hope is CEA.  I did this by modifying config.txt and rebooting.

Modes tested were :

Pioneer manual          mode

1920x1080i@50hz     1, 20

720*576p@50Hz       1, 17

1080*720p@50Hz      1, 19

1920*1080i@60Hz     1, 5

720*480p@60Hz        1, 2

1280*720p@60Hz       1, 4

Nothing worked.

Here's the output from the tvservice calls (same for all 3 TVs, which sounds unlikely to be correct)

-----------------------

device_name=SAM-SyncMaster

Group DMT has 19 modes:

           mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive

           mode 5: 640x480 @ 72Hz 4:3, clock:31MHz progressive

           mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive

           mode 8: 800x600 @ 56Hz 4:3, clock:36MHz progressive

           mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive

           mode 10: 800x600 @ 72Hz 4:3, clock:50MHz progressive

           mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive

           mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive

           mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive

           mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive

           mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive

           mode 28: 1280x800 @ 60Hz 16:10, clock:83MHz progressive

           mode 32: 1280x960 @ 60Hz 4:3, clock:108MHz progressive

           mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive

           mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive

           mode 47: 1440x900 @ 60Hz 16:10, clock:106MHz progressive

           mode 48: 1440x900 @ 75Hz 16:10, clock:136MHz progressive

           mode 51: 1600x1200 @ 60Hz 4:3, clock:162MHz progressive

           mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive

Group CEA has 14 modes:

           mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive

           mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive

           mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive

           mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive

           mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced

  (native) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive

           mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive

           mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive

  (native) mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive

           mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced

  (prefer) mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive

           mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive

           mode 33: 1920x1080 @ 25Hz 16:9, clock:74MHz progressive

           mode 34: 1920x1080 @ 30Hz 16:9, clock:74MHz progressive

I know it worked straight out of the box on the Pioneer because I remember sitting in front of it setting it up on Christmas Day 4 months ago.  If anyone can post the default config.txt file (or contents) I'll try that.

disable_overscan=1

start_x=1

gpu_mem=128

From my config.txt

Clem

Thanks for another suggestion. Sadly it didn't help.  If this was my PC I'd assume that some windows update had screwed something up - I assume that apt-get update is not likely to have done something bad ?  If there had been something equivalent to an updated display driver which didn't support HDMI v1.1 any more, and that was pushed put through an update and bundled into all the other OS combinations I've tried it might explain it, but that still wouldn't explain why NOOBS doesn't show either on the TV, would it.  It all sounds rather unlikely.

Just in case I have gone back to NOOBS (1.3.9) and re-installed Raspbian from that.  No better. I can't find a download of NOOBS 1.3.9 anywhere - it's all 1.4.0 (which I tried and also doesn't work).

I just can't understand how it worked on 2 TVs and a monitor straight out of the box on Christmas day, but now won't work on any of those, but still works on another TV and monitor, despite reloading everything.  It just sounds like a hardware fault to me.  I'm just about ready to chuck it all back in the box and send it back.

Sorry I could not help you. It may be the HDMI 1.1 standard is not supported by newer software on Raspberry Pi. Since you have berry boot, try another OS maybe.

Clem

Hi Clem (and everyone else who had replied),

Thanks for all the suggestions. I'm going to contact the people I bought it through and see what they have to say.  If I get any solution I'll post it here for info, although I admit the original title is probably not especially helpful given the place I'm at now.

Thanks again

Tim