• 1
  • 74
  • 75
  • 76(current)
  • 77
  • 78
  • 277
OpenELEC Testbuilds for RaspberryPi Part 2
(2013-10-20, 21:22)RichG Wrote:
(2013-10-20, 21:20)f1vefour Wrote: I am sure this is a firmware issue, at least on other distributions.

Same firmware with Frodo seems to be OK here......

What do you mean, I wasn't talking about Frodo? Try downgrading the firmware several revisions back and reboot works as intended on Gotham, I am not sure how the two are related but you should test before jumping to conclusions.
(2013-10-20, 21:26)f1vefour Wrote:
(2013-10-20, 21:22)RichG Wrote:
(2013-10-20, 21:20)f1vefour Wrote: I am sure this is a firmware issue, at least on other distributions.

Same firmware with Frodo seems to be OK here......
I am not sure how the two are related but you should test before jumping to conclusions.

I think you should drink a coffee before jumping on a thread!
(2013-10-20, 21:11)Swifty Wrote: I'm using Mediaportal backend, I see the same behaviour with recordings as well as live.

Pressing 'O' while it's playing shows that it's using omx-h264, I assume that is hw decoded on the Pi ?

(At the moment I've not purchased any of the additional codecs since I'm changing to a different Pi next week (a 512mb model).

Yes, h264 is hw decoded.
The 256MB might explain the slowness you're describing. What's the RAM distribution you have in config.txt? My very first PI (256MB) Pi works quite well, only slower than all others I own (all 512MB).

Unfortunately I can't help you with Mediaportal backend. Never used it!

(2013-10-20, 21:43)RichG Wrote:
(2013-10-20, 21:26)f1vefour Wrote:
(2013-10-20, 21:22)RichG Wrote: Same firmware with Frodo seems to be OK here......
I am not sure how the two are related but you should test before jumping to conclusions.

I think you should drink a coffee before jumping on a thread!

More coffee? He might have a stroke!Rofl

@f1vefour, calm down. It's Sunday. Have a beer instead! This is such a friendly community. Nod
Smile
(2013-10-20, 21:26)f1vefour Wrote: Try downgrading the firmware several revisions back and reboot works as intended on Gotham, I am not sure how the two are related but you should test before jumping to conclusions.

Searching might be a better alternative to testing in this case... Wink

It's a known issue in OE Gotham builds, and has been for some time. popcornmix even posted a link to the commit which may be responsible. It's certainly not firmware related.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2013-10-20, 22:05)MilhouseVH Wrote:
(2013-10-20, 21:26)f1vefour Wrote: Try downgrading the firmware several revisions back and reboot works as intended on Gotham, I am not sure how the two are related but you should test before jumping to conclusions.

Searching might be a better alternative to testing in this case... Wink

It's a known issue in OE Gotham builds, and has been for some time. popcornmix even posted a link to the commit which may be responsible. It's certainly not firmware related.

It's not only OE that suffers from this bug. I appreciate your links but without testing previous versions how are you certain it's not firmware related? I am genuinely asking, not saying you don't know what your taking about.

@hudo
I am perfectly calm, me saying don't jump to conclusions is a natural response. No malice was intended ;-)
(2013-10-20, 22:22)f1vefour Wrote: I appreciate your links but without testing previous versions how are you certain it's not firmware related? I am genuinely asking, not saying you don't know what your taking about.

Did you click on the links? The seg fault is Python related, and causes xbmc.bin to terminate with an unexpected exit code which is used to determine whether to reboot, power off or - when the exit code isn't recognised - restart xbmc.bin.

There's no need to test previous firmware - reverting the commit identified by popcornmix solves the problem. During your testing, have you observed the seg fault and associated traceback?
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2013-10-20, 22:43)MilhouseVH Wrote:
(2013-10-20, 22:22)f1vefour Wrote: I appreciate your links but without testing previous versions how are you certain it's not firmware related? I am genuinely asking, not saying you don't know what your taking about.

