(2016-03-21, 23:28)fisherman55 Wrote: Working for me!

(2016-03-21, 23:31)Matt Devo Wrote:

(2016-03-21, 23:28)fisherman55 Wrote: Working for me!

pretty sure Neil123 is referring to the link I provided him previously for force-loading a saved EDID at boot, not the general download links

(2016-03-22, 07:38)Neil123 Wrote: That I am. Would it work to sh in and delete the "cpio file". Chromebox works fine when connected directly to tv. So it is something with the EDID from my AVR how do I go about solving that.?

(2016-03-22, 17:27)andrej770 Wrote: Matt, Thanks for all you do. I have two Chromeboxes (one for the family and one I ticker with). In your opinion, which Dual boot setup is best for this level of tickering (new OS's from you, new builds, testing 17.0, etc.)? The OpenElec Dual boot or the Ubuntu Dual boot setup? From doing a lot of research, OpenElec is said to be faster, but I haven't tested it yet. But when new RC's come out or new Boot loaders come from you, which dual boot combo is best for this? Lastly, (I'm sure you'll provide a link), how does one update the firmware or boot OS you provide without a complete redo? I've read a lot of the post here and the wiki's and just need some clarification. Forgive me if I missed a post that explains all this already.

Thanks again!

(2016-03-22, 17:34)Matt Devo Wrote:

(2016-03-22, 17:27)andrej770 Wrote: Matt, Thanks for all you do. I have two Chromeboxes (one for the family and one I ticker with). In your opinion, which Dual boot setup is best for this level of tickering (new OS's from you, new builds, testing 17.0, etc.)? The OpenElec Dual boot or the Ubuntu Dual boot setup? From doing a lot of research, OpenElec is said to be faster, but I haven't tested it yet. But when new RC's come out or new Boot loaders come from you, which dual boot combo is best for this? Lastly, (I'm sure you'll provide a link), how does one update the firmware or boot OS you provide without a complete redo? I've read a lot of the post here and the wiki's and just need some clarification. Forgive me if I missed a post that explains all this already.

Thanks again!

dual boot OpenELEC for sure. There's rarely a need to update the legacy boot firmware component after the initial installation, but if you did want or need to, you would simply re-run the setup script from ChromeOS and choose the appropriate option from the menu. Updating OpenELEC is as simple as downloading the update file, dropping it in the update folder, and rebooting. If you need to start fresh, just re-run the dual boot option from the setup script and it will format/reinstall OpenELEC.

(2016-03-22, 18:45)aptalca Wrote: EDIT: Haha nevermind, I just saw that you have been committing to their github repo :-)

(2016-03-02, 23:12)Matt Devo Wrote:

(2016-03-02, 22:49)knives of ice Wrote: matt,

is there anything that a debug log would even show for this issue? not sure how i can go about trying to get it fixed.

thanks

if you're getting the same issue on the Krypton pre-beta builds, I'd post in those threads to get the attention of fritsch/Millhouse (with a debug log of course). If a fix can be identified, I can easily backport it to Jarvis

(2016-03-23, 00:57)knives of ice Wrote: finally had time to go back and check OpenElec official builds. not sure if you can backport or not but here are results

finally got a chance to test things with official OpenElec builds

5.08 - dual output works
6.03 - the dual output works no problem
6.95.1 - broken, only displays on one screen which flickers as well.

so it appears there has been some type of regression in the Jarvis builds perhaps? what i'm referencing if you don't remember is how video ouput from displayport/hdmi no longer works at the same time.

not really sure the best way to go about getting this fixed. it has been happening in Jarvis for quite some time i'm not sure where/when it started.

(2016-03-23, 01:03)Matt Devo Wrote:

(2016-03-23, 00:57)knives of ice Wrote: finally had time to go back and check OpenElec official builds. not sure if you can backport or not but here are results

finally got a chance to test things with official OpenElec builds

5.08 - dual output works
6.03 - the dual output works no problem
6.95.1 - broken, only displays on one screen which flickers as well.

so it appears there has been some type of regression in the Jarvis builds perhaps? what i'm referencing if you don't remember is how video ouput from displayport/hdmi no longer works at the same time.

not really sure the best way to go about getting this fixed. it has been happening in Jarvis for quite some time i'm not sure where/when it started.

As I mentioned in the other thread, this is unlikely to be an issue with Kodi itself, but more likely an OpenELEC/Intel driver/graphics subsystem issue. If we can identify the issue, I can get a fix integrated into the 7.0 branch (and final release), but at this point I'm not sure where to start looking - will need to talk to some of the other devs

(2016-03-23, 02:48)knives of ice Wrote: ok thanks. if there is anything you need log wise let me know. i'm not really sure what to do at this point to help out i posted a thread about it on the OpenElec forums as well.

(2016-03-23, 08:11)Matt Devo Wrote:

(2016-03-23, 02:48)knives of ice Wrote: ok thanks. if there is anything you need log wise let me know. i'm not really sure what to do at this point to help out i posted a thread about it on the OpenElec forums as well.

if I get some time I'll try to reproduce it here, and then elevate the issue to the other devs

(2016-03-24, 03:20)knives of ice Wrote: great, thanks so much. I'm surprised more people don't take advantage of the 2 outputs on the chromebox because it saves you from having to buy a 2nd box to another tv if you have the right setup. then again i'm lucky in that my 2nd receiver is directly below my living room tv so it is easy to drop the cord down.