•   
  • 1
  • 335
  • 336
  • 337(current)
  • 338
  • 339
  •   
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server
hi,

I wanted to ask you if the tutorial at the first post is different for ubuntu server 19.10 or if it remains identical

thanks
Sorry for grammatical errors, use an online translator
Reply
Try it and tell us afterwards. I don't maintain it anymore, therefore I have no idea.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
I took the new nuc 10i7FNH and I've been trying for a couple of days to install kodi as I had on the old nuc (J5005) but there's no way to make it work.
Decode only in software mode, I've been trying to install everything by updating everything but I can't get out of it.

I pray the guru @fritsch in a magic

- Xorg
- mesa
- Libva
- Kodi log
- id
- amixer
- dmesg
Sorry for grammatical errors, use an online translator
Reply
sTry:
sudo apt install intel-media-va-driver-non-free

And first make sure to go back to a sane base.

Afterwards:
export LIBVA_DRIVER_NAME=iHD
vainfo | pastebinit

If that works, make sure to expose the env before starting kodi, like e.g.
Code:
sudo sh -c "echo 'LIBVA_DRIVER_NAME=iHD' >> /etc/environment"

and reboot.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2020-02-04, 04:49)fritsch Wrote: sTry:
sudo apt install intel-media-va-driver-non-free

And first make sure to go back to a sane base.

Afterwards:
export LIBVA_DRIVER_NAME=iHD
vainfo | pastebinit

If that works, make sure to expose the env before starting kodi, like e.g.
Code:
sudo sh -c "echo 'LIBVA_DRIVER_NAME=iHD' >> /etc/environment"

and reboot.  

sudo vainfo
error: XDG_RUNTIME_DIR not set in the environment.
error: can't connect to X server!
error: failed to initialize display


dpkg -l |grep mesa | pastebinit
DISPLAY=:0 vainfo | pastebinit :
Code:
DISPLAY=:0 vainfo | pastebinit
libva info: VA-API version 1.5.0
libva info: va_getDriverName() returns -1
libva info: User requested driver 'iHD'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_5
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 18
vaInitialize failed with error code 18 (invalid parameter),exit

cat ~/.kodi/temp/kodi.log | pastebinit
dmesg | pastebinit
id | pastebinit
amixer | pastebinit -> amixer: Mixer attach default error: No such file or directory
cat /var/log/Xorg.0.log | pastebinit
Sorry for grammatical errors, use an online translator
Reply
Too bad. Use libreelec.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2020-02-04, 21:16)fritsch Wrote: Too bad. Use libreelec.
Sad

thank you anyway for your time and also because you are always kind and helpful with everyone.
Sorry for grammatical errors, use an online translator
Reply
Yeah, please report back if LE works. Try their nightly.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2020-02-04, 21:42)fritsch Wrote: Yeah, please report back if LE works. Try their nightly.
I already know it works because there is another user who has the same nuc and with librelec it works. (https://forum.kodi.tv/showthread.php?tid...pid2921633) in post 31 :Video and audio playback and nsf shares works. I'm now setting up the rest.

Instead look what I saw in my kodi log:
Code:
2020-02-04 19:48:12.192 T:27857  NOTICE: VDPAU::CreateContext - creating decoder context
2020-02-04 19:48:12.193 T:27857  NOTICE: vdp_device = 0x00000000 vdp_st = 0x00000001
2020-02-04 19:48:12.193 T:27857   ERROR: (VDPAU) unable to init VDPAU - vdp_st = 0x1.  Falling back.
2020-02-04 19:48:12.193 T:27857   DEBUG: GLX_EXTENSIONS: GLX_ARB_context_flush_control GLX_ARB_create_context GLX_ARB_create_context_profile GLX_ARB_fbconfig_float GLX_ARB_framebuffer_sRGB GLX_ARB_get_proc_address GLX_ARB_multisample GLX_EXT_create_context_es2_profile GLX_EXT_create_context_es_profile GLX_EXT_fbconfig_packed_float GLX_EXT_framebuffer_sRGB GLX_EXT_import_context GLX_EXT_texture_from_pixmap GLX_EXT_visual_info GLX_EXT_visual_rating GLX_MESA_copy_sub_buffer GLX_MESA_query_renderer GLX_OML_swap_method GLX_SGIS_multisample GLX_SGIX_fbconfig GLX_SGIX_pbuffer GLX_SGIX_visual_select_group GLX_SGI_make_current_read
2020-02-04 19:48:12.193 T:27857  NOTICE: CRenderSystemGL::InitRenderSystem - Version: 3.1 Mesa 19.2.8, Major: 3, Minor: 1
2020-02-04 19:48:12.193 T:27857  NOTICE: GL_VENDOR = VMware, Inc.
2020-02-04 19:48:12.193 T:27857  NOTICE: GL_RENDERER = llvmpipe (LLVM 9.0, 256 bits)
2020-02-04 19:48:12.193 T:27857  NOTICE: GL_VERSION = 3.1 Mesa 19.2.8

since I also have virtualbox (6.1) isn't that kodi is using its libraries? can't I force it to use the "system" libraries somehow?
Sorry for grammatical errors, use an online translator
Reply
That log just means, you did not install a proper graphics driver
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2020-02-04, 22:12)fritsch Wrote: That log just means, you did not install a proper graphics driver

