I installed the dual boot OpenELEC+XBMC using v 2.6 script when I first got the Chromebox. Thanks Matt for making it so easy for a novice!
If I run a later script, e.g. v2.10, to get an OS update, will my XBMC library survive or will I have to re-scan my media shares?
(2014-06-20, 21:32)AJ500 Wrote: [ -> ]I installed the dual boot OpenELEC+XBMC using v 2.6 script when I first got the Chromebox. Thanks Matt for making it so easy for a novice!
If I run a later script, e.g. v2.10, to get an OS update, will my XBMC library survive or will I have to re-scan my media shares?
You don't use the script to update OpenELEC; you simply enable auto-updates within the OpenELEC settings. Or, you can manually update OpenELEC using the steps listed on their wiki. Neither method will touch your media library.
With a dual-boot setup, you would only need to re-run the script to change the boot options, or update the legacy BIOS (if needed). Neither of which will affect your OpenELEC install in any way.
(2014-06-20, 21:09)Matt Devo Wrote: [ -> ] (2014-06-20, 18:05)noggin Wrote: [ -> ]*** EDIT : Not to worry. Decided I didn't really need ChromeOS - so went for the Stanalone Option and installed OpenElec standalone. So far so good. This little box should really rock. ***
*** EDIT 2 : Though sadly not quite perfect yet. I'd read there were problems with VAAPI. I have some 35Mbs Blu-ray H264 interlaced stuff that needs VAAPI to playback without skipping/dropping - and it hangs. In software mode it can't keep up with both H264 decoding and de-interlacing at this bitrate. I'm in Standalone mode. Is this likely to be helped by switching to a dual channel RAM set-up? ***
1) where the heck are you finding 35Mbps interlaced Bluray content?
Stuff I've mastered myself mainly from high quality 1080/50i Pro Res HQ / DNXHD captures from HD-SDI sources. I work in the broadcast industry - and the stuff is Blu-ray compliant, mainly mastered with x264 or Adobe Encore. Plays fine on other OpenElec installs, as well as on consumer Blu-ray players when burned to disc.
Quote:2) so it hangs with VAAPI enabled, or disabled b/c it can't keep up?
Occasional total freezes with VAAPI enabled. With VAAPI disabled it can't keep up (even with multithreaded decoding enabled) with decoding and deinterlacing. Even BOB. At least one CPU hits 100%.
Quote:If the latter, try it with VAAPI enabled.
Yep - the only realistic way of watching this stuff is with VAAPI enabled. Should add that the same content works fine with VAAPI and S/W deinterlacing on a Celeron 1007U Acer Revo RL80.
Quote:The driver bug doesn't seem to affect all types of content; I've yet to experience it myself
I've had one freeze with OpenElec - no way of knowing what caused it - but it was watching high bitrate 1080/50i H264 Blu-ray content.
Will try watching more content and update you based on findings.
Got it. Thanks. I'm learning. Can XBMC be updated similarly?
(2014-06-20, 21:39)noggin Wrote: [ -> ]Will try watching more content and update you based on findings.
appreciate the detailed reply. If you're able to get any logs of the lockup(s) (OE periodically collects/zips logs, check the SMB /logs dir), feel free to send them my way.
(2014-06-20, 21:42)AJ500 Wrote: [ -> ]Got it. Thanks. I'm learning. Can XBMC be updated similarly?
OpenELEC and XBMC are updated as a single item; there's no (good, user-friendly) way to update XBMC indepenently of OE
I just flashed the BIOS, when I boot with SeaBIOS nothing happens when I press ESC.
I noticed the caps lock & num lock light doesn't work. Normally I would say the keyboard isn't being recognized. The same keyboard was recognized by ChromeOS. I tried switching to a different USB port and another keyboard.
The SeaBIOS is recognizing the flash drive. Is there another way to boot from the flash drive without the keyboard?
The OpenELEC flash drive I created outside of the flash script. I tested it on another Intel system, boots Ok. I'm guessing this shouldn't matter, it's not even boot the flash drive.
Thanks.
(2014-06-20, 21:54)YellowDog Wrote: [ -> ]I just flashed the BIOS, when I boot with SeaBIOS nothing happens when I press ESC.
I noticed the caps lock & num lock light doesn't work. Normally I would say the keyboard isn't being recognized. The same keyboard was recognized by ChromeOS. I tried switching to a different USB port and another keyboard.
The SeaBIOS is recognizing the flash drive. Is there another way to boot from the flash drive without the keyboard?
Thanks.
Assume you are running a standalone setup? what keyboard(s) have you tried?
FWIW, my caps/num lock/scroll lock keys do not work on the SeaBIOS boot menu screen either
Yes I'm doing a stand alone install.
I tried 2 wired keyboards, one from Dell. I know the Dell needs power to work, cause it doesn't work on my KVM switchbox. The other keyboard I know doesn't need any power, it's a Inland.
(2014-06-20, 22:02)YellowDog Wrote: [ -> ]Yes I'm doing a stand alone install.
I tried 2 wired keyboards, one from Dell. I know the Dell needs power to work, cause it doesn't work on my KVM switchbox. The other keyboard I know doesn't need any power, it's a Inland.
I've got a wired logitech netplay neyboard here that doesn't work, lemme see if I can figure out what's going on.
In the meantime, I've personally verified that the Logitech K360 and K520 wireless keyboards both work
Ok, I got it to boot from the flash drive. I have OpenELEC installed, looks great so far.
I think the SeaBIOS didn't like I pressed ESC to many times, but I'm not entirely sure. Thanks for your help Matt
* YellowDog emails Matt a beer.
(2014-06-20, 22:20)YellowDog Wrote: [ -> ]Ok, I got it to boot from the flash drive. I have OpenELEC installed, looks great so far.
I think the SeaBIOS didn't like I pressed ESC to many times, but I'm not entirely sure. Thanks for your help Matt
* YellowDog emails Matt a beer.
good deal, glad to hear.
my non-working Logitech keyboard is showing the same timeout issue I saw previously with USB sticks that didn't show up in the boot menu. The timeout is currently set to 5s per the USB spec, and I even raised it to 10s - the keyboard still timed out. I'm guessing that there are just some devices out there that are not quite spec-compliant in certain ways in which SeaBIOS isn't accommodating.
what is the login and password for ssh openelec i have tried different passwords, also any password and it doesnt connect
(2014-06-20, 21:42)Matt Devo Wrote: [ -> ] (2014-06-20, 21:39)noggin Wrote: [ -> ]Will try watching more content and update you based on findings.
appreciate the detailed reply. If you're able to get any logs of the lockup(s) (OE periodically collects/zips logs, check the SMB /logs dir), feel free to send them my way.
It has frozen consistently on the same frame of content with VAAPI decoding. Will double check with a Haswell i5 - but pretty certain that was OK.
Not sure the best way of uploading the full .zip of the logs but this looks relevant :
02_system.log :
Code:
[ 95.318466] [drm] stuck on bsd ring
[ 95.318475] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 95.318479] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 95.318482] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 95.318485] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 95.318488] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
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.
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.