[fritsch]

No Debug Log no issue. That gpu most likely can only do vaapi Bob and bilinear scaling.

[Axman]

No Debug Log no issue. That gpu most likely can only do vaapi Bob and bilinear scaling.

Here is debug log:
cat $HOME/.kodi/temp/kodi.log

Looks good to me, no errors and no concerning warnings.

In debug output during playback I see FPS varies around 23-24fps, and my display is successfully synced to 24p. CPU usage is around 15-20%.

"VAAPI - Bob" method works - video playback better now but still not 100% butter.
Audio is in sync though which is great!

Re: my GPU - would upgrading from HD2500 to HD4000 but staying on Ivy Bridge help improve playback? Or do I need to change architecture to get support for VAAPI-MCDI and VAAPI-MADI?

Overview
Intel HD Graphics 4000 Desktop are Integrated Graphics in some of Intel's Desktop Ivy Bridge Processors.

Architecture
The Ivy Bridge GT2 Core includes support for DirectX 11, OpenCL 1.2 and OpenGL 4.0. Additionally, it also offers Hardware Tessellation, Dedicated L3 Cache and better Video Decoding Performance, when compared to its Predecessor.

GPU
It equips a GPU Codenamed GT2 which offers 16 Shader Processing Units, 4 TMUs and 4 ROPs. The Central Unit Initially Runs at 200MHz and goes up to 1150MHz, in Turbo Mode.

From GameDebate on 2500 vs 4000

Thanks for helping

[fritsch]

Maadi and mcdi have decent quality on hsw first. Ivb 4000 can handle it, but it looks not good.

[Axman]

I see. Learning a lot about CPU Arch limitations and advancements today, as well as VAAPI. http://forum.kodi.tv/showthread.php?tid=252916 is a great place to get info on this, for anyone interested.

So in conclusion, to get butter playback on my system I need a new platform (CPU & Motherboard) - Skylake is what makes sense to upgrade to today from a price perspective.

But I think I'll put this on hold until HVEC, 4K & HDR content is more mainstream.

Thanks for the enlightenment!

[christianha]

Thanks for the great instructions. I just followed the step by step manual to install Kodi on my Beebox N3150 and so far everything went well!!

Only issue I ran into is that external usb HDDs aren’t getting auto-mounted. Strangely when I disconnect a drive an information box stating “Successfully removed storage device” appears.

I can manually mount the drives and play videos without any issue.

Is anyone else experiencing the same problem?


-------------------------------------Log Files-----------------------
kodi@beebox:~$ dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/21703653/
kodi@beebox:~$ 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/21703662/
kodi@beebox:~$ cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/21703670/
kodi@beebox:~$ dmesg | pastebinit
http://paste.ubuntu.com/21703676/
kodi@beebox:~$ id | pastebinit
http://paste.ubuntu.com/21703688/
kodi@beebox:~$ amixer | pastebinit
http://paste.ubuntu.com/21703705/

[fritsch]

I posted a udevil workaround somewhere in here. Mind searching for: udevil?

[christianha]

Thanks Fritsch, I'll have a search.

[Kukki]

Hello

I perform apt-get upgrade this morning on my Ubuntu 16.04, now it's 16.04.1, and Kodi displays a full green screen on the TV. The sound is working fine though.
(It used to work before I run apt-get upgrade)

Could you please review the log and help me out? thanks.

(debug log updated, previously with wrong user account)
====
kodi@HTPC-N3150:~# dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/21755561/

kodi@HTPC-N3150:~# DISPLAY=:0 vainfo | pastebinit
error: can't connect to X server!
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/21755597/

kodi@HTPC-N3150:~# cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/21755685/

kodi@HTPC-N3150:~# dmesg | pastebinit
http://paste.ubuntu.com/21755717/

kodi@HTPC-N3150:~# id | pastebinit
http://paste.ubuntu.com/21755740/

kodi@HTPC-N3150:~# amixer | pastebinit
http://paste.ubuntu.com/21755809/
====

[fritsch]

Please follow the How-To. All your logs indicate that you run a configuration that uses root user.

[Kukki]

(debug log updated, previously with wrong user account)
====
kodi@HTPC-N3150:~# dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/21755561/

kodi@HTPC-N3150:~# DISPLAY=:0 vainfo | pastebinit
error: can't connect to X server!
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/21755597/

kodi@HTPC-N3150:~# cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/21755685/

kodi@HTPC-N3150:~# dmesg | pastebinit
http://paste.ubuntu.com/21755717/

kodi@HTPC-N3150:~# id | pastebinit
http://paste.ubuntu.com/21755740/

kodi@HTPC-N3150:~# amixer | pastebinit
http://paste.ubuntu.com/21755809/
====

[fritsch]

Sorry, not a Debug Log. At least play a movie that shows the issue while debug logging is turned on.

[hackno]

I got the same issue... Care to have a look please?

dpkg -l |grep mesa | pastebinit
http://paste.ubuntu.com/21782265/

DISPLAY=:0 vainfo | pastebinit
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/21782297/

cat ~/.kodi/temp/kodi.log | pastebinit
http://paste.ubuntu.com/21782323/

dmesg | pastebinit
http://paste.ubuntu.com/21782364/

id | pastebinit
http://paste.ubuntu.com/21782395/

amixer | pastebinit
http://paste.ubuntu.com/21782429/

[fritsch]

If you'd care to post a Debug Log... change your deint method please while watching such a green movie, please. Turn it off and then Auto again, save for all files.

[hackno]

Solved!

deint method was "Auto select". I've tried all the options and only the bob method doesn't work. All the other methods work flawlessly. Strangely, the auto select seems to be selecting bob. Any clue why?
Which one should be selected?
- Off
- VAAPI - Motion Compensated
- VAAPI - Motion Adaptive
- VAAPI - Bob
- Deinterlace

[fritsch]

If you can afford it: VAAPI - Motion Compensated

there is something fishy with the auto method.