nothing to do, I tried to clean it all up again but I can't figure out what's wrong.
I'm googling it but nobody's talking about it.
My problem is that I can't use ubuntu server installation because as soon as it has to wash on nvme disk crashes the installer.
I have to install ubuntu desktop 19.10 and with the taksel utility delete everything and select ubuntu server.
Maybe the problem is right here, I do not have a clean installation.

Do you know if it is possible to get a "nightly" iso of ubuntu server live install always at release 19.10?
Sorry for grammatical errors, use an online translator
Reply
The daily is 20.04 only i think: http://cdimage.ubuntu.com/ubuntu-server/
| myHTPC |
Reply
guys, I'm not giving up

I tried to put this "i915.alpha_support=1" in the grub and finally something moves :
Quote:2020-02-07 21:52:14.474 T:3647  NOTICE: GL_VENDOR = Intel
2020-02-07 21:52:14.474 T:3647  NOTICE: GL_RENDERER = Mesa Intel® UHD Graphics (CML GT2)
2020-02-07 21:52:14.474 T:3647  NOTICE: GL_VERSION = 4.6 (Compatibility Profile) Mesa 20.1.0-devel (git-26ab38f 2020-02-07 eoan-oibaf-ppa)
2020-02-07 21:52:14.474 T:3647  NOTICE: GL_SHADING_LANGUAGE_VERSION = 4.60
2020-02-07 21:52:14.474 T:3647  NOTICE: GL_EXTENSIONS = GL_3DFX_texture_compression_FXT1 GL_AMD_conservative_depth GL_AMD_depth_clamp_separate GL_AMD_draw_buffers_blend GL_AMD_multi_draw_indirect GL_AMD_performance_monitor GL_AMD_pinned_memory GL_AMD_query_buffer_object GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_stencil_export GL_AMD_shader_trinary_minma>2020-02-07 21:52:14.479 T:3647    INFO: GL: Maximum texture width: 16384
2020-02-07 21:52:14.479 T:3647   DEBUG: guilib: Fill viewport on change for solving rendering passes
but I still don't have hardware acceleration but only software.
Quote:2020-02-07 21:53:51.892 T:3731  NOTICE: Creating video codec with codec id: 27                                                                                                                                                               
2020-02-07 21:53:51.892 T:3731  NOTICE: CDVDVideoCodecFFmpeg::Open() Using codec: H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10                                                                                                                  
2020-02-07 21:53:51.892 T:3731   DEBUG: CDVDVideoCodecFFmpeg - Updated codec: ff-h264
 
Quote: sudo DISPLAY=:0 vainfo
error: XDG_RUNTIME_DIR not set in the environment.
libva info: VA-API version 1.5.0
libva info: va_getDriverName() returns 0
libva info: User requested driver 'iHD'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_5
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.5 (libva 2.5.0)
vainfo: Driver version: Intel iHD driver - 1.0.0
vainfo: Supported profile and entrypoints
      VAProfileNone                   : VAEntrypointVideoProc
      VAProfileNone                   : VAEntrypointStats
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Simple            : VAEntrypointEncSlice
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointFEI
      VAProfileH264Main               : VAEntrypointEncSliceLP
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointFEI
      VAProfileH264High               : VAEntrypointEncSliceLP
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointVLD
      VAProfileJPEGBaseline           : VAEntrypointEncPicture
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264ConstrainedBaseline: VAEntrypointFEI
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
      VAProfileVP8Version0_3          : VAEntrypointVLD
      VAProfileVP8Version0_3          : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointVLD
      VAProfileHEVCMain               : VAEntrypointEncSlice
      VAProfileHEVCMain               : VAEntrypointFEI
      VAProfileHEVCMain10             : VAEntrypointVLD
      VAProfileHEVCMain10             : VAEntrypointEncSlice
      VAProfileVP9Profile0            : VAEntrypointVLD
      VAProfileVP9Profile2            : VAEntrypointVLD
Sorry for grammatical errors, use an online translator
Reply
Full kodi log please.

Now it should work. Why do you run vainfo as root? Permission issues? Groups wrong?

Please post all logfiles again run as kodi user.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
dpkg -l |grep mesa | pastebinit
cat ~/.kodi/temp/kodi.log | pastebinit
dmesg | pastebinit
id | pastebinit
amixer | pastebinit
cat /var/log/Xorg.0.log | pastebinit

DISPLAY=:0 vainfo | pastebinit
error: can't connect to X server!
error: failed to initialize display

with sudo DISPLAY=:0 vainfo | pastebinit


I noticed that if I leave this directory empty "/etc/X11/xorg.conf.d/ ",  then use intel, if I create the link (/usr/share/doc/xserver-xorg-video-intel/xorg.conf 10-intel.conf ) instead use llvmpipe again
Sorry for grammatical errors, use an online translator
Reply
  •   
  • 1
  • 335
  • 336
  • 337(current)
  • 338
  • 339
  •   



Logout Mark Read Team Forum Stats Members Help
Intel VAAPI howto with Leia v18 nightly based on Ubuntu 18.04 server18
This forum uses Lukasz Tkacz MyBB addons.