(2014-06-21, 17:42)hdmkv Wrote: I used Matt's tool and set-up standalone OpenELEC w/o ever using ChromeOS and setting the clock. Now XBMC shows the wrong time... anyone know how I can set the clock?

(2014-06-21, 05:04)smitbret Wrote: Well, took Matt Devo's advice from the XBMC forum linked above. My TV wasn't synching up fast enough and when I hit CTRL-D from the moment I turned on the Chromebox, instead of waiting for the display, it got me into the OS far enough that I could CTRL-SHFT-F2. Anyway, followed his guide from there and got stuck again, even worse this time.

Anyway, after messing with 4 different flash drives, I finally stuck the bootable OpenELEC on a MicroSD card with adapter. I discovered that if I stuck that MicroSD card in along with the Chrome OS recovery image on Flash Drive and then booted with the paper clip in the reset hole then I had about 2 seconds to hit the ESC button and get the list of 3 bootable choices. I was able to then install from the SD card. This time it took.

Quote:Boots right into XBMC from the HDD and is running really smooth. For some reason the box just wouldn't recognize any of the flash drives as bootable. I must have not set up the boot configuration very well. I don't know. I could have sworn that I checked and double checked along the way.

Anyway, pretty pleased so far. I have a FLIRC as the IR receiver paired with my Logitech Harmony and I still need to get the delay settings correct, there's some pretty bad lag, but I should be able to get ironed out.

Thanks for the help.

(2014-06-21, 16:23)rukusx7 Wrote: In my standalone OpenELEC setup, I have had success with the following peripherals:
HP wired mouse
HP wired keyboard
USB wireless Tronsmart TSM-01 air mouse
Samsung TV wireless USB adapter
Transcend 760 16gb USB flash drive
Sandisk Cruzer mirco 8GB flash drive
Western Digital mybook 1150 2TB (which its worth to mention, does not (always) return from its own suspend state when the chromebox is woken from suspend.)
Samsung LED TV UN46d6300

Also want to mention that if you use visualization when playing music, I've noticed that FishBMC and GOOM result in high CPU usage. ProjectM (although looks more intensive) uses the least CPU and possibly makes more use of the GPU. I'm not sure.

If anyone know of a linux distro they can recommend that suits our chipset/device, please let me know. I'd like something where its not necessary for me to manually update the kernel to keep up with latest stable kernel. Linux mint lost points because of this.

This was posted within OpenELEC with chromium-browser.

(2014-06-21, 16:23)rukusx7 Wrote: If anyone know of a linux distro they can recommend that suits our chipset/device, please let me know. I'd like something where its not necessary for me to manually update the kernel to keep up with latest stable kernel. Linux mint lost points because of this.

