Is there an old „journalctl“? I had to powercycle the system. Or shall I try to recreate the issue while running journalctl?
[x86-64] What to log to find the reason for hangs?
-
Skeeve -
November 9, 2025 at 3:36 PM -
Thread is Unresolved
-
Code
journalctl > /storage/journal.log && journalctl -f >> /storage/journal.logSSH in and run ^ after boot. It will dump the initial log to file then tail/append future journal content to the same file. Now go start something playing until it hangs. The logging task will die when the system hangs but the file will remain on-disk after you power cycle and log back in. Then do:
a) cat /storage/journal.log | paste
b) cat /storage/.kodi/temp/kodi.old.log | paste
Share the URL's and if you're lucky there's a trace of something in the system log that correlates to the kodi old log.
-
-
.·°՞(っ-ᯅ-ς)՞°·.
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?
-
So maybe my device simply(?) has a defect.
The most likely issue is an ancient AMD GPU based on TeraScale 2 architecture from 2009.
-
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.
-
Try LE 13 nightly.
-
Try LE 13 nightly.
Hm… I'm a bit reluctant to because my current setup works. Why do you think LE13 will help?
-
Hm… I'm a bit reluctant to because my current setup works. Why do you think LE13 will help?
Updated drivers on newer Linux kernel.
PS:
Quote2025-11-12 19:50:07.762 T:1129 info <general>: load skin from: /storage/.kodi/addons/skin.xperience1080/ (version: 10.0.0)
Use the default skin to rule out any complications with a custom skin.
