[Symbiot]

Hi

I've been experiencing some problems with my openElec raspberry pi..

Logs can be found here:

http://xbmclogs.com/show.php?id=95712

Scenario:

install via berryboot..
let openelec/xbmc autoupdate etc..
Add autostart.sh to mount network folder.
Add said folders as 'movies' & 'tv series' and let xbmc scan the folders.
Now I did this yesterday.. a clean install, freshly formatted SD-card & usb stick.
All was well...
Then today.. came home from work and wanted to watch an episode of law & order..
but no... when I select the episode I want to watch.. it says 'working' for some seconds then the 'working' disappear and nothing else happens..

I've seen this issue 3 or four times now.. and each time I've tried checking the logs.. and found the same error each time.. again I refer you to the log..
the main error.. as I see it is:

Code:

19:15:48 T:2769286240   ERROR: COMXCoreComponent::Initialize - could not get component handle for OMX.broadcom.clock omx_err(0x80001009

I can't seem to find much on google.. so I am hoping someone here can decipher the logs and point me in the right direction!

[popcornmix]

Can you post the complete log?
Has this install every played videos for you?

[Symbiot]

hi

this is the complete log:

http://xbmclogs.com/show.php?id=95722

please ignore the 'is missing' entries.. they are NOT the issue..

this install played videos just fine yesterday.. no problems.

today... not so much.. I have tried the usual reboots etc. but didn't help..

---

I've had this issue with & without overclocking as well...
always the same powersupply..

I did an upgrade, for the fun of it, to gotham from my old install which never gave me problems... I just wanted to try it.. and after this I've seen this issue... even after I returned to stock openelec 3.0.3

[popcornmix]

This looks like the problem:

Code:

19:14:16 T:3047075840  NOTICE: Raspberry PI firmware version: Sep  7 2013 20:11:30

Recent xbmc builds need a recent firmware version.

I wonder if BerryBoot is confusing the openelec updater?

I'd suggest download the latest:
start_x.elf
fixup_x.dat
bootcode.bin
from https://github.com/Hexxeh/rpi-firmware.

and copy them to openelec's boot partition (I think with berryboot that is the first partition, but I'm not sure).
You may need to rename start_x.elf to start.elf and fixup_x.dat to fixup.dat when copying them.

[Symbiot]

will give it a go.
What's the difference between the start.elf & start_x.elf? ( and the rest of the _x)

[popcornmix]

will give it a go.
What's the difference between the start.elf & start_x.elf? ( and the rest of the _x)

The _x versions include software codecs (VP6, VP8, Theora) and camera support.
Normally you add start_x=1 to config.txt to use them, but openelec doesn't use that, but renames them to start.elf/fixup.dat.

[Symbiot]

replacing the bootcode.bin file fcuks up the boot. as soon as I revert back.. it works again.. well it boots.

I replaced the fixup_x.dat & start_x.elf

I didn't rename them... I also formatted the SD card and started over...

dunno if NOT renaming the files will make a difference?

[popcornmix]

replacing the bootcode.bin file fcuks up the boot. as soon as I revert back.. it works again.. well it boots.

I replaced the fixup_x.dat & start_x.elf

I didn't rename them... I also formatted the SD card and started over...

dunno if NOT renaming the files will make a difference?

You may have to ask this in a berry boot forum. I'm not sure exactly what it does.
Obviously installing openelec to a dedicated sdcard is one solution.

I would guess that copying those files without renaming (or adding start_x=1 to config.txt) will have no effect,
but as I'm not really sure exactly what berry boot does, I can't be certain.

[Symbiot]

I am only using berryboot because it was easy.. I have no need for it.. but last time I tried just installing openElec.. I failed.. but perhaps I should give it a go again.. any new guides up?

[popcornmix]

It pretty easy to update builds once you have any version of openelec installed.

So you could download OpenELEC-RPi.arm-3.0.6.img.zip from here:
http://openelec.thestateofme.com/

write it to sdcard (using a tool like http://sourceforge.net/projects/win32diskimager/)

That's quite an old image. It will probably auto-update to latest stable (3.2.4), but
you can manually update to custom builds with the SMB exported update folder. See:
http://wiki.openelec.tv/index.php?title=...g_OpenELEC

[soulchild]

I ran into this problem as well. Indeed, the problem seems to be the old raspberry firmware. Just download/clone the repository at

https://github.com/raspberrypi/firmware

and copy everything from the /boot directory to the root of your SD card overwriting the old firmware files. Hope this helps!