(2014-08-05, 20:12)wally_666 Wrote: 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.

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

Quote: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.

(2014-08-05, 20:17)Matt Devo Wrote: 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).

(2014-08-05, 16:15)Matt Devo Wrote:

(2014-08-05, 07:51)soundpwns909 Wrote: 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.

(2014-08-05, 22:48)soundpwns909 Wrote: 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?

(2014-08-06, 03:21)betterhalf Wrote: 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?

(2014-08-05, 20:17)Matt Devo Wrote:

(2014-08-05, 20:12)wally_666 Wrote: 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.

(2014-08-06, 05:36)magy77 Wrote: From where did you know this? I didnt found some infos for 4.1.3

(2014-08-06, 05:37)Matt Devo Wrote:

(2014-08-06, 05:36)magy77 Wrote: 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

(2014-08-06, 06:04)magy77 Wrote: Directlink? Thx

(2014-08-05, 22:48)soundpwns909 Wrote: 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?

(2014-08-06, 07:02)magy77 Wrote: Anybody knows a releasedate for 4.1.3.?