Try LE 13 nightly.
Hm… I'm a bit reluctant to because my current setup works. Why do you think LE13 will help?
Try LE 13 nightly.
Hm… I'm a bit reluctant to because my current setup works. Why do you think LE13 will help?
The most likely issue is an ancient AMD GPU based on TeraScale 2 architecture from 2009.
Maybe. On the other hand: I installed Kodi on Alpine Linux and currently there are no issues.
.·°՞(っ-ᯅ-ς)՞°·.
So maybe my device simply(?) has a defect.
I will do a last experiment and install another Linux flavour.
I will report here whether or not I was successful. Is that okay, even when it's only remotely LibreElec related?
I fear there is nothing in the journalctl.
BTW: I ran in background:
while journalctl --cursor-file /storage/journalctl.crsr >> /storage/journalctl.log; do sleep 60 ; done &
The content is: https://paste.libreelec.tv/good-bullfrog.log
The old log is: https://paste.libreelec.tv/fluent-martin.log
Is there an old „journalctl“? I had to powercycle the system. Or shall I try to recreate the issue while running journalctl?
https://paste.libreelec.tv/full-ferret.log
After an hour of playback the system started to act crazy, i.e. the next video started had artifacts and the system reacted slowly. After stopping and starting it seemed okay and I paused it. When I looked next time, the system was frozen. I had to powercycle it.
Btw. Before I started the first video, the system ran for hours without issues.
Also the video is streamed over nfs. Previously I streamed via UPNP and had the same issues.
I installed the newest 12.2.1 from a fresh download on a Wyse 5010 thin client with about 2GB and a 16GB SSD.
After installing 12.2.1, I had the system running for a day without using it. No issue at all.
Then I watched an episode of a series for about an hour. After that, issues started.
First when starting the next episode, I saw in the debug on screen that the cpu usage went up and the video was heavily distorted with artifacts. Even the on-screen log output wasn't refreshed.
I stopped playback and waited a minute or so before starting it again. This time there were no artifacts, but I paused playback.
Currently the system is completely unresponsive, but I haven't had the time yet to reboot and upload the log.
Seems to be AMD, not intel or nvidia.
The other version is now installed.
I just erased the installation and wanted to start from scratch.
Can it be that
Legacy Generic PC (for older PCs and NVIDIA GPUs)
Generic-legacy LibreELEC-Generic-legacy.x86_64-12.2.1.img.gz
Is not for my deevice? I thought, as the Wyse 5010 is such an old Thin Client that would work.
Instead I ended up in an endless reboot cycle.
Trying now
Generic PC (no NVIDIA support)
So this morning I watched an episode. After that I started a new one and paused it half way through. I just checked and noticed that my machine just rebooted. Here is it’s log.
https://paste.libreelec.tv/assured-finch.log
P.S. There was no crash log.
Quoteset the log level to 1 at advancedsettings.xml
vm.overcommit_memory=2
vm.overcommit_ratio=100
vm.vfs_cache_pressure=1000to /storage/.config/sysctl.d/sysctl.conf
MALLOC_ARENA_MAX=1
to /storage/.config/kodi.conf (create the file if it's not there)
Reboot.
I did that now and will check tomorrow whether or not the system will hang again after about 1-1.5h of playback.
QuoteATM it's unclear whether it's a crash or a hanger.
Not a crash, I assume, because the system still displays the last frame of whatever I was watching. Also there is no crashlog after switching off and on again.
https://paste.libreelec.tv/amused-amoeba.log
I hope someone sees something.
Shortly before the system hung, the playback stuttered. CPU usage, as displayed by the log, didn’t go high.
But when the issue occurs, the system is unresponsive and I have to switch it off to get it to work again.
I installed LibreElec on a Wyse Thin Client some time ago and from the beginning on I had issues with zhe system. Usually I can watch one episode of a series, flawlessly, but most of the time I start getting issues when starting another one.
I also have the feeling that it's not that I view something, but it seems to be related to the system itself hanging after, maybe an hour or two.
I just upgraded to the newest 12.2 version and I'm wondering which files to constantly monitor in order to see what's the reason for the hangs.
Currently I'm running this from my Laptop:
while (true)
do
(date;ssh kodiwyse 'uptime;echo "-------";dmesg')>kodiwyse.txt
head -2 kodiwyse.txt
sleep 30
done
So just monitoring dmesg. Is there anything else you recommend to look out for?
Hi.
Thanks to all the support I received here, I was able to get an old Jolly Click 1:1 IR remote control connected to my Raspberry (3b).
Since it has more than 40 buttons there is plenty of room for making certain buttons do useful stuff for me.
This is what I implemented:
1. Channel down plays the next video in the current directory
2. Channel up plays the previous video
3. One button will now toggle the "watched status" of the currently selected video
1 & 2 I find quite helpful when binge-watching a series
3 is for "quickly" setting videos to "watched". I regularly delete watched videos with a script. So this help me mark those videos without actually having watched them til the end, which sometimes happens with YT videos.
/storage/.kodi/userdata/scripts/skiponeback.py
import xbmc
xbmc.executebuiltin('Action(Stop)')
xbmc.executebuiltin('Action(UP)')
xbmc.executebuiltin('Action(Play)')
/storage/.kodi/userdata/scripts/skiptonext.py
import xbmc
xbmc.executebuiltin('Action(Stop)')
xbmc.executebuiltin('Action(Down)')
xbmc.executebuiltin('Action(Play)')
/storage/.kodi/userdata/scripts/togglewatched.py
import xbmc
xbmc.executebuiltin('Notification(Toggle Watched Status,Pleas wait…,5000)')
xbmc.executebuiltin('Action(ToggleWatched)')
The notification is for me to see, that the button was registered. Sometimes it takes some time for the system to actually get the status changed.
/storage/.kodi/userdata/keymaps/keymap.xml
<keymap>
<global>
<remote>
<guide>ToggleDebug</guide>
</remote>
</global>
<videos>
<remote>
<blue>runScript(/storage/.kodi/userdata/scripts/togglewatched.py)</blue>
</remote>
</videos>
<fullscreenvideo>
<remote>
<pageplus>runScript(/storage/.kodi/userdata/scripts/skiponeback.py)</pageplus>
<pageminus>runScript(/storage/.kodi/userdata/scripts/skiptonext.py)</pageminus>
</remote>
</fullscreenvideo>
</keymap>
Display More
Thanks again HiassofT.
Thanks to all your support I now have two very convenient scripts for my channel buttons.
Two questions:
1. Is there a best practice, where to put such scripts?
2. Is there a section in this forum where to share them?
Unfortunately no, kodi uses a hardcoded set of button codes.
Another question: Is it possible to replace the Lircmap.xml?
Currently there are some duplicates, meaning: Two keys mapped to the same kodi remote button.
Maybe it's possible to use other kodi remote button instead to be able to map them to scripts or actions?