Hi Matt,
I just gave up on the dual boot thing and went to using the custom BIOS. from there, loaded Ubuntu 14.04 from a install USB that I had laying around. That worked great.. boots up in a few sec! thanks for your help, and glad to see this running so fast.
I do still see the string descriptor malformed error but it just flashes by so can't really notice it unless I'm looking for it.
Once again great script!
a question to hp/asus chromeboxes owners, does the power supply supports both 110-220v? so it can work in Europe just by adding EU power plug?
(2014-11-02, 13:23)sh33p Wrote: [ -> ]a question to hp/asus chromeboxes owners, does the power supply supports both 110-220v? so it can work in Europe just by adding EU power plug?
Yes - however the Asus PSU has an integrated fold-out US 2-pin plug (so is a large wall wart) rather than a socket for a flying mains cable, so you will need to either use a US->EU/UK adaptor or source a replacement. Both my US Asus models came with the same PSU.
I don't have one, but apparently the HP accepts a standard cloverleaf mains cable like most laptop PSUs - so you can simply switch out the mains cable for a UK/EU one.
For info - the PSU that comes with an i5 NUC is compatible with the Asus.
Ok,
So I finally got around to making a video of the display issue I am having with my Asus Chromebox with OpenELEC/XBMC.
Again I am running dual boot with ChromeOS and OpenELEC/XBMC.
A few things I do not mention in the video, I have tried mutipule different TVs and I have used over a dozen diffent HDMI cables, all with this result.
I am not sure what going, but I would like to just figure out the best way to resolve it at this point. complete wipe? restore?
Thanks ahead of time for anyones help, and sorry for the quality shot on my phone.
(2014-11-03, 06:03)JonniMR Wrote: [ -> ]Ok,
So I finally got around to making a video of the display issue I am having with my Asus Chromebox with OpenELEC/XBMC.
Again I am running dual boot with ChromeOS and OpenELEC/XBMC.
A few things I do not mention in the video, I have tried mutipule different TVs and I have used over a dozen diffent HDMI cables, all with this result.
I am not sure what going, but I would like to just figure out the best way to resolve it at this point. complete wipe? restore?
Thanks ahead of time for anyones help, and sorry for the quality shot on my phone.
1) does it do the same thing if you boot to ChromeOS vs OpenELEC?
2) what happens if you change to HDMI2 before powering on?
3) are you using the latest Legacy BIOS update from my script?
4) does it behave the same when connected to a standard PC monitor vs a TV?
(2014-11-03, 07:35)Matt Devo Wrote: [ -> ]1) does it do the same thing if you boot to ChromeOS vs OpenELEC?
2) what happens if you change to HDMI2 before powering on?
3) are you using the latest Legacy BIOS update from my script?
4) does it behave the same when connected to a standard PC monitor vs a TV?
1) I am going to run out and get a usb keyboard now to see if ChromeOS is doing the same thing or not.
2) Most of theTV's I tried could not be switched to an input that had no signal. A couple that I tried could, the result was the same as above.
3) I did update the Legacy BIOS when I first installed the OpenELEC/XBMC
4) I don't have a standard PC monitor to test, sorry.
I will report back very shorty.
Ok Matt,
Went and grabbed a USB keyboard. ChromeOS is doing the exact something.
***Diffrent TV - Diffrent HDMI Cable, same results.
Ideas from here?
I'm stuck, my Chromebox is stuck trying to boot from the hard drive and I can't choose an option from the boot menu to install OpenELEC.
I followed the instructions for a standalone OpenELEC install.
1. Dev Mode
2. Disabled Firmware Write Protect
3. Downloaded EZ Setup Script
4. Ran Standalone option and backed up firmware
5. Created OpenELEC install media
6. Shutdown / boot with install media
I have tried the install media created by script and have created install media manually on SD Card and USB 2.0 jump drive.
Either way my Chromebox boots straight to hard drive no matter what I do - I press ESC on the keyboard and I see a list of boot media but it boots from hard drive anyway - I don't get to choose a device to boot from.
What are my options at this point?
(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?
did it do this from the start, ie before you switched to dev mode and/or before you ran the dual boot setup from the script?
(2014-11-03, 22:38)prickly Wrote: [ -> ]I'm stuck, my Chromebox is stuck trying to boot from the hard drive and I can't choose an option from the boot menu to install OpenELEC.
I followed the instructions for a standalone OpenELEC install.
1. Dev Mode
2. Disabled Firmware Write Protect
3. Downloaded EZ Setup Script
4. Ran Standalone option and backed up firmware
5. Created OpenELEC install media
6. Shutdown / boot with install media
I have tried the install media created by script and have created install media manually on SD Card and USB 2.0 jump drive.
Either way my Chromebox boots straight to hard drive no matter what I do - I press ESC on the keyboard and I see a list of boot media but it boots from hard drive anyway - I don't get to choose a device to boot from.
What are my options at this point?
when you press ESC and the boot menu shows, the boot menu should stay on screen indefinitely until you choose one of the numeric options from the menu (or press ESC again). Are you choosing the USB drive from the list (option 2 I assume)? If you're pressing ESC more than once initially, that may be causing it show the menu and then boot directly to the internal HDD.
(2014-11-03, 23:37)Matt Devo Wrote: [ -> ] (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?
did it do this from the start, ie before you switched to dev mode and/or before you ran the dual boot setup from the script?
No, It was fine before running the script. I don't really have anything I need in xbmc, Is it possible to redo everything?
(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
Hi Matt, Guess I am still a bit lost.Have not been successful in getting openelec to boot.The EZ script did install your SeaBios. I used the usb stick that your script used to make the bootable drive. I selected it for the boot device to try and rerun. Some code ran but nothing was gained. I am now trying to make a usb stick using OpenElec-Generic.x86_64-3.95.6-Chromebox. When I run the create_installstick.bat it asks for the drive letter of the usb on my windows machine. When I enter it, it say invalid drive selected even though the correct letter is installed. I've tried different usb ports but nothing. Sure this is simple to someone with your knowledge. Can you give me some guidance. Thanks for your attention to this thread!
(2014-11-04, 01:32)kilbo Wrote: [ -> ]Hi Matt, Guess I am still a bit lost.Have not been successful in getting openelec to boot.The EZ script did install your SeaBios. I used the usb stick that your script used to make the bootable drive. I selected it for the boot device to try and rerun. Some code ran but nothing was gained. I am now trying to make a usb stick using OpenElec-Generic.x86_64-3.95.6-Chromebox. When I run the create_installstick.bat it asks for the drive letter of the usb on my windows machine. When I enter it, it say invalid drive selected even though the correct letter is installed. I've tried different usb ports but nothing. Sure this is simple to someone with your knowledge. Can you give me some guidance. Thanks for your attention to this thread!
1) use the current version of OpenELEC, 4.2.1:
http://openelec.tv/get-openelec/download...ric-x86-64
2) use the .exe, not the .bat to create the install media.
Thanks Matt.
Did as you said. Using the newly created install stick, I now get missing operating system
