2016-09-15, 02:03
(2016-09-14, 23:44)RayTrace77 Wrote: Yeah that's what I did earlier today, I followed the guide in the link below to set a custom xorg.conf which used an extracted edid but that made no difference, still no video out, I just resumed it from sleep now(while my other equipment was already on) and it STILL didn't send in video through, I extracted all the logs and have uploaded them to the link below, if anyone can take a look, I looked through all of the dmesg logs but couldn't tell which message shows how it was turned on.
custom xorg link:
http://wiki.openelec.tv/index.php/Config...#tab=Intel
my kodi logs:
https://dropfile.to/i5IbRzO
(2016-09-15, 01:50)RayTrace77 Wrote: So I did some more testing, my setup is as below:
ChromeBox > LG System > TV
It seems to be an issue with the LG System, connecting the Chromebox directly to the TV and restarting 6-7 times and suspending/resuming seemed fine, only when going through the LG System does the no video issue kick in, if the Chromebox is on BEFORE the LG System is on then most of the time there is nothing I can do to get the Chromebox to output video, not even reboots, not even using xrandr to send output to HDMI1, only a power off on the Chromebox and back on brings video back, there has been 1 or 2 times where in this situation using xrandr has working in bringing video back, but it's 50/50 wether it works or not.
I reverted back to OpenELEC 5.0.8 which seemed to be a bit more stable, as long the LG System was on before the Chromebox, rebooting and resuming seemed to go ok, I'm at a complete and utter loss here, it's so intermittent and I've been trawling through the logs to try and identify what is going on but can't find anything that would explain it, then there's the issue of it randomly turning itself on, it did it 2 times, in the link below is the logs for when it did it, would anyone be able to tell me what turned the Chromebox on in the logs below ?
https://dropfile.to/JoVjScV
these logs tell me:
- you're still running the stock firmware -- is this a dual boot setup?
- you didn't implement the EDID loading as described in the link; the xorg file isn't what you need, the EDID is
- the PS3 DB remote woke the system from sleep
the custom EDID will likely address the issues caused by the LG system and the newer Intel drivers
