Kodi Community Forum
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)



RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-15

(2017-12-15, 11:40)fritsch Wrote: That's not for libva - that's for general rendering. But funny - please remove only this line - same artefacts?
 I'll remove the DRI option line and test.

I'm also planning on getting the drm debug logs from the kernel today and do the key pressing thing when there are artefacts on screen. Sorry, I've been kept away from the machine yesterday, but I'm still on it! Interest is not lost!


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-15

(2017-12-15, 11:40)fritsch Wrote: That's not for libva - that's for general rendering. But funny - please remove only this line - same artefacts?
Right, everything stock (kernel, libva, mesa, dri, libva), but X running the intel driver with DRI2 (not 3) and not the modesetting driver, and I'm getting artefacts within a minute).

Let me add more recent things in there, one by one, and I'll report.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - camelreef - 2017-12-15

(2017-12-15, 11:40)fritsch Wrote: That's not for libva - that's for general rendering. But funny - please remove only this line - same artefacts?
I should change the test film, I'm getting way too familiar with Wonder Woman, however nice she looks! 

From pure stock:
  • intel driver (DRI2): artefacts within 5mn
  • Stock, intel driver (DR2), libva PPA: artefacts within 15mn
  • Stock, intel driver (DRI2), libva PPA, xorg edgers PPA: artefacts within 25mn
  • Stock, intel driver (DRI2), libva PPA, xorg edgers PPA, mainline 4.14.5 kernel: artefacts within 35
With a sample of 1 for each test, I wonder how valuable the timings are...

Right... With that said, on to kernel drm debug and key pressing with hidden debug logging turned on!


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - sibu - 2017-12-15

(2017-12-15, 09:21)fritsch Wrote:
(2017-12-15, 00:07)sibu Wrote: I installed Kodi on my Asrock Beebox in 2016 using this How-To. Everything worked well until today, after I updated the packages using apt-get dist-upgrade and updated the Kernel (because of a bug that seemed to be fixed in a new kernel).
Now Kodi won't start anymore. I'm using Ubuntu 16.04.3 LTS (GNU/Linux 4.10.0-43-generic x86_64), Kodi version 18.0-ALPHA1 Git:20171104-a5436a4

Log files:
http://paste.ubuntu.com/26185437/
http://paste.ubuntu.com/26185438/
http://paste.ubuntu.com/26185439/
http://paste.ubuntu.com/26185440/
http://paste.ubuntu.com/26185442/
http://paste.ubuntu.com/26185475/

Can anybody see the issue here? Thank you in advance for any help!
Quote:22:50:37.175 T:139950595938688 ERROR: CSettings: error loading settings definition from special://xbmc/system/settings/settings.xml, Line 0
Failed to open file
22:50:37.175 T:139950595938688 FATAL: Unable to load settings definitions
22:50:37.176 T:139950595938688 DEBUG: LogindUPowerSyscall - delay lock released

Is your /home directory not mounted properly? Some LVM magic that bites you / encrypted home?      
Thank you for your reply. I think I have an encrypted /home directory. However I can access all files normally. What I also noticed, when I want to start Kodi using the command
Code:
kodi --standalone
, there is the error "Unable to find path to Kodi data files!". When I start Kodi using the workarround found here, with
Code:
KODI_HOME=/usr/share/kodi/ kodi --standalone
, it gives me this error message "ERROR: Unable to create application. Exiting
Segmentation fault (core dumped)
Crash report available at ..."
And the crash rebort is identical to this one: https://paste.ubuntu.com/26185439/

Is my profile corrupted or something? Do you need any additional log files?

UPDATE: I fixed it! Seems like Kodi was not installed properly. I saw this thread and executed
Code:
sudo apt install kodi
. Now everything is fine. Thanks for your help!


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-17

@camelreef I just came home and tested the complete sample on my ASRock J4205. No problems at all. I use intel driver + DRI3 + a drm-tip kernel from some time ago. I am starting to think that something else on your system (running next to kodi) causes your issue by either blocking the CPU or even causing interference - DVB card? Some server process acting up?

I watched the complete 15 minutes. I also opened the OSD randomly, as the Codec-Info - no issue. Poor fox, nice eagle - funny how they got the camera on top of her (they told the eagle is a her). What an eagle fight - like Karate kid. Now I got hungry ;-)

Mesa 17.2.2
xserver-xorg-video-intel: 2:2.99.917+git1711090734.37a682~oibaf~z <- I recompiled fabio's latest version (but should work with everything else)
Kernel: drm-tip intel (2 weeks ago)
xserver: 1.19.5-0ubuntu2
vainfo: Driver version: Intel i965 driver for Intel® Broxton - 1.8.3
NFS-share via 5 GHz AC Bridge
DTS-HD passthrough enabled.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - theghost3131 - 2017-12-17

Hi

Do you know why I get this error ? 

libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)

