Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server - Printable Version +- 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: New Era: VAAPI with EGL interoperation - jteeuw - 2015-07-17 (2015-07-17, 11:47)fritsch Wrote: If your remove the kodi.bin from the autostart file, does the xserver alone come up? I removed the kodi.bin but the xserver does not come up DISPLAY=:0 glxinfo | pastebinit http://paste.ubuntu.com/11892036/ I see a very strange kernel error on your side - can you try with the shipped 3.19 kernel of Vivid? Same problem. OpenELEC from USB stick works? not tried yet, is the OpenELEC a live stick ? kind regards RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-07-17 Yes, gunzip the img.gz then dd it to an usb stick. On boot enter "live" without the "". RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-07-17 Please triple verify, that you did not forget the: dpkg-reconfigure x11-common to set it to everybody. Also get me the user name you are using and the output of "id" with that user. RE: New Era: VAAPI with EGL interoperation - jteeuw - 2015-07-17 The openelec stick works, dpkg-reconfigure x11-commom is set to everybody , i have installed everthing with user kodi with id kodi RE: New Era: VAAPI with EGL interoperation - jteeuw - 2015-07-17 I did some more testing and if i connect the pc with vga to a monitor i see everything (bios,prompt and then kodi) When I connect with hdmi is see the following: bios ,prompt and then nothing When I connect hdmi and vga , I see on the hdmi monitor :bios, prompt and then kodi on the vga monitor RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-07-17 Quote:BOOT_IMAGE=/vmlinuz-4.1.2-040102-generic root=/dev/mapper/htpc--vg-root ro You don't use encrypted homes, do you? From the dmesg it seems the GPU has issues with your HDMI monitor and it cannot determine its size. As it does not work with normal ubuntu either, it seems to be a bug, that you need to file at bugs.freedesktop.org cause it is sadly unrelated to the code we are testing here. RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-07-17 Before filing, you can of course try: Code: mkdir kernel-drm Have fun. RE: New Era: VAAPI with EGL interoperation - jteeuw - 2015-07-17 (2015-07-17, 13:39)fritsch Wrote: Before filing, you can of course try: I have no encrypted homes and did run the kernal update but still the same problem, will report it @ bugs.freedesktop.org RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-07-17 Btw. did this ever work for you? :-) What hardware is that? Edit: Quote:[ 0.063471] smpboot: CPU0: Intel® Core i5-3450 CPU @ 3.10GHz (fam: 06, model: 3a, stepping: 09) Should work . What reveiled the OpenELEC test? RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-07-17 I talked with chris wilson on IRC, have a look here: https://bugs.freedesktop.org/show_bug.cgi?id=88331 and subscribe yourself. chris added a patch that fix it for you: https://bugs.freedesktop.org/show_bug.cgi?id=88331 <- though you need to build linux kernel from source and applying that patch manually. RE: New Era: VAAPI with EGL interoperation - jteeuw - 2015-07-17 (2015-07-17, 14:07)fritsch Wrote: Btw. did this ever work for you? :-) What hardware is that? It worked with this tutorial : http://forum.kodi.tv/showthread.php?tid=165707 , the hardware is a dell OptiPlex 3010 With openelec it worked ! RE: New Era: VAAPI with EGL interoperation - jteeuw - 2015-07-17 (2015-07-17, 14:18)fritsch Wrote: I talked with chris wilson on IRC, have a look here: https://bugs.freedesktop.org/show_bug.cgi?id=88331 and subscribe yourself. Thanks for the asking on IRC but my knowledge of Linux is to so great that I can compile a linux kernal ;-( RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-07-17 Then there is still something wrong with the initial setup, as OpenELEC (the builds I provide here) use the very same kernel (4.1.x). Get me again: id | pastebinit then do: sudo systemctl stop kodi and afterwards X & DISPLAY=:0 kodi Edit: And as you are at it, get me: sudo journalctl -a | pastebinit too RE: New Era: VAAPI with EGL interoperation - jteeuw - 2015-07-17 [quote='fritsch' pid='2054970' dateline='1437139407'] Then there is still something wrong with the initial setup, as OpenELEC (the builds I provide here) use the very same kernel (4.1.x). id | pastebinit http://paste.ubuntu.com/11892840/ sudo systemctl stop kodi X & DISPLAY=:0 kodi kodi@htpc:~$ X & [1] 1160 kodi@htpc:~$ DISPLAY=:0 kodi X.Org X Server 1.17.1 Release Date: 2015-02-10 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu Current Operating System: Linux htpc 4.2.0-994-generic #201507170159 SMP Fri Jul 17 02:01:25 UTC 2015 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-4.2.0-994-generic root=/dev/mapper/htpc--vg-root ro Build Date: 19 March 2015 09:26:59AM xorg-server 2:1.17.1-0ubuntu3 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.32.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 17 15:45:22 2015 (==) Using system config directory "/usr/share/X11/xorg.conf.d" The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols > Ignoring extra symbols Errors from xkbcomp are not fatal to the X server but no screen output to hdmi kodi@htpc:~$ sudo journalctl -a | pastebinit Traceback (most recent call last): File "/usr/bin/pastebinit", line 345, in <module> content = sys.stdin.read() File "/usr/lib/python3.4/codecs.py", line 319, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa6 in position 12429: invalid start byte kodi@htpc:~$ sudo journalctl -a | pastebinit Traceback (most recent call last): File "/usr/bin/pastebinit", line 345, in <module> content = sys.stdin.read() File "/usr/lib/python3.4/codecs.py", line 319, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa6 in position 12429: invalid start byte RE: New Era: VAAPI with EGL interoperation - fritsch - 2015-07-17 Yeah, then you need to upload the journalctl -a > debug.txt somewhere. But I think you are affected by the bug mentioned above, so it won't work. |