+- 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 - fritsch - 2017-12-19
(2017-12-19, 18:11)camelreef Wrote:xrandr --output YOUROUTPUT --mode 1920x1080(2017-12-19, 18:06)fritsch Wrote: The "ds" clearly show that whatever happened is totally unknown to kodi - nothing in the log. No resync, nothing - absolutely nothing.I know, nada in the logs, it's not good...
Now - try - as asked some weeks before: Set your resolution to 1080p, play the same video again, let it scale down with "bilinear" scaling. Same artefacts?
How do I hard set to 1080p?
And in kodi disable "Adjust Refreshrate". Make sure you manually set scaling to bilinear - as otherwise it would stutter like hell as the GPU is too slow to do lanczos 3 downscaling.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-19
(2017-12-19, 18:38)fritsch Wrote:I put the xrandr in the openbox autostart?(2017-12-19, 18:11)camelreef Wrote:xrandr --output YOUROUTPUT --mode 1920x1080(2017-12-19, 18:06)fritsch Wrote: The "ds" clearly show that whatever happened is totally unknown to kodi - nothing in the log. No resync, nothing - absolutely nothing.I know, nada in the logs, it's not good...
Now - try - as asked some weeks before: Set your resolution to 1080p, play the same video again, let it scale down with "bilinear" scaling. Same artefacts?
How do I hard set to 1080p?
And in kodi disable "Adjust Refreshrate". Make sure you manually set scaling to bilinear - as otherwise it would stutter like hell as the GPU is too slow to do lanczos 3 downscaling.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-19
Wherever you want it Sherlock :-) you can also do it via ssh: DISPLAY=:0 xrandr --output whatever --mode 1920x1080
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-19
(2017-12-19, 19:34)fritsch Wrote: Wherever you want it Sherlock :-) you can also do it via ssh: DISPLAY=:0 xrandr --output whatever --mode 1920x1080Sir, yes, Sir! :o)
So, same conditions/PPAs/kernel as above, still intel driver.
Adjust Refreshrate disabled
I issued the 1080p xrandr command through ssh after the movie started playing, as Kodi got going with an initial switch to 2160p.
Yes, artefacts showed-up, very visibly, 15mn into the movie.
Debug log: http://paste.ubuntu.com/26216448/
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-19
Good. I think we have to end this here. There is nothing left I can do for you.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-19
(2017-12-19, 20:04)fritsch Wrote: Good. I think we have to end this here. There is nothing left I can do for you.OK... Would you care to explain?
And who can I turn to, now?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-19
(2017-12-19, 20:07)camelreef Wrote:Your issue has zero to do with kodi. Whatever happens is only happening for you on your installed / configured system. Clean installations with e.g. LibreELEC proved that. We asked many others running Ubuntu (including me) to test your samples. No one had that issue (Edit(2017-12-19, 20:04)fritsch Wrote: Good. I think we have to end this here. There is nothing left I can do for you.OK... Would you care to explain?
And who can I turn to, now?
and most importantly there is absolutely no correlation with anything in kodi's log.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-20
(2017-12-19, 20:12)fritsch Wrote:I can't fail you there... But one last question.(2017-12-19, 20:07)camelreef Wrote:Your issue has zero to do with kodi. Whatever happens is only happening for you on your installed / configured system. Clean installations with e.g. LibreELEC proved that. We asked many others running Ubuntu (including me) to test your samples. No one had that issue (Edit(2017-12-19, 20:04)fritsch Wrote: Good. I think we have to end this here. There is nothing left I can do for you.OK... Would you care to explain?
And who can I turn to, now?
So I've reinstalled from scratch, bare server, then your guide, step by step. The only thing I've added is the xorg.conf file for the intel driver (though it looked like it was working with the modesetting driver while I had forgotten about the intel driver).
The only difference from the previous install is that I've learned about netplan and didn't force an ifupdown network setup. We learn everyday...
It looked like it was working very sweetly and crisply!
Then I started my Roon server install. There is a dependency on ffmpeg/libav-tools + cifs-utils. Could those packages be a source of conflict?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-20
(2017-12-20, 03:14)camelreef Wrote:(2017-12-19, 20:12)fritsch Wrote:I can't fail you there... But one last question.(2017-12-19, 20:07)camelreef Wrote: OK... Would you care to explain?Your issue has zero to do with kodi. Whatever happens is only happening for you on your installed / configured system. Clean installations with e.g. LibreELEC proved that. We asked many others running Ubuntu (including me) to test your samples. No one had that issue (Edit
And who can I turn to, now?
So I've reinstalled from scratch, bare server, then your guide, step by step. The only thing I've added is the xorg.conf file for the intel driver (though it looked like it was working with the modesetting driver while I had forgotten about the intel driver).
The only difference from the previous install is that I've learned about netplan and didn't force an ifupdown network setup. We learn everyday...
It looked like it was working very sweetly and crisply!
But it's not.
I'm not straying outside bare Ubuntu Server and your install guide, nothing weird. And still, I get artefacts...
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - mirtouf - 2018-01-06
Hi,
for this first post of 2018 I start with a problem, I switched from a N3150-ITX (which ran smoothly) to a J3455-ITX Asrock mainboard using the recommendations of the first page and I have a problem with libva and the va API leading to all required HW accelerated videos being software rendered.
I also tried with a kernel from Ubuntu 17.10 and I ended with the same results.
Code:
dpkg -l |grep mesaCode:
DISPLAY=:0 vainfo (definitely a problem here)Code:
cat ~/.kodi/temp/kodi.logCode:
dmesgCode:
idCode:
amixerRE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2018-01-06
It seems i965-va-driver is not installed. While at it, make sure to add wsnipex's vaapi ppa and use the intel driver from there
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - mirtouf - 2018-01-06
I did not had time to edit my message and indicate I am using wsnipex repo:
Code:
i965-va-driver is already the newest version (1.8.3-4+ppa~xenial).aptitude search "?origin (wsnipex) ?installed"
i i965-va-driver - VAAPI driver for Intel G45 & HD Graphics family
i libva-drm1 - Video Acceleration (VA) API for Linux -- DRM runtime
i libva-intel-vaapi-driver - VAAPI driver for Intel G45 & HD Graphics family (transitional package)
i libva-wayland1 - Video Acceleration (VA) API for Linux -- Wayland runtime
i libva-x11-1 - API d'Accélération Vidéo (VA) pour Linux -- exécution X11
i libva1 - API d'accélération vidéo pour Linux - exécutables
i vainfo - Video Acceleration (VA) API for Linux -- info program
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2018-01-06
dpkg -L i965-va-driver | pastebinit
sudo apt-get -f install
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2018-01-06
Try:
export LIBVA_DRIVER_NAME=i965
DISPLAY=:0 vainfo
what does this do?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - mirtouf - 2018-01-06
https://paste.ubuntu.com/26334303/
Code:
sudo apt-get -f install
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.Code:
export LIBVA_DRIVER_NAME=i965
DISPLAY=:0 vainfo
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns -1
libva info: User requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
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