Login at Kodi Home

Milhouse · 2016-05-28, 13:39

(2016-05-28, 13:13)Shanyel Wrote: Tried that. I do get replies from all pool.ntp.org clusters, though the date is incorrect...
My router time is OK, checked also with windows 10 pc/laptop and time is synced correctly

"ntpd -w" won't set your date but you should see an "offset" calculated which is the difference in seconds between the correct date/time and your current system date/time - if the offset isn't being calculated correctly for pool.ntp.org then I don't know why that isn't working.

If you have the same issue with OpenELEC/LibreELEC release builds then it's not a test build issue. If it's only an issue with these test builds, what build does it start etc.

User 99401 · (This post was last modified: 2016-05-28, 20:14 by User 99401.)

(2016-05-28, 13:39)Milhouse Wrote:
(2016-05-28, 13:13)Shanyel Wrote: Tried that. I do get replies from all pool.ntp.org clusters, though the date is incorrect...
My router time is OK, checked also with windows 10 pc/laptop and time is synced correctly

"ntpd -w" won't set your date but you should see an "offset" calculated which is the difference in seconds between the correct date/time and your current system date/time - if the offset isn't being calculated correctly for pool.ntp.org then I don't know why that isn't working.

If you have the same issue with OpenELEC/LibreELEC release builds then it's not a test build issue. If it's only an issue with these test builds, what build does it start etc.

OK - so tried several LibreELEC builds, no luck. when installed from scratch time and date are now synced. Will wait for the next update and see

I meant, i got no timeout, hence interent is fine...
It was OK with previous builds on LibreELEC as far as I recall, let me go back and see whether I can come back where it started...

Little_Kitty · 2016-05-28, 22:07

(2016-05-28, 03:58)Milhouse Wrote: @Little_Kitty: Given the above, if you have set the correct timezone but still have incorrect time (your date is "correct" purely by chance, something that will stop being the case in future once systemd is not built on a daily basis, and probably will be incorrect if you reboot after midnight) then I can only imagine that you do not have a functioning internet connection and will need to look at the rest of your network to determine where the fault lies.

it showed wrong time and date.
But i got it fixed now.
i had the timeservers setup on my router. but no idea why it didnt send the info to the PI.

So i setup NTP specially for the PI IP on my router as the PI has a static IP. i cant use pool.ntp on there i have to put in IP address so i did. When i now start it it show the correct time/date.

Little_Kitty · (This post was last modified: 2016-05-28, 22:54 by Little_Kitty.)

(2016-05-28, 00:13)Milhouse Wrote: connmand handles ntp.

What is the output from:

Code:
cat /storage/.cache/timezone connmanctl clock | pastebinit connmanctl services | pastebinit connmanctl services $(connmanctl services | awk '/^\*/ {print $NF}') | pastebinit journalctl -a | pastebinit

1)TIMEZONE=Europe/Amsterdam ( which is correct)
2) http://sprunge.us/BMUH
3) http://sprunge.us/YidW
4) http://sprunge.us/ViFQ
5) http://sprunge.us/fOUg

Bor_NL · 2016-05-29, 10:21

I have a issue while switching channels in dvblink PVR with #0527 build.
First channel works ok but switching to the 2nd or 3th channel it gives a blank screen. No problem whatsoever with #0526 build.

Some logs :

#0527

http://sprunge.us/eUij

#0526

http://sprunge.us/WMMA

Any other logs that could help ?

Thx for the hard work !

**popcornmix** · 2016-05-29, 12:42

(2016-05-29, 10:21)Bor_NL Wrote: Some logs :

You don't have debug enabled. Can you enable debug and "video" component specific debug and capture a log from #527.
I suspect it is the preroll commit but can't immediately think of the failure mode.

MONSTA · 2016-05-29, 14:10

Hi
Here a video from phone https://drive.google.com/file/d/0B9_XmyO...sp=sharing
Massive artifacts with hardware acceleration.
Thanks

popel · (This post was last modified: 2016-05-29, 15:08 by popel.)

Hi, new to this forum.
I use the libreelec builds for my rPi2, but the last build I can use is #505. Newer builds update, but I don´t get a picture in Kodi. I can connect via smb/ssh and downgrade to #507 and it works again. Also for newer builds there is no connection for Yatse (remote). If you tell me which, I can upload the logfile, but there are 10 of them. (And where to upload it)

Another problem is the keyboard layout: Changed it to German QWERTZ, but when I use my keyboard it is still Englisch QWERTY.

Bor_NL · 2016-05-29, 15:25

(2016-05-29, 12:42)popcornmix Wrote:
(2016-05-29, 10:21)Bor_NL Wrote: Some logs :

You don't have debug enabled. Can you enable debug and "video" component specific debug and capture a log from #527.
I suspect it is the preroll commit but can't immediately think of the failure mode.

I hope i've done it the right way this time.

http://sprunge.us/WGPZ

**popcornmix** · 2016-05-29, 16:46

(2016-05-29, 14:55)popel Wrote: I use the libreelec builds for my rPi2, but the last build I can use is #505. Newer builds update, but I don´t get a picture in Kodi. I can connect via smb/ssh and downgrade to #507 and it works again.

This isn't clear to me. You seem to be saying #505 is the newest build you can use, but #507 also works?

Is that just a typo, and #505 is good, and #506 is bad for you?

popel · 2016-05-29, 16:56

Oh sorry. #507 is the last that works for me! From #508 it begins not to work

**popcornmix** · 2016-05-29, 17:27

(2016-05-29, 16:56)popel Wrote: Oh sorry. #507 is the last that works for me! From #508 it begins not to work

Okay, main change there was splash video related. Do you normally have a working splash video when booting?
Is it the default LibreELEC one, or have you customised it?

Does disabling the splash video fix the newer builds?

Code:
touch /storage/.config/splash.disable"

popel · (This post was last modified: 2016-05-29, 18:37 by popel.)

No, I use the default builds.
Looks like there is no splash video, wo I will try to disable (learning by doing for me)

€: Worked!! Thanks a lot! But how will I be able to use the splash video? or was it just missing?

**popcornmix** · 2016-05-29, 20:41

(2016-05-29, 18:32)popel Wrote: €: Worked!! Thanks a lot! But how will I be able to use the splash video? or was it just missing?

Milhouse can probably help here, but it sounds like perhaps the splash video file is missing or corrupted.

Milhouse · (This post was last modified: 2016-05-29, 20:43 by Milhouse.)

(2016-05-29, 18:32)popel Wrote: No, I use the default builds.
Looks like there is no splash video, wo I will try to disable (learning by doing for me)

€: Worked!! Thanks a lot! But how will I be able to use the splash video? or was it just missing?

Hmmm, a missing splash video should not block Kodi startup. A non-standard splash video could delay Kodi startup if the video is ridiculously long.

Not sure if a corrupt video file might cause problems - if this is possible, then obtaining a copy of /storage/.cache/splash.h264 might be useful so that it can be debugged further.

What is the output from the following commands:

Code:
ls -la /storage/.cache

md5sum /storage/.cache/splash.h264 2>/dev/null || echo "md5sum: Splash video not found"

time /usr/bin/hello_video.bin /storage/.cache/splash.h264

Also, try the following which should reproduce "blocked Kodi", then paste the results:

Code:
rm -f /storage/.config/splash.disable

texturecache.py debugon

systemctl restart kodi

sleep 60

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

To "unblock" Kodi:

Code:
touch /storage/.config/splash.disable

systemctl restart kodi

sleep 20

texturecache.py debugoff