Login at Kodi Home

Matt Devo · 2015-05-17, 18:13

I promise, it is that easy. You need to boot ChromeOS by pressing CTRL-D *before* the black SeaBIOS screen appears. Then download and run the script. First set the boot options back to the default, then redo the dual boot setup. Hitting ESC on the SeaBIOS screen won't work because the stock SeaBIOS (which was reinstalled when you did the factory reset/recovery) is broken - not that it would help now, because you need to boot ChromeOS.

Markyboy8891 · (This post was last modified: 2015-05-17, 18:29 by Markyboy8891.)

Matt, Thank You! i truly thought i had knackered it. shows you that i am still a newb!
i think the keyboard power issue was down to it being wireless. plugged in a wired keyboard as was good to go.
Very much appreciated mate. :-)

rmilyard · 2015-05-18, 23:22

(2015-01-02, 00:54)Takashuri Wrote: Running Openelec 5.0 on the Asus Chromebox for a few days now. Working flawlessly together with my Lightpack.

Big thumbs up for Matt for making this so easy!

Do you have some instructions as to how you set this up? Thinking about getting 2 for my 65" Samsung soon.

Matt Devo · 2015-05-19, 00:04

Pretty sure there are other threads specific to lightpacks, no?

billyvnilly · (This post was last modified: 2015-05-19, 04:19 by billyvnilly.)

Hi Matt,

