+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server (/showthread.php?tid=231955)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-14
Ah, nope! It just takes more time to start showing issues.
Test 2
- xorg.conf: none
- kernel: mainline 4.14.5
- vaapi PPA: ON
- xorg-edgers PPA: OFF
- Test result: success! Nope, it just takes more time to fail
- Kodi debug log: http://paste.ubuntu.com/26180936/
- xorg log: http://paste.ubuntu.com/26180935/
I will keep testing, xorg edgers PPA is next.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-14
Enable drm.debug=0xe and see. Btw this gets now really off topic as it's proven to be an issue with the Ubuntu kernel.
Try with latest stock 4.13.x from Ubuntu mainline and compare. Then file a bug with the Ubuntu people. As 4.14 works upstream will have limited interest.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-14
(2017-12-14, 08:39)fritsch Wrote: Enable drm.debug=0xe and see. Btw this gets now really off topic as it's proven to be an issue with the Ubuntu kernel.Sorry, 4.14.5 mainline doesn't work either, I did a follow-up post about it. It just takes more time for the issue to show-up.
Try with latest stock 4.13.x from Ubuntu mainline and compare. Then file a bug with the Ubuntu people. As 4.14 works upstream will have limited interest.
I'll post a debug log soon, the TV is busy right now.
Then I'll try xorg-edgers, see if a more recent libdrm and mesa helps in any way. My work is not done yet!
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - Stanislav - 2017-12-14
For audio issue I confirm that latest nightly works without AE_SINK workaround.
Thanks!
-- Stanislav
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-14
So, I'm exploring more.
Test 1 - LibreELEC Milhouse live nightly build
I did revisit the nightly Milhouse live stick, and really let it run for a good, good while, to see if anything developed after some time.
No issues, all good and spotless. Real nice!
Reference data:
- kernel is 4.14.4
- vainfo: http://sprunge.us/bdOj - Note, libva and driver are 2.0.0. The version in Ubuntu and the PPA is 1.8.3
- dmesg: http://sprunge.us/KJKE
- amixer: http://sprunge.us/NHLX
- Kodi debug logs: http://sprunge.us/FPXj
Test 2 - Ubuntu install with mainline 4.14.5 kernel, vaapi and xorg edgers PPAs
Going all in! At least with what I know is available... The xorg edgers PPA brings more recent libdrm-intel, mesa-va-drivers, mesa...
Issues are there after about 30-40mn, still a long time later than any other test. I played it for longer without issues on a previous test, but I had no debug logging on, and I thought that all was good. Could debug logging interfere (that overlay on screen, maybe?). I'll retry that without debug going later, just to be sure.
Reference data:
- kernel is mainline 4.14.5
- mesa versions: http://paste.ubuntu.com/26183990/
- vainfo: http://paste.ubuntu.com/26183994/ - Note, libva and driver are 1.8.3, LibreELEC is using 2.0.0
- dmesg: http://paste.ubuntu.com/26183997/
- id: http://paste.ubuntu.com/26183999/
- amixer: http://paste.ubuntu.com/26184003/
- Kodi debug logs: http://paste.ubuntu.com/26184275/
Test 3 - Ubuntu install with stock Ubuntu kernel, vaapi and xorg edgers PPAs
While wondering if the kernel really brought anything and if upgrading mesa/libdrm could not be enough, and willing to use a kernel that I will not have to maintain more or less myself... I have downgraded the kernel from mainline 4.14.5 to stock Ubuntu 4.13.
Results are the same as test 2
Reference data:
- kernel is stock Ubuntu 4.13
- mesa versions: http://paste.ubuntu.com/26184333/
- vainfo: http://paste.ubuntu.com/26184335/
- dmesg: http://paste.ubuntu.com/26184336/
- id: http://paste.ubuntu.com/26184338/
- amixer: http://paste.ubuntu.com/26184341/
- Kodi debug logs: http://paste.ubuntu.com/26184469/
Conclusions, so far
Without knowing the version used in the LibreELEC nightly, it's difficult to know the exact impact of mesa, mesa-drivers-va and libdrm.
Kernel impact appears to be null.
I really would like to know if there is a PPA for libva 2.0.0 anywhere, or if the current PPA could be brought up to that version. My gut feeling is that a jump from 1.8.3 to 2.0.0 is not something without impact. But... My guess is that Kodi (and all other dependencies in the distro) would have to be built targetting 2.x instead of 1.8, which I foresee as a blocker in an Ubuntu world.
Still on the agenda
I've just remembered a post asking me to enable drm.debug=0xe. I'll get to this and post as soon as I have figured out where/how that needs to happen!
I'll run another test 3 without debug logging, to check whether the overlay is cause for issues or not. Is this thing random, now?
I'm ready to go about any other test, suggestion, etc. that you may have!
Thanks again, everyone involved, for the time, effort, patience... It's fantastic that a numpty like me can have access to such support!
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-14
libva 2.0 has zero to do with your issue. Remember: Milhouse uses intel driver, not the modesetting driver. You have to use the xorg.conf I gave you for using it.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-14
(2017-12-14, 20:40)fritsch Wrote: libva 2.0 has zero to do with your issue. Remember: Milhouse uses intel driver, not the modesetting driver. You have to use the xorg.conf I gave you for using it.Understood for libva 2.0.
Then I will try again the intel driver with your setting. I had tried it yesterday, I believe, with no positive results. But there are a few combos more to try with it. I'll report back!
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-14
Turn on hidden debug logging (see advancedsettings.xml) and whenever you see the artifacts press a key on the keyboard - choose one that does nothing. That way we can see if anything in kodi.log correlates with your issue.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-14
(2017-12-14, 20:48)fritsch Wrote: Turn on hidden debug logging (see advancedsettings.xml) and whenever you see the artifacts press a key on the keyboard - choose one that does nothing. That way we can see if anything in kodi.log correlates with your issue.Will do
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-14
(2017-12-14, 20:44)camelreef Wrote:(2017-12-14, 20:40)fritsch Wrote: libva 2.0 has zero to do with your issue. Remember: Milhouse uses intel driver, not the modesetting driver. You have to use the xorg.conf I gave you for using it.Understood for libva 2.0.
Then I will try again the intel driver with your setting. I had tried it yesterday, I believe, with no positive results. But there are a few combos more to try with it. I'll report back!
Code:
Section "Device"
Identifier "Device0"
Driver "intel"
Option "DRI" "3"
EndSectionThat gives me instant artefacts (4.13 stock kernel, vaapi and xorg edgers PPAs).
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-14
(2017-12-14, 20:48)fritsch Wrote: Turn on hidden debug logging (see advancedsettings.xml) and whenever you see the artifacts press a key on the keyboard - choose one that does nothing. That way we can see if anything in kodi.log correlates with your issue.
Code:
<loglevel hide="false">1</loglevel>That will do it? 1 being Debug logging (without showing text on screen)
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - sibu - 2017-12-15
I installed Kodi on my Asrock Beebox in 2016 using this How-To. Everything worked well until today, after I updated the packages using apt-get dist-upgrade and updated the Kernel (because of a bug that seemed to be fixed in a new kernel).
Now Kodi won't start anymore. I'm using Ubuntu 16.04.3 LTS (GNU/Linux 4.10.0-43-generic x86_64), Kodi version 18.0-ALPHA1 Git:20171104-a5436a4
Log files:
http://paste.ubuntu.com/26185437/
http://paste.ubuntu.com/26185438/
http://paste.ubuntu.com/26185439/
http://paste.ubuntu.com/26185440/
http://paste.ubuntu.com/26185442/
http://paste.ubuntu.com/26185475/
Can anybody see the issue here? Thank you in advance for any help!
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-15
(2017-12-15, 00:07)sibu Wrote: I installed Kodi on my Asrock Beebox in 2016 using this How-To. Everything worked well until today, after I updated the packages using apt-get dist-upgrade and updated the Kernel (because of a bug that seemed to be fixed in a new kernel).
Now Kodi won't start anymore. I'm using Ubuntu 16.04.3 LTS (GNU/Linux 4.10.0-43-generic x86_64), Kodi version 18.0-ALPHA1 Git:20171104-a5436a4
Log files:
http://paste.ubuntu.com/26185437/
http://paste.ubuntu.com/26185438/
http://paste.ubuntu.com/26185439/
http://paste.ubuntu.com/26185440/
http://paste.ubuntu.com/26185442/
http://paste.ubuntu.com/26185475/
Can anybody see the issue here? Thank you in advance for any help!
Quote:22:50:37.175 T:139950595938688 ERROR: CSettings: error loading settings definition from special://xbmc/system/settings/settings.xml, Line 0
Failed to open file
22:50:37.175 T:139950595938688 FATAL: Unable to load settings definitions
22:50:37.176 T:139950595938688 DEBUG: LogindUPowerSyscall - delay lock released
Is your /home directory not mounted properly? Some LVM magic that bites you / encrypted home?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - wsnipex - 2017-12-15
(2017-12-14, 22:25)camelreef Wrote:AFAIK, libva does not support DRI3(2017-12-14, 20:44)camelreef Wrote:(2017-12-14, 20:40)fritsch Wrote: libva 2.0 has zero to do with your issue. Remember: Milhouse uses intel driver, not the modesetting driver. You have to use the xorg.conf I gave you for using it.Understood for libva 2.0.
Then I will try again the intel driver with your setting. I had tried it yesterday, I believe, with no positive results. But there are a few combos more to try with it. I'll report back!Code:Section "Device"
Identifier "Device0"
Driver "intel"
Option "DRI" "3"
EndSection
That gives me instant artefacts (4.13 stock kernel, vaapi and xorg edgers PPAs).
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-15
That's not for libva - that's for general rendering. But funny - please remove only this line - same artefacts?