Solved NUC running OpenELEC works on one TV, not another
#1
Hi all, tearing my hair out and it was suggested I post here, I hope I've included enough detail. Apologies if I've left anything out. (Original post: here).)

I have a NUC (the 2820 Bay Trail version) with OpenELEC 4.2.1 currently installed that has worked without incident for a year on one of my 2 Pioneer plasma TVs (a KRP-500M). Having bought another NUC for the other TV (a Pioneer LX5090) I cannot see anything beyond the NUC splash screen with either the old or the new NUC. I can F2 into bios and make changes, etc. so the HDMI connection is working that far at least. As it turns out OpenELEC is starting, I just can't see anything on the LX5090 after the initial NUC splash screen (I don't even get the OpenELEC screen during the boot process). I've tried various inputs and cables, all with no joy, just a black screen.

When I ssh into the box and run xrandr it tells me that HDMI1 is disconnected, so I can't even see what modelines it's willing to accept. There's just no evidence that OpenELEC is finding the screen at all.

Anyway, I've used one of the NUCs (the older one) to perform some identical steps on each of the TVs and have saved the debug logs in the hope that somebody here might be able to shed some light.

I first connected the NUC to the (working) KRP500, booted it up, used the Yatse app to start and stop a movie, and then posted the resulting debug log file to
http://sprunge.us/TBPF

Next, I connected the same NUC to the (not working) LX5090, booted it up, used the Yatse app to start and stop the same movie (and was able to confirm via the app that it was indeed playing, although I could not see it on the TV) and posted the resulting debug log file to
http://sprunge.us/hICb

Eyeballing the results without any knowledge whatsoever, it seems that no video modes are returned from the LX5090 at all. Does anyone have any ideas as to how I might proceed? At the moment I'm concerned that I now have an expensive doorstop.

I should also say that this is the first item to give HDMI problems on this TV. Everything else (DVD players, Blu ray players, games consoles, Chromecast, laptop running Windows 7, etc.) has worked without incident.
Reply
#2
The only difference I can see so far is the fact, that the working TV provides a proper EDID:

Quote:20:40:05 T:140254277613376 NOTICE: Device 3
20:40:05 T:140254277613376 NOTICE: m_deviceName : hdmi:CARD=PCH,DEV=0
20:40:05 T:140254277613376 NOTICE: m_displayName : HDA Intel PCH
20:40:05 T:140254277613376 NOTICE: m_displayNameExtra: HDMI
20:40:05 T:140254277613376 NOTICE: m_deviceType : AE_DEVTYPE_HDMI
20:40:05 T:140254277613376 NOTICE: m_channels : FL,FR,BL,BR,FC,LFE,SL,SR
20:40:05 T:140254277613376 NOTICE: m_sampleRates : 32000,44100,48000,88200,96000,176400,192000
20:40:05 T:140254277613376 NOTICE: m_dataFormats :

As you can see in the line "m_displayNameExtra" no info is given here which differs for the following:

Quote:20:15:50 T:140299740366656 NOTICE: Device 3
20:15:50 T:140299740366656 NOTICE: m_deviceName : hdmi:CARD=PCH,DEV=0
20:15:50 T:140299740366656 NOTICE: m_displayName : HDA Intel PCH
20:15:50 T:140299740366656 NOTICE: m_displayNameExtra: PIO PIONEER-M on HDMI
20:15:50 T:140299740366656 NOTICE: m_deviceType : AE_DEVTYPE_HDMI
20:15:50 T:140299740366656 NOTICE: m_channels : FL,FR
20:15:50 T:140299740366656 NOTICE: m_sampleRates : 32000,44100,48000
20:15:50 T:140299740366656 NOTICE: m_dataFormats :

Here you can see the "PIO PIONEER-M on HDMI". So your other TV doesnt support proper EDID, I suppose. Do you use any adapters, switches or anything else on that TV or did you plugged it in directly?
Reply
#3
Thank you. No, there's nothing added to the mix here, just a direct connection to the tv with a good quality cable. Admittedly the cable is about 6 years old, but I wouldn't have expected that to cause a problem. Still, you have me wondering whether the nuc is expecting a version of HDMI that the cables to that tv aren't specced to provide. Hmmm...
Reply
#4
HDMI cables are compatible with all versions.
Reply
#5
Problem is solved, something simple as usual.

The comment about cables got me thinking, I started googling around looking for reasons why the EDID might not be successfully read at all, and one of the pages pointed out that the +5V pin that triggers the EDID read is actually set slightly further back than the others, so if the cable connector is slightly out of the socket it won't connect and the EDID won't be read. For whatever reason, the HDMI cables connected to the LX5090 and set into the wall behind the TV all have a kind of "stop" (so the classic HDMI shape doesn't go all the way to the back) so the net effect was that the connector wasn't going far enough into the socket. All 3 cables, despite being different, have the same shape connector, and all 3 were suffering from this. Can you believe it? I found a HDMI female-male adapter lying around that cost nearly nothing, and plugging that into the NUC allows the cables to make a full connection, EDID gets read, and lo-and-behold, OpenELEC is now working perfectly.

I'm glad this has been resolved but I feel like a bit of an idiot. Let's never speak of this again.
Reply

Logout Mark Read Team Forum Stats Members Help
NUC running OpenELEC works on one TV, not another0