Did you click on the links? The seg fault is Python related, and causes xbmc.bin to terminate with an unexpected exit code which is used to determine whether to reboot, power off or - when the exit code isn't recognised - restart xbmc.bin.

There's no need to test previous firmware - reverting the commit identified by popcornmix solves the problem. During your testing, have you observed the seg fault and associated traceback?

My issue was apparently different. When selecting shutdown from within XBMC the Pi would only reboot, I am uncertain if a segfault condition was occurring although I don't believe so as reverting firmware resolved this issue.

I apologize to RichG for doing exactly what I said don't do and jumping to conclusions. The issue persists on concurrent revisions of Gotham, your debugging seems sane and correctly identifies the problem. I forgo the firmware theory and will take your word on it.
(2013-10-20, 20:05)Koloss Wrote:
(2013-10-20, 12:27)botribun Wrote: It looks like this in advancedsettings.xml and disabling the DIM screensaver brings down the load and temps.

Code:
<gui>
       <algorithmdirtyregions>3</algorithmdirtyregions>
       <nofliptimeout>1</nofliptimeout>
   </gui>

What is now your idle temperatue?
Its back at ~52C/~20% cpu load, with Amber/Confluence and screensaver OFF.

There must be a incompatibility with this build and the screensaver addon, after a fresh boot the temps and load are fine but as soon the screensaver kicks in, the cpu load is at ~90% while idle and the temp are rising up to ~75C degree and doesn't goes down, till I boot again.

With screensaver disabled, the temps and cpu load are back to normal on any menu/screen position.

/edit
using Frodo (18.10.2013)
Which rbej build is exhibiting increased temperatures?

Additionally, I am looking to download Rbej's Gotham 10-02 build. But then I notice there is also Popcorn's 10-02 build as well. What is the difference between the two?

I am only utilize the build to stream live video.

Many thanks in advance.
Hi,

I've recently upgraded from the stable Frodo build to Rbej's Gotham 10-02 build and the "resume" function doesn't seem to work anymore, either using the MythTV PVR addon or in videos over upnp. The videos just start playing from the start again. I've also tried popcornmix's 10-09 build and I have the same problem.

I realise these are a work in progress so I'd just thought I'd let you know as I haven't seen it mentioned.
Experiencing a rather strange issue not 100% sure if its related to your builds specifically/gotham. Video files with subtitles take a while to start. So long in fact I thought the box had frozen up until I let it sit for a while. After almost an hour the video started playing out of nowhere. The logs weren't really much help for googling the issue so I decided to see if anyone else has experienced this. Here is a snippet of my log file.

