Kodi Community Forum

Full Version: OpenELEC Testbuilds for RaspberryPi (Kodi 15.0) Part 2
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Thanks. Smile

If you're installing from scratch, I'd recommend a 512MB primary FAT partition (with the remainder of the SD card used for the ext4 partition) so that you can install debug-enabled builds should the need ever arise.
Hi guys,

strange this was that it was also happening when the framerate did not change and the tv did not have to switch.
Now I have changed to omxplayer enabled I think the problem is gone.

I will have it on now and test for a couple of days and report back to you.
Strange crash where it looks like fetching addons failed right before the crash, log at http://sprunge.us/LXQJ
(2015-04-27, 21:59)zaphod24 Wrote: [ -> ]Strange crash where it looks like fetching addons failed right before the crash, log at http://sprunge.us/LXQJ

Code:
#0  0x00849f24 in PVR::CPVRClient::GetDriveSpace(long long*, long long*) ()
#1  0x0061cc5c in PVR::CPVRGUIInfo::UpdateBackendCache() ()
#2  0x0061d588 in PVR::CPVRGUIInfo::Process() ()
#3  0x00956834 in CThread::Action() ()
#4  0x009570a0 in CThread::staticThread(void*) ()

Looks like either m_pStruct, iTotal or iUsed must be NULL (or otherwise invalid).

Really need someone who knows the PVR code to comment. Might be worth creating a trac ticket.
I have a question. On my raspberry pi 2 OMXplayer was disabled by default. should it be like this?

And why is OMXplayer here, is it something special for the raspberry?
(2015-04-27, 22:07)popcornmix Wrote: [ -> ]
(2015-04-27, 21:59)zaphod24 Wrote: [ -> ]Strange crash where it looks like fetching addons failed right before the crash, log at http://sprunge.us/LXQJ

Code:
#0  0x00849f24 in PVR::CPVRClient::GetDriveSpace(long long*, long long*) ()
#1  0x0061cc5c in PVR::CPVRGUIInfo::UpdateBackendCache() ()
#2  0x0061d588 in PVR::CPVRGUIInfo::Process() ()
#3  0x00956834 in CThread::Action() ()
#4  0x009570a0 in CThread::staticThread(void*) ()

Looks like either m_pStruct, iTotal or iUsed must be NULL (or otherwise invalid).

Really need someone who knows the PVR code to comment. Might be worth creating a trac ticket.

Thanks! I opened up trac #15942.
(2015-04-27, 22:12)OurJermain Wrote: [ -> ]I have a question. On my raspberry pi 2 OMXplayer was disabled by default. should it be like this?

And why is OMXplayer here, is it something special for the raspberry?

omxplayer is disabled on Pi2 in these builds, but enabled on Pi1.
omxplayer has better performance, so is essential on Pi1 for hard videos (e.g. raw Blu-Ray rips).
Pi2 has plenty of performance so can play raw Blu-Ray rips with or without omxplayer.

dvdplayer (which you get when omxplayer is disabled) has a few advantages:
supports alsa sink for USB/I2S audio devices
supports DVD menus
supports software codecs
is more standard/widely tested so may behave better in some circumstances
New OpenELEC Isengard build #0427: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a
Linux rpi512 4.0.0 #1 Mon Apr 27 21:02:22 BST 2015 armv6l GNU/Linux

# vcgencmd version
Apr 21 2015 14:40:08
Copyright (c) 2012 Broadcom
version 2d5ad04b63af4233440c3f7c8587108223201102 (clean) (release)

# lsb_release
OpenELEC (Milhouse) - Version: devel-20150427210128-#0427-g160dc2d [Build #0427]

# vcdbg log msg 2>&1 | grep DTOK
001543.220: Kernel trailer DTOK property says yes

# Kernel device tree status: Enabled

Based on tip of OpenELEC master (160dc2d8, changelog) and tip of XBMC master (7c2d63c7, changelog) with the following modifications: Build Highlights:
  1. Improve seek performance
Build Details:
  1. newclock4:
    • New commits in this build:
      • player: implement SeekTimeRelative, disable accurate seeking for relative seeks (22f0974f)
      • get rid of inaccurate seek size percent calculation (871f9631)
      • get rid of CGUIInfoManager dependency (e1eda01c)
Why those false handshakes occur, cousing kodi constantly to reboot? Can they be avoided? The only way is to power it off for few seconds and then power it on.

http://pastebin.com/3Keyz2y6
(2015-04-28, 07:18)illiac4 Wrote: [ -> ]Why those false handshakes occur, cousing kodi constantly to reboot? Can they be avoided? The only way is to power it off for few seconds and then power it on.

http://pastebin.com/3Keyz2y6

This isn't right...
Code:
07:14:43  71.737206 T:1968623616  NOTICE: Raspberry PI firmware version:
07:14:43  71.737350 T:1968623616  NOTICE: ARM mem: 0MB GPU mem: 0MB MPG2:0 WVC1:0

Does this problem happen everytime you boot the Pi? What is in your /flash/config.txt? Which is the first build that has this problem?

Can you connect with ssh and enter "vcgencmd version" and paste the results.
Apr 21 2015 14:40:08
Copyright © 2012 Broadcom
version 2d5ad04b63af4233440c3f7c8587108223201102 (clean) (release)

http://pastebin.com/RTSkb6JC

No it does not happens every time. Mostly it happens when i upgrade the version. It also does not happen every time. Can not say about the build since it happens randomly.
Is it possible to extract edid from within openelec and use a static edid since i assume that it is my monitor.

Note: Now it crashes every time even after entering hdmi_safe=1
@illiac4: did you run that vcgencmd command while Kodi is in a restart loop, or had Kodi started successfully? I'm wondering if you might get a different result (ie. an error) while Kodi is restarting.

"vcdbg log msg 2>&1" might be useful too (while Kodi is restarting).
After the last test build my Rpi 1 suddenly rebooted. This also happened with the previous build (woke up to see my tv was on).
@Gregoire: Are you sure the Pi (OpenELEC) rebooted, and it wasn't just Kodi restarting? Check /storage/.kodi/temp for a kodi_crashlog, and upload the latest file if you find one.
(2015-04-28, 11:03)Milhouse Wrote: [ -> ]@Gregoire: Are you sure the Pi (OpenELEC) rebooted, and it wasn't just Kodi restarting? Check /storage/.kodi/temp for a kodi_crashlog, and upload the latest file if you find one.

As I remember the last "reboot" it was a sudden black screen and then the kodi logo. So I guess it must have been kodi restarting.