thanks for your hard work and persistence (im very impressed how active you're on the forum, id get tired out).

I remember a very long time ago, you said to use ctrl+d and ctrl+l we couldn't use a logitech keyboard, like the K400. Will that always be true? (asus chromebox)

Also, Any easy method you've found for restarting chrome os. currently im ctrl+alt+t and sudo reboot'ing ....just didn't know if there was an easier method.

thanks again.

Matt Devo · (This post was last modified: 2015-05-19, 05:24 by Matt Devo.)

I said you couldn't use the K400 specifically, most logitech wireless keywords work fine (like the K360, K520, and K750 I have). It's an issue with the device itself and the level of initialization it requires to work, so I don't expect it will ever work for dual boot selection

I'm not a ChromeOS user, so I've never looked to see if there's an easier way

knives of ice · 2015-05-19, 06:13

i don't know how i am missing this but where is the link to download the setup script? i have everything else done. is it the link to the source github? i've read the setup 4 times now not seeing it anywhere

knives of ice · 2015-05-19, 06:14

sorry....i see it auto downloads it when you run the command. d'oh!

SurfnTurfCA · 2015-05-19, 07:55

First off, I am a complete newbie and with that disclaimer, I am concerned that I bricked my Asus Chromebox M107U. In efforts to install dual boot with OpenELEC, I went to reboot and my USB ports are no longer active. The following is what appears:
__________________________________________________________________________________________________________
SeaBios (version -20141003_164257-build122-m2)

Press ESC for boot menu (as keyboard no longer works, I wait and then the following flashes on the screen before going black. Captured text with Slo-Mo on iPhone).

Decompressing Linux..... Parsing ELF.... Performing relocations... done.
Booting the kernel.
___________________________________________________________________________________________________________

Screen goes black and nothing. When I press the Recovery button and power on, I get the Chrome window with message that Chrome OS is missing, etc. In the upper left, I have the following script

gbb.flags is nonzero: 0x00000489
read-only firmware id: Google_Panther.4920.24.26
active firmware id: Google_Panther.4920.24.26

Inserting a ChromeOS recovery image on USB is non-responsive.

Does anyone have any helpful advice as to next steps ? Being the newbie, I have neither the tools nor the expertise to flash the firmware but am willing to take any advice and give it a try (minus hating on iPhones).

Thanks

Matt Devo · 2015-05-19, 08:06

(2015-05-19, 07:55)SurfnTurfCA Wrote: First off, I am a complete newbie and with that disclaimer, I am concerned that I bricked my Asus Chromebox M107U. In efforts to install dual boot with OpenELEC, I went to reboot and my USB ports are no longer active. The following is what appears:

[snip]

Screen goes black and nothing. When I press the Recovery button and power on, I get the Chrome window with message that Chrome OS is missing, etc. In the upper left, I have the following script

gbb.flags is nonzero: 0x00000489
read-only firmware id: Google_Panther.4920.24.26
active firmware id: Google_Panther.4920.24.26

Inserting a ChromeOS recovery image on USB is non-responsive.

Does anyone have any helpful advice as to next steps ? Being the newbie, I have neither the tools nor the expertise to flash the firmware but am willing to take any advice and give it a try (minus hating on iPhones).

Thanks

this is what happens when one doesn't follow directions, and sets the boot flags before completing the 2nd half of the dual boot setup (and before testing things out).

The boot flags (0x489) tell me that you set it to boot OpenELEC/Ubuntu by default, but since the dual boot setup hasn't completed, 1) OpenELEC isn't installed yet, so it tries (and fails) to boot ChromeOS in legacy boot mode (which it can't do), 2) the script hasn't installed the updated SeaBIOS yet, so the USB ports (including any connected keyboard) aren't functional.

The solution is to hit [CTRL-D] to boot ChromeOS *before* the 1s boot timeout (which may be before video initializes even), and download/run the script again to complete the dual boot setup, as per the instructions Smile

KaterM · 2015-05-19, 13:47

Hello Matt, this is my first post. Thank you for your efforts.

Although I have read the whole thread and studied your well commented script in detail, I still have a question.

I am using a Celeron Asus Chromebox with 4G RAM.
I bought it as a replacement for my burnt out Asrock ION 300.
I rescued the hdd with ubuntu on it and put it in a case connected by sata/usb3. I can read and write fine to it from my chromebox under Chrome OS and crouton/ubuntu.
The connected periferics have not changed, I also am able to boot from the hdd in question on a friend's laptop.

So:
I just would like to boot to this hdd from my chromebox, if I want to, but still be able to use ChromeOS and automatic updates.
I suppose the part
"-----------------------------------------
Update Legacy BIOS (dual boot)
-----------------------------------------"
of your script would do that, but I am still uncertain.
Would you please advise?

Thanks a lot,
KaterM

Matt Devo · 2015-05-19, 15:44

(2015-05-19, 13:47)KaterM Wrote: So:
I just would like to boot to this hdd from my chromebox, if I want to, but still be able to use ChromeOS and automatic updates.
I suppose the part
"-----------------------------------------
Update Legacy BIOS (dual boot)
-----------------------------------------"
of your script would do that, but I am still uncertain.

correct, if all you want to do is boot an OS off a USB device, then updating the legacy BIOS is sufficient. In your case, I would choose to set the option to boot from USB by default. You may also want to set the boot options to change the boot timeout and/or default OS/boot type

lancastrian · 2015-05-19, 19:58

(2015-04-13, 11:51)lancastrian Wrote: I'm experiencing an issue with my HP Chromebox (dual boot ChromeOS and OpenElec) where the portable hard drive (1TB Samsung M3) frequently disconnects when I try to copy new files to it, either in the Kodi file manager or via my phone or PC. This doesn't happen in normal use, e.g. reading files, only when writing. I'd say > 80% it will lose connection to the hard drive and require a restart. It's not a problem I've had when using the hard drive with my PC, but I couldn't rule out a fault with the hard drive itself. I've tried copying from other USB devices and from the Chomebox's SSD but it makes no difference.

Is this something anyone else has experienced or has a cause for? The only similar thing I've found when searching was someone whose Asus Chromebox was behaving similarly with a 1TB Seagate drive. Their theory was that it was a USB 3.0 issue and that using a USB 2.0 hub remedied the situation.

Has anyone got any thoughts on it? I'd ideally prefer to use USB 3.0, but if downgrading to USB 2.0 is going to fix it I'll guess I'll buy a USB 2.0 hub.

If anyone else experiences the same issue and comes across the post, just to let you know that using a cheap USB 2.0 hub has solved it for me. Weird, but at least it works.

busta.rhymes · 2015-05-20, 15:07

Hi guys, so i was looking at this issue with my ps3 bluetooth remote where i thought that it just disconnects after a while.
Now after looking at this issue for a month it seems to be the problem that the batteries go empty in a week or so. It isnt a bluetooth disconnect.
My remote seems to always drain power or something because otherwise i canot explain why it burns through fresh batteries in a week. Can anybody give me some advice?

Matt Devo · 2015-05-20, 16:06

(2015-05-20, 15:07)busta.rhymes Wrote: Hi guys, so i was looking at this issue with my ps3 bluetooth remote where i thought that it just disconnects after a while.
Now after looking at this issue for a month it seems to be the problem that the batteries go empty in a week or so. It isnt a bluetooth disconnect.
My remote seems to always drain power or something because otherwise i canot explain why it burns through fresh batteries in a week. Can anybody give me some advice?

enable standby after pairing via trust and connect