I already tried a lot of solution but everytime, I continue to get this error under Kodi 17.6 and Ubuntu 17.04 / 17.10 ....

I'm not sure if VAAPI is used or not even if the cpu stays around 10% instead of 95% like before. If I fix this issue that will be perfect.

Thnak you in advance for your advices.

NB: I already tried to add video and audio group like I saw somewhere in this forum but nothing changed.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-17

(2017-12-17, 20:35)theghost3131 Wrote: Hi

Do you know why I get this error ? 

libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns -1
libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)

I already tried a lot of solution but everytime, I continue to get this error under Kodi 17.6 and Ubuntu 17.04 / 17.10 ....

I'm not sure if VAAPI is used or not even if the cpu stays around 10% instead of 95% like before. If I fix this issue that will be perfect.

Thnak you in advance for your advices.

NB: I already tried to add video and audio group like I saw somewhere in this forum but nothing changed.

Post all the log from page one and I can tell you - else I cannot.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - theghost3131 - 2017-12-17

mhhh how can I get the log ?, sorry to be a noob on that, otherwise that will be with pleasure


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-17

Just please read the very second line of this thread, it's called: Reporting issues and under that is a simple list, see here: https://forum.kodi.tv/showthread.php?tid=231955


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - theghost3131 - 2017-12-17

(2017-12-17, 20:44)fritsch Wrote: Just please read the very second line of this thread, it's called: Reporting issues and under that is a simple list, see here: https://forum.kodi.tv/showthread.php?tid=231955
 ok sorry to missed that. 

I hope I done correctly the log otherwise tell me if something is missing:

dpkg -l |grep mesa | pastebinit
DISPLAY=:0 vainfo | pastebinit
cat ~/.kodi/temp/kodi.log | pastebinit
dmesg | pastebinit
id | pastebinit
amixer | pastebinit
http://paste.ubuntu.com/26203510/
libva info: VA-API version 0.40.0
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_40
libva info: va_openDriver() returns 0
http://paste.ubuntu.com/26203511/
http://paste.ubuntu.com/26203513/
http://paste.ubuntu.com/26203514/
http://paste.ubuntu.com/26203515/


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-17

Two things:

1) disable VDPAU in kodi settings
2) sudo usermod -a -G cdrom,audio,video,plugdev,users,dialout,dip,input kevin
3) sudo reboot

After the reboot, please post kodi.log (in debug mode) again, after you played a movie. Also post dmesg | pastebinit after that again - as your kernel log is full of port scanning activities - I cannot see anything in that.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - theghost3131 - 2017-12-17

(2017-12-17, 20:52)fritsch Wrote: Two things:

1) disable VDPAU in kodi settings
2) sudo usermod -a -G cdrom,audio,video,plugdev,users,dialout,dip,input kevin
3) sudo reboot

After the reboot, please post kodi.log (in debug mode) again, after you played a movie. Also post dmesg | pastebinit after that again - as your kernel log is full of port scanning activities - I cannot see anything in that.
Ok I done the 1) 2) and 3)

This is the result of dmesg | pastebinit: http://paste.ubuntu.com/26203749/


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-17

Don't paste logs inline - don't cut logs - I need a Debug Log from the beginning. Turn on debuglogging, stop, kodi, start kodi. I have already seen your Exodus and Piracy addons ... but thought we would come along with that ...


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - theghost3131 - 2017-12-17

I don't use this pluggin "Exodus", I only tried it ones to see how it works. Maybe I forgot to remove it if you see it ...

I use everyday only trackTv which is very usefull.


RE: Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server - fritsch - 2017-12-17

Quote:20:06:49.104 T:140145846708608 INFO: Available videomodes (xrandr):20:06:49.104 T:140145846708608 INFO: Output 'XWAYLAND0' has 1 modes
20:06:49.104 T:140145846708608 INFO: ID:0x22 Name:1920x1080 Refresh:59.962841 Width:1920 Height:1080
20:06:49.104 T:140145846708608 INFO: Pixel Ratio: 1.025735
20:06:49.104 T:140145846708608 NOTICE: Checking resolution 16
20:06:49.115 T:140145846708608 DEBUG: Window Manager Name: GNOME Shell
20:06:49.135 T:140145846708608 NOTICE: Using visual 0x24

You run kodi on wayland (namely xwayland) - which is 100% not what this howto wants you to do. VAAPI won't work in xwayland.

Two options for you:

a) Follow the howto and keep v17 as you have it, but use X11 instead of wayland
b) Upgrade to the nightly of kodi via the kodi nightly ppa. Additionally also install ppa:wsipex/vaapi which patches the vaapi drivers to properly work

sudo apt-add-repository ppa:team-xbmc/xbmc-nightly
sudo apt-add-repository ppa:wsnipex/vaapi
sudo apt-get update
sudo apt-get install kodi kodi-wayland
sudo apt-get dist-upgrade

Now start kodi again.