(2017-01-28, 09:28)fritsch Wrote: [ -> ]What was your issue again with self-builing? If you search for make-kpkg in this forum, you see that it is just 5 commands to get a kernel?
Nothing. Just some physical logistics. (esxi server went down). Just thought it made sense to use a custom kernel with the mini pc that I bring with me everywhere, to guarantee it working properly with all TVs. (without needing manual overrides)
Don't run kodi as root and RC2 is long outdated. Upgrade first. Your kodi.log is not a
Debug Log.
(2017-01-28, 15:41)fritsch Wrote: [ -> ]Uploaded 4.9.6 as I built it anyways.
Thanks, you always end up helping out, even after saying no first
are the gfx glitches gone for you too with this kernel?
I don't use it on my htpc. I never had any glitches though. running 4.10-rc6 or something on my J4205.
No - it's not working in Ubuntu 16.04 and not working in kodi v17 nor v18.
You need mesa master and kodi-agile
https://github.com/FernetMenta/kodi-agile build as:
cmake -DENABLE_VAAPI=1 -DENABLE_CEC=0 -DCMAKE_BUILD_TYPE=Release
make -j4
Nice, Thanks fritsch. I'll try tonight.
Regards.
PS: Working very well, thanks again fritsch
Another question is the 16-235 conversion range. In Jarvis, I set up my Intel GPU to 0-255 (xrandr -display :0 --output DP1 --set "Broadcast RGB" "Full" only for test, via terminal) so I see that Kodi crushes blacks (correctly) and xrandr --verbose shows me that the range is Full. Nice. In Jarvis, I enabled "16-235" option and perfect, blacks are correct and I confirmed with AVS709 Black Clipping.
Now I do the same thing in Krypton (and Leia compiled), I see the GUI OK, but when I play the AVS 709 pattern, I see ALL the blacks bar (in Jarvis I only see 17-25). Maybe a regressive double 16-235 compression bug?
Jarvis did not have any proper 16:235 Output support _at all_ for VAAPI, everything was upscaled to 0..255 range when used via VAAPI Output.
In order to get the original limited range. Set xrandr to full and enable limited range within kodi. That way the original colors will be output, which are in 16 ..235 range. (Read the first post, please). It was verified and tested by some thousand people ...
Dahm, I'm idiot.
Usually I always work with a television, these days I'm testing in a computer monitor...that effectively works only with 0-255.
My apologies again and thanks you for all fritsch.
I've followed fritsch' guide on p1 to the letter, and have a nicely working Kodi-based HTPC running on my new Kaby Lake i5 platform now.
But, I too am keen on getting 4K HEVC hw decoding working.
(2017-02-01, 22:41)tocinillo Wrote: [ -> ]Nice, Thanks fritsch. I'll try tonight.
Will you let me know how it worked out for you?
Some notes on experiences building and installing mesa master and kodi agile would be fantastic
(2017-02-05, 13:41)Axman Wrote: [ -> ]I've followed fritsch' guide on p1 to the letter, and have a nicely working Kodi-based HTPC running on my new Kaby Lake i5 platform now.
But, I too am keen on getting 4K HEVC hw decoding working.
(2017-02-01, 22:41)tocinillo Wrote: [ -> ]Nice, Thanks fritsch. I'll try tonight.
Will you let me know how it worked out for you?
Some notes on experiences building and installing mesa master and kodi agile would be fantastic
Yes, It's not complicated. You only must download latest Kodi-agile from git (clone it in any folder) and then inside it you can see the readme files. You only need download and install all the dependencies and finaly make and install it. That's all.
On the other hand, to install latest libva and mesa, you must add Padoka PPA and update all the packages (libegl, libwayland, libva, i965, mesa-drivers, etc.).
Regards.
OK great, thanks! I might give it a shot. You still follow fritsch's steps to to auto-boot to Kodi etc?