[azimuth01]

I already did but Windows-related questions/issues have their own thread, so take things there please. Don't want that crap polluting this one ;-)

Oops! Sorry.

I will check the posts there, and will post my questions if I have any.

Thanks Matt and Soli..

[matf]

Thanks to the guide here I've successfully set up my HP Chromebox as dual-boot - and generally it's working perfectly! Using with PlexBMC, and Live TV streamed from a DVBLink server. I have encountered some issues:

1. Overscan settings not saved - there's a significant amount of overscan. I used the Video Calibration in Kodi to fix, but it appeared it wasn't saving after a reboot. SOLUTION: In the end, I went in via SSH and directly amended the guisettings.xml for every resolution combination shown and so far that seems to be working.
2. Crushed blacks - MAYBE SOLUTION: set the limit in Video settings: Settings -> System -> Video output -> Use limited color range (16-235). It's better, though I still think blacks look really, really black...I've read elsewhere in this thread that turning off VAAPI might help, so I'll try that but not sure if there are other consequences.
3. Suspend/Wake - Suspend works great, but when I wake it always reboots back to the Developer screen. Using Flirc and tried a variety of remotes. Lots of people here say suspend is working perfectly, so if anyone can help I'd be grateful!

Thanks Matt though - stunning piece of work.

[Roby77]

Thanks to the guide here I've successfully set up my HP Chromebox as dual-boot - and generally it's working perfectly! Using with PlexBMC, and Live TV streamed from a DVBLink server. I have encountered some issues:


2. Crushed blacks - MAYBE SOLUTION: set the limit in Video settings: Settings -> System -> Video output -> Use limited color range (16-235). It's better, though I still think blacks look really, really black...I've read elsewhere in this thread that turning off VAAPI might help, so I'll try that but not sure if there are other consequences.
3. Suspend/Wake - Suspend works great, but when I wake it always reboots back to the Developer screen. Using Flirc and tried a variety of remotes. Lots of people here say suspend is working perfectly, so if anyone can help I'd be grateful!

Thanks Matt though - stunning piece of work.

For me, using open elec, i leave option 16-235 unchecked and set limited for tv hdmi settings (on my pana vt60), if i change that value kodi graphics black and white washed out but the video doesn't get effect so i leave it unchecked

Cause black was too much black (i notice it in dark scene) i calibrated again the tv with +3 for brightness) and panel brightness mid

No problem for 1 and 3.

[Matt Devo]

Thanks to the guide here I've successfully set up my HP Chromebox as dual-boot - and generally it's working perfectly! Using with PlexBMC, and Live TV streamed from a DVBLink server. I have encountered some issues:

1. Overscan settings not saved - there's a significant amount of overscan. I used the Video Calibration in Kodi to fix, but it appeared it wasn't saving after a reboot. SOLUTION: In the end, I went in via SSH and directly amended the guisettings.xml for every resolution combination shown and so far that seems to be working.4

overscan settings are saved on a per-resolution/re-refresh rate basis, so if you have the option to auto-adjust the refresh rate to match video frame rate selected, you need to set the overscan settings for each refresh rate by either changing in the GUI or editing the xml as you did.

2. Crushed blacks - MAYBE SOLUTION: set the limit in Video settings: Settings -> System -> Video output -> Use limited color range (16-235). It's better, though I still think blacks look really, really black...I've read elsewhere in this thread that turning off VAAPI might help, so I'll try that but not sure if there are other consequences.

while it may be a color space issue, it might also just be a display calibration issue (or it could be both). If enabling 'use limited color range' still results in a picture with crushed blacks, I'd lean towards display calibration. Also, be sure that you have the video acceleration setting 'prefer VAAPI renderer' unchecked for the limited color range setting to take effect during video playback.

3. Suspend/Wake - Suspend works great, but when I wake it always reboots back to the Developer screen. Using Flirc and tried a variety of remotes. Lots of people here say suspend is working perfectly, so if anyone can help I'd be grateful!

known issue with the stock firmware + OpenELEC, and listed in the wiki. It's related to the TPM, which isn't usable by anything other than ChromeOS.

Thanks Matt though - stunning piece of work.

gracias

[fma965]

Matt, Your script doesn't seem to work at setting the USB as default, i loaded ubuntu 14 x64 and ran the script, updated the firmware and pressed y at the prompt but still boots internal ssd first.any ideas?

EDIT: i tried with chormiumOS and same thing, no errors just doesn't work, I even factory reset everything back to fully stock and then re-wrote the standalone firmware to it... but still nothing.

not sure what you tell you, just tested it and it works fine here. If you press ESC for the boot menu, you should see that any USB devices are now listed first, whereas previously the internal SSD was.

hi, thanks for the reply, nope i still see internal first, i have to press 2 still for USB HDD, is it cause i'm using a HP chromebox? i'm guessing your testing on a ASUS one? Thanks.

[Matt Devo]

Which chromebox has no effect. If I had to guess, it's either an issue with your input for the usb question or the headless one before it, or something weird with Ubuntu. Try running again but instead of answering N for the headless firmware just hit enter

[Freakshow999]

Hello All,

Is anyone aware of a suspend issue on the chromebox as of the latest firmware update?
System is an HP Chromebox running OpenElec native.
The suspend command was working perfectly with my remote control systems. I had a corrupt 5.08 OpenElec update so I updated to the latest firmware and did a fresh USB install of OpenElec.
Now when I send the suspend command via IR the unit goes into suspend and a split second later comes right back out of it.

Any suggestions would be appreciated? TIA

there's no suspend issues with the latest firmware and OE, most likely some device you have connected is causing the immediate wake from suspend. Check the kernel log to see which device or remove all peripherals and add them back one at a time.

Went through the logs and I couldn't find anything definitive in the Kodi log but found a weird error in the syslog. It ended up being a strange usb error due to the built in card reader. (I had added an sd card for more picture storage) pulled the card out and suspend is back to working normally. I just wanted to post it in case someone else runs into the same kind of issue.

[Matt Devo]

Went through the logs and I couldn't find anything definitive in the Kodi log but found a weird error in the syslog. It ended up being a strange usb error due to the built in card reader. (I had added an sd card for more picture storage) pulled the card out and suspend is back to working normally. I just wanted to post it in case someone else runs into the same kind of issue.

thanks for reporting the resolution

[Tyler Durden]

I finally got around to getting my Chromebox and installing OE with this script.
Works great and had no problems (apart from finding the right keyboard for the installation)

One tiny issue I have with mine however is that it doesn't seem to detect my Gigabit ethernet at all... I've tried many devices on the same cable and different ports but the Chromebox just doesn't detect it.

Anyone else have issues with theirs running through gigabit ethernet?

Me! I am having this issue. The box just doesn't react in any way to having an ethernet cable plugged in. The cable is known to work in an other machine. Did you fix the issue?

[Tyler Durden]

I also cannot get my wired connection to work whether it be through openELEC or Chrome OS.

Can anyone help with that too?

was it working when you downloaded/ran the script for the dual boot install? or did you use wireless then? The wired connection not working is usually caused by something hardware-related (cable, switch, etc); there's nothing ChromeBox-specific to suggest that google won't tell you.

No, it has never worked. I am now on my second Chrome Box, but the issue remains. The ethernet cable is known to work on other systems such as an AMLogic M8, a Dell LapTop, a Sky HD box. Only the HP Chrome Box doesn't register it at all.

[Tyler Durden]

Having tried a ethernet cable direct to the router I now have a working connection......

So, either there is something broken in my wiring that doesn't effect the other systems that work, or the Chrome Box doesn't work going through an unmanaged switch. I'll keep investigating.

[noggin]

Having tried a ethernet cable direct to the router I now have a working connection......

So, either there is something broken in my wiring that doesn't effect the other systems that work, or the Chrome Box doesn't work going through an unmanaged switch. I'll keep investigating.

Have run Asus Chromeboxes through Netlink, TPLink and Belkin 100 and 1000Mbs unmanaged switches with no problems.

[D-an-W]

Works fine on my Gigabit Netgear switches too.

[ant_thomas]

Same here, unmanaged switches with no problems running Gigabit.

[driekus]

Got my Chromebox and literally set it up in fifteen minutes.

Works amazingly, put all sorts of tough 1080p through it and it didnt seem to break a sweat.

Thank you Matt for setting up such an easy inexpensive way of getting a topshelf Kodi player