+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: PVR & Live TV Support (https://forum.kodi.tv/forumdisplay.php?fid=167)
+---- Forum: Tvheadend (https://forum.kodi.tv/forumdisplay.php?fid=168)
+---- Thread: Linux Ubuntu 22.04 lts-Kodi 20 Omega-PVR-HTS- VAAPI/vpp vaCreateConfig error (/showthread.php?tid=374978)
Ubuntu 22.04 lts-Kodi 20 Omega-PVR-HTS- VAAPI/vpp vaCreateConfig error - petediscrete - 2023-11-08
As outlined above this error is appearing in the log as soon as I launch Live TV. While it doesn't appear to be affecting the playing of Live TV the error is currently flooding the log. I've only just discovered this recently when checking the log for a different reason. I did check elsewhere on this error and found that it might be a bug in Kodi but I'm not sure if it's conclusive or was ever fixed. I've included the output for both vainfo and hwinfo --display just in case it helps.
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.14 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel® Gen Graphics - 22.3.1 ()
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
hwinfo --display
17: PCI 02.0: 0300 VGA compatible controller (VGA)
[Created at pci.386]
Unique ID: _Znp.x3cfdQwIPa8
SysFS ID: /devices/pci0000:00/0000:00:02.0
SysFS BusID: 0000:00:02.0
Hardware Class: graphics card
Device Name: "Onboard IGD"
Model: "Intel HD Graphics 630"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x5912 "HD Graphics 630"
SubVendor: pci 0x103c "Hewlett-Packard Company"
SubDevice: pci 0x8299
Revision: 0x04
Driver: "i915"
Driver Modules: "i915"
Memory Range: 0x1ffe000000-0x1ffeffffff (rw,non-prefetchable)
Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable)
I/O Ports: 0x3000-0x303f (rw)
Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
IRQ: 130 (368614 events)
Module Alias: "pci:v00008086d00005912sv0000103Csd00008299bc03sc00i00"
Driver Info #0:
Driver Status: i915 is active
Driver Activation Cmd: "modprobe i915"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Primary display adapter: #17
Please find attached the logs https://paste.kodi.tv/unoxubabam.kodi
RE: Ubuntu 22.04 lts-Kodi 20 Omega-PVR-HTS- VAAPI/vpp vaCreateConfig error - izprtxqkft - 2023-11-08
that issue was reported 2 years and 11 months ago (almost 3 years)
https://github.com/intel/libva/issues/477
no resolution and issue remains open
RE: Ubuntu 22.04 lts-Kodi 20 Omega-PVR-HTS- VAAPI/vpp vaCreateConfig error - petediscrete - 2023-11-08
Yes I assumed that from what I unearthed. I just disabled logging as a temporary fix at my end. Everything else appears to be fine. Btw I tried it on both Nexus and Omega. Same result. Funny thing I can’t remember noticing it in Matrix but no doubt it was there.
RE: Ubuntu 22.04 lts-Kodi 20 Omega-PVR-HTS- VAAPI/vpp vaCreateConfig error - izprtxqkft - 2023-11-08
on the plus side, there is really no benefit to hardware decoding MPEG-2 in my opinion so the worst part is log spam
agree it should be fixed though, at least stop trying to open hardware acceleration for it once it reports it's not able - (more opinion)
RE: Ubuntu 22.04 lts-Kodi 20 Omega-PVR-HTS- VAAPI/vpp vaCreateConfig error - petediscrete - 2023-11-08
At least anyone passing through will know that it’s an ongoing unaddressed issue and clearly not high on the priority list of fixes anytime soon. Thanks.