+- 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 - abudabi - 2016-08-04
Regarding EDID, which is the recommended option... edit xorg or edit grub?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-08-04
As xorg does absolutely nothing for intel, guess :-)
For the other poster: check the manual x11-common and especially the x11 legacy permissions.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - tudstudent - 2016-08-04
(2016-08-04, 19:29)maurer Wrote: 1) When rebooting nuc with display shut after i turn on the display there is no image - only fix is to reboot the nuc with display on which leads to issue:I made a post before yours with how to save your monitor edid and make ubuntu start with it (Fritisch has made the post multiple times). This will solve this problem. It comes forth out of the fact that Kodi needs xrandr on startup if it fails Kodi will not start properly or so.
Make the adjustments and you should be fine
Post: http://forum.kodi.tv/showthread.php?tid=231955&pid=2387505#pid2387505
(2016-08-04, 19:29)maurer Wrote: 2) When powering the nuc with display on kodi doesn't start - i have to manually enter (in ssh) " sudo systemctl start kodi"
This question is quite easy, Fritisch has described how to start systemctl manually, but as I just scanned quickly did not include a command to start it by default when rebooting. This is done with the following command:
Code:
sudo systemctl enable kodi.serviceHope this helps.
Kind regards,
tudstudent
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-08-05
That howto is not complete. I posted another one including changing the initramfs somewhere else.
Remember: display off means no handshake. This is by design. It's like unplugging cable and complaining to see no image. The edid overwriting is no bugfix but a workaround.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - User 182116 - 2016-08-05
I'm a little confused.
With sudo systemctl start kodi it starts by default with a reboot already.
So what is the advantage of using sudo systemctl enable kodi.service?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-08-05
Nothing ... it's the most laziest workaround I have ever seen proposed :-) you save to reboot if you switch on your TV late, but other workarounds (drm_kms_helper and so on are better suited). See the LibreELEC / OpenELEC wiki for a beginner's howto on cpio contained workaround.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - User 182116 - 2016-08-05
Thank you.
I will read up on the guide.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - maurer - 2016-08-06
thanks for the info
I've managed to fix my first (and worst) issue - system starts X with display off following second post tutorial link.
I've enabled kodi service but it still doesn't start correctly - it enters failed state and can't seem to find the log why
Do you have yours auto starting ?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-08-06
How about posting the logfiles (all of them) including dmesg | pastebinit the first post wants?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-08-06
Here for completeness: http://forum.kodi.tv/showthread.php?tid=231955&pid=2148505#pid2148505 _always_ provide dmesg | pastebinit after you have applied _all_ the fixes.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - tudstudent - 2016-08-06
Fritsch, what I do not understand (honestly, please explain if you would). is that in your previous link for edid you post Ubuntu needs a workaround for initramfs.
However I read somewhere else that you have during boot late and early binding of edid.
With just the grub line added you will have late KMS binding. With ramfs you have an early binding. Why would you want early binding?
I am certainly no expert and all I know is just by googling... Realy appreciated if you could clarify.
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-08-06
Quite easy:
- Try it and check with dmesg | pastebinit to spot the difference
You will realize that the first time drm_kms_helper searches for the edid file it can't access it. At the time of writing the Braswells did not (!) enable the video output at all if there was no faked edid connected at this early stage, that's why it is there. This is btw. what I am using here in my living room.
So, just check what happens if you boot without TV attached and compare with and without "early binding".
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - maurer - 2016-08-06
(2016-08-06, 06:47)fritsch Wrote: How about posting the logfiles (all of them) including dmesg | pastebinit the first post wants?root@ubuntu:/home/kodi# dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/22432306/
root@ubuntu:/home/kodi# DISPLAY=:0 vainfo | pastebinit
error: XDG_RUNTIME_DIR not set in the environment.
libva info: VA-API version 0.39.2
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_0_39
libva info: va_openDriver() returns 0
http://paste.ubuntu.com/22432307/
root@ubuntu:/home/kodi# cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/22432309/
root@ubuntu:/home/kodi# dmesg | pastebinit
http://paste.ubuntu.com/22432311/
root@ubuntu:/home/kodi# id | pastebinit
http://paste.ubuntu.com/22432315/
root@ubuntu:/home/kodi# amixer | pastebinit
http://paste.ubuntu.com/22433531/
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2016-08-06
We never run kodi as root -> follow the howto, please.
Quote:19:11:37 T:140604249237440 NOTICE: Starting Kodi (14.0-RC2 Git:35b4f38). Platform: Linux x86 64-bit
^^ Are you kidding me?
RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - Jan0sh - 2016-08-07
Hi after an update (I guess) kodi no longer starts neither thorug provided systemd service nor running the ExecStart command as kodi user. dmesgs shows a segfault witin kodi.
attached find the logfiles
https://paste.ubuntu.com/22569055/
https://paste.ubuntu.com/22569053/
https://paste.ubuntu.com/22569033/
https://paste.ubuntu.com/22569027/
https://paste.ubuntu.com/22569017/
https://paste.ubuntu.com/22569009/
any help is appreciated. thanks in advance