(2014-06-21, 21:04)Igor2014 Wrote: I would suggest Fedora 20 (I'm using KDE Spin + Openbox/XBMC). I tested various linux distros and Fedora was the most stable for me. Also it boots faster than any other distro (including OpenELEC). I'm running XBMC in Openbox (using autostart on boot) and while it uses a little more memory (11% vs 5% for OpenELEC) it allows me to run Steam & Chromium from inside XBMC without headaches. Also many Steam games run quite well on celeron. Tested with DOTA2, HL2:EP2, DofD & TF2.

(2014-06-21, 23:13)hdmkv Wrote: Matt, if I want to update to v2.11 of your tool from having used v2.10 and installed OpenELEC standalone, how would I go about this?

(2014-06-21, 22:55)Matt Devo Wrote:

(2014-06-21, 21:04)Igor2014 Wrote: I would suggest Fedora 20 (I'm using KDE Spin + Openbox/XBMC). I tested various linux distros and Fedora was the most stable for me. Also it boots faster than any other distro (including OpenELEC). I'm running XBMC in Openbox (using autostart on boot) and while it uses a little more memory (11% vs 5% for OpenELEC) it allows me to run Steam & Chromium from inside XBMC without headaches. Also many Steam games run quite well on celeron. Tested with DOTA2, HL2:EP2, DofD & TF2.

Fedora + OpenBox + XBMC boots in <5 seconds? b/c that's what OpenELEC is at.

I think OE is ideal for people who want a dedicated XBMC appliance with little more. Anything else (eg, Steam) is going to require a more full fledged distro, and I think right now Fedora is the best for the Haswell platform. Not sure it meets rukusx7's requirement for automatic? kernel updates though

(2014-06-22, 02:01)Igor2014 Wrote: It boots into openbox + XBMC in around 8-10 seconds. Strangely, for OpenELEC it took longer to boot, around 20-30 seconds (maybe because of tpm issue). Anyway the first thing I tried once I rooted chromebox was OpenELEC. I was expecting trouble-free experience but unfortunately it was not the case. The most notable issue was that it refused to download video-addons (while other addons it downloaded successfully). I was searching over internet for possible solution, but then gave up and decided to try other distros. Ubuntu + XBMC didn't work for me because of a lot of hangs and freezes during playback and menu navigation. Mint has a problem with mounting my external NTFS formated drives + many other issues. As for now Fedora is the most trouble-free distro for me. Not to mention that Ubuntu and Fedora are the only distros officialy supported by Intel Linux Drivers Team. And it seems they are going to drop Ubuntu soon as they stated they are not going to support Mir and will stay committed to Wayland only.

(2014-06-22, 02:06)Matt Devo Wrote: sounds like something was awry with your OE install, I've had no issues with video add-ons, and it's booted in ~5s since the first Coreboot firmware I released (2014-05-18).

I may give your setup a whirl though, as I like the idea of having Steam and Chromium integrated as well. How do you have it set up to switch between XBMC, Steam, and Chromium?

(2014-06-22, 02:16)Igor2014 Wrote: I'm using Advanced Launcher for XBMC to start Steam and Chromium.
(--kiosk option to start Chromium in full screen mode, Alt+F4 to close it and get back to XBMC)
(-bigpicture option to start Steam in full screen mode.)

(2014-06-22, 02:18)Matt Devo Wrote:

(2014-06-22, 02:16)Igor2014 Wrote: I'm using Advanced Launcher for XBMC to start Steam and Chromium.
(--kiosk option to start Chromium in full screen mode, Alt+F4 to close it and get back to XBMC)
(-bigpicture option to start Steam in full screen mode.)

cool, thx. Any reason to use the KDE Fedora spin vs something more lightweight, like xfce or lxde?

(2014-06-21, 19:14)Matt Devo Wrote:

(2014-06-21, 05:04)smitbret Wrote: Well, took Matt Devo's advice from the XBMC forum linked above. My TV wasn't synching up fast enough and when I hit CTRL-D from the moment I turned on the Chromebox, instead of waiting for the display, it got me into the OS far enough that I could CTRL-SHFT-F2. Anyway, followed his guide from there and got stuck again, even worse this time.

Anyway, after messing with 4 different flash drives, I finally stuck the bootable OpenELEC on a MicroSD card with adapter. I discovered that if I stuck that MicroSD card in along with the Chrome OS recovery image on Flash Drive and then booted with the paper clip in the reset hole then I had about 2 seconds to hit the ESC button and get the list of 3 bootable choices. I was able to then install from the SD card. This time it took.

for the original flash drive you tested, did you create the OpenELEC install media using the script, or did you run OE's USB creator tool? The latter, under Windows, doesn't re-partition the drive, which can create problems if there's a small hidden partition in front of the larger/bootable/FAT32 one.

To be clear, with the Coreboot firmware installed, the recovery button has absolutely no function (which is why you have to re-flash your original firmware before restoring ChromeOS). And if there is more than 1 bootable device connected (ie, any USB or SD devices), you will have 5 seconds to hit ESC before it automatically boots the internal HDD.

Quote:Boots right into XBMC from the HDD and is running really smooth. For some reason the box just wouldn't recognize any of the flash drives as bootable. I must have not set up the boot configuration very well. I don't know. I could have sworn that I checked and double checked along the way.

Anyway, pretty pleased so far. I have a FLIRC as the IR receiver paired with my Logitech Harmony and I still need to get the delay settings correct, there's some pretty bad lag, but I should be able to get ironed out.

Thanks for the help.

If you have USB flash drives which are not detected by the SeaBIOS boot menu (which is different than being detected, but not booting from it), then please PM me so I can walk you thru getting me the firmware boot log and I can see what's going on. And be sure to let me know the date stamp in the SeaBIOS version string on the boot menu.