It looks like you're new here. If you want to get involved, click one of these buttons!
Crashed again watching a movie
@bo1e, "Can provide logs if anyone wants to have a look." You should upload the log and provide the link. Saves another message asking for it.
Someone can look the memory consumption of LibreELEC when playing a 4k hdr movie please ?
I want to try this board but don't know if I need 1or2gb memory for using only with LibreELEC.
Logs when backup of settings crashed. Debug was not enabled when it crashed later in video playback.
Also testing the xbox one version now, so was having problems remembering which bugs went where
@Warnings : i have a custom advancedsettings.xml because of 4k but if I remember well, it did not go over 1g.
But I have a 2g version so everything is fine for me
@invik, There are some optimizations like using zswap and zram which can greatly reduce memory requirements. I would expect that the 1GB version runs just fine with 4K since the boards are equiped with DDR2133 unlike most other devices with only DDR1333. u-boot does need to be tweaked to go that fast though. The optimal setting we found was DDR2112 or 1056MHz which was the fastest overall in our testing.
@invik and @loverpi thank you for your reply !
Just one last thing, you need a jumper for activate HDMI-CEC or it's working without out of the box ? (not found the document about this jumper and the right position if needed)
@Warnings, I would use a multimeter to determine which pin on the header next to UART is connected to CEC. The middle pin is connected to the CEC pad on the SoC. Measure the continuity of the other pins to see which one is hooked into the 40 pin header. The one not hooked into the 40 pin header is connected to HDMI CEC. See the schematics under the documents page: https://libre.computer/products/boards/aml-s905x-cc/
@loverpi it's good solution for found the right jumper position
I miss this detailed pin on the schematic but pin 2&3 for the jumper position.
Thank you for all
@loverpi I had some suttering issues on rapid action scenes when the bitrate went close to 100Mbits/s (80MBits/s). So my configuration is the enable caching even over Ethernet LAN and increase cache size.
Here it is:
@invik, This would be for @kszaq as we do not manage the Kodi builds. Is it a h.264 stream or h.265? That's an really high bitrate and I am surprised you can decode that high of a bit rate as most other SBCs will not.
@loverpi You use PVR ? It's just not possible 80Mbits for a movie...
@loverpi I have checked during a specific scene using kodi cpu meter, top and nload on the NAS side.
When I saw that the cpu was around 10-15% activity overall but about 70-75Mbit/s of network load during this particular scene, I knew that something was to be done to cache more.
The rest of the movie seems to be between 30 and 45Mbits/s.
And this configuration uses around 700MB of RAM
These devices are perfectly cable of handling even the highest 400Mbps jellyfish demo, saying that there is a limit as to what can be played over the network, 80Mbps seems to be the limit.
I would not recommend a buffer of more than 150MB on 1GB devices as Kodi will use 3x the figure of your available RAM.
I have watched another movie tonight. And while the first one I have tested is fine, the one of tonight is not.
It is always close to the 80Mbps and sometimes Kodi displays a message which states that the source is too slow.
But the source is a 1Gbps RAID5 NAS.
So, back to the advancedconfiguration.xml tuning.
I have 2GB or RAM on my Lepotato which will give me more room to avoid bufferings.
@jaffac Please use LibreElec forum to address issues with these Alpha builds. Usually they need Kodi log files to analyse issue. Please read first posts at LibreElec forum carefully.
There's a new release out now that seems to work better than the earlier versions. They were all unusable on my board (constant freezing). I've at least been able to start and stop a few movies without it freezing with the release build. It did lock up on me the first time I tried to play a movie after library sync, but that movie plays fine now. My media is all on an NFS mount. Audio passthrough and HDR appear to be working...at least the receiver claims to be getting the right signals.
@frerk I'm one of the maintainers of CoreELEC
I don't often check these forums much or even the LE one, but if you have any issues I would ask that you raise them here, as that will get the attention of all of the developers in the project.
I use the LePotato as my main testing board after kindly receiving one from loverpi and Raybuntu also has one or 2?, so if there is any specific problems we can try and help resolve them.
I'm more than happy to help anybody who has purchased a LePotato, I wish more people would buy them rather than the Chinese boxes that have flooded the market.
Unfortunately LePotato build is not working for me on SD card.
@wappi We recommend using CoreELEC for now. LibreELEC has focus on mainline Linux which is not ready at this point.
@wappi If you try CoreELEC you might want to try all of the versions (there are 3 currently). I have the most reliability with 8.90.0 which is the oldest. That said, I still get freezes in all versions, usually when navigating through the main menu or movies list.
@frerk True. I had best results with @kszaq builds... might need a little bit time to get CoreElec stable for LePotato. We are used to wait... right? :-)))
TL;DR: OS Crash on Large File Transfers regardless of Kodi version or if Kodi is running or not.
I love this compact board for the Kodi application.
Unfortunately so far every Kodi distribution that I have tried crashes with the same repeatable fault: Copying large or numerous files in Kodi or just in the OS causes a Segmentation Fault. The source & destination (local or network NFS) is immaterial.
I have never managed to copy more than 800MB before a crash occurs.
If you do not do any file transfers it seems quite stable.
If you are logged in at console via SSH you may briefly see "Segmentation Fault" before SSH freezes. Ping also stops responding. If Kodi was running, it freezes.
Again, it does not seem to be Kodi causing the issue, but rather the OS.
Only recourse is Power removal and reboot.
This of course affects Movie watching/Library Imports or Exports/Kodi Backups (via the LibreElec/CoreElec APP etc. Anything that involves data transfer. Took me about 3 days of restarting every few hours to import my library.
I understand that Kodi 18 is still Alpha but this seems to be the underlying OS causing it
Kodi 17.6 underlying OS show the same symptoms.
I have eliminated the following PSU, SD Card, CPU Temp and EMMC and Network Switches/Cables/Ports/Duplex etc. as everything was tested on other devices (except for EMMC).
I have tried:
CoreELEC 8.90.2 release
CoreELEC 8.90.1 release
CoreELEC 8.90.0 release
systemctl stop kodi does not cure the problem.
Is there anything I can provide to try and narrow down or eliminate this behaviour?
What am I doing wrong?
Thanks for your time.
@oz_ra I think this issue is alrealy known:
However, it seems not fixed yet. Maybe it is helpful to post your feedback also to provide as much as possible information to developers.
"This has been a known issue for some time, unfortunately we have been unable to find the root cause of it and its likely that this issue will only be resolved when we move to mainline kernel."
This is actually a hardware issue, the XTAL_IN is hooked incorrectly on LePotato, a SoC PLL has been used rather than an external crystal, probably as a cost saving measure (5 cents?).
This could be fixed with some PHY calibration and the proper schematic which I don't have.
A simple way to test is to increase CPU load during transfer, ethernet will die because PLL will wane.
Hola que tal están todos,viendo los comentarios de antes, en mi experiencia con las ultimas actualizaciones de Coreelec y Libreelec,tuve que volver a la version LibreELEC-S905.arm-8.2-220.127.116.11-LePotato,porque esta versión no me da problemas de cogelamiento cuando reproduzco películas en 4k mkv con sonido truehd y dts-hd,las ultimas actualizaciones dan ese problema media hora despues del inicio de una pelicula