My Pi only outputs DVI, not HDMI

You would of hoped the PI/TV combo would of auto configured even if there was only a narrow range of workable modes. Your use of the monitor seems to preclude anything fundamentally wrong with the PI+.

I would probably start by checking the SHA checksum of the binary I downloaded if OK then re write it on to the SDCard and try again.

I there's a problem with the checksum you will need to re-download the whole lot again unfortunately.

When you boot initially make sure the monitor/TV is already plugged in etc and let the Automagical-stuff set up the device it works 99.9% of the time so really should be no reason not here.

Thanks for the suggestions.

I have now

1) tried Berryboot - I get nothing on the TV but if I switch the cable to the DVI I get the config screen

2) tried a new download of OpenELEC - I get nothing on the TV but it's fine on the DVI monitor. Interestingly the config options within OpenElec for screen resolution are only 3 options, rather than the ten or so a friend of mine gets on his, and none of those match the native resolution of the monitor.

That makes 4 complete OS variants, from 3 sources.  3 PSUs.  2 HDMI cables.  2 TVs.  I'm coming to the conclusion that it's Pi hardware fault of some sort ?

What HDMI standard on the TV? Is it 1.4 or something more advanced than the level for the Pi? What is the TV and model we are talking about?

Clem

The TVs are: Pioneer 43" plasma circa 2007, Some generic thing from Tesco circa 2009.  Not new by any stretch.  No idea what standards they support, I'm afraid.  NOTE that I set it all up on Christmas day on the Pioneer without any trouble - it just worked out of the box.

Thanks again for the continuing efforts

Really, you're having a weird problem: HDMI is just DVI with sound added. And different connectors. But electrically it is the same. This leads me to say: If your TV displays the image when you use a DVI cable, but not when you use an HDMI cable then the problem is more likely in the tv or the HDMI cable. So: Is the HDMI port on your TV working? (I believe you've said you've tested the HDMI cable, already, right?) Maybe you need to push some buttons on the TV to get it to display the image on that HDMI port?

Hi, thanks for the suggestion.  I use the Pioneer TV every day on HDMI for Sky or Blu-ray, using the same HDMI socket, so it's not that.  Don't use the HDMI on the other TV.  I have one more (newer) TV I could try, but that involves unmounting it from the wall which I'm trying to avoid .

So far I've tried: 2 TVs, 3 PSUs, 2 cables, 4 software installations, 2 MicroSD cards.  I hear what you're saying about HDMI being electrically the same as HDMI.  My guess is that the Pi is consciously deciding not to use HDMI and using DVI modes instead.

To recap an earlier post, one of the OS installations was the Raspbian I've been using over SSH for a few months (running my VPN server) and I've been into that and tried very very many combinations of switches in /boot.config.txt to no avail. I can change the screen resolution on the DVI monitor by choosing a hdmi_group=2, but if I try say group=1/mode=19 (720p 50Hz) it just outputs DVI in some default mode.

If I still had the unadulterated config.txt that came with it I could try that, but like a donkey I went in and changed it without backing it up. D'Oh!

Update !!!!!

I decided to take the newer TV off the wall so I cold get to the HDMI, and that works !  This is currently running BerryBoot and it's only got to the setup screen so far, but that's something, right ?

SO why can't it output to my Pioneer TV (which is older I accept, but worked fine when I set it all up on Christmas day).

I'm going to go through the setup and see if I can choose a mode that the older TV should be able to display, the try switching it over.

As so often, I don't have a ready-made answer for you. But your suggestion about using DVI modes is unlikely. There are a bunch of modes that are "common on DVI and uncommon on HDMI" that are grouped as DVI modes. And the other way around.

The 'pi asks the monitor (HDMI or DVI both cases): " What mode would you like?" The monitor/tv/whatever then gets to answer: "I'd prefer XXX x YYY, as that's my native mode, but if you can't handle that, these other modes are fine as well. " Suggestion: In theory it should be able to do this with the TV turned off. But just in case, turn on the TV before you power up the 'pi. (I have once encountered a screen that was not designed according to spec, and didn't allow the query when powered down).

Once booted into raspbian or something like that, you might be able to list these for yourself:

tvservice -n

(What's your name?)

tvservice -m DMT

(What DVI modes do you  like?)

tvservice -m CEA

(what HDMI modes do you accept?)

My monitor is a VGA monitor (analog) with an adapter. It lists 12 DMT (DVI) modes(3 variants of 640x480, 4x 800x600, 3x 1024x768, and two 1280x102), preferring the 1280x1024@60Hz. And it lists no CEA (HDMI) modes.

Thanks - I'll certainly try those.  I was looking at another post on OpenElec forum and he listed similar suggestions, but eventually he said he'd sent his Pi back and the replacement worked fine !

http://openelec.tv/forum/67-display/69592-no-signal-on-hdmi

I guess the theory is to check the supported modes, then assuming I get a sensible response, see if I can select those manually through config.txt ?  Let's see what it reports first.

Thanks again

http://www.pioneerelectronics.com/ephox/StaticFiles/PUSA/Files/Car-Firmware/xx4CMX_DRIVER.zip

for a http://www.pioneerelectronics.com/PUSA/Professional/Plasma/PDP-434CMX tv are windows drivers.

These appear to be 720P HDMI 1.2 ish...

Clem

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.

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