[magy77]

Ive installed 4.1.4 and sw filter is off. No freezing untill now...

[Matt Devo]

Ive read this but its no more freezing. Since 4.1.3

really? have you tested enough? that would be great news

Ive installed 4.1.4 and sw filter is off. No freezing untill now...

look, not to be a dick, but there's a high probability that you're going to run into the bug without the 'Use SW filter for VAAPI' setting enabled. I don't really care if you didn't have an issue up until 4.1.4; the bug still exists, so use the recommended setting (which has zero performance impact) until it's confirmed as fixed. Then, if you're still having issues, provide a sample file and debug log.

[magy77]

Well, that was hard but its ok. Its noted

[falgarin]

I found that in order to fix HDMI sound I had to go to xbmc system then setting then audio (top part) you will see hdmi selected then pick 2.0 or 5.1 then pick fixed for next choice and last pick 192 on rate selection, that will make audio work.Then to increase volume play any movie .When you see the movie playiing you will an icon for audio select that
The first two setting will increase volume I find setting first to 8 and moving the second to middle will work, but you try
what works best for you. Last pick make this selection default for all video and that should fix it.

Matt is there anyway to update (run script again) the setup without resetting to factory staus and running script, I find if
I run the script again it just resets my old install on xmbc and OpenElec.
Thanks

[Matt Devo]

Matt is there anyway to update (run script again) the setup without resetting to factory staus and running script, I find if
I run the script again it just resets my old install on xmbc and OpenElec.
Thanks

I'm not sure what you're asking exactly. If you want to reset XBMC/OpenELEC, there's a built-in function to do that (System -> OpenELEC -> System -> Reset to Defaults).

[JonniMR]

Can anyone help me here.

My Chromebox wont boot it goes to a black screen and displays the following at the top left corner:

Code:

***Error in check_disks: could not repair filesystem, dropping to debug shell, try to run 'fsck' manually: ***
### Starting debugging shell... type exit to quit ###
sh: can't access tty; job control turned off
#_

Not sure what happened here.

[falgarin]

Matt
What I want to do is rerun the script so I get new version of OpenElec beta and any new improvement you have made to the script.When I boot my version it says dated 6/20 I would like the version where it says 07/20.
Thanks

[Matt Devo]

Matt
What I want to do is rerun the script so I get new version of OpenElec beta and any new improvement you have made to the script.When I boot my version it says dated 6/20 I would like the version where it says 07/20.
Thanks

updating the firmware (via the script) and OpenELEC are two completely different operations, both of which are covered in the wiki page. If you're not having any issues, I'd recommend leaving the firmware alone.

[jmhenry5150]

Stupid newb question...

Now that XBMC 13.2 is out, do we wait for OpenELEC to update itself or are we supposed to update XBMC?

Thanks!

-Mike

[Matt Devo]

Stupid newb question...

Now that XBMC 13.2 is out, do we wait for OpenELEC to update itself or are we supposed to update XBMC?

Thanks!

-Mike

update OpenELEC manually if you want the latest beta, or wait for the next stable to update automatically. XBMC is not able to be updated independently of OpenELEC.

[jmhenry5150]

Stupid newb question...

Now that XBMC 13.2 is out, do we wait for OpenELEC to update itself or are we supposed to update XBMC?

Thanks!

-Mike

update OpenELEC manually if you want the latest beta, or wait for the next stable to update automatically. XBMC is not able to be updated independently of OpenELEC.

Ok so from what I gather, don't do anything and let OpenELEC do the updating when it's ready?

[Matt Devo]

Ok so from what I gather, don't do anything and let OpenELEC do the updating when it's ready?

if you're using a stable version (eg, 4.0.7) it won't automatically update to a beta (eg, 4.1.4), so you'll have to do that manually. There's more info and a link in the wiki. The ChromeBox is no different than any other x86 PC when it comes to running OpenELEC, so all the info/documentation on their site is valid as well.

[jmhenry5150]

Ok well you lost me there...sorry...

My thinking is that OpenELEC and XBMC are 2 different animals and when a new version of XBMC comes out (like the new stable release of 13.2 did), us OpenELEC users do nothing and wait for OpenELEC to create a new version...then we let OpenELEC do the updating...

Right?

[Matt Devo]

Ok well you lost me there...sorry...

My thinking is that OpenELEC and XBMC are 2 different animals and when a new version of XBMC comes out (like the new stable release of 13.2 did), us OpenELEC users do nothing and wait for OpenELEC to create a new version...then we let OpenELEC do the updating...

Right?

right - OpenELEC users only update OpenELEC (either automatically or manually, as I previously noted); XBMC is part of the OS image and is not able to be updated independently.

[JonniMR]

Can anyone help me here.

My Chromebox wont boot it goes to a black screen and displays the following at the top left corner:

Code:

***Error in check_disks: could not repair filesystem, dropping to debug shell, try to run 'fsck' manually: ***
### Starting debugging shell... type exit to quit ###
sh: can't access tty; job control turned off
#_

Not sure what happened here.

Anyone know what caused this?