Code:
20:37:45 T:2851775584   DEBUG: FactoryCodec - Overlay: SSA Subtitle Decoder - Opening
20:37:45 T:2851775584   DEBUG: SECTION:LoadDLL(libass.so.4)
20:37:45 T:2731537504   DEBUG: COMXPlayerAudio - CDVDMsg::PLAYER_STARTED 0
20:37:45 T:2851775584   DEBUG: Loading: libass.so.4
20:37:45 T:2851775584    INFO: CDVDSubtitlesLibass: Creating ASS library structure
20:37:45 T:2851775584    INFO: CDVDSubtitlesLibass: Initializing ASS library font settings
20:37:45 T:2851775584    INFO: CDVDSubtitlesLibass: Initializing ASS Renderer
20:38:00 T:2815423584   DEBUG: Thread JobWorker 2815423584 terminating (autodelete)
20:38:00 T:2902205536   DEBUG: Thread JobWorker 2902205536 terminating (autodelete)
20:38:00 T:2797818976   DEBUG: Thread JobWorker 2797818976 terminating (autodelete)
20:38:00 T:2806207584   DEBUG: Thread JobWorker 2806207584 terminating (autodelete)
20:39:40 T:2936026208   DEBUG: ### [Qlock] - Delaying 3 secs
20:40:00 T:2936026208   DEBUG: Previous line repeats 9 times.
20:40:00 T:2936026208   DEBUG: ### [Qlock] - Delaying 240 secs
20:40:50 T:3061891600  NOTICE: NFS: sending keep alive after 180 s.
20:44:00 T:2936026208  NOTICE: Previous line repeats 1 times.
20:44:00 T:2936026208   DEBUG: ### [Qlock] - Delaying 240 secs
20:47:08 T:3061891600  NOTICE: NFS: sending keep alive after 180 s.
20:47:59 T:2936026208   DEBUG: ### [Qlock] - Delaying 240 secs
20:50:17 T:3061891600  NOTICE: NFS: sending keep alive after 180 s.
20:51:59 T:2936026208   DEBUG: ### [Qlock] - Delaying 240 secs
20:53:26 T:3061891600  NOTICE: NFS: sending keep alive after 180 s.
20:55:59 T:2936026208   DEBUG: ### [Qlock] - Delaying 240 secs
20:56:36 T:3061891600  NOTICE: NFS: sending keep alive after 180 s.
20:59:58 T:2936026208  NOTICE: Previous line repeats 1 times.
20:59:58 T:2936026208   DEBUG: ### [Qlock] - Delaying 240 secs
21:02:54 T:3061891600  NOTICE: NFS: sending keep alive after 180 s.
21:03:58 T:2936026208   DEBUG: ### [Qlock] - Delaying 240 secs
21:06:03 T:3061891600  NOTICE: NFS: sending keep alive after 180 s.
21:07:57 T:2936026208   DEBUG: ### [Qlock] - Delaying 240 secs
21:09:13 T:3061891600  NOTICE: NFS: sending keep alive after 180 s.
21:11:57 T:2936026208   DEBUG: ### [Qlock] - Delaying 240 secs
21:12:22 T:3061891600  NOTICE: NFS: sending keep alive after 180 s.
21:15:56 T:2936026208  NOTICE: Previous line repeats 1 times.
21:15:56 T:2936026208   DEBUG: ### [Qlock] - Delaying 240 secs
21:18:40 T:3061891600  NOTICE: NFS: sending keep alive after 180 s.
21:19:56 T:2936026208   DEBUG: ### [Qlock] - Delaying 240 secs
21:21:49 T:3061891600  NOTICE: NFS: sending keep alive after 180 s.
21:22:44 T:2851775584    INFO: CDVDSubtitlesLibass: Creating new ASS track
21:22:44 T:2851775584   DEBUG: FactoryCodec - Overlay: SSA Subtitle Decoder - Opened

Full log can be found here http://xbmclogs.com/show.php?id=70482

I've never had any issues with subtitled videos before and nothing really stands out in the logs to me. I originally thought it was an issue with my NFS shares so I tried it via SMB and experienced the same issue.
I've been having a fair few problems with LiveTV with the 10/02 build that I don't think I had before. Sometimes when stopping it gets stuck looping the sound and I have to power cycle to unfreeze it. Other times it just freezes midstream whilst playing, as it did here http://xbmclogs.com/show.php?id=73517
Apparently the reason why I can't install the skin xTV-SAF and am getting "Dependencies not met" is because the 10/02 Gotham rbej build I'm using is missing xbmc.json. There is a folder usr/share/xbmc/addons/xbmc.json with an addon.xml in it but no other files.
(2013-10-22, 16:54)doveman2 Wrote: I've been having a fair few problems with LiveTV with the 10/02 build that I don't think I had before. Sometimes when stopping it gets stuck looping the sound and I have to power cycle to unfreeze it. Other times it just freezes midstream whilst playing, as it did here http://xbmclogs.com/show.php?id=73517

Are you playing live rtmp streams?
  • 1
  • 74
  • 75
  • 76(current)
  • 77
  • 78
  • 277

Logout Mark Read Team Forum Stats Members Help
OpenELEC Testbuilds for RaspberryPi Part 223