[wally_666]

While this thread is all about installing, could we please have a small discussion about updating?

I ran the script and have a working OpenELEC standalone with Matt's "custom" build and Coreboot firmware. After applying the tweaks mentioned in this thread and the youTube addon thread, everything seems to work perfectly with the only "defect" being the hardware acceleration issue which doesn't seem to cause me any problems after the SW-filter tweak.

My gut says "if it ain't broke, don't fix it!" so my questions are:

Is it worth enabling automatic updates in OpenELEC now? Which it appears would initially "upgrade" me to 4.0.7 from Matt's 4.0.7-chromebox.

Do I need to update the Coreboot firmware again before updating? Which I installed around July 18th, 2014.

I finally got a Chromium image to boot from an 8GB USB stick, my Logitech K400 seems flaky with it but when it does work it seems OK. Is there a way in Chromium to "grow" the system image to use the entire 8GB stick? My 4GB stick didn't work and since the Chromebox came with an 16GB mSATA drive I figure the extra space could be useful. My Google-Fu is weak here, all I've found was some github stuff to suggest that its been worked on in the past.

I was impressed enough with the ChromeOS performance on the Chromebox for the little playing around I did with it to check out / verify the hardware before wiping that "dual booting" ChromiumOS via a USB stick seems adequate for me to get some more experience playing with it.

[Matt Devo]

While this thread is all about installing, could we please have a small discussion about updating?

I ran the script and have a working OpenELEC standalone with Matt's "custom" build and Coreboot firmware. After applying the tweaks mentioned in this thread and the youTube addon thread, everything seems to work perfectly with the only "defect" being the hardware acceleration issue which doesn't seem to cause me any problems after the SW-filter tweak.

My gut says "if it ain't broke, don't fix it!" so my questions are:

Is it worth enabling automatic updates in OpenELEC now? Which it appears would initially "upgrade" me to 4.0.7 from Matt's 4.0.7-chromebox.

4.1.2 has wake from USB enabled, so custom builds no longer needed. 4.1.3 will likely have a fix for one of the VAAPI hardware acceleration bugs (the one which the 'Use SW filter for VAAPI' option does not mitigate). I'd enable auto-updates for OE and let it do its thing, but you may have to manually update to a standard OE build before the auto-updating works.

Do I need to update the Coreboot firmware again before updating? Which I installed around July 18th, 2014.

not unless you need the fix from the 7/29 firmware. Firmware updates and OE updates are completely separate / not interdependent.

I finally got a Chromium image to boot from an 8GB USB stick, my Logitech K400 seems flaky with it but when it does work it seems OK. Is there a way in Chromium to "grow" the system image to use the entire 8GB stick? My 4GB stick didn't work and since the Chromebox came with an 16GB mSATA drive I figure the extra space could be useful. My Google-Fu is weak here, all I've found was some github stuff to suggest that its been worked on in the past.

I'd expect so, but I haven't looked into it myself, since I only use ChromiumOS for testing script/firmware updates.

[furii]

4.1.3 will likely have a fix for one of the VAAPI hardware acceleration bugs (the one which the 'Use SW filter for VAAPI' option does not mitigate).

just to make sure i'm following correctly, this is the bug with the Joe sample, right? if so that's good news as that should mean paired with the SW filter for VAAPI option there shouldn't be problems with using hardware acceleration for all material.

[soundpwns909]

Hey Matt, thanks for the guide. I've gotten openelec installed on my hp chromebox alongside chromeos, but when I try to set boot options it says: write protect enabled, non-stock firmware installed or not running chromeos; cannot set boot options.
I know I'm running ChromeOS, and I haven't flashed any firmware, so it has to be that write protect is enabled, correct?
I cannot for the life of me find any documentation of which screw I need to remove on the HP Chromebox, I have opened it up and removed the only screw that I could find that made sense, the second screw on the only corner of the motherboard that has 2 screws. But that doesn't do it either.

What am I missing? I have a feeling it's something really simple....

that error is returned only under the conditions listed; if you're running ChromeOS, then it's because you have not removed the write protect screw. It should be in the same location on your HP box as on the Asus - see pic in the wiki.

That's what I thought, and that's what has me confused, I stared at the inside of that box for hours last night trying to find the screw, but I can only find one screw that makes any sense, seems like its in the same place as the asus device, but I still get the error even after that screw is removed. Could it maybe be shorting itself even without the screw?

[Matt Devo]

That's what I thought, and that's what has me confused, I stared at the inside of that box for hours last night trying to find the screw, but I can only find one screw that makes any sense, seems like its in the same place as the asus device, but I still get the error even after that screw is removed. Could it maybe be shorting itself even without the screw?

look at the picture of the screw hole on the wiki - you'll see that the two metal sides are separated, and that the screw, when installed, connects the two to complete the circuit.

open up a shell prompt on your box, and type the following command:

Code:

sudo crossystem

look at the last two lines of output, for wpsw_cur and wpsw_boot. both should be 0, if not then write-protect is still enabled, and that's why you can't set the boot options.

[wally_666]

It looks like ChromiumOS is pretty unusable. I've tried three different USB sticks and two different "builds". The user interface is sluggish and mouse movement is very jumpy even with the lowest speed in "settings". About the only thing that seemed to work was adjusting the display size for overscan compensation.

Nothing else I've tried seems to actually work, Angry Birds (I did run this on the ChromeOS) locks up at "installing 60%". Pandora installs but says I need Flash, but Adobe's flash page says I have the latest version. I tried iHeartRadio and couldn't scroll down to acknowledge the "terms and conditions" to create and account.

Utterly useless as far as I can tell
In fact two of the three sticks now give a kernel panic when I try to boot them
Other than getting one to boot to Ctrl-Alt-F2 for the login to rerun your script I'd say forget about ChromiumOS on the Chromebox.

[betterhalf]

Just got my chrome box.

Standalone Setup / coreboot Firmware Install / Update

This option will allow you to replace the stock firmware with a custom build of coreboot. This custom firmware fixes many issues with the stock firmware and significantly reduces the boot time, but is not ChromeOS compatible. (You can, however, run the open-source variant ChromiumOS. Downloads are available at http://chromium.arnoldthebat.co.uk/)

Confused on this step. If I wanted to do standalone with openelec do I have to replace the stock firmware with core boot (ChromeOS) before installing openelec via usb?

[Matt Devo]

Confused on this step. If I wanted to do standalone with openelec do I have to replace the stock firmware with core boot (ChromeOS) before installing openelec via usb?

Yes, run step 5 then 6

[magy77]

While this thread is all about installing, could we please have a small discussion about updating?

I ran the script and have a working OpenELEC standalone with Matt's "custom" build and Coreboot firmware. After applying the tweaks mentioned in this thread and the youTube addon thread, everything seems to work perfectly with the only "defect" being the hardware acceleration issue which doesn't seem to cause me any problems after the SW-filter tweak.

My gut says "if it ain't broke, don't fix it!" so my questions are:

Is it worth enabling automatic updates in OpenELEC now? Which it appears would initially "upgrade" me to 4.0.7 from Matt's 4.0.7-chromebox.

4.1.2 has wake from USB enabled, so custom builds no longer needed. 4.1.3 will likely have a fix for one of the VAAPI hardware acceleration bugs (the one which the 'Use SW filter for VAAPI' option does not mitigate). I'd enable auto-updates for OE and let it do its thing, but you may have to manually update to a standard OE build before the auto-updating works.

From where did you know this? I didnt found some infos for 4.1.3

[Matt Devo]

From where did you know this? I didnt found some infos for 4.1.3

I'm looking at the commits to the 4.2 branch, which will be used for the next beta. Also following the bug tracker on freedesktop.org, where the fix has been tested and confirmed

[magy77]

From where did you know this? I didnt found some infos for 4.1.3

I'm looking at the commits to the 4.2 branch, which will be used for the next beta. Also following the bug tracker on freedesktop.org, where the fix has been tested and confirmed

Directlink? Thx

[Matt Devo]

Directlink? Thx

https://bugs.freedesktop.org/show_bug.cgi?id=81447
https://github.com/OpenELEC/OpenELEC.tv/...fdd8ede289
http://forum.xbmc.org/showthread.php?tid...pid1766386

[magy77]

Anybody knows a releasedate for 4.1.3.?

[DocG]

That's what I thought, and that's what has me confused, I stared at the inside of that box for hours last night trying to find the screw, but I can only find one screw that makes any sense, seems like its in the same place as the asus device, but I still get the error even after that screw is removed. Could it maybe be shorting itself even without the screw?

In case there should be any doubts...



And yes, it does work for me.

[Matt Devo]

Anybody knows a releasedate for 4.1.3.?

When it's ready