(2015-07-20, 17:25)PityOnU2 Wrote: Having some issues with my Asus Chromebox here. Running standalone Openelec 5.0.8. Using the most up-to-date version of your BIOS as well.

If I turn on the Chromebox before my AV unit (Yamaha RX-V773), it does not send any signal to the AV unit (case 1). If I do it the other way around (AV unit and then Chromebox), everything works as expected (case 2).

I am able to get the Chromebox to display on my TV in case 1 if I manually run "xrandr --output HDMI1 --auto" after everything is turned on. However, adding that to autostart.sh still results in case 1.

Any thoughts?

(2015-07-20, 18:21)sammydottee Wrote: I have the Samsung i5 Chromebox, and when the box is left on overnight, nothing seems to work until I try to switch back and forth making active the wireless and wired connections.

(2015-07-20, 17:36)Matt Devo Wrote:

(2015-07-20, 17:25)PityOnU2 Wrote: Having some issues with my Asus Chromebox here. Running standalone Openelec 5.0.8. Using the most up-to-date version of your BIOS as well.

If I turn on the Chromebox before my AV unit (Yamaha RX-V773), it does not send any signal to the AV unit (case 1). If I do it the other way around (AV unit and then Chromebox), everything works as expected (case 2).

I am able to get the Chromebox to display on my TV in case 1 if I manually run "xrandr --output HDMI1 --auto" after everything is turned on. However, adding that to autostart.sh still results in case 1.

Any thoughts?

your Yamaha isn't properly returning valid EDID data when in standby, so you have three options:

1) replace it with a receiver that works properly
2) capture the EDID data when powered on, then force load it at startup so the receiver's power state doesn't matter.
3) always power up the ChromeBox after your AVR

I don't have a link handy for #2, but think the info should be out there. I'll try to find it later and add it to the wiki

(2015-07-20, 23:22)PityOnU2 Wrote: Thanks for the info. I will choose option 2.

Finding a guid on how to do option 2 is a bit difficult, though. Here is an old guide for nVidia chipsets, which seems convoluted and doesn't apply to this box. I followed the guide here to the letter, but it doesn't seem to have done anything.

Did you ever come up with that link to an updated guide?

(2015-07-20, 23:22)PityOnU2 Wrote: ...
Thanks for the info. I will choose option 2.

Finding a guid on how to do option 2 is a bit difficult, though. Here is an old guide for nVidia chipsets, which seems convoluted and doesn't apply to this box. I followed the guide here to the letter, but it doesn't seem to have done anything.

Did you ever come up with that link to an updated guide?

(2015-07-21, 15:39)Boulder Wrote: After changing my receiver from Yamaha RX-V567 to an Anthem MRX300, I have two open questions:

1) I've noticed that sometimes 23.976 fps content is skipping a frame here and there. If I check the output frame rate with the popup menu in Kodi (in the W section there), it shows 23.98 fps. The receiver says 24p and the TV shows that it's in 24 Hz mode. I have tried setting the receiver to enable/disable film mode auto detection and also set it to passthrough to my TV but they don't seem to have any effect. This would point to the fact that the Chromebox might be causing the skips. So: what should the W section show for the output fps for 23.976 fps material? If I playback true 24p content, it does say 24 fps.

Quote:2) Now that I see everything that prints out on the screen during bootup, I've noticed that the Chromebox spends a lot of time trying to boot from CD/DVD. I have set it so that it should boot Kodi as fast as possible so is there anything to correct this issue? I do have an external HDD attached via USB which seems to be the device that the Chromebox tries to boot even if that option is disabled with your excellent script.

(2015-07-21, 17:41)Matt Devo Wrote:

(2015-07-21, 15:39)Boulder Wrote: After changing my receiver from Yamaha RX-V567 to an Anthem MRX300, I have two open questions:

1) I've noticed that sometimes 23.976 fps content is skipping a frame here and there. If I check the output frame rate with the popup menu in Kodi (in the W section there), it shows 23.98 fps. The receiver says 24p and the TV shows that it's in 24 Hz mode. I have tried setting the receiver to enable/disable film mode auto detection and also set it to passthrough to my TV but they don't seem to have any effect. This would point to the fact that the Chromebox might be causing the skips. So: what should the W section show for the output fps for 23.976 fps material? If I playback true 24p content, it does say 24 fps.

the Kodi framerate display isn't all that accurate/precise. The skipped/dropped frame count is the way to tell if bad things are happening. What you're describing sounds like 23.976 content being played back at 24p.

Quote:what do you mean by "spends a lot of time trying to boot from CD/DVD" ? When external bootable devices are connected, the firmware gives you 5s to press ESC for the boot menu. If no key is pressed, it will (should) default to the internal HDD unless you selected the USB option when flashing/updating. Now, regardless of the default boot device, prior to displaying the 'Press ESC' text, the firmware will probe/initialize any connected devices, so if you have an external device that's taking a while to init, that could be the issue. Not much I can do about that except recommend a better power supply and/or tell the manufacturer to fix their buggy firmware

(2015-07-21, 20:08)Boulder Wrote: ]I mean after the wait for ESC is finished. After that it says "Booting from DVD/CD.." and then says "Boot failed. Cannot read from CDROM". My external HDD (WD Elements) should be up and running by the time the ESC wait is done, a similar device takes a few seconds to spin up on my desktop computer.

I have tried reflashing the latest SeaBIOS with the script and made sure that I have set it to boot directly from the internal HDD but it didn't change anything.

(2015-07-21, 20:36)knives of ice Wrote: Just wondering if anyone using a chromebox ever has issues where you hit pause, skip, etc and these graphics will not go away for a little bit even after the material is playing fine?

i discuss this with a log and video here:

http://forum.kodi.tv/showthread.php?tid=228594&pid=2057776#pid2057776

there are a few of us with chromebox's that have the issue and some have thought it could be hardware related, though i don't think it is at all since the problem goes away immediately when running Helix.

(2015-07-21, 21:02)Matt Devo Wrote:

(2015-07-21, 20:08)Boulder Wrote: ]I mean after the wait for ESC is finished. After that it says "Booting from DVD/CD.." and then says "Boot failed. Cannot read from CDROM". My external HDD (WD Elements) should be up and running by the time the ESC wait is done, a similar device takes a few seconds to spin up on my desktop computer.

I have tried reflashing the latest SeaBIOS with the script and made sure that I have set it to boot directly from the internal HDD but it didn't change anything.

that's not supposed to be the case - for some reason SeaBIOS thinks your HDD is a CD/DVDROM and is giving it priority. shoot me a PM or hit me up on IRC and I'll have you pull a firmware boot log so I can figure out what's going on.

(2015-07-21, 20:36)knives of ice Wrote: Just wondering if anyone using a chromebox ever has issues where you hit pause, skip, etc and these graphics will not go away for a little bit even after the material is playing fine?

i discuss this with a log and video here:

http://forum.kodi.tv/showthread.php?tid=228594&pid=2057776#pid2057776

there are a few of us with chromebox's that have the issue and some have thought it could be hardware related, though i don't think it is at all since the problem goes away immediately when running Helix.

can't reproduce here, either with OE 5.95.3, nor Fritsch's new VAAPI builds