(2016-03-20, 16:14)redking Wrote: I've tried using both the EZ script and the dedicated script on both boxes. Both boxes are running ubuntu 14.04 LTS 32bit. One box does have the latest kernel 4.4.6. The other is 4.1.X

(2016-03-20, 18:29)Matt Devo Wrote: I'm pretty sure the utilities downloaded and used by the scripts are 64-bit executables, and that's the issue. Try booting a 64-bit live USB and run from there

(2016-03-20, 17:19)Boulder Wrote: If you want to invest some cash, an EDID emulator is something that might help you. I had to buy one myself because my old Yamaha wouldn't do the handshake properly.

(2016-03-20, 15:42)tate16t Wrote: Thanks so much.

Has anyone setup VPN on OpenELEC with PIA successfully using this process,

http://www.kodipiguide.com/guides/setup-vpn-openelec-addon/

(2016-03-20, 16:30)Neil123 Wrote: Please can someone help me. After having problems with a black screen on start up, hdmi handshake problems. I bought new cables and inputed a autostart.sh that goes

#!/bin/sh
xrandr --output HDMI1 --mode 1920x1080 -r 60

as i was told to do by Mr.Chromebox. Everything has been ok ish. I have to start my avr my chromebox and then restart the chromebox to get a picture up. But for some reason the problem has come back. Now I have to use around 20mins of restarting etc to get things up and running. Any ideas what I can try next to fix this problem its driving me crazy..

(2016-03-20, 19:47)Neil123 Wrote: The thing is it has worked fine for a year. But suddenly the black screen so it does work with my AVR it must just be a setting thats wrong.

(2016-03-20, 19:24)Bogustime Wrote: I'm looking to confirm if my asus chromebox is officially bricked.

I previously had standalone openelec running and had successfully used the ChromeOS device Firmware Utility Script to restore the stock firmware. Unfortunately, I am unable to successfully get anything to boot using the reset button. I also no longer have access to seabios to boot from usb.

(2016-03-20, 20:36)Matt Devo Wrote:

(2016-03-20, 15:42)tate16t Wrote: Thanks so much.

Has anyone setup VPN on OpenELEC with PIA successfully using this process,

http://www.kodipiguide.com/guides/setup-vpn-openelec-addon/

have you tried it and it's nor working? Or are you just looking to see if anyone else has it working on something other than a rPi? Either way, the OE forums are likely to have more activity/info on the topic since it's not Chromebox specific in any way.

(2016-03-20, 16:30)Neil123 Wrote: Please can someone help me. After having problems with a black screen on start up, hdmi handshake problems. I bought new cables and inputed a autostart.sh that goes

#!/bin/sh
xrandr --output HDMI1 --mode 1920x1080 -r 60

as i was told to do by Mr.Chromebox. Everything has been ok ish. I have to start my avr my chromebox and then restart the chromebox to get a picture up. But for some reason the problem has come back. Now I have to use around 20mins of restarting etc to get things up and running. Any ideas what I can try next to fix this problem its driving me crazy..

(2016-03-20, 19:47)Neil123 Wrote: The thing is it has worked fine for a year. But suddenly the black screen so it does work with my AVR it must just be a setting thats wrong.

have you updated the firmware on your amp? updated OpenELEC? updated the Chromebox firmware? Regardless, the issue is that the Chromebox isn't getting a valid EDID at boot. The easiest way to fix this will be to capture the EDID once you have it working, then load it at boot. See the 'Custom EDID' section of http://wiki.openelec.tv/index.php/Configuring_a_Custom_xorg.conf#tab=Intel

(2016-03-20, 19:24)Bogustime Wrote: I'm looking to confirm if my asus chromebox is officially bricked.

I previously had standalone openelec running and had successfully used the ChromeOS device Firmware Utility Script to restore the stock firmware. Unfortunately, I am unable to successfully get anything to boot using the reset button. I also no longer have access to seabios to boot from usb.

did you restore from your own backup, or use one of the ones provided? which Chromebox? If it is bricked, I offer free recovery services if you're in the USA/Canada, just cover shipping. Shoot me an email if interested.

(2016-03-20, 20:36)Matt Devo Wrote:

(2016-03-20, 15:42)tate16t Wrote: Thanks so much.

Has anyone setup VPN on OpenELEC with PIA successfully using this process,

http://www.kodipiguide.com/guides/setup-vpn-openelec-addon/

have you tried it and it's nor working? Or are you just looking to see if anyone else has it working on something other than a rPi? Either way, the OE forums are likely to have more activity/info on the topic since it's not Chromebox specific in any way.

(2016-03-20, 20:55)Neil123 Wrote: No firmware update available for amp. Fresh install on Chromebox. Is this the right thing I need to load at boot??

(2016-03-20, 22:12)Neil123 Wrote: Keep getting message at host is not communicating for more than 15 seconds. before it fails.

(2016-03-20, 20:36)Matt Devo Wrote:

(2016-03-20, 19:24)Bogustime Wrote: I'm looking to confirm if my asus chromebox is officially bricked.

I previously had standalone openelec running and had successfully used the ChromeOS device Firmware Utility Script to restore the stock firmware. Unfortunately, I am unable to successfully get anything to boot using the reset button. I also no longer have access to seabios to boot from usb.

did you restore from your own backup, or use one of the ones provided? which Chromebox? If it is bricked, I offer free recovery services if you're in the USA/Canada, just cover shipping. Shoot me an email if interested.

(2016-03-20, 23:18)Bogustime Wrote: I had restored from the ones provided for the Asus CN60 (panther).

(2016-03-20, 23:11)Veronica Wrote: I have reported a similar problem sometime ago @matt said it was a Handshake issue but the difference is that I don't have an AVR system.
Same as @Neil123 it has worked just fine since I got the Chromebox and even with same cable plus I've installed Windows and different Linux distros including OpenElec in the past with no problems of that kind.

I haven't had the time to get a new good cable to test but I know my Sony TV is not the problem because I have a Chromecast and an Android TV Stick hooked in with no problem.
Later today I'll try hooking up my bro's windows laptop with my HDMI cable to see if there is Handshake issue.

I still have a hunch that is the Chromebox after I upgraded firmware. In one of my last posts I have mentioned the last working firmware for me with no Handshake issue.
Right now I have latest coreboot firmware version installed because I thought maybe it got fixed but no it wasn't.