I dont have any video with Atmos, it happens randomly.
I am not alone
I wanted to find out, if the problem is in underlying Linux OS, to I have tried OpenELEC 8.0.4 - maybe they have some things different from LibreELEC. It happens also on OpenELEC 8.0.4 wich runs KODI 17.
Currently testing it with OpenELEC 7.0.1 (kernel 4.4), which runs KODI 16.1. Skin is Aeon Nox, on which I encountered the problem before. I am startying to believe that it can be KODI 17.x issue.
Hello, for longer time, I am encountering strange freeze problems when using LibreELEC with Kodi 17.
Asrock AM1H-ITX motherboard AM1 socket
Athon 5350 APU with Radeon R3 graphics
2GB RAM DDR3
Kingston UV400 128GB SSD for OS, 1TB WD Black SATA HDD for media, formatted to ext3
LibreELEC - I have tried three versions
v7.95.2 (kernel Linux 4.9.3, KODI 17)
v8.0.2 (kernel Linux 4.9.29, KODI 17.3)
v8.2.0 (kernel Linux 4.11.8, KODI 17.5)
Full Logs - KODI.log is 22MB after unpacking, because of logging some things during watching one hour video.
There is about 150 000 repetitive lines of some video decoding...or whatever it is. It was logged as I watched 1-hour long video.
Stripped down version of KODI.log - I have stripped off those 150 000+ lines of the repetitive log info.
It is commented in the file. Either in this stripped down version, it was too bug for pastebin, so I am uploading it to dropbox:
When I hit stop utton on remote to stop playing movie, KODI will freeze just in the moment when video stops playing and the picture is switching (fade-out and fade-in) back into KODI's GUI, where the list of videos (and other texts and GUI elements) is "rolling" from screen edges back to its places on screen. But this transition will not be done completely, I can see KODI's GUI, but that GUI is partielly still dimmed, because it will freeze in its "fade in" transition. GUI elements are almost at their places, as they "roll out" from the edges of the screen, until it freeze.
Here is video, you can clearly see what it does:
You can see, when it freezes, the entire GUI stays a little dimmed...this is not its proper brightness - the transition from video back into KODI GUI was not completed. This happened exactly in the moment as I hit stop button on remote.
So far I have also discovered, that if I turn on debug logging, when KODI displays that three lines with logging info on screen permanently (CPU, path to log files, memory), it will not freeze. I have tested it - without debug on, it may freeze even 3-4 times a day. With debug on and its info on screen, it not freeze during two weeks. And I have watched something every day suring those 2 weeks, so it have plenty of time to freeze.
So I have turn on debug log in different way - through advancedsettings.xml. I have set debug to hide and loglevel to "1" - debug info is not visible on screen, but it doing its job in background. Provided debug logs was obtained with this setting.
I have a theory: what if displaying that debug info is somehow preventing KODI from freeze? By keeping GUI refreshing in background under videoplayer screen or something like that?
Few times, I have also encountered some picture artifacts like this. That blue area flickers as I move up or down in the movie list.
But it dissapeared when I go back in the main menu and then return into back Videos. But this happens very, very rarely. For last year, I have seen it maybe three times.
What I discovered so far:
It is regardless of containers, codecs or resolutions (360p - 1080p, codecs such as mpeg4, h264, h265, mkv, mp4, avi) of movies.
When that freeze occurs, it freezes just KODI itself. I can still SSH into LibreELEC underlying Linux system and restart KODI by "systemctl restart kodi" command.
I have noticed it for first time when I installed LibreELEC 8.0 and when using Bello 6 skin. I thought it would be a skin related problem. So I switch to Aeon Nox skin, where everything worked OK. But only for day or two. So I think it is not skin related.
What I have tried so far:
- clean install of LibreELEC v 7.95.2, where KODI 17 final was first implemented
- clean install of LibreELEC v 8.0 and 8.0.2 including formatting system drive.
- update from LibreELEC 8.0.2 to 8.2.0, then 8.2.1
- disable Cool n Quiet and C6 mode in BIOS
- set shared graphics memory from 512MB to 1024MB
- completely disable VDPAU
- use another skin, because I have thought before, that it is skin related. But it occurs also with Aeon Nox skin.
...but nothing helped, problem still persists.
I have searched KODI forum, LibreELEC and OpenELEC forums, KODI Trac, even bugzilla.kernel.org and bugzilla.freedesktop.org (where Mesa and such things have its bugs reported), and I did not find anything what can help me.
So, I really dont know, where can be the problem. It happens in multiple skins, so I think that the GPU drivers, kernel or something in LibreELEC's underlying system may be the culprit. Or even KODI itself.
Sorry for my english, I am not native english speaker.
Oh, nevermind, I forgot to read release notes for newer LE. Disabling LIRC servise descrbed there helped, all works OK.
today, i wanted to update my LE 8.0.2 installation to newest version. After successful update, my (so far) normally working remote control (Microsoft RC-6) started to behave like crazy.
When I pushed button on remote, LE sees it like I push it two or three times, so navigation become nearly not possible. When I push for example -> key, it jumps two or three items right, instead of just one. That applies to any other remote button.
But control through an old PS/2 keyboard is fine. However, I have keyboard just as emergency solution, I cant route cable to the couch.
I revert from 8.2.0 to 8.1.0 and it still worked bad. Reverting back to 8.0.2 solved the problem, the remote behaves as it should.
Tested on GRID and BELLO 6 skins...but I think the skins are not culprit here.
Someone encountered with similar problem? Or someone know what setting is need to change somewhere in configs? Thanks,.
True, it will not work there yet. I have posted this to the Bello 6 support thread in KODI forums too, so we will see, if it can be solved somehow. I really dont know where can be the problem, like you said - it's either a bug in the skin or the skin is uncovering a bug in Kodi.
for the start, I dont even know where exactly to ask for help with my issue. Because from my point of view and knowledge (I work as PC hardware and OS service technician) the problem might be in more than one thing - KODI itself , Libreelec linux OS or its drivers....
Asrock AM1H-ITX motherboard
Athon 5350 APU with Radeon R3 graphics
2GB RAM DDR3
SSD for OS, 1TB HDD for media
When I use LibreELEC 8.0.2 with Bello 6 skin, it will start to randomly freeze when I stop video playback. It will freeze just in the moment when video stops playing and the picture may switch back into KODI's GUI, where you have list of videos to play. But this transition will not be done completely, I can see KODI's GUI, but that GUI is not displayed with full brightness, because it will freeze in its "fade in" transition.
Its regardless of what type of videos I play, it can randomly freeze when I stop playing simple 480p h264 / h265, or 1080p h264 / h265
When that freeze occurs, it freezes just KODI itself. I can still SSH into LE Linux system and restart KODI by "systemctl restart kodi" command.
But, when I switch to any other skin (Eminence, Aeon Nox, etc), I will not encounter any random freeze when stopping video playback.
Also, when I enable debug logging I will not encounter any freezes. I have used my HTPC with enabled debug logging (with those info about memory and CPU load on screen) in two-three weeks, and no freeze. Without debug log, it can freeze even three times a day.
Few times, I have also encountered some picture artifacts like this. That purple area flickers as I move up or down in the movie list.
...but it dissapeared when I go back in the main menu and then return into back Videos.
What I have tried so far:
- clean install of LE v 8.0 and 8.0.2
- clean install of LE v 7.95.2, where KODI 17 final was first implemented
...nothing works, in that Bello 6 skin, the problem persist in any LE version with KODI 17
So, I dont know, where the problem might be. KODI iself, The Skin? Its somewhat possible for particular skin to use some feature, with which KODI have some problems? Or can it be some non compatible driver in LE's Linux kernel / system, which can cause this when this particular skin is used? I think the GPU driver may be the culprit.
Have someone encounter such problems?
Sorry for my english, I am not native english speaker.
Thanks you all, Will try that e2label command.
Which format does the drive have?
Post the output of the command blkid please.
Hey, hre is output of blkid command:Code
- Mediacenter:~ # blkid
- /dev/sda1: LABEL="System" UUID="593A-6005" TYPE="vfat" PARTLABEL="primary" PARTUUID="a0cbd241-1526-4124-8f28-1d5e72938926"
- /dev/sda2: LABEL="Storage" UUID="b2790391-452e-4e4c-b7a2-0979950c45ef" TYPE="ext4" PARTLABEL="primary" PARTUUID="632dac6a-4257-462d-9bf7-87f1a0203f83"
- /dev/sdb1: UUID="ee3b69bc-d50c-4539-832e-4c8da41cd5d1" TYPE="ext3" PARTUUID="f69ef69e-01"
- /dev/loop0: TYPE="squashfs"
- Mediacenter:~ #
Its ext3 or ext4...dont know exactly by now.
Thanks for answers, will post info when I get home.
My libreelec installation sees the HDD with all movies, music, etc as something like: sdb1-ata-WDC_WD1001FALS-0
Is it possible to change it into something shorted, more suitable, for ex. "HDD" or such?
Or, even better, is there a way to somehow mount the directories on that HDD to those kodi specific sources like Movies, Music, Pictures, to avoid setting up Sources in Kodi? Something like hardlinks.
is there something what prevents from connecting to libreelec from different subnet?
From my network knowledge, I dont see any problem for it to work, if I have correctly set my router, so all subnets can access each other. All is happening on the router.
For now, I found some workaround - I got htpc and main pc on the same subnet and now I can access samba shares. This proving my theory that libreelec's samba sharing works only on the same subnet. Or not?
Can you please provide more information about libreelec's samba shares, how it work, etc. or is there some info? Because I dont know what to do or try, if I dont know how it works.
No, I am using latest stable 7.0.2 for pc.
But I look at the link and there is slightly different problem. That guy there needs to see his shared folder on his NAS from HTPC.
And I need to access my HTPC (libreelec) from my Main PC (windows) so I can copy the files in/out HTPC when I am on Main PC.
I have just encounter a strange thing.
First, some background:
I have mikrotik router RB951G-2HnD which was configured from the factory to operate with bridge enabled, just like any other SOHO router.
I reset it, and set it to work without that bridge, so any interface (LAN port) on the router is fully manageable by now, can have its own subnet, etc. There is also some other benefits from this.
For example, LAN port 2, where my main pc is plugged in, have ip range 192.168.2.2-254
And LAN port 3, where htpc is, have ip range 192.168.3.1-254. htpc currently have ip 192.168.3.2
Those who seen Mikrotik routers before will know.
Nothing else changed, except resetting my router to set it into without-bridge mode and changing ip adresses on main pc and htpc. No changes to anything else, no change to any other setting in libreelec, except its ip adress.
But I can't now access samba shares on htpc from the main pc. When I try to access them through windows explorer like before, but now, of course through its new ip \\192.168.3.2, it just give me those well known windows error like "you dont have access and check your credentials" and also "specified logon session does not exist. it may already been terminated" and such.
As we know, samba and windows filesharing is using ports 135-139 and 445. I have those ports allowed in the router, so there is no problem.
The strange thing is, that I can SSH into it, which uses port 22. But not acces samba shares.
So, is there any firewall, its rule, or any other setting which is preventing to reach samba shares from different subnet?
Because if I set on my router that the htpc and main pc will be on the same subnet - main pc is 192.168.2.2 and htpc is 192.168.2.3 then samba shares works ok.
I think that samba shares in libreelec are operating similarly like netbios in windows - it only can access from the same subnet, and nothing else. Is that true?
I tried to look on iptalbes and its rules, if there are any. But it only give me this:Code
...so there isn't any?
I would like to know how exactly those samba shares operating, if there is any firewall running there, or something what not allowing access from computer in different subnet to libreelec.
Well, maybe next time in the future, when I will not have too much data on it. So it will not take very long to copy them back
I dont have another HDD for test.
Thanks for the advices, will try them when I ran in trouble with usb stick