[jsp1]

Yeah, it is no big deal. I think perhaps the box resumes faster than my AVR is capable of detecting or something. I'll check in with OE chat when I get some time.

I did some googling on the issue. Really haven't had a chance to implement the supposed fixes, but it appears it has something to do with HMDI CEC+ Anynet connections. Basically, when you "power" off your AVR, it may / may not allows a passthrough HDMI connection to a connected TV which your Chromebox tries to "adjust" to on the fly. So when you resume, it remembers the passthrough connection as the last audio driver and not the correct default AVR connection.

I have the same issue with my Chromebox, that when / if power it on without my AVR turned on first, I get no video because Chromebox thinks there are no active video outputs connected at the time it powered on. I fixed that by making the Harmony power this on last when I start the activity, but it is definitely similar problem to the audio resume issue.

Now I wish I could turn off the "smart adjust on the fly" features of the XBMC (Chromebox). In other words, force it to always output HDMI#1 1920 x1080p and the same deault DENON HDMI audio driver even if God himself tells it otherwise or powers it on. In other words, I would love for XBMC to have a "I'm not paying you to think" checkbox and always default to the same audio / video settings REGARDLESS of what is connected to it. But alas this is wish-thinking and coding this via ssh is beyond my ability.

Makes a lot of sense, because when the issue occurs my Pioneer AVR is no longer listed under HDMI1 were it used to be. So the box remains on HDMI1 but somehow the handshake doesn't occur. It would be nice to just throw a reboot command in the autostart.sh file, but I have a feeling this isn't triggered after a resume.

While I'm at it, why no threads discussing video lockup? I know about this: https://bugs.freedesktop.org/show_bug.cgi?id=78960
but it is really lacking in any info and quite discouraging to be honest. I know it will take someone some (presumably) hard work to fix and I'm not trying to rush anyone...it just seems like it would be nice to post an update on possible progress every once in a while. Is the issue linux wide for haswell or chromebox specific? Anyone know?