Well, I tryed different distros, here are some results:
1. Now i use Xubuntu 14.04.5 with Kodi 17.6 session - smooth playback.
2. Xubuntu 16.04.5 with Kodi 18 session - freezes.
3. Xubuntu 18.04.1 with Kodi 18 session - freezes.
4. Libreelec stable - smooth.
5. Libreelec alpha - same problem. When Vsync on - freezes, when off - smooth, until VsyncOff (ctrl-shift-O OSD) became greater then 40 (10-15 sec.) and then drops down - i see little freeze at this moment.
It looks like the problem is Open GL 4 in modern distros. It's time to change J1900 with J3455?
(2018-12-18, 08:05)fritsch Wrote: [ -> ]https://www.mesa3d.org/envvars.html <- force GL 2.1 if you think this is the problem.
Thanks, I'll try it out.
And how do you think what component or lib causes
CGLContextEGL::SwapBuffers: last msc time greater than interval in kodi.log?
Yes. The old way which worked much better (sadly) was removed as it was against the standard. The new way of doing things seems to cause issues. With some drivers it works better with others it's quite bad :-(
fritsch Wrote:https://www.mesa3d.org/envvars.html <- force GL 2.1 if you think this is the problem.
Tryed, dosn't help.
(2018-12-18, 20:42)fritsch Wrote: [ -> ]Yes. The old way which worked much better (sadly) was removed as it was against the standard. The new way of doing things seems to cause issues. With some drivers it works better with others it's quite bad :-(
Well, I compare debug log of
14.04 - Kodi17.6 and
16.04 - Kodi18.0 and yes - the things are different. I see:
Code:
ERROR: CYUVShaderGLSL::CYUVShaderGLSL - failed to open file gl_shader_frag_texture_lim.glsl
NOTICE: GL: No pixel shader, fixed pipeline in use
In new version.
Even on very old Intel machine with
Code:
GL_RENDERER = Mesa DRI Intel(R) Q45/Q43
GL_VERSION = 2.1 Mesa 18.0.5
I don't see "No pixel shader". BayFail )) And C-state bug still here, - I have to switch to C1 max C-state in BIOS.
It's time to change hardware, it seems.
fritsch, did you have any troubles with Vsync on Apollo Lake?
No - all fine here. And comparing 14.04 with anything is just bogus ... 4 year old drivers ... make no sense in compairing. the C1 bug is fixed in recent kernel versions. Use 4.18 or later.
Hello,
i have a question. Is the intel i5 9600k not supported? Kodi have huge cpu usage. All cores are between 20% - 80 % and the playback is too slow and stucks.
With my i5 4670k runs Kodi perfect smooth.
My current config (Hardware):
I5 9600k
MSI MAG Z390M
16Gb DDR 4
See the first post. All the mandatory logfiles are missing.
(2018-12-22, 20:20)fritsch Wrote: [ -> ]Quote:dpkg -l |grep mesa | pastebinit
DISPLAY=:0 vainfo | pastebinit
cat ~/.kodi/temp/kodi.log | pastebinit
dmesg | pastebinit
id | pastebinit
amixer | pastebinit
cat /var/log/Xorg.0.log | pastebinit
dpkg -I =
http://paste.ubuntu.com/p/WBKDT9PBRf/
Display= libva info: VA-API version 1.2.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
vaInitialize failed with error code -1 (unknown libva error),exit
You are trying to send an empty document, exiting.
cat= cat ~/.kodi/temp/kodi.log | pastebinit
cat: /home/htpc/.kodi/temp/kodi.log: No such file or directory
You are trying to send an empty document, exiting.
Dmesg=
http://paste.ubuntu.com/p/qfgRJMcyjw/
ID=
http://paste.ubuntu.com/p/FVZCt58pxg/
Amixer= amixer | pastebinit
amixer: Mixer attach default error: No such file or directory
You are trying to send an empty document, exiting.
Cat Xorg=
http://paste.ubuntu.com/p/Zw8xjBZSCG/
I hope its now right sorry i´m a semi noob.
thanks for your patient.
Quote:uid=1000(htpc) gid=1000(htpc) groups=1000(htpc),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev)
You did not follow the howto - your username is different. means: your htpc named user is not member of
video and not member of
audio group
. Fix that please.
Quote:cat= cat ~/.kodi/temp/kodi.log | pastebinit
cat: /home/htpc/.kodi/temp/kodi.log: No such file or directory
You are trying to send an empty document, exiting.
This command needs to be run with the user actually starting kodi! If the file is not there - htpc is most likely not your "kodi user" ...
Seems you mixed up the howto with some freestyle of your own (username, etc.)
(2018-12-22, 23:49)fritsch Wrote: [ -> ]Quote:uid=1000(htpc) gid=1000(htpc) groups=1000(htpc),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev)
You did not follow the howto - your username is different. means: your htpc named user is not member of video and not member of audio group. Fix that please.
Quote:cat= cat ~/.kodi/temp/kodi.log | pastebinit
cat: /home/htpc/.kodi/temp/kodi.log: No such file or directory
You are trying to send an empty document, exiting.
This command needs to be run with the user actually starting kodi! If the file is not there - htpc is most likely not your "kodi user" ...
Seems you mixed up the howto with some freestyle of your own (username, etc.)
Now I´m logget in with user Kodi. I´m so stupid sorry that i waste your time...
I hope now it is alright and you can see my problem so i can solve it.
so lets begin the 3rd.
Dpkg=
http://paste.ubuntu.com/p/qH3xbqnMMq/
Display= DISPLAY=:0 vainfo | pastebinit
error: XDG_RUNTIME_DIR not set in the environment.
libva info: VA-API version 1.2.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_2
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
You are trying to send an empty document, exiting.
cat Kodi=
http://paste.ubuntu.com/0/ (Dont work)
https://paste.kodi.tv/rifanahafa.kodi
dmseg=
http://paste.ubuntu.com/0/ (also dont work)
https://paste.kodi.tv/tecuxideju
ID=
http://paste.ubuntu.com/p/QhYqHtPjW4/
amixer=
http://paste.ubuntu.com/p/xTQTbvDVFQ/
Xorg=
http://paste.ubuntu.com/0/ (and another one)
https://paste.kodi.tv/miqotiwava
Kodi.log ,xorg0 log and dmseg over paste.kodi
thx allot
you don't have the Intel gfx driver installed, libva seems to be the wrong version..
In short, you didn't follow the howto
Looks like Ubuntu 16.04 ...