Good Morning,
I updated to the latest nightly build. UNfortunately, I can't play mp4 from my gopro. It starts, but only artefacts are visible. The same with Amazon Prime. I tried to upload the logs, but I get "failed to paste log files, try again". Can I upload the zip files directly in the forum?
Please help me ;-)
Thanks
Markus
is there a new default password?
i want to login after updating but i have no gui access, only ssh
(2018-12-01, 14:15)BLADERUNNER6 Wrote: [ -> ]is there a new default password?
No, the default root password for ssh is still
libreelec.
The only change in the last two builds is that you can change this password in the LibreELEC Settings addon (in Services > SSH). If you change it and want your default (insecure, well known) password back, you'll need to termporarily set a password you can login with, then run
rm /storage/.cache/shadow and reboot - next time you login the password will be back to
libreelec.
(2018-12-01, 14:15)BLADERUNNER6 Wrote: [ -> ]i want to login after updating but i have no gui access, only ssh
You mean you see no GUI? Please post your kodi.log and also
journalctl -a | pastebinit. When did this issue start? What version did you upgrade from?
(2018-12-01, 13:47)Freuli Wrote: [ -> ]Now it worked.
Http://ix.io/1uZv
Regards
Markus
Is there still a problem?
If so when you say "I updated to the latest nightly build" it would be helpful if you say the version you updated from.
If this is a new problem, then it will have been introduced in a build between your last working version and this latest version, so identifying that first non-working build can be very helpful (actually essential, in many cases).
(2018-12-01, 03:08)Milhouse Wrote: [ -> ]@kakkabolle post a complete debug log (wiki), which includes a period of buffering.
Hi sure, here are two debug reports. One
with default, one
with changed cache settings. Both resulting in buffering.
thx!
(2018-11-27, 17:17)raptorjr Wrote: [ -> ] (2018-11-15, 00:10)Milhouse Wrote: [ -> ] (2018-11-14, 21:52)raptorjr Wrote: [ -> ] I have no overclocking, and it is no problem to disable Emby to test if that is the problem. Is it enough to disable or do I need to uninstall Emby addon?
Just disabling should be enough in theory, although if you're able to test with a more-or-less "clean" .kodi (no extra addons, just your local sources etc.) then that might be a better option.
I didn't test with a clean .kodi, but I uninstalled Emby. If nothing can be found in these logs I will do a clean test. But it did take much longer without Emby. Don't know why I got two log files with a few minutes apart. Only restarted once, but I'll put both here.
If nothing is found I will do it again, clean. But if I should make some changes for better success with next log, please tell me.
https://drive.google.com/open?id=1-zJ0Wj...cSwbCVhQW5
https://drive.google.com/open?id=1X6SUUT...I-vXV_Mxj7
Is there anything to be found here?
(2018-12-01, 21:51)raptorjr Wrote: [ -> ] Is there anything to be found here?
Not particularly, as it doesn't show any out-of-memory event taking place. Also, memory that is leaking doesn't really leave much trace in the logs (unless there is an OOM event) which is why it's so hard to pin down.
You could try running
bcmstat.sh -ZAD d30 and see if you can correlate the memory allocations to your activity.
Also test with a clean .kodi - no extra addons. If the problem only occurs once you install Emby, then contact the Emby developers.
New LibreELEC.tv Leia build #1201:
RPi /
RPi2
(Supercedes previous build)
SHA256 Checksum:
5227318f0c5f7b8641b0dc785a4d89bbad72dc26663432fa114e419f15a0c500 (RPi)
SHA256 Checksum:
f70ec996662e2ba190074d0cc9073bb0e1d06c9b6ff24a6a0c1244d3eca7e1eb (RPi2)
text:
# uname -a
Linux rpi512 4.19.5 #1 Sat Dec 1 21:04:05 GMT 2018 armv6l GNU/Linux
# vcgencmd version
Nov 23 2018 19:39:01
Copyright © 2012 Broadcom
version d8054e0f49c3f96936956a4079b2290b11a5d428 (clean) (release)
# lsb_release
LibreELEC (Milhouse): devel-20181201210246-#1201-g5dc77c9 [Build #1201]
# Kodi version
(18.0-RC2 Git:5880ccf). Platform: Linux ARM 32-bit
Based on tip of
LibreELEC.tv master (5dc77c9,
changelog) and tip of
XBMC master (5880ccf,
changelog) with the following modifications:
- Includes newclock5 patches
- Includes latest commits from kernel branch rpi-4.19.y
- Includes latest bcm2835-driver master (b428bdd)
- Includes latest kodi-platform master (e8574b8)
- Includes latest libcec master (d57d3ac)
- Includes latest libnfs master (6dfc87d, ahead +10)
- Includes latest p8-platform master (1eb12b1)
- Includes latest addons: inputstream.adaptive (efd4b4f, +3), inputstream.rtmp (ce7f559), peripheral.joystick (1f4225a, +2), peripheral.xarcade (f09a0e7), pvr.argustv (83aa1e9), pvr.demo (964686d), pvr.dvblink (4ae42fe, +1), pvr.dvbviewer (cda813e), pvr.filmon (e850633), pvr.hdhomerun (a9d7309), pvr.hts (6a12442), pvr.iptvsimple (90a8d6f), pvr.mediaportal.tvserver (b17fdad), pvr.mythtv (d3a5af2, +3), pvr.nextpvr (ccdfd63), pvr.njoy (4467cac), pvr.octonet (203f800), pvr.pctv (b60b971), pvr.stalker (2245b0d, +1), pvr.teleboy (50689bd), pvr.vbox (6ed2f63), pvr.vdr.vnsi (cbb75ab), pvr.vuplus (1207082), pvr.wmc (81e2090), pvr.zattoo (4688f45), vfs.libarchive (6d39012), vfs.sftp (6749200)
- Include [env] compare (perma): TESTING: increase timeout to ensure OS is able to create core dump/crash log
- Include [env] patch: RPi/RPi2: enable Broadcom WiFi debugging (see details)
- Include [env] patch: kodi: use upstream repo for Milhouse RPi builds
- Include [env] patch: kodi: remove annoying, excessively repetitive addon logging
- Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.* and os.*
- Include [env] patch: rev hack for kodi
- Include [env] patch: Bump included addon versions to prevent online updates
- Include [env] patch: Add experimental splash video for RPi
- Include [env] patch: Add kodi binary addons (pvr, adsp, inputstream, vfs, peripheral.joystick/xarcade, other)
- Include [env] PR:3130 (perma): linux (RPi/Generic): update to linux-4.19.5
- Include [env] PR:3138 (perma): libssh: update to libssh-0.8.5
- Include [env] PR:3141 (perma): fix .config/firmware handling
- Include [pkg] patch: ssh: allow setting of default libreelec password (service.libreelec.settings)
- Include [pkg] PR:106 (perma): Adds ability to change SSH root password from LE settings (service.libreelec.settings)
- Include [pkg] PR:137 (perma): Load config if enabled (pvr.vuplus)
- Include [pkg] PR:14924 (perma): [games] Fix crash in PCSX ReARMed with BIOS
Build Highlights:
- fix .config/firmware handling
- ssh: allow setting of default libreelec password
- pvr.vuplus: Load config if enabled, plus extra logging
Build Details:
- peripheral.joystick:
- [Android] added buttonmap for XBOX 360 controller (PR:157, 2 commits, 6 files changed)
- Additional commits/pull requests/changes not yet merged upstream:
- Added: [env] PR:3141 (perma): fix .config/firmware handling
- Added: [pkg] patch: ssh: allow setting of default libreelec password (service.libreelec.settings)
- Added: [pkg] PR:137 (perma): Load config if enabled (pvr.vuplus)
(2018-12-01, 22:30)Milhouse Wrote: [ -> ] (2018-12-01, 21:51)raptorjr Wrote: [ -> ] Is there anything to be found here?
You could try running bcmstat.sh -ZAD d30 and see if you can correlate the memory allocations to your activity.
Also test with a clean .kodi - no extra addons. If the problem only occurs once you install Emby, then contact the Emby developers.
That could be hard since I do nothing. Just leave Kodi on for a couple of days or week.
But I will try with a clean Kodi.
Thank you.
Hallo,
i thought, it worked it the past ,but I tried it with old builds and I had the Artefacts as well.
Any chance to get it solved?
In case of testing something, I would be ready.
Thanks
Markus
(2018-12-02, 23:38)Freuli Wrote: [ -> ]Hallo,
i thought, it worked it the past ,but I tried it with old builds and I had the Artefacts as well.
Any chance to get it solved?
In case of testing something, I would be ready.
Thanks
Markus
What kind of artefacts, can you post a screenshot/photo, or better yet a sample file that has the problem?
New LibreELEC.tv Leia build #1202:
RPi /
RPi2
(Supercedes previous build)
SHA256 Checksum:
3588baed7861bfb1ab8ffd2b2c3c9b8750612db1ae6a34f43adff3d085dd97bd (RPi)
SHA256 Checksum:
bf4b7b9a47b89155d971f4f82bd5f75bf8a7c72d0d129b7497e56c88dda110f5 (RPi2)
text:
# uname -a
Linux rpi512 4.19.5 #1 Sun Dec 2 21:56:17 GMT 2018 armv6l GNU/Linux
# vcgencmd version
Nov 23 2018 19:39:01
Copyright © 2012 Broadcom
version d8054e0f49c3f96936956a4079b2290b11a5d428 (clean) (release)
# lsb_release
LibreELEC (Milhouse): devel-20181202215419-#1202-g99f4e4b [Build #1202]
# Kodi version
(18.0-RC2 Git:812855d). Platform: Linux ARM 32-bit
Based on tip of
LibreELEC.tv master (99f4e4b,
changelog) and tip of
XBMC master (812855d,
changelog) with the following modifications:
- Includes newclock5 patches
- Includes latest commits from kernel branch rpi-4.19.y
- Includes latest bcm2835-driver master (b428bdd)
- Includes latest kodi-platform master (e8574b8)
- Includes latest libcec master (d57d3ac)
- Includes latest libnfs master (6dfc87d, ahead +10)
- Includes latest p8-platform master (1eb12b1)
- Includes latest addons: inputstream.adaptive (efd4b4f, +3), inputstream.rtmp (ce7f559), peripheral.joystick (1f4225a, +2), peripheral.xarcade (f09a0e7), pvr.argustv (83aa1e9), pvr.demo (964686d), pvr.dvblink (4ae42fe, +1), pvr.dvbviewer (cda813e), pvr.filmon (e850633), pvr.hdhomerun (a9d7309), pvr.hts (6a12442), pvr.iptvsimple (90a8d6f), pvr.mediaportal.tvserver (b17fdad), pvr.mythtv (d3a5af2, +3), pvr.nextpvr (ccdfd63), pvr.njoy (4467cac), pvr.octonet (203f800), pvr.pctv (b60b971), pvr.stalker (2245b0d, +1), pvr.teleboy (50689bd), pvr.vbox (6ed2f63), pvr.vdr.vnsi (cbb75ab), pvr.vuplus (1207082), pvr.wmc (81e2090), pvr.zattoo (4688f45), vfs.libarchive (6d39012), vfs.sftp (6749200)
- Include [env] compare (perma): TESTING: increase timeout to ensure OS is able to create core dump/crash log
- Include [env] patch: RPi/RPi2: enable Broadcom WiFi debugging (see details)
- Include [env] patch: kodi: use upstream repo for Milhouse RPi builds
- Include [env] patch: kodi: remove annoying, excessively repetitive addon logging
- Include [env] patch: HACK: Disable multiple PVR addons during migration. Always enable inputstream.* and os.*
- Include [env] patch: rev hack for kodi
- Include [env] patch: Bump included addon versions to prevent online updates
- Include [env] patch: Add experimental splash video for RPi
- Include [env] patch: Add kodi binary addons (pvr, adsp, inputstream, vfs, peripheral.joystick/xarcade, other)
- Include [env] PR:3130 (perma): linux (RPi/Generic): update to linux-4.19.6
- Include [env] PR:3138 (perma): libssh: update to libssh-0.8.5
- Include [env] PR:3141 (perma): fix .config/firmware handling
- Include [pkg] PR:106 (perma): Adds ability to change SSH root password from LE settings (service.libreelec.settings)
- Include [pkg] PR:137 (perma): Load config if enabled (pvr.vuplus)
- Include [pkg] PR:14924 (perma): [games] Fix crash in PCSX ReARMed with BIOS
Build Highlights:
- [linux] powermanagement: change logind detection to also use Dbus
Build Details:
- LibreELEC.tv:
- WeTek_Core, WeTek_Play: Disable suspend and emulate poweroff by suspending the device (PR:3142, 2 commits, 4 files changed)
- [busybox] Fixed 'getedid delete' section (PR:3143, 1 commit, 1 file changed)
- XBMC:
- [linux] powermanagement: change logind detection to also use Dbus (PR:14976, 1 commit, 1 file changed)
- [docs] Missing docs for ListItem.NextDuration (PR:14975, 1 commit, 2 files changed)
- Additional commits/pull requests/changes not yet merged upstream:
- Updated: [pkg] PR:106 (perma): Adds ability to change SSH root password from LE settings (service.libreelec.settings)
Hi,
I will send a photo and an example tonight.
Because I am pretty convinced, that it worked already in the past, could it be a hardware issue with my RPI?
Regards
Markus
(2018-12-01, 02:03)kakkabolle Wrote: [ -> ]Unfortunately I am experiencing some buffering/stuttering issues on the most recent (and also on previous builds) with MVC files (3D, but also when watching those in 2D). I am using a Raspberry pi 3b+.
Would be good to identify if this is a network bandwidth issue, or a decoding issue.
Can you try playing the file locally (e.g. from sdcard or a directly attached USB stick)?