2016-03-20, 17:19
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, 18:29
(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
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, 19:17
(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
Thanks matt! Booting a 64bit live usb script installed fine on both boxes. Thanks for the help.
Next time I reformat should I use the 64bit version of ubuntu? I only used the 32bit cause my chrome boxes only have 2GB of memory.
2016-03-20, 19:24
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.
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, 19:47
(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.
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, 20:36
(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-...lec-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/Config...#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:55
(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-...lec-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/Config...#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.
No firmware update available for amp. Fresh install on Chromebox. Is this the right thing I need to load at boot??
EDID:
00ffffffffffff002067630165000000
0912010380502d780a0dc9a057479827
12484c00000001010101010101010101
010101010101f339801871382d40582c
4500c48e2100001e011d8018711c1620
582c2500c48e2100009e000000fc0041
56523235342f352f3335340a000000fd
002d410f440f000a20202020202001d7
02034a7050901f051404130211031206
15071620013b097f070d7f070f7f0761
7e00657e00677e00597e015d7e015f7e
012c1507503d1fc05706004d0200835f
000067030c003000b826000000000000
00000000000000000000000000000000
00000000000000000000000000000000
000000000000000000000000000000a0
2016-03-20, 21:01
Im a little concerned last time I tried this I had to reinstall everything. Hence the fresh install of Chromebox.
2016-03-20, 21:08
(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-...lec-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.
You're right and I will do that thanks.
2016-03-20, 22:12
Keep getting message at host is not communicating for more than 15 seconds. before it fails.
2016-03-20, 22:21
(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??
couldn't tell just by looking at the ascii hex.
(2016-03-20, 22:12)Neil123 Wrote: Keep getting message at host is not communicating for more than 15 seconds. before it fails.
I'm not sure what this means, can you post a screenshot or something?
I would recommend updating the Chromebox firmware and choosing the headless option, which will prevent it from hanging at boot without a proper handshake. Then force-load the EDID as per the link I provided. I had to do this for a customer, and wrote those wiki instructions myself so I know they work ;-)
2016-03-20, 23:11
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.
Its been getting worst actually because now my Sony TV will sometimes completely lose signal and I have to insist with my keyboard or remote control to get signal back or simply reboot the Chromebox. Also sometimes screen would go really crazy with greenish or pink colours, see screenshot for an example:
I don't live in the US and is difficult to pick a reliable HDMI cable, they are pricey and I can't return if it doesn't work. I purchased Amazon Basics HDMI cable long ago and it has worked just fine all this time. I'll report back later.
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.
Its been getting worst actually because now my Sony TV will sometimes completely lose signal and I have to insist with my keyboard or remote control to get signal back or simply reboot the Chromebox. Also sometimes screen would go really crazy with greenish or pink colours, see screenshot for an example:
I don't live in the US and is difficult to pick a reliable HDMI cable, they are pricey and I can't return if it doesn't work. I purchased Amazon Basics HDMI cable long ago and it has worked just fine all this time. I'll report back later.
2016-03-20, 23:18
(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.
I had restored from the ones provided for the Asus CN60 (panther).
2016-03-21, 00:44
(2016-03-20, 23:18)Bogustime Wrote: I had restored from the ones provided for the Asus CN60 (panther).
I don't know why that wouldn't work, as I've done it dozens of times myself during testing, but like I said I'm happy to recover/unbrick it for you.
2016-03-21, 00:48
(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.
it's definitely a HDMI handshaking issue; which component is to blame can be difficult to determine. It's quite possible that the updated video BIOS included in my recent firmware versions is for some reason less-compatible with your particular display - I don't have a good way to troubleshoot that, but would suggest you stick with the older firmware (and older vbios) if that works better in your case. Newer isn't always better ;-)
