(2014-11-04, 01:19)Matt Devo Wrote: [ -> ] (2014-11-04, 00:47)JonniMR Wrote: [ -> ]No, It was fine before running the script. I don't really have anything I need in xbmc, Is it possible to redo everything?
sent you a PM with some instructions to install an older version of SeaBIOS, to see if the newer VGA BIOS I'm using is causing the issue
Thanks Matt,
Got your PM and I am going to give it a try here in a few minutes.
I started thinking about how I use my chromebox, and I am thinking a standalone set up would have been a better route for me. With where I stand now and have a dual boot, after I test the older version of the SeaBIOS, could I just re-run the script and proceed with a standalone setup and use OpenELEC?
Thanks.
Those links you posted did the trick. Can't thank you enough.
Am sending you a donation to the email on the script. Not enough to buy a new Ferrari but a token of appreciation.
(2014-11-04, 16:48)kilbo Wrote: [ -> ]Those links you posted did the trick. Can't thank you enough.
Am sending you a donation to the email on the script. Not enough to buy a new Ferrari but a token of appreciation.
thanks! I'm not sure why that worked, unless you used a different USB media than before, since the script does the exact same thing (in terms of OE install media creation).
Hi there,
Great forum,
Just purchased the HP chrome box and followed the instructions for installing dual boot with openelec.
I Removed the write-protect screw but still I am getting a message that write protect is enabled.
Any ideas?
Thanks a lot
(2014-11-04, 19:51)sf56 Wrote: [ -> ]Hi there,
Great forum,
Just purchased the HP chrome box and followed the instructions for installing dual boot with openelec.
I Removed the write-protect screw but still I am getting a message that write protect is enabled.
Any ideas?
Thanks a lot
double check that you removed the correct screw, since that is literally the only thing that could cause your problem. The write-protect screw has a segmented metal ring on the board underneath it, so that the two halves are not connected when the screw is removed
(2014-11-04, 20:02)Matt Devo Wrote: [ -> ] (2014-11-04, 19:51)sf56 Wrote: [ -> ]Hi there,
Great forum,
Just purchased the HP chrome box and followed the instructions for installing dual boot with openelec.
I Removed the write-protect screw but still I am getting a message that write protect is enabled.
Any ideas?
Thanks a lot
double check that you removed the correct screw, since that is literally the only thing that could cause your problem. The write-protect screw has a segmented metal ring on the board underneath it, so that the two halves are not connected when the screw is removed
Thanks for the quick response.
Hi checked and rechecked the screw is removed but write protect is enabled. based on an earlier suggestion I checked with "sudo crossytem" command and got "1" at the the last 2 lines. Is it important when in the process the screw should be removed? i.e., if I repeat the process should I put back the screw and remove it only after I put the box in development mode?
(2014-11-04, 20:36)sf56 Wrote: [ -> ]Thanks for the quick response.
Hi checked and rechecked the screw is removed but write protect is enabled. based on an earlier suggestion I checked with "sudo crossytem" command and got "1" at the the last 2 lines. Is it important when in the process the screw should be removed? i.e., if I repeat the process should I put back the screw and remove it only after I put the box in development mode?
it doesn't matter when the screw is removed, only the status at boot time. Take a picture showing your entire crosssytem output please
(2014-11-04, 21:06)Matt Devo Wrote: [ -> ] (2014-11-04, 20:36)sf56 Wrote: [ -> ]Thanks for the quick response.
Hi checked and rechecked the screw is removed but write protect is enabled. based on an earlier suggestion I checked with "sudo crossytem" command and got "1" at the the last 2 lines. Is it important when in the process the screw should be removed? i.e., if I repeat the process should I put back the screw and remove it only after I put the box in development mode?
it doesn't matter when the screw is removed, only the status at boot time. Take a picture showing your entire crosssytem output please
Here is a link, let me know if the quality is OK
Thanks
SF
https://onedrive.live.com/redir?resid=3E...hoto%2cjpg
(2014-11-04, 21:34)sf56 Wrote: [ -> ]Here is a link, let me know if the quality is OK
Thanks
SF
https://onedrive.live.com/redir?resid=3E...hoto%2cjpg
outside of the write-protect status, nothing stands out. Unless there's been some change, I don't know why you'd still be seeing that after removing the WP screw
(2014-11-04, 22:32)Matt Devo Wrote: [ -> ] (2014-11-04, 21:34)sf56 Wrote: [ -> ]Here is a link, let me know if the quality is OK
Thanks
SF
https://onedrive.live.com/redir?resid=3E...hoto%2cjpg
outside of the write-protect status, nothing stands out. Unless there's been some change, I don't know why you'd still be seeing that after removing the WP screw
Thanks for your efforts, I'll try and look for a solution from HP
(2014-11-03, 20:07)JonniMR Wrote: [ -> ]Ok Matt,
Went and grabbed a USB keyboard. ChromeOS is doing the exact something.
***Diffrent TV - Diffrent HDMI Cable, same results.
Ideas from here?
Well I know what's going on but unfortunately I don't have a solution for you... The flicker and static that you saw in your previous video are both results of a HDMI handshake problem, I just ran into this on a DVDO matrix switch having problems with an older HDMI balun and TV. The only thing I can think of is that somehow your display driver isn't reporting correctly, so you may need to reformat the box. I wouldn't think that it's a hardware incompatibility since I've done three of these boxes with Matt's script so far and hooked them up to a variety of displays without any issues.
Hope you get it figured out!
New to chromeboxes and planning to get the Asus but have yet to decide on a remote.
Have one simple question tho:
Will this
remote work on the Asus chromebox w/OE
or would it be better to get a flirc and pair it with an ir remote?
(2014-11-04, 22:36)sf56 Wrote: [ -> ] (2014-11-04, 22:32)Matt Devo Wrote: [ -> ] (2014-11-04, 21:34)sf56 Wrote: [ -> ]Here is a link, let me know if the quality is OK
Thanks
SF
https://onedrive.live.com/redir?resid=3E...hoto%2cjpg
outside of the write-protect status, nothing stands out. Unless there's been some change, I don't know why you'd still be seeing that after removing the WP screw
Thanks for your efforts, I'll try and look for a solution from HP
Matt, one more question if you will. I installed the dual boot, received "Openelec installation complete" message everything seems OK, all this without removing the write protect screw (actually after screwing it back). I hit the cnrl-D and entered the Openelec and everything seems to work fine. so what is the purpose of this screw except for changing the boot delay
Thanks, SF
(2014-11-05, 04:14)skeetz Wrote: [ -> ]New to chromeboxes and planning to get the Asus but have yet to decide on a remote.
Have one simple question tho:
Will this remote work on the Asus chromebox w/OE
or would it be better to get a flirc and pair it with an ir remote?
I'm not sure that particular remote has been tested. In general, any remote which works under Linux will work fine, though some remotes have issues when connected to USB3 ports (which is all the ChromeBox has). The list on the wiki is a good starting point.
(2014-11-05, 07:51)sf56 Wrote: [ -> ]Matt, one more question if you will. I installed the dual boot, received "Openelec installation complete" message everything seems OK, all this without removing the write protect screw (actually after screwing it back). I hit the cnrl-D and entered the Openelec and everything seems to work fine. so what is the purpose of this screw except for changing the boot delay
Thanks, SF
on a dual boot setup, the removal of the write-protect screw is only needed to change the boot delay and/or default OS.