Login at Kodi Home

querty1000 · 2015-05-07, 13:30

(2015-05-07, 11:46)popcornmix Wrote:
(2015-05-07, 09:28)querty1000 Wrote: Stupid question, how are the values used to get a performace boost?

By default the CEC button repeat rate is determined by the TV. For some manufacturers this may only be a couple of repeats a second which can be slow for scrolling long lists.
In settings/system/input/peripherals/cec adjust the "repeat rate" from default of 0 to, perhaps 100, which will give ten repeats a second when held down.

Thanx, i will try it afternoon at home. I'm not shure, if the LG-Simplelink is really crap and if i can something tune to work "snapier".

**zaphod24** · 2015-05-07, 15:10

(2015-05-07, 04:39)Milhouse Wrote: I had a situation where my overlays folder had become corrupt (I had a file called "FSCK0000.REC" that looked like the contents of the overlays directory) and produced the same error in vcdbg. I'd suggest renaming or removing the overlays folder from the first Pi, then re-upgrading to #0506 so that a new overlays folder is copied over. Then see if you have a working sdhost.

Well, I didn't have any weird files in the overlay folder but I deleted it and re-upgraded to 0506 and now dmesg reports the SDHost driver is being used again. Thanks Milhouse!

Milhouse · 2015-05-07, 16:59

(2015-05-07, 11:55)startv Wrote: I checked the debug option, then I have tried 3 more times,still I can't get any logfiles. Sorry. Wish somebody to keep on it.

It's unusual for you not to have a crash log if Kodi is actually crashing. Either you're not running a test build (ie. still on 5.0.8) or Kodi isn't crashing but exiting normally for some other reason.

Can you run the following and paste the links:

Code:
cat /storage/.kodi/temp/kodi.log | pastebinit

ls -la /storage/.kodi/temp | pastebinit

startv · 2015-05-07, 18:00

(2015-05-07, 16:59)Milhouse Wrote:
(2015-05-07, 11:55)startv Wrote: I checked the debug option, then I have tried 3 more times,still I can't get any logfiles. Sorry. Wish somebody to keep on it.

It's unusual for you not to have a crash log if Kodi is actually crashing. Either you're not running a test build (ie. still on 5.0.8) or Kodi isn't crashing but exiting normally for some other reason.

Can you run the following and paste the links:

Code:
cat /storage/.kodi/temp/kodi.log | pastebinit ls -la /storage/.kodi/temp | pastebinit

I execute
cat /storage/.kodi/temp/kodi.log | pastebinit
ls -la /storage/.kodi/temp | pastebinit
the ssh windwos show nothing, so I closed ssh windows,Then ssh in again, Run "cp /storage/.kodi/temp/kodi.log /storage/logfiles,I got a kodi.log file,
I upload to the below link ,please download it.
http://pan.baidu.com/s/1jGmszqe

Milhouse · (This post was last modified: 2015-05-07, 18:26 by Milhouse.)

(2015-05-07, 18:00)startv Wrote: I execute
cat /storage/.kodi/temp/kodi.log | pastebinit
ls -la /storage/.kodi/temp | pastebinit
the ssh windwos show nothing, so I closed ssh windows

If pastebinit is not working, this would suggest your Pi has internet connectivity issues.

Without a crashlog, I'm not able to help you - you'll need to find the crashlogs and upload the most recent file to pastebin.com in order to take this forward.

(2015-05-07, 18:00)startv Wrote: Then ssh in again, Run "cp /storage/.kodi/temp/kodi.log /storage/logfiles,I got a kodi.log file,
I upload to the below link ,please download it.
http://pan.baidu.com/s/1jGmszqe

Please use pastebin.com if you can, my Chinese isn't too hot. I managed to download your log, and it appears your Pi is failing to get any data from 192.168.1.50:8089.

Better yet, upload your most recent crashlog to pastebin.com. If Kodi really is crashing then you'll have up to 10 crashlogs in the /storage/.kodi/temp folder.

For example, this is what I have:

Code:
rpi512:~ # ls -la /storage/.kodi/temp/

total 17472

drwxr-xr-x    7 root     root          4096 May  6 22:58 .

drwxr-xr-x    9 root     root          4096 Jan  2 18:46 ..

-rw-r--r--    1 root     root      17185792 Feb  1 13:33 commoncache.db

srwxr-xr-x    1 root     root             0 May  6 22:58 commoncache.socket

-rw-r--r--    1 root     root          1069 May  7 16:08 cookies.dat

drwxr-xr-x    2 root     root          4096 Dec 15 11:55 fonts

drwxr-xr-x    2 root     root          4096 May  2 16:22 kodi

-rw-r--r--    1 root     root        194118 May  7 16:08 kodi.log

-rw-r--r--    1 root     root         50342 May  6 22:56 kodi.old.log

-rw-r--r--    1 root     root         10755 Apr 20 20:10 kodi_crashlog_20150420201037.log

-rw-r--r--    1 root     root         10755 Apr 20 20:10 kodi_crashlog_20150420201045.log

-rw-r--r--    1 root     root         10755 Apr 20 20:10 kodi_crashlog_20150420201052.log

-rw-r--r--    1 root     root         10755 Apr 20 20:11 kodi_crashlog_20150420201100.log

-rw-r--r--    1 root     root         10755 Apr 20 20:11 kodi_crashlog_20150420201107.log

-rw-r--r--    1 root     root         10755 Apr 20 20:11 kodi_crashlog_20150420201116.log

-rw-r--r--    1 root     root         10755 Apr 20 20:11 kodi_crashlog_20150420201129.log

-rw-r--r--    1 root     root         10755 Apr 20 20:11 kodi_crashlog_20150420201144.log

-rw-r--r--    1 root     root         10755 Apr 20 20:12 kodi_crashlog_20150420201158.log

-rw-r--r--    1 root     root        298741 Apr 27 17:56 kodi_crashlog_20150427175601.log

drwxr-xr-x    8 root     root          4096 Aug 22  2014 scrapers

drwxr-xr-x    2 root     root          4096 Apr  3  2013 temp

drwxr-xr-x    2 root     root          4096 Aug 20  2013 weather

Upload the most recent crashlog file (in my case, that would be "kodi_crashlog_20150427175601.log").

What would also help is for you to determine the last test build that works for you - can you go backwards, starting with #0505 until you find the last working build. You mentioned #0411 as working, so it's somewhere in that range. Maybe the recent curl bump is causing your problem?

startv · (This post was last modified: 2015-05-08, 00:11 by startv.)

(2015-05-07, 18:25)Milhouse Wrote:
(2015-05-07, 18:00)startv Wrote: I execute
cat /storage/.kodi/temp/kodi.log | pastebinit
ls -la /storage/.kodi/temp | pastebinit
the ssh windwos show nothing, so I closed ssh windows

If pastebinit is not working, this would suggest your Pi has internet connectivity issues.

Without a crashlog, I'm not able to help you - you'll need to find the crashlogs and upload the most recent file to pastebin.com in order to take this forward.

(2015-05-07, 18:00)startv Wrote: Then ssh in again, Run "cp /storage/.kodi/temp/kodi.log /storage/logfiles,I got a kodi.log file,
I upload to the below link ,please download it.
http://pan.baidu.com/s/1jGmszqe

Please use pastebin.com if you can, my Chinese isn't too hot. I managed to download your log, and it appears your Pi is failing to get any data from 192.168.1.50:8089.

Better yet, upload your most recent crashlog to pastebin.com. If Kodi really is crashing then you'll have up to 10 crashlogs in the /storage/.kodi/temp folder.

For example, this is what I have:

Code:
rpi512:~ # ls -la /storage/.kodi/temp/ total 17472 drwxr-xr-x 7 root root 4096 May 6 22:58 . drwxr-xr-x 9 root root 4096 Jan 2 18:46 .. -rw-r--r-- 1 root root 17185792 Feb 1 13:33 commoncache.db srwxr-xr-x 1 root root 0 May 6 22:58 commoncache.socket -rw-r--r-- 1 root root 1069 May 7 16:08 cookies.dat drwxr-xr-x 2 root root 4096 Dec 15 11:55 fonts drwxr-xr-x 2 root root 4096 May 2 16:22 kodi -rw-r--r-- 1 root root 194118 May 7 16:08 kodi.log -rw-r--r-- 1 root root 50342 May 6 22:56 kodi.old.log -rw-r--r-- 1 root root 10755 Apr 20 20:10 kodi_crashlog_20150420201037.log -rw-r--r-- 1 root root 10755 Apr 20 20:10 kodi_crashlog_20150420201045.log -rw-r--r-- 1 root root 10755 Apr 20 20:10 kodi_crashlog_20150420201052.log -rw-r--r-- 1 root root 10755 Apr 20 20:11 kodi_crashlog_20150420201100.log -rw-r--r-- 1 root root 10755 Apr 20 20:11 kodi_crashlog_20150420201107.log -rw-r--r-- 1 root root 10755 Apr 20 20:11 kodi_crashlog_20150420201116.log -rw-r--r-- 1 root root 10755 Apr 20 20:11 kodi_crashlog_20150420201129.log -rw-r--r-- 1 root root 10755 Apr 20 20:11 kodi_crashlog_20150420201144.log -rw-r--r-- 1 root root 10755 Apr 20 20:12 kodi_crashlog_20150420201158.log -rw-r--r-- 1 root root 298741 Apr 27 17:56 kodi_crashlog_20150427175601.log drwxr-xr-x 8 root root 4096 Aug 22 2014 scrapers drwxr-xr-x 2 root root 4096 Apr 3 2013 temp drwxr-xr-x 2 root root 4096 Aug 20 2013 weather

Upload the most recent crashlog file (in my case, that would be "kodi_crashlog_20150427175601.log").

What would also help is for you to determine the last test build that works for you - can you go backwards, starting with #0505 until you find the last working build. You mentioned #0411 as working, so it's somewhere in that range. Maybe the recent curl bump is causing your problem?

I down to #0504,PVR working ,then update to #0505,continue rebooting, I closed DVBviewer Server from PC, Pi backup to normal,but testbuild has no VPN networking setup,so I down to #0508,setup VPN, then ssh in,run cat $(ls -1 /storage/.kodi/temp/kodi_crash* | tail -1) | pastebinit,finally,I got the link, wish it be useful
http://sprunge.us/VKjJ

there is many network connect limited in PRC. Confused

Milhouse · 2015-05-08, 00:13

New OpenELEC Isengard build #0507: RPi / RPi2
(Supercedes previous build)

Code:
# uname -a

Linux rpi512 4.0.1 #1 Thu May 7 22:05:00 BST 2015 armv6l GNU/Linux

# vcgencmd version

May  1 2015 18:56:06 

Copyright (c) 2012 Broadcom

version f5f5ba5f2423c3dff6ccd4ca4b832264cd33f12a (clean) (release)

# lsb_release

OpenELEC (Milhouse) - Version: devel-20150507220411-#0507-gf46312e [Build #0507]

# vcdbg log msg 2>&1 | grep DTOK

001545.238: Kernel trailer DTOK property says yes

# Kernel device tree status: Enabled

Based on tip of OpenELEC master (f46312e3, changelog) and tip of XBMC master (db6e8e82, changelog) with the following modifications:

Includes newclock4 patches
Excludes the OpenELEC fernetmenta patches due to conflicts with newclock4
Excludes the OpenELEC linux-01-RPi_support patch in favour of sourcing these and possibly more recent patches directly from kernel branch rpi-4.0.y
Default setting for "Show RSS Feed" changed to disabled (new installs only) [patch details]
Disabled "Total Duration" in Confluence (see build #0221 for details)
Includes latest dcadec master (98fb3b60)
Includes latest kodi-platform master (054a42f6)
Includes latest libcec master (e39ec0fc)
Includes latest libnfs master (77e3d80f)
Includes platform master (c2819010)
Includes latest addons: audiodecoder.modplug (c7e8ca82), audiodecoder.nosefart (c77e5a12), audiodecoder.sidplay (f2e7d985), audiodecoder.snesapu (9fc775b1), audiodecoder.stsound (775c858d), audiodecoder.timidity (bf9ff93d), audiodecoder.vgmstream (0c3a51a2), audioencoder.flac (84acb141), audioencoder.lame (3eb59de9), audioencoder.vorbis (d556a687), audioencoder.wav (40aaedfa), pvr.argustv (2c8fd66f), pvr.demo (da6b9cb6), pvr.dvblink (7a246406), pvr.dvbviewer (cf13773a), pvr.filmon (933482c0), pvr.hts (e27bf37e), pvr.iptvsimple (48b11900), pvr.mediaportal.tvserver (ca7abf3e), pvr.mythtv (7c1f311f), pvr.nextpvr (c13e8e26), pvr.njoy (deea68bd), pvr.pctv (d80844ba), pvr.stalker (92cb0210), pvr.vbox (d5f4669b), pvr.vdr.vnsi (153fb125), pvr.vuplus (e47adee6), pvr.wmc (c25a7deb)
Include master...stefansaraev:81460ebe: Add platform package, libCEC 3.0.0 support
Include patch: Add experimental splash video
Include patch: Enable audiodecoder, audioencoder, pvr and visualization addons
Include PR:6732: [pvr] fixed crash when multiple add-on instances get registered
Include PR:6919: added: also hide thumbs for unwatched episodes if option to show plot is off
Include PR:7048: videodb: Don't allow column value length to exceed key size of unique index
Include PR:7061: addons: pvr and audiodecoder are optional addons, disable by default
Include PR:7065: [pvr] Bump pvr.hts to version 2.1.8
Include PR:7072: [pvr] bumps addons to use libplatform

Build Highlights:

newclock4: include CEC repeating keypress commits

Build Details:

OpenELEC:
- libhdhomerun: bump to 20150406 (PR:4131, 1 commit, 1 file changed)
XBMC:
- Ignore android build artifact (PR:7075, 1 commit, 1 file changed)
- fixed: make sure we don't match a substring of an extension or a mime… (PR:7077, 1 commit, 1 file changed)
- [win32] Fix: CWinIdleTimer::StartZero - do not set ES_SYSTEM_REQUIRED… (PR:7066, 1 commit, 1 file changed)
- update re-Touched skin (db6e8e82)
newclock4:
- New commits in this build:
  - [libcec] Add repeating keypress patch from popcornmix' repo (dbc81189)
  - [cec] Allow repeat delay to be increased higher (a725c024)
- Commits no longer in build:
  - Revert "[cec] Temp - more logging" (90e2a644)
  - Revert "[cec] Don't discard buttons when repeat mode is enabled" (0fc1c68f)
  - Revert "[cec] Add settings for configuring button repeats" (b5ca9aaa)
  - fixup! [players] Add settings option to enable MVC support (b7429503)
  - [screensavers] Couple more... (4fb91fde)
  - fixup! renderer: Allow an opaque pointer to be passed from renderer to codec (30ef9a6b)
  - fixup! [screensavers] Couple more... (8e6ed05c)
  - squash: Move renderinfo into a structure (7aa22258)
Additional commits/pull requests/changes not yet merged upstream:
- Updated: master...stefansaraev:81460ebe: Add platform package, libCEC 3.0.0 support

Milhouse · (This post was last modified: 2015-05-08, 00:29 by Milhouse.)

(2015-05-08, 00:11)startv Wrote: I down to #0504,PVR working ,then update to #0505,continue rebooting, I closed DVBviewer Server from PC, Pi backup to normal,but testbuild has no VPN networking setup,so I down to #0508,setup VPN, then ssh in,run cat $(ls -1 /storage/.kodi/temp/kodi_crash* | tail -1) | pastebinit,finally,I got the link, wish it be useful
http://sprunge.us/VKjJ

Thanks for persevering. Smile

However your crashlog is from #0504, which you say is working, so I'm confused - can you double check which build is working? Presumably #0503 is working...

From the crashlog, it appears that #0504 is choking on the EPG database update. Can you try renaming your /storage/.kodi/userdata/Database/Epg10.db file as follows:

Code:
systemctl stop kodi

mv /storage/.kodi/userdata/Database/Epg10.db /storage/.kodi/userdata/Database/Epg10.db.bak

systemctl start kodi

and then test #0504 (preferably #0507) again - confirm if it continues to crash, or is now OK.

If the crashing continues, you probably need to throw it over to the pvr.dvbviewer addon maintainer and see what he/she thinks.

startv · 2015-05-08, 00:48

(2015-05-08, 00:28)Milhouse Wrote:
(2015-05-08, 00:11)startv Wrote: I down to #0504,PVR working ,then update to #0505,continue rebooting, I closed DVBviewer Server from PC, Pi backup to normal,but testbuild has no VPN networking setup,so I down to #0508,setup VPN, then ssh in,run cat $(ls -1 /storage/.kodi/temp/kodi_crash* | tail -1) | pastebinit,finally,I got the link, wish it be useful
http://sprunge.us/VKjJ

Thanks for persevering.

However your crashlog is from #0504, which you say is working, so I'm confused - can you double check which build is working? Presumably #0503 is working...

From the crashlog, it appears that #0504 is choking on the EPG database update. Can you try renaming your /storage/.kodi/userdata/Database/Epg10.db file as follows:

Code:
systemctl stop kodi mv /storage/.kodi/userdata/Database/Epg10.db /storage/.kodi/userdata/Database/Epg10.db.bak systemctl start kodi

and then test #0504 (preferably #0507) again - confirm if it continues to crash, or is now OK.

If the crashing continues, you probably need to throw it over to the pvr.dvbviewer addon maintainer and see what he/she thinks.

after excute
systemctl stop kodi
mv /storage/.kodi/userdata/Database/Epg10.db /storage/.kodi/userdata/Database/Epg10.db.bak
systemctl start kodi

I update to #0504 from 5.0.8,PVR works fine,no crash.

I tested #0507, rebooting.

Milhouse · 2015-05-08, 01:10

(2015-05-08, 00:48)startv Wrote: I tested #0507, rebooting.

Rebooting? Or Kodi restarting? If the latter, I'll need another crashlog...

startv · (This post was last modified: 2015-05-08, 01:25 by startv.)

(2015-05-08, 01:10)Milhouse Wrote:
(2015-05-08, 00:48)startv Wrote: I tested #0507, rebooting.

Rebooting? Or Kodi restarting? If the latter, I'll need another crashlog...

just the same as #0505,#0506 do
It seems no crash log be record.

sorry for my poor english

Milhouse · (This post was last modified: 2015-05-08, 01:34 by Milhouse.)

(2015-05-08, 01:25)startv Wrote:
(2015-05-08, 01:10)Milhouse Wrote:
(2015-05-08, 00:48)startv Wrote: I tested #0507, rebooting.

Rebooting? Or Kodi restarting? If the latter, I'll need another crashlog...

just the same as #0505,#0506 do
It seems no crash log be record.

Hmmm.

With #0507, run the following two lines in ssh and copy the output from your ssh window into this thread once the second command has finished executing (ie. once Kodi has crashed):

Code:
systemctl stop kodi

/usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd

Also upload /storage/.kodi/temp/kodi.log once the above has been completed, and paste the link.

startv · 2015-05-08, 03:40

(2015-05-08, 01:32)Milhouse Wrote:
(2015-05-08, 01:25)startv Wrote:
(2015-05-08, 01:10)Milhouse Wrote: Rebooting? Or Kodi restarting? If the latter, I'll need another crashlog...

just the same as #0505,#0506 do
It seems no crash log be record.

Hmmm.

With #0507, run the following two lines in ssh and copy the output from your ssh window into this thread once the second command has finished executing (ie. once Kodi has crashed):

Code:
systemctl stop kodi /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd

Also upload /storage/.kodi/temp/kodi.log once the above has been completed, and paste the link.

/usr/lib/kodi/kodi.bin: symbol lookup error: /usr/lib/kodi/addons/pvr.dvbviewer/pvr.dvbviewer.so: undefined symbol: _ZN8XMLUtils9GetStringEPK9TiXmlNodePKcR7CStdStrIcE

kodi.log
http://pan.baidu.com/s/1mgL0lBE

nickr · 2015-05-08, 03:50

No one is interested in logs on baidu. Please use pastebin.

Milhouse · 2015-05-08, 03:51

I think this needs to be reported to the dvbviewer maintainer(s). Could be an OE build issue, or something to do with the kodi-platform/platform split. Ping @negge/@h.